Emergency Medical Services Patient Care Report, Release 3 CDA PSS

1a. Project Name Emergency Medical Services Patient Care Report, Release 3 CDA 1b. Project ID 1716 1c. Is Your Project an Investigative Project (aka PSS-Lite)? No 1d. Is your Project Artifact being Reaffirmed or proceeding to Normative directly after being either Informative or STU? Yes 1e. Today's Date Nov 24, 2021 1f. Name of standard being reaffirmed Emergency Medical Services Patient Care Report, Release 2 CDA 1g. Project Artifact Information A project artifact is balloting Normative (no STU) (this includes reaffirmations) 1h. ISO/IEC Standard to Adopt Emergency Medical Services Patient Care Report, Release 3 CDA 1i. Does the standard include excerpted text from one or more ISO, IEC or ISO/IEC standards, but is not an identical or modified adoption? No 1j. Unit of Measure Both 2a. Primary/Sponsor WG Clinical Interoperability Council 2b. Co-Sponsor WG Structured Documents 2c. Co-Sponsor Level of Involvement Request formal content review prior to ballotOther Involvement. Specify details in text box below 2c. Co-Sponsor Involvement Review Changes 2d. Project Facilitator Jay Lyle 2e. Other Interested Parties (and roles) 2f. Modeling Facilitator Jay Lyle 2g. Publishing Facilitator Jay Lyle 2h. Vocabulary Facilitator Jay Lyle 2i. Domain Expert Representative Clay Mann 2j. Business Requirements Analyst 2k. Conformance Facilitator Jay Lyle 2l. Other Facilitators 2m. Implementers ImageTrend: Kelly Clarke, kclarke@imagetrend.com Doug Butler, dbutler@imagetrend.com ESO: Andrew Hawthorn, andrew.hawthorn@eso.com Jennifer Wilson, MBA, EMT, jennifer.wilson@eso.com Beyond Lucid Technologies: David Saylor, david.saylor@beyondlucid.com Jonathon Feit, jonathon.feit@beyondlucid.com Biospatial: Chris Lunsford, chris.lunsford@biospatial.io Zoll: Peter Del Santo, pdalsanto@zoll.com Keenan Early, KEarly@zoll.com AngelTrack: Kaitlyn Hanka, kaitlyn@angeltracksoftware.com EMS Charts: Adam Mihlfried, adam@emscharts.com 3a. Project Scope This project will update the elements in the current Patient Care Report CDA guide to meet the requirements defined in NEMSIS version 3.5. Most changes involve terminologies; three elements will have relaxed cardinality. We will update the IG to address any gaps with compliance with the current CDA IG Quality Criteria. MDHT will be used to update the CDA-IG. Attachments HL7_CDAR2L3IG EMSRUNRPT_R2_2016.pdf 3b. Project Need EMS implementers are moving toward FHIR, but they will need an updated CDA specification to support reporting in the interim. 3c. Security Risk No 3d. External Drivers 3e. Objectives/Deliverables and Target Dates • Changes drafted August 2021 • Terminology updates to SDOs August 2021 • Ballot January 2022 3f. Common Names / Keywords / Aliases: 3g. Lineage HL7 Implementation Guide for CDA® Release 2 – Level 3: Emergency Medical Services; Patient Care Report, Release 1 – US Realm 3h. Project Dependencies 3i. HL7-Managed Project Document Repository URL: https://confluence.hl7.org/display/CIC 3j. Backwards Compatibility No 3k. Additional Backwards Compatibility Information (if applicable) 3l. Using Current V3 Data Types? Yes 3l. Reason for not using current V3 data types? 3m. External Vocabularies Yes 3n. List of Vocabularies LOINC, SNOMED CT, UCUM, HL7, CDC (race), ICD-10, FDA (routes); see attached prior IG for value set names 3o. Earliest prior release and/or version to which the compatibility applies 4a. Products V3 Documents – Clinical (e.g. CDA) 4b. For FHIR IGs and FHIR Profiles, what product version(s) will the profiles apply to? 4c. FHIR Profiles Version 4d. Please define your New Product Definition 4d. Please define your New Product Family 5a. Project Intent Revise current standard 5a. White Paper Type 5a. Is the project adopting/endorsing an externally developed IG? 5a. Externally developed IG is to be (select one) 5a. Specify external organization 5a. Revising Current Standard Info HL7 Implementation Guide for CDA® Release 2 – Level 3: Emergency Medical Services; Patient Care Report, Release 2 – US Realm (2016) Prior standard remains in effect while vendors transition to NEMSIS data set version 3.5. 5b. Project Ballot Type Normative (no STU) 5c. Additional Ballot Info 5d. Joint Copyright No 5e. I understand I must submit a Joint Copyright Letter of Agreement to the TSC in order for the PSS to receive TSC approval. no 6a. External Project Collaboration Sponsoring agency is NEMSIS Technical Assistance Center 6b. Content Already Developed 0 6c. Content externally developed? No 6d. List Developers of Externally Developed Content 6e. Is this a hosted (externally funded) project? Yes 6f. Stakeholders 6f. Other Stakeholders 6g. Vendors EHR, PHR, Health Care IT, HIS 6g. Other Vendors 6h. Providers Emergency Services, Local and State Departments of Health, Healthcare Institutions (hospitals, long term care, home care, mental health) 6h. Other Providers 6i. Realm U.S. Realm Specific 7d. US Realm Approval Date Jul 20, 2021 7a. Management Group(s) to Review PSS CDA 7b. Sponsoring WG Approval Date May 25, 2021 7c. Co-Sponsor Approval Date Jul 08, 2021 7c. Co-Sponsor 2 Approval Date 7c. Co-Sponsor 3 Approval Date 7c. Co-Sponsor 4 Approval Date 7c. Co-Sponsor 5 Approval Date 7c. Co-Sponsor 6 Approval Date 7c. Co-Sponsor 7 Approval Date 7c. Co-Sponsor 8 Approval Date 7c. Co-Sponsor 9 Approval Date 7c. Co-Sponsor 10 Approval Date 7e. CDA MG Approval Date Jul 27, 2021 7f. FMG Approval Date 7g. V2 MG Approval Date 7h. Architecture Review Board Approval Date 7i. Steering Division Approval Date 7j. TSC Approval Date Aug 30, 2021