CodeScribe EMS

For EMT and paramedic programs ยท Free 45-day pilot

Every student scribes every mock code. You see all of them.

Students run CodeScribe EMS on their own phones during scenarios, the same app crews use on real arrests. Each mock code reaches your dashboard the moment it ends, with the scenario name, time to first compression, shock and epi, cycle timing against the protocol you set, CPR pauses, and what the student left undocumented.

The dashboard link opens a demo program with made-up data, no sign-in.

The dashboard's Codes tab: one row per code with times to first compression, shock and epi, and outcome. Tap to open the instructor demo.

Why instructors use it

Documentation becomes visible

Students learn to scribe on the tool they'll use on the truck. What they left blank shows up on the screen in front of the class, not in a chart review weeks later.

The debrief has real times

Open any scenario and see every intervention by minute and second. Print it on one page. No more "the epi was around four minutes in."

One protocol for the whole cohort

Set the buttons, timers and drug list once. Every student's phone runs the same screen, locked if you want it locked.

What a program gets

Every mock code, right away

Departments wait 12 to 72 hours for a summary, a privacy measure for real arrests. A training program has no patient, so each code shows up at the student's next check-in, in time for the debrief.

Scenario names

Students type the scenario on the record ("Scenario 3, VF with ROSC") and it comes through with the code, so you can compare everyone's run of the same scenario.

Numbers by student

Codes scribed, how many were fully documented, and median time to first compression, for each student beside the cohort's.

Timing against your protocol

Epi intervals and rhythm checks judged against the timers you set, with every CPR pause counted. Same report a department's medical director gets.

The one-page debrief

Any code prints as a timeline with its timing verdicts, ready to hand the student. See a sample.

Term reset

At the end of the term, Department tab, Remove all students. Instructors stay, the codes stay, and next term's students join with the same code. Students' phones keep working as the standalone app, with their own records.

CodeScribe EMS is a documentation aid, not clinical decision support. It never tells a student what to give or when; your curriculum and your protocols do.

How it works

  1. You get a join code

    We set your program up as a training program and email you a join code. Sign in at app.codescribeems.org with that same email and enter the code; you're the instructor. No phone needed for that part.

  2. Students join in the app

    Each student installs CodeScribe EMS, signs in once, and enters the code. About two minutes per phone. We'll walk a class through it.

  3. Scenarios show up as they end

    A student scribes the mock code, names the scenario on the record, and it's on your dashboard before the debrief starts.

Pricing

A free 45-day pilot, timed so it covers your scenario labs. Seats are set to your class size plus instructors; there's no 25-seat cap for programs. At the end we ask what it was worth to you, and the first programs that stay on keep their starting price for three years. Priced per program per year, not per student, because cohorts turn over, and flexible: tell us your class size and budget and we'll find a number that fits your lab fees. Email us and we reply within a day or two.

Questions instructors ask

Do students need to buy the app?

Each student needs the app, which is $4.99 once on the App Store. For a pilot we send you free download codes for your class, so nobody pays to try it. We don't want the price of the app to be the reason a class can't use it.

Should students use the "Training, don't count this" switch?

No. In a training program every code is already a mock code, and that switch would take the run off your dashboard. It's meant for crews in real departments. Students just name the scenario.

What about student data?

Instructors of your program see each student's roster name, the runs they scribed (with the scenario name) and when their app last checked in. Nobody outside your program sees any of it, and we receive no grades, student IDs or school records. Remove all students at term end takes them off the roster; their names stay on past runs until a student deletes their account or joins another department, and we remove names or delete the program's data whenever you ask. It's set up so it shouldn't hold education records, but if your school treats it as one, it stays under your control.

Is there any patient data?

No. These are practice scenarios, and the summaries carry the same stripped fields a real department receives, plus the scenario name the student typed. The privacy policy covers training programs in its own paragraph.

Android?

Not yet; iPhone and iPad only. The dashboard runs in any browser. If Android is what's stopping your program, tell us.

Can students keep using it after the course?

Yes. Their records stay on their phones, the app keeps working on its own, and when they join a department that uses CodeScribe they already know it.

Does it grade?

No. It shows what was recorded and when, against the timers you set. What that means for the student is your call.

What does it look like on day one?

Empty, with a short getting-started list. The demo shows a program with a term's worth of scenarios.

Something else? support@codescribeems.org.

Try it with your program

We're looking for a few EMT and paramedic programs to pilot it free for 45 days and tell us what's missing.