Guides
Ten practical guides on the mechanics of mock codes and resuscitation rehearsal: the intervals worth tracking, the pauses worth counting, the roles worth assigning and the timeline worth reviewing afterwards with your team. Written for the people holding the clipboard during a practice session.
Before you read any of this
These guides are educational material about process, recording and rehearsal. They are not clinical guidance, not a protocol and not a substitute for training. They contain no doses, no joule settings and no treatment recommendations. Resuscitation practice is defined by your institution's protocol and by current AHA or ERC guidelines. MedCode is a practice and training tool. It does not interpret rhythms, recommend medications, perform clinical calculations or tell anyone what to do next. It is not a medical device.
MedCode is a practice and training tool. It is not a medical device, not clinical decision support, and not a substitute for your institution's required documentation or protocol. Any use during a real event is the individual clinician's own professional judgement.
Start here
The things a stopwatch cannot tell you after a mock code: how long compressions actually lasted, how consistent the pacing was, and whether dose intervals stayed on target.
CPR quality
How compression fraction is calculated, where the pauses hide in a timeline, and how to use the session record to identify habits worth changing.
Read the guide →Timing
Why repeating intervals are easy to lose track of, how a dedicated timer helps keep them consistent, and what to look for in the session timeline afterwards.
Read the guide →CPR quality
The target rate, how compression speed drifts without a cue, and how to use an audible beat during skills practice to build consistent pacing.
Read the guide →The record
Memory compresses and reorders a twenty-minute session. Everything you want to review in the debrief has to be captured while the mock code is running, or it is gone.
Documentation
The categories a code timeline needs to capture, why timestamps drift when reconstructed from memory, and how to log entries as they happen during practice or training.
Read the guide →Reference
The medications that show up in a code timeline, their reference concentrations, and how to use adjustable steppers to record the amount given.
Read the guide →Rhythms
VF and pulseless VT versus PEA and asystole, why rhythm at each check matters for the record, and how to log rhythm changes and shocks as they happen.
Read the guide →The team
Most mock code chaos is a role-assignment problem, not a knowledge problem. Eight people arrive and four of them do compressions. Setting roles before you start makes the practice session worth repeating.
Team
Team leader, compressor, airway, access, meds, recorder and timekeeper — what each role does and where to assign them before a practice session starts.
Read the guide →Training
How to set up an in-situ mock code, what to capture while it runs, and how to use the timestamped record to make the debrief specific and useful.
Read the guide →Debrief
Hot debriefs versus cold, a structure that fits in five minutes, and how a timestamped timeline makes the review specific rather than general.
Read the guide →Tools
A phone stopwatch, a paper sheet, a simulation platform log or a purpose-built practice timer. Each is right for some training settings and wrong for others.
Comparison
Stopwatches, generic interval timers and purpose-built code timers compared — and what matters when choosing a tool for practice, training or personal use.
Read the guide →Start here
The single guide that frames every other one: what a code timeline has to capture, and why the reconstruction problem is the root of most training and review challenges.
Read the guide →The app
Two independent clocks, a metronome, timestamped event logging and a PDF timeline you can hand over. All on-device, one payment, no account.
See the app →Two independent timers, a metronome, medication logging with adjustable steppers, and a timestamped timeline you can export as a PDF when the session ends. Everything stays on the phone.