Lighthouse AdvisorySLED AI Adoption Intelligence
← Back to results

From the Emergency Services edition of September 23, 2026

Academic researchMixedNewly relevant · Mar 2026

MADLAD RCT: ML risk scores raised correct low-acuity ambulance prioritization from 62.5% to 68.3% in Swedish resource-constrained situations

Uppsala University / Västmanland Hospital (Sweden EMS dispatch centers) · Emergency medical dispatch / EMS academic clinical trial · Uppsala and Västmanland regions, Sweden (combined population ~499,000)

Publisher
PLOS Medicine
Original publication
2026-03-31
Source retrieved
2026-09-24
Read original source

What happened

In a parallel-group RCT of adult low-priority (2A/2B) ambulance patients during Resource Constrained Situations at two Swedish nurse-staffed EMD centers, 1,245 RCS were analyzed. Dispatchers aided by an openTriage gradient-boosting risk tool prioritized the patient with the highest subsequent NEWS2 in 68.3% of intervention RCS versus 62.5% under usual practice (OR 1.28, 95% CI 1.00–1.63, p=0.047). Post-hoc, prioritized patients had shorter dispatch delays (29 vs 32 minutes); full model compliance would have raised the OR to 1.56. Authors emphasize underpowering (ended early at n=1,245 vs planned 1,500), edge-of-significance p-values sensitive to imputation seeds, nurse-staffed CDSS context, and restriction to low-acuity adults—not high-acuity or non-conveyance cohorts.

Why it matters

Rare randomized evidence that ML decision support can modestly improve EMS dispatch prioritization under resource constraints—directly transferable as a cautionary benchmark for U.S. PSAPs and fire/EMS agencies evaluating AI triage prompts after the current non-emergency and nurse-line AI wave. Why now: yesterday’s CSPD Axon launch and Seattle Corti debates lack RCT outcome evidence; MADLAD supplies measured prioritization deltas with explicit limits.

Evidence and measured results

Opened full PLOS Medicine HTML. Primary outcome and OR/CI/p from abstract and results; sample flow, compliance 80.9%, secondary composite OR 1.31, and limitations from methods/discussion. Trial NCT04757194; published 2026-03-31.

Limitations and uncertainty

Underpowered; p at edge of significance; Sweden nurse-staffed CDSS; low-acuity only; international transferability limited; not a U.S. PSAP deployment result.

Put this evidence to work

Lighthouse Advisory interpretation, grounded in this source. Enriched 2026-09-23; this does not change the original publication date. Each role follows the same checklist so takeaways compare across sources.

Sales

Role takeaway
Customer problem
When multiple low-acuity patients wait for scarce ambulances, agencies lack proven tools to pick who gets the next unit.
Stakeholders
  • EMS medical directors
  • Dispatch center managers
  • CAD/IT leads
  • Quality/research officers
Discovery questions
  • How often do multi-patient waits occur?
  • Who staffs triage—nurses or telecommunicators?
  • What acuity proxy (NEWS/ePCR) can you measure?
  • Will overrides be logged without punitive scoring?
Value hypothesis
ML risk ranking can modestly raise correct first-unit assignment among low-acuity waits if humans retain final authority and outcomes are measured.
Potential engagement
Retrospective openTriage-class validation and RCT/pilot protocol workshop—not a production 911 AI sale.
Unsupported claims
  • Guaranteed replication of 68.3% accuracy
  • Safe use on lights-and-sirens priority 1 without new trials
  • U.S. PSAP staffing equivalence to Swedish nurse EMD

Pre-sales engineering

Role takeaway
Fit
Decision-support risk ranker for concurrent low-priority ambulance waits inside CAD/CDSS—not autonomous dispatch.
Architecture and integration
API scoring service with structured CDSS + bag-of-words text features; UI markers; audit store for scores even when hidden.
Prerequisites
  • Complete triage documentation
  • Outcome linkage to vitals/ePCR
  • Randomization/override logging
  • Model refresh process
Constraints
  • Feature mismatch vs Swedish MBS
  • Non-blinding of dispatchers
  • Low-acuity scope only
Security
Protect identifiable EMS narratives under regional health-data rules; define training-data retention and researcher access.
Proof of value
  • Primary prioritization accuracy vs NEWS
  • Compliance rate
  • Dispatch-delay delta
  • Drift correlation over time

Delivery

Role takeaway
Work
Train dispatchers on protocol, stand up DMC, wire outcome extraction, and monitor compliance vs model confidence.
Dependencies
  • CAD vendor UI hooks
  • Hospital/ED vitals access
  • Ethics approval
  • openTriage or equivalent model ops
Ownership
EMS medical director owns clinical authority; dispatch manager owns daily protocol; IT owns scoring service.
Skills and adoption
Build trust so overrides are reasoned, not ignored; share confidence calibration with staff.
Governance checkpoints
  • Protocol lock
  • Safety event review cadence
  • Interim power review
  • Publication of limitations
Acceptance criteria
  • Logged human final decision
  • Primary endpoint analysis plan followed
  • Documented sample-size shortfall if any
Risks
  • Overclaiming significance
  • Punitive compliance culture
  • Silent model drift

Implementation considerations

Lighthouse Advisory interpretation across the operating dimensions a public-sector buyer must settle before this evidence becomes a design. Each note answers the question under its heading for this specific source.

Architecture and integration

What must connect, and where does the AI sit in the workflow?

Expect CDSS/CAD-integrated risk scoring with structured + free-text features, confidence display, and nurse–dispatcher conferral before unit assignment. Design for non-blinding, compliance tracking, model refresh against covariate drift, and clear failover when scores are unavailable.

Governance

Who approves, reviews and stays accountable for outcomes?

Require preregistered outcomes (e.g., NEWS-aligned), ethics review for deferred consent, Data Monitoring Committee oversight, and published power/limitation statements before claiming clinical benefit. Do not generalize nurse-EMD results to U.S. telecommunicator staffing without local validation.

Security and privacy

What data, permissions and controls need testing?

Models used personal identifiers and clinical narratives owned by regional health authorities; individual-level data not publicly releasable. U.S. ports need HIPAA/EMS record agreements and training-data controls.

Accessibility and workforce

Who is affected, and what skills or accommodations follow?

Supports dispatcher decision speed under load but was tested with nurse triage staff uncommon in many U.S. PSAPs; workforce transfer needs local role mapping.

Procurement

What should contracts, pricing and exit terms secure?

Open-source openTriage reference favors build/adapt over sole-source voice agents; still budget for outcome measurement and ethics oversight.

Operating model

Which teams own the service once it runs?

Adds an advisory ML conferral step among waiting low-acuity patients without replacing nurse/dispatcher judgment.

Publication history

  1. 2026-09-23Emergency Services · Issue 185 resources
Read preserved resource versions (JSON)

Stable resource ID: plos-madlad-ems-dispatch-ml-rct-20260331