What a 2.6 Percent Feedback Rate Reveals About Governing Data That's Supposed to Flow Both Ways
Emergency medical services transport patients to hospitals across the United States millions of times a year. As of 2023, according to the organization that runs the national EMS data standard, only 2.6 percent of those transports resulted in hospital outcome data flowing back to the EMS agency that made the call, up from 0.9 percent two years earlier. This paper extends The Governed Signal to the specific half of health data exchange that general interoperability regulation has not yet reached: real-time, bidirectional data between EMS crews and the hospitals they transport to.
Signal Paper XV described the general case of health data exchange: a FHIR-standardized API request, authorized and fulfilled in a format two systems agree on. Emergency medical services expose a specific, harder case of the same underlying problem, one general interoperability regulation has not yet solved. An EMS crew needs a patient's relevant medical history at the scene, in real time, often with no advance notice of which hospital they will transport to. The receiving hospital needs the crew's patient care report the moment the patient arrives. And the EMS agency needs to know what happened to the patient after handoff, both to close the clinical loop and to improve its own protocols. That third leg, hospital outcome data flowing back to the transporting agency, is the one this paper focuses on, because it is the one with a specific, current, and startling number attached to it.
This paper applies Signal Paper I's doctrine, Captured ≠ Governed, to the EMS-hospital handoff specifically, and grounds its central claim in the National EMS Information System's own published reporting: as of 2023, only 2.6 percent of relevant hospital transports resulted in outcome data reaching the transporting EMS agency, up from 0.9 percent in 2021. Both figures come from the organization that operates the national data standard this problem is measured against, not from an outside estimate.
An EMS patient care report, the structured record a crew produces documenting a patient's condition, treatment, and transport, is captured in the field, often under real-time pressure, using whatever medical history the crew can access at the scene. Delivering that report to the receiving hospital closes half of the loop this paper is concerned with. The other half, information about what happened to the patient after handoff, a diagnosis, a procedure, an outcome, flowing back to the EMS agency that made the transport, is the half that has historically not happened at any meaningful scale.
This is not a hypothetical concern about data hygiene. An EMS agency that never learns whether its field impression matched the hospital's eventual diagnosis has no structured way to evaluate or improve its own protocols against real outcomes. A crew that transported a suspected stroke patient, for example, generally has no systematic way to learn whether the diagnosis was confirmed, which is precisely the kind of feedback loop quality improvement in any clinical setting depends on.
The National EMS Information System, the organization that maintains the national data standard for EMS documentation, states plainly on its own materials that EMS has historically been left out of national healthcare data interoperability efforts. EMS providers, per NEMSIS's own description, rarely have real-time electronic access to a patient's medical history, EMS patient care reports are rarely available within the electronic health records of the hospitals patients are transported to, and EMS rarely receives electronic notification of hospital outcomes for the patients it transports. A dedicated EMS Interoperability Task Force, a partnership between NEMSIS's technical assistance center and IHE USA, met monthly from February 2023 through June 2024 specifically to address this gap.
The reasons this gap persisted while general hospital-to-hospital interoperability advanced, discussed in Signal Paper XV, are structural rather than incidental. Signal Paper XV's federal interoperability mandate, built around FHIR-based APIs between certified electronic health record systems, was designed around the relationship between hospitals, payers, and patients. EMS agencies are a different kind of institution entirely, often municipal or county-run, using specialized computer-aided dispatch and electronic patient care report software built to NEMSIS's own data standard rather than to hospital EHR certification criteria, and operating in the field rather than within a hospital's IT infrastructure. EMS was not excluded from interoperability regulation by oversight so much as it sits organizationally and technically outside the boundary that regulation was drawn around.
illumin8's approach to EMS-hospital data exchange extends the architecture described in Signal Paper XV to a case where governance has to hold in both directions and under real-time constraint. Synergy® evaluates both legs of the handoff, the patient care report moving from EMS to hospital at the moment of arrival, and the outcome data moving from hospital back to EMS after treatment, as governed actions in their own right rather than treating the return leg as an optional courtesy notification. A governed handoff carries a SecuriSync™ Trust Record on both legs, extending this series' "governed at the point of action" pattern to a two-way exchange rather than the one-directional request-and-response pattern described in Signal Paper XV.
The real-time constraint is addressed the same way Signal Paper VII describes for defense sensor data operating without live infrastructure: a governed record can be established and self-certify at the point of capture, at the scene, in the ambulance, at the moment of hospital arrival, without waiting for a live round-trip confirmation, and reconciles against the broader governed chain once connectivity or system access allows it. This does not require EMS agencies or hospitals to adopt new clinical protocols; it requires the data each side already produces, the patient care report and the discharge or outcome summary, to carry governance from the moment each is created rather than depending on a voluntary, manually-initiated data-sharing agreement between the specific agency and the specific hospital involved.
The architectural basis for extending this claim to structured EMS and clinical outcome data follows the same patent scope established in Signal Paper I and applied again in Signal Paper XV to FHIR-mediated health data exchange. This paper does not re-derive that claim or its stated limits; see Signal Paper I, Section 05.
NEMSIS's own reporting, updated in February 2025, describes 265,510 patient records with hospital outcome data present in the national EMS database in 2021, out of 28,641,062 total hospital transports recorded that year, a rate of 0.9 percent. By 2023, that rate had improved to 2.6 percent nationally, still leaving the overwhelming majority of transports without a closed feedback loop. The variance beneath that national average is instructive: NEMSIS reporting describes one Nevada agency improving from 4 percent in 2021 to 69 percent by 2024 or 2025, and a Texas agency reaching 39 percent over a comparable period, alongside a description of Montgomery County Hospital District, an EMS agency north of Houston covering roughly 1,100 square miles, a population of about 600,000, and averaging around 70,000 calls a year, achieving a notably higher completion rate by participating directly in national data-network reporting rather than relying on point-to-point connections with individual hospitals.
That variance suggests the underlying technology and standards, NEMSIS's data dictionary alongside the HL7 and FHIR standards EMS software increasingly maps onto, are not the binding constraint. Agencies that participate in structured, standards-based data networks rather than negotiating individual point-to-point connections with each hospital they transport to appear to close the loop at rates many multiples higher than the national average, which is consistent with this paper's argument that the gap is organizational and architectural rather than a matter of unavailable technology.
This paper does not claim that illumin8 has been deployed by any specific EMS agency, hospital, or regional health information exchange, and no specific transport, patient outcome, or agency performance figure beyond those cited from NEMSIS's own reporting is represented here. It does not claim that the 0.9 percent and 2.6 percent figures describe every category of EMS transport or every jurisdiction; they describe national aggregate reporting to the NEMSIS database specifically, and individual agency and state participation varies, as Section 04 describes. It does not claim that closing this feedback loop, on its own, improves clinical outcomes; it claims that closing the loop is a precondition for an agency to systematically evaluate whether its own protocols are producing the outcomes intended, which is a narrower and more defensible claim.
Emergency medical services data exchange inherits the pattern the last two papers in this series established from different directions: a real, dated, verifiable industry or regulatory milestone solves part of a problem, and a specific, measurable gap remains exactly where the stakes are highest. Signal Paper XV found that gap in autonomous AI access to health records; Signal Paper XVI found it in business messaging encryption; this paper finds it in the return half of a data exchange that was only ever partially built as a one-way street.
It follows Telecom specifically because both papers close out this run of growth-arc papers on the same note: a percentage or a scope limitation, RCS for Business's transport-only encryption, EMS's 2.6 percent feedback rate, that is precise, sourced, and small enough to sound like a rounding error until its real-world consequence is stated plainly.
This series remains open past its initial twelve-paper arc, and this paper closes the current run of growth-vertical additions at seventeen papers total. Future additions will follow the same discipline established across all of them: a real, checkable governance gap, grounded in verifiable sources, stated plainly alongside whatever could not be verified.
As of 2023, only 2.6 percent of EMS hospital transports resulted in outcome data flowing back to the transporting agency, per NEMSIS's own reporting, up from 0.9 percent two years earlier. illumin8 governs both legs of the handoff, the patient care report to the hospital and the outcome data back to the crew, from the moment each is created. This is Signal Paper XVII.
Request Platform Access → Full White Paper Series