Difference between revisions of "EMS Transport Summary"

From IHE Wiki
Jump to navigation Jump to search
Line 34: Line 34:
 
==Specification==
 
==Specification==
  
'''Profile Status:''' [[Comments| Final Text]]   
+
'''Profile Status:''' [[Comments| Trial Implementation]]   
''<Replace "Final Text" with "Trial Implementation" or "Public Comment" as appropriate.>''
 
  
 
'''Documents:'''  
 
'''Documents:'''  
Line 42: Line 41:
  
 
'''Underlying Standards:'''
 
'''Underlying Standards:'''
 
+
* HL7 CDA R2
  
 
''<list all the standards on which the profile is based; if possible with links to sources>''
 
''<list all the standards on which the profile is based; if possible with links to sources>''

Revision as of 12:55, 19 July 2016

The EMS Transport Summary (ETS) Profile details how information is shared during situations where patients are being transported to a hospital emergency department facility.

Summary

The ability to share information collected during the transport of a patient from any setting to the hospital emergency department facility with those who will be receiving the patient, regardless of transport time, is essential to complete patient care. The events focus on in this profile include those that involve a transport team, which is defined as any team of licensed or certified care providers that create content for the EMR. This team may be part of a fixed wing, helicopter, or ambulance transport. Multiple events associated with long term patient care are out of scope. Each incident that requires a specific number of transports between health care settings is the primary focus of this profile.


<Insert a simple graphic that, at a glance, visually summarizes what the profile is about. Do not use an actor/transaction diagram here. Show your graphic to someone for 5 seconds (literally) and ask them what it's about. If what they say hits the main points in your summary paragraph, you have succeeded. E.g. a graphic of a hospital, a clinic, and a lab with patient records moving between them. .>


Benefits

  • Provides opportunity for emergency department staff to be well-prepared for an arriving patient
  • Elimination or reduction of medical errors
  • Increase effectiveness and efficiency of hospital resource usage, including but not limited to healthcare staff

Details

Upon determination of the patient identity, the prehospital provider consumes data previously gathered in other IHE PCC Profiles (e.g., through PHR or HIE system). The prehospital provider creates new data relevant to the care provided. This combined data of the prehospital emergency care provided is then shared with the emergency department content consumer (EDIS). The shaded actors are defined elsewhere in IHE PCC profiles. For details on these actors, see section X.5.6 Grouping with Other PCC Content Profiles.

Systems Affected

  • Emergency Department Information System (EDIS)
  • Electronic Medical Record (EMR)
  • Personal Health Record (PHR)


Actors & Transactions:

  • Content Agent
  • Content Creator
  • Content Consumer


Specification

Profile Status: Trial Implementation

Documents:


Underlying Standards:

  • HL7 CDA R2

<list all the standards on which the profile is based; if possible with links to sources>

See Also

<The following sections can be left out if there is nothing to point to. This is just to show where such information can go.>


Related Profiles

<List profiles this one depends on, profiles that depend on this one, profiles that are synergistic with this one. Start with the name of the other profile as a link and then explain the relationship.>


Consumer Information

The Profile FAQ Template answers typical questions about what the Profile does. <Replace the link with a link to the actual FAQ page for the Profile>

The Profile Purchasing Template describes considerations when purchasing equipment to deploy this Profile. <Replace the link with a link to the actual Purchasing page for the Profile>

Implementer Information

The Profile Implementation Template provides additional information about implementing this Profile in software. <Replace the link with a link to the actual Implementation page for the Profile>

Reference Articles

<List References (good and bad) (with link if possible) to Journal Articles that mention IHE's work (and hopefully include some analysis). Go ahead, Google: IHE <Profile Name> abstract or Google: IHE <Profile Name> and under the "more" select "Scholar". You might be surprised. >


This page is based on the Profile Overview Template