Having a medical emergency? Call 911 — this site is educational only. Partnered with OpenAI Contact us →
For AI teams & researchers

Domain-Specific AI Research for Prehospital Care

AI literacy for EMS providers, an evaluation framework built for emergencies, and the research, ethics and data practices behind our prototypes. Start here if you want to evaluate, collaborate or build.

AI literacy module

AI literacy for EMS: What AI Can Do, Where It Fails, and Who Decides

A short module for students and providers. Use it alone or alongside the teaching resources.

What AI can do

  • Summarize and draft documentation for your review
  • Retrieve and cite protocol passages from an approved library
  • Find patterns in ECG, vitals or video data
  • Generate practice scenarios and feedback

What AI cannot do

  • Examine your patient or see the scene
  • Know your local protocol unless it is given the text
  • Verify its own statements
  • Take responsibility for a decision

How to spot errors

  • Check every dose, unit and route against your protocol
  • Ask for the source, then open it
  • Be wary of confident wording with no citation
  • Check the answer is within your scope of practice
  • Treat missing information as unknown, not as absent

Clinical judgment stays with the provider. AI output is an input to your assessment, never an order. You remain accountable for what you do, under your protocols and medical direction. Automation bias, the tendency to over-trust a machine suggestion, is a patient-safety risk, so verify before you act.

Self-check

1. An AI tool gives a medication dose that differs from your protocol. What do you follow?

Your local protocol and medical direction. Treat the mismatch as an AI error and report it.

2. A chatbot answers confidently but gives no source. What should you do?

Treat it as unverified. Find the claim in an approved source before using it.

3. A report summary says "no chest pain" but the narrative never mentions chest pain. Is that a finding?

No. Absence of documentation is not evidence of absence. It is an information gap to confirm.

Research agenda

Open Questions and Planned Studies

Where we are looking next, and where collaborators could fit. Everything below is planned work, not completed work.

Open questions in prehospital AI

  • How should uncertainty be shown so providers calibrate trust rather than over-rely?
  • How do we evaluate across different jurisdictions and protocol versions?
  • Can systems reliably separate caller-reported, EMS-confirmed and AI-inferred information?
  • Which failure modes appear with time-critical, low-information inputs?
  • How do we measure automation bias in EMS practice?
  • How do we evaluate safely without exposing patient data?

Planned studies

StudyProjectQuestionStatus
Extraction accuracyDispatch-to-Patient NeedsHow well do extracted symptoms match expert annotations of de-identified narratives?Planned
Gap-detection reliabilityPatient Care Report AnalyzerWhat are the false-positive rates when flagging documentation gaps?Planned
ETA baselinesArrival Time to Hospital MLDoes the model beat historical-average and mapping-service baselines on time-based splits?Planned
Measurement validationCPR AnalyzerDo video-derived rate and interruption estimates agree with reference manikin sensors?Planned
Larger protocol test setParamedic AI CopilotDo results hold on a larger, harder set, and what caused the remaining errors?Planned

Where you could fit: clinician graders, de-identified data partners, statisticians, protocol owners, and EMS agencies for user testing. Tell us your interest.

Evaluation framework

How We Test Models on Prehospital Tasks

General benchmarks miss emergencies. This framework builds on the evaluation design in our Paramedic AI Copilot report. Grading procedures marked "proposed" are the standard we intend for released sets.

Task definitions

TaskInputExpected outputPrimary measures
Protocol Q&AQuestion, optionally with retrieved protocol textAnswer with its sourceClinical correctness, protocol and source consistency
Medication referenceDrug questionIndication, contraindications, dosing referenceMedication accuracy, dose errors
ECG interpretationECG description or tracingRhythm and key findingsInterpretation accuracy
Scenario decision supportSimulated patient scenarioPriorities and recognition of life threatsRecognition, completeness, uncertainty handling
Documentation extractionDe-identified report textStructured fieldsField accuracy, false-positive rate

Scoring rubric

