Skip to content

Med Math docs

Dosage calculation and blood gas practice, where every answer is worked out step by step.

These pages explain Med Math the way I'd explain it to a friend sitting next to me before an exam: what each screen is for, what counts as a right answer, and how the train in "Show me" works. If you're new, read "What is Med Math?" first and then "Practicing a topic", which is most of what you need. "How the train works" is worth a read even if you know dimensional analysis already, because it explains what the drawings mean. The page under "Under the hood" is for changing Med Math itself, and you only need it if you're working on the code.

Getting started

  • What is Med Math? — what it does, who it's for, where it works, and what stays in your browser

Using Med Math

  • Practicing a topic — the problem, the answer box, Check, Show me and Next, what counts as right, and your progress
  • How the train works — the engine, the cars, the struck-out units, the caboose, rounding, and the formula way
  • The quiz and the formula sheet — a mixed quiz of 10, the results, retrying the misses, and printing the sheet

Blood gases

  • Blood gases — reading an ABG with ROME and tic-tac-toe, oxygen and the P/F ratio, Henderson-Hasselbalch, expected compensation, the anion gap, explaining it to patients, and the sources
  • Memorizing blood gases — the memory trick cards (which are standard and which are made up), flashcards with Leitner boxes, building formulas from tiles, fill the blank, the speed round and the brain dump

Reference

  • The 14 topics — what each dosage topic asks, with an example and the rounding it uses
  • Settings — rounding, pounds and kilograms, the clock, which topics go in the quiz, the look, and resetting progress

Under the hood

  • Developing — the files, the two ways every answer is worked out, the tests, the walk and deploying

Something wrong, or missing?

If an answer looks wrong to you, or a problem doesn't read like a real order, or you'd like a topic that isn't there, open an issue on the GitHub repo and say what the problem said and what you expected. A screenshot helps a lot, and for a wrong answer it helps most of all.