Paramedicine Care Summary (PCS)

The Paramedicine Care Summary (PCS) Profile provides the structures and transactions for providing the patient's paramedicine encounter information to the receiving facility.

Summary

Currently, interventions and assessments are written into an ambulance electronic Patient Care Record (ePCR), and are either manually updated by the Emergency Medical Services (EMS) crew, or collected from electronic devices (e.g., hemodynamic monitor). The ePCR is updated with treatments and interventions that are administered during the transport. The hospital will not typically have access to paper or electronic versions of this patient information until the report is finished and signed in the ePCR and it is requested by the hospital. In this profile, the prehospital and paramedicine interventions and patient assessments are made available to the hospital/emergency room IT system electronically when the patient arrives, or in advance of patient arrival to the hospital. This informs medical decision making during the hospital treatment to improve patient care and to save lives.

Benefits

Having access to the Paramedicine transport information, informs medical decision making during the hospital treatment to improve patient care and to save lives.

Details

This profile maps the FHIR and CDA options for transferring this information from the electronic patient care record to the receiving facility's system using a document sharing [PCC-1] transaction.

Actors & Transactions:

• Content Creator
• Content Consumer
• Document Sharing (PCC-1)

Specification

Profile Status: Trial Implementation

Documents: PCS Supplement

Referenced Standards

FHIR transaction HL7 Version 3 Domain Analysis Model: Emergency Medical Services, Release 1 <http://www.hl7.org/implement/standards/product_brief.cfm?product_id=39>

HL7 Version 3 Domain Information Model; Emergency Medical Services, Release 1 <http://www.hl7.org/implement/standards/product_brief.cfm?product_id=302>

HL7 Version 3 Implementation Guide for CDA Release 2 - Level 3: Emergency Medical Services; Patient Care Report, Release 2 - US Realm <http://www.hl7.org/implement/standards/product_brief.cfm?product_id=438>

HL7 Version 3 Domain Analysis Model: Trauma Registry Data Submission, http://www.hl7.org/implement/standards/product_brief.cfm?product_id=363

HL7 CDA® R2 Implementation Guide: Trauma Registry Data Submission, Release 1 - US Realm http://www.hl7.org/implement/standards/product_brief.cfm?product_id=355

HL7 Version 2.7.1 Implementation Guide: Message Transformations with OASIS Tracking of Emergency Patients (TEP), Release 1 http://www.hl7.org/implement/standards/product_brief.cfm?product_id=439

National Trauma Data Standard Data Dictionary https://www.facs.org/~/media/files/quality%20programs/trauma/ntdb/ntds/data%20dictionaries/ntds%20data%20dictionary%202018.ashx

HL7 FHIR standard STU3 http://hl7.org/fhir/STU3/index.html

CDA Transaction: HL7 CDA Release 2.0 http://www.hl7.org/documentcenter/public/standards/dstu/CDAR2_IG_PROCNOTE_DSTU_R1_2010JUL.zip

HL7 Implementation Guide for CDA Release 2 – Level 3: Emergency Medical Services; Patient Care Report, Release 2 – US Realm http://www.hl7.org/implement/standards/product_brief.cfm?product_id=438

HL7 Version 3 Domain Analysis Model, Emergency Medical Services, Release 1 http://www.hl7.org/implement/standards/product_brief.cfm?product_id=421

HL7 version 3 Domain Information Model; Emergency Model Services, release 1 http://www.hl7.org/implement/standards/product_brief.cfm?product_id=302

Structure definitions

http://ihe.net/fhir/StructureDefinition/IHE.PCC.PCS.Composition

http://ihe.net/fhir/StructureDefinition/IHE.PCC.PCS.Patinet

http://ihe.net/fhir/StructureDefinition/IHE.PCC.PCS-CS.Patinet

http://ihe.net/fhir/StructureDefinition/IHE.PCC.PCS.Condition

http://ihe.net/fhir/StructureDefinition/IHE.PCC.PCS.Procedure

http://ihe.net/fhir/StructureDefinition/IHE.PCC.PCS.MedicationAdministration

http://ihe.net/fhir/StructureDefinition/IHE.PCC.PCS.MedicationStatement

http://ihe.net/fhir/StructureDefinition/IHE.PCC.PCS.Observation

http://ihe.net/fhir/StructureDefinition/IHE.PCC.PCS.Encounter

http://ihe.net/fhir/StructureDefinition/IHE.PCC.PCS-CS.Encounter

http://ihe.net/fhir/StructureDefinition/IHE.PCC.PCS.Location

http://ihe.net/fhir/StructureDefinition/IHE.PCC.PCS-CS.Location

http://ihe.net/fhir/StructureDefinition/IHE.PCC.PCS.RelatedPerson

http://ihe.net/fhir/StructureDefinition/IHE.PCC.PCS.AllergyIntolerance

http://ihe.net/fhir/StructureDefinition/IHE.PCC.PCS.AdverseEvent

http://ihe.net/fhir/StructureDefinition/IHE.PCC.PCS.ClinicalImpression

http://ihe.net/fhir/StructureDefinition/IHE.PCC.PCS.Device

http://ihe.net/fhir/StructureDefinition/IHE.PCC.PCS.DocumentReference