While I agree with some points above and disagree with others, I would suggest that the technologies that solve all of the above currently exist. And the implementation of the technologies is not overly complex (if done well).
I think the public (consumers) are rapidly (I think many have already, with the exception of tech adverse seniors) expecting health care to work like the rest of the business world already have been transitioning to, a world where one click in an app does the magic (why can’t I automatically fill out my paperwork at the doctors office with a click??). Companies like iBeat and RapidSOS are offering emergency responders data. It’s up to emergency systems to use it or not. Similarly, it’s up to the investor to be intelligent enough to ask about interoperability, and how data goes from point a to b.
In a world of there’s an API for that, the ePCR vendors need to start standing up inbound data API’s that can ingest HL7. There are tons of Fire/EMS (granted more on the EMS side) use cases, many of which can significantly enable automation of processes, which could yield significant time (money) savings for EMS operations.
The IoT devices (Apple is currently implementing this with about 20 health systems via HealthKit storing the records as FHIR resources on your phone) can utilize the HL7 FHIR standard to output the medical data contained in HealthKit to FHIR. If I recall correctly, Apple is expecting this functionality to exit beta sometime this fall. I don’t think adding the FHIR messaging to the outbound RapidSOS messaging would be overly complex.
The method to pass the data to the correct ePCR could be implemented in a variety of ways, but here’s a simple one. FHIR messaging from a device can be included as a JSON array in the messaging sent to 911. Your 911 system includes the FHIR JSON array in the outbound message to the ePCR. It doesn’t really need to have any notion of the content, unless for some reason it wants to acquire more data in the 911 system. The ePCR can then translate the FHIR data to it’s data model and populate the ePCR record.
On the outbound side, if so inclined, the patients complete history from a device (such as a complete historical medical record), plus the EMS encounter could be output as a CCD, and submitted to the hospital.
Once your CAD can pass HL7, and your ePCR can ingest it, you could wind up with some really interesting interoperability and automation options.
While this doesn’t currently work this way, it could. And relatively simply, using existing, well established technologies.