Each response is scored on: clinical correctness, completeness, protocol consistency, medication accuracy, ECG interpretation, recognition of life-threatening conditions, appropriate handling of uncertainty, and reference/source consistency. Each response is also checked for unsafe recommendations. Proposed scale: correct, partially correct, incorrect.

Error categories

  • Incorrect medication or dose
  • Contraindicated intervention
  • Failure to recognize a life-threatening condition
  • Incorrect ECG interpretation
  • Fabricated protocol information
  • Unsupported clinical claims
  • Failure to acknowledge insufficient information
  • Inappropriate confidence
  • Incorrect interpretation of retrieved material

The unsafe-response rate is responses containing a predefined unsafe recommendation divided by all evaluated responses. Retrieval is scored separately (for example Recall@K).

Clinician grading (proposed)

  • Credentialed EMS clinicians grade against a written reference standard
  • Graders are blinded to which model or configuration produced each answer
  • Two independent graders per item, with a third adjudicating disagreements
  • Inter-rater agreement is reported
  • Model version, prompts, knowledge base and hardware are documented for reproducibility
Datasets & benchmarks

Test Sets and Comparison Table

Status: our training datasets are listed on the Datasets & Demos page. A documented evaluation benchmark has not been released yet. We plan a small, well-documented set of EMS scenarios (protocol questions, ECG interpretation, triage cases). The table below is our own internal prototype evaluation, not an open leaderboard.

Each release will document

  • Contents, size and how items were written
  • Who reviewed them and how
  • Intended use and out-of-scope use
  • De-identification or synthetic-data method
  • Version, known limitations and license [license to be chosen before first release]

Results so far (internal, not independently validated)

SystemTest setOverall accuracyNotes
Paramedic AI Copilot, RAG100 simulated EMS scenarios92/100 (92%)Medication 100%, ECG 91%, 0 unsafe responses
Same model, no retrieval100 simulated EMS scenarios71/100 (71%)29 incorrect responses vs 8 with RAG

Simulated scenarios only. These results do not establish clinical efficacy or safety. Want to be listed once a public set exists? Email us.

What we offer AI teams

Services for Teams Building AI For Emergency Care

Domain expertise from EMS clinicians and researchers.

Service

Domain evaluations

Run your model on prehospital tasks using our rubric and error categories.

Service

Scenario & dataset creation

Clinician-written scenarios with reference answers and documentation.

Service

Clinical review

Credentialed EMS reviewers grade outputs and explain failures.

Service

Red-teaming

Probe for unsafe doses, fabricated protocols and overconfidence.

Service

User testing with EMS providers

Usability and trust studies with working providers [subject to ethics review].

Talk to us

Use-case briefs

Where AI Could Help in EMS, And What Must Hold True

One-page summaries. These describe opportunities, not deployed products.

Documentation

Problem
Reports vary in completeness and consistency.
AI could
Draft summaries and flag missing elements for review.
Risks
Invented findings; treating missing text as an omitted action; PHI exposure.
Constraints
De-identified or secure data; clinician review.
Success
Fewer gaps with no added clinician time, traceable flags, low false positives.

Dispatch support

Problem
Crews arrive with limited, unstructured information.
AI could
Create a structured pre-arrival summary and list unknowns.
Risks
Anchoring on caller reports; delaying dispatch.
Constraints
Never replaces dispatch protocols; must add no delay.
Success
Accurate extraction against expert annotation; crews find it useful.

Protocol lookup

Problem
Finding the right guidance under time pressure.
AI could
Retrieve and cite approved protocol passages.
Risks
Fabricated or outdated protocols; wrong jurisdiction.
Constraints
Approved, versioned sources; defer to local protocol and medical direction.
Success
Correct passage retrieved, zero unsafe answers, uncertainty flagged.

Education

Problem
Students need more practice and feedback.
AI could
Generate scenarios and give feedback on ECG or CPR practice.
Risks
Wrong teaching content; over-reliance.
Constraints
Instructor review; scope-of-practice labels.
Success
Learners can spot AI errors; content passes clinical review.
Case study

