HL7 C-CDA Discharge Summary to NEMSIS Transformation Updated

9 views
Skip to first unread message

Joshua Legler

unread,
Jul 8, 2024, 6:51:19 PMJul 8
to ems-tas...@googlegroups.com

EMS Interoperability Task Force,

 

I have updated the XSL transformation that extracts information from an HL7 C-CDA R2.1 Discharge Summary representing a patient’s hospital encounter and transforms it into the NEMSIS “eOutcome” format. Previously, the transformation was intended to work only on discharge summaries representing inpatient encounters. Now, it supports both inpatient and emergency department encounters.

 

Another change in the transformation relates to the fact that diagnosis and procedure codes may use a variety of code systems in C-CDA documents, whereas NEMSIS only recognizes ICD-10 codes. I’ve modified the transformation to make it easy to add an API call to an external terminology mapping service to translate between code systems.

 

Along with the updated transformation file, I’ve added a second pair of sample documents so both inpatient and emergency department encounters are covered by the samples.

 

Here’s the updated resource:

 

https://github.com/IHE/EMS/blob/main/Transformations/HL7%20CDA%20to%20NEMSIS/C-CDA-R2.1_DS_to_NEMSIS-3.5.0.md

 

There are a couple of potential uses for this resource:

 

  1. It can serve as a reference implementation showing where to find data in C-CDA Discharge Summary documents and convert it into the format defined by the eOutcome section of the NEMSIS standard.
  2. It can be embedded in actual implementations, where a Discharge Summary is first processed by this XSLT, then the resulting NEMSIS eOutcome fragment can be parsed by an ePCR system and attached or incorporated into the NEMSIS patient care report.

 

I’m interested in any feedback you have from reviewing or running the transformation. Next month I will publish an XSLT to transform from Continuity of Care Document (CCD) to NEMSIS.

 

Thanks,

 

Josh

 

-- 

Joshua Legler

971-264-4702

jo...@joshualegler.com

linkedin.com/in/joshualegler

 

Reply all
Reply to author
Forward
0 new messages