I'll present a NEMSIS public training on the #NEMSIS #Git repositories on Tues., 9/9, from 10 to 11am MT. When the NEMSIS repos went offline for a few months earlier this year, I was surprised how many people didn't have their own copy of the repos. Zoom meeting ID: 84590557428.

Last day of #NEMSIS Annual Meeting: many attendees recommended getting more agency-level people, billers, and EMS educators involved in these #EMS #data discussions.

Join millions who have switched to Grok.

Some people commenting at #NEMSIS Annual Meeting that NEMSIS needs to move from incident/response-based to patient-based records. That's how the rest of healthcare is, but fire and law enforcement are incident/response-based.

Talking about versioning in #NEMSIS Annual Meeting today. No timeline has been set for the next version yet, but NEMSIS TAC is receiving and vetting change requests.

Recognizing Dr. Greg Mears at the #NEMSIS Annual Meeting this morning for his pivotal contributions to #EMS #data.

Just finished Day "0" of the #NEMSIS Annual Meeting, with pre-meetings for agencies, states, vendors, and the advisory board. Lots of "refinement" work, but also work on big topics like how to support the new things happening in EMS.

RT @QualityEms: Help shape the future of EMS post-crash care!.NEMSQA seeks public comment on draft quality measures to evaluate care after….

#TEFCA now has a searchable map of participants in the nationwide healthcare data interoperability framework! I can't filter by participant type, but I am seeing a few #EMS agencies on the list.

I've published an XSLT to extract patient data from an HL7 C-CDA Clinical Document into the ePatient, ePayment, and eHistory sections in NEMSIS format. This supports EMS getting patient information from other healthcare providers for better patient care.

This report said "dead/alive" determination is only available on <1% of #NEMSIS #EMS records. I was curious what element(s) were being used to get "dead/alive". Turns out it's ED and Hospital Disposition -- elements that are only available from hospitals.

I've updated the HL7-to-NEMSIS and NEMSIS-to-HL7 transformations in the IHE EMS repository to support NEMSIS 3.5.1.

You're an EMS agency, and you know it's important to get hospital outcome info on your patients. But why? What do you do with the information once you get it? I'm hosting a NEMSIS TAC webinar tomorrow (Tue, 5/6) to answer that question. 10:00-11:00am MT.

Due to a bug in the national EMS database at the time, and bugs in ePCR systems, this study probably WAY undercounted prehospital blood transfusions:

#HIMSS Healthcare IT News posted an update on #EMS #interoperability. 2024 is the first year the national EMS database had more than a million EMS reports with hospital outcomes recorded -- but it's still just a sliver of the 35M reports that should have.

This data is also available via the API that systems can use to incorporate national performance stats into their reports.

The #NEMSIS Performance Measures Dashboard now allows exploring the #NEMSQA performance measures by pediatric vs adult patients.

#NEMSIS version 3.5.1 was released this month. It's a minor update that's backwards-compatible. Any document that is valid in v3.5.0 is also valid in v3.5.1, but v3.5.1 adds some new options that were not available previously.

Here's a call to move beyond "response times" as the primary way of measuring how well #EMS is doing its job. Response times matter (a lot) in a small percentage of EMS calls. But there are so many other things that matter-- on all calls.

NEMSQA's inaugural "Measure Report" focuses on #EMS #airway management:

The US federal govt is closely monitoring violations of "information blocking" in #healthcare #data #sharing. #EMS agencies see themselves as recipients of other providers' information. but how many EMS agencies can provide PCRs on demand via an API?