From the Emergency Services edition of November 9, 2026
Uppsala study: regression and gradient-boosting EMS travel-time models validated on later data explain 70-79% of ground variance but only 38-46% for helicopters
Uppsala University and Uppsala University Hospital (Scandinavian Journal of Trauma, Resuscitation and Emergency Medicine) · EMS dispatch / ambulance versus helicopter selection · Uppsala region, Sweden
- Publisher
- Scandinavian Journal of Trauma, Resuscitation and Emergency Medicine
- Original publication
- Published 2 November 2026, Volume 34, article 170
- Source retrieved
- 2026-11-10
What happened
Researchers used 2022-2024 dispatch and flight-log data from Region Uppsala (24,756 priority-1 incidents, 527 with helicopter response) to adjust open-source routing estimates for ground ambulances, and great-circle distances for helicopters, with linear regression and gradient boosting. In validation data collected after the methods were finalized, the best ground models explained R2 0.79 (travel to incident) and 0.70 (travel to hospital); helicopter models reached R2 0.46 and 0.38. Mean absolute percentage error was 18-20% across techniques and intervals. Regression and gradient boosting performed similarly, with a slight edge for boosting. The authors say open-source code could help dispatchers estimate relative travel times and judge whether a helicopter saves time.
Why it matters
Concrete, openly published decision-support input for dispatchers choosing between ground and air resources. It is classical prediction rather than generative AI and was not tested in live dispatch, so relevance to AI programs is partial.
Evidence and measured results
Opened the full open-access article on Springer Nature Link via HTTPS curl (User-Agent SLED-research-bot/1.0), read abstract, study setting, results and limitations, and saved the text. Supplementary model specifications were not opened.
Limitations and uncertainty
Single Swedish region; priority-1 missions transported to one primary hospital only; extreme long travel times tended to be under-estimated; helicopter volume was small (527 responses); no patient-outcome or live-dispatch evaluation; Swedish road network and agency structure.
Put this evidence to work
Lighthouse Advisory interpretation, grounded in this source. Enriched 2026-11-10; this does not change the original publication date. Each role follows the same checklist so takeaways compare across sources.
Sales
Role takeaway
- Customer problem
- Dispatchers must decide whether a costly, scarce helicopter will beat a ground ambulance with limited travel-time information.
- Stakeholders
- EMS medical director
- Air-medical programme manager
- Dispatch centre manager
- Regional EMS administrator
- Discovery questions
- How are ground and helicopter ETAs estimated at tasking today?
- Do you track the error of those estimates?
- Who decides when a helicopter is launched?
- Value hypothesis
- Locally calibrated travel-time estimates may help dispatchers judge relative time benefit, as interpretation of one regional validation.
- Potential engagement
- Four-to-six-week audit of current ETA accuracy and prototype calibration using local dispatch history.
- Unsupported claims
- That helicopter or ambulance tasking improves patient outcomes
- That accuracy transfers outside Uppsala
- That helicopter estimates are reliable
Pre-sales engineering
Role takeaway
- Fit
- Relevant to dispatch centres tasking both ground and air units and holding multi-year mission logs.
- Architecture and integration
- Open-source routing service plus regression or boosting calibration reading CAD data, returning estimated ground and air times to the dispatcher screen.
- Prerequisites
- Clean mission and flight logs
- Documented unit starting points
- Routing engine with local road data
- Constraints
- Single region and priority-1 only
- Under-estimation of the longest trips
- Weaker helicopter model
- Security
- Treat incident locations and times as sensitive; restrict model-training data access and log outputs shown to dispatchers.
- Proof of value
- Hold-out replay on a later local period
- Error reported by distance band and mission type
- Tail-error review of long trips
Delivery
Role takeaway
- Work
- Rebuild and validate travel-time estimators on local data and design the dispatcher display and override.
- Dependencies
- Dispatch and flight-log data owners
- Routing engine setup
- Medical director sign-off
- Ownership
- Dispatch centre manager with the air-medical programme lead.
- Skills and adoption
- Dispatchers need to understand estimate error and when to ignore it.
- Governance checkpoints
- Data-use review
- Validation results review
- Go or no-go before live display
- Acceptance criteria
- Agreed MAPE and tail-error thresholds met on a later period
- Documented override path
- Dispatcher feedback reviewed after trial
- Risks
- Poor starting-point data
- Over-reliance on estimates
- Under-estimated long trips
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?
A routing engine plus a small calibration model fed by historical dispatch and flight logs; output is an estimate shown to dispatchers, not an automated decision.
Governance
Who approves, reviews and stays accountable for outcomes?
Travel-time estimates that steer scarce helicopter use need documented error bounds and a clear rule that clinicians and dispatchers keep final authority.
Security and privacy
What data, permissions and controls need testing?
Training uses incident locations and times from dispatch records; de-identification and access controls are needed before reuse.
Accessibility and workforce
Who is affected, and what skills or accommodations follow?
Not addressed by the source.
Procurement
What should contracts, pricing and exit terms secure?
Agencies can ask vendors for validation on post-training data and for error measures such as MAPE; open-source code lowers lock-in risk.
Operating model
Which teams own the service once it runs?
Intended to inform relative ground-versus-helicopter judgments at tasking; the study did not test changes in dispatcher behaviour or patient outcomes.
Publication history
- 2026-11-09Emergency Services · Issue 642 resources
Stable resource ID: scand-j-trauma-ems-travel-time-models-uppsala-ground-helicopter-20261102