Paramedic AI Copilot: Does Retrieval Improve Protocol-Grounded Answers?

A summary of our preliminary evaluation. Read the full report.

Problem and approach

Problem
General language models can state unsupported clinical information.
Approach
A locally hosted model (Ollama) plus retrieval over a curated EMS knowledge base, with source citations. The model is instructed not to fabricate protocols or doses and to defer to local protocol and medical direction.

Evaluation

Design
100 standardized simulated scenarios, with and without retrieval.
Scoring
Rubric categories on this page, plus a separate unsafe-response check.
MeasureWith retrievalWithout retrieval
Correct responses92/10071/100
Incorrect responses829
Medication scenarios100% accurate80% accurate
ECG scenarios91% accurate80% accurate
Unsafe responses identified00

Limitations

  • Prototype evaluation on simulated scenarios, not real patients
  • Does not establish clinical efficacy, safety or readiness for patient care
  • A zero observed unsafe rate does not mean the system is safe
  • The 8 retrieval-condition errors still need root-cause analysis
  • About 9% of ECG cases were not fully correct
  • Larger and harder test sets are needed

More case studies will be added as evaluations are completed.

Research ethics & IRB statement

How We Approach Research Ethics

Draft for EMARI review. Items in [brackets] must be completed or confirmed by EMARI, and this statement should be reviewed by your institution or counsel before you rely on it.

  • Current work: prototypes are evaluated on simulated scenarios and public or de-identified data. EMARI does not collect identifiable patient data for them [confirm].
  • Human participants: studies involving EMS providers or students, or any non-public patient data, will go through IRB review or a documented exempt or not-human-subjects determination before data collection begins.
  • IRB status: [EMARI to state current status, for example "No IRB-reviewed studies to date"] and the reviewing body [name].
  • Not medical devices: our prototypes are for research and education and are not clinically validated.
  • Honest reporting: planned capabilities are never presented as completed, and limitations are published with results.
  • Disclosure: EMARI is partnered with OpenAI; see the partnership page. [Add any other funding or conflicts.]
  • Contact: emergencymedai@gmail.com
Privacy & data governance

How we Handle Data

Draft for EMARI review. Items in [brackets] must be completed or confirmed by EMARI, and this statement should be reviewed by your institution or counsel before you rely on it.

  • No protected health information on this site or in public AI tools
  • Any patient-derived data is de-identified (HIPAA Safe Harbor or expert determination) or kept in an approved secure environment with access controls
  • Simulated or synthetic scenarios are the default
  • Local model hosting keeps scenario text on the device where possible
  • Data minimization: collect only what a study needs; retention period [to be set]
  • Dataset releases are checked for re-identification risk and carry versioned documentation
  • Incident reporting: [contact and process to be defined]
  • This site has no accounts or tracking backend; feedback arrives by email
Changelog & roadmap

What Has Changed and What Comes Next

No versioned model releases yet. Each future release will list the model and version, knowledge-base version, and any evaluation rerun.

Changelog

WhenChange
Oct 25, 2026Added AI Education Resources, Current Projects and this AI research page
Oct 25, 2026Added the Datasets & Demos page with dataset links, demo video and terms of use
ReportedPreliminary Paramedic AI Copilot evaluation on 100 simulated scenarios

Roadmap

ProjectNext phases (planned)
CPR AnalyzerValidate against reference equipment, then real-time and sensor work
Patient Care Report AnalyzerStructured extraction and validation, completeness checks, protocol-grounded analysis
Arrival Time MLBaseline comparisons on time-based splits, then geographic and traffic data
Dispatch Needs AnalyzerStructured classification, protocol-grounded analysis, pre-arrival briefing
BenchmarksPublish a documented EMS scenario set with a comparison table

See Current projects for each written plan.

Partnered with OpenAILearn about our partnership →