Difference between revisions of "Routine Interfacility Patient Transport (RIPT)"

From IHE Wiki
Jump to: navigation, search
(Specification)
 
(42 intermediate revisions by 3 users not shown)
Line 1: Line 1:
''This template is for the one or two page user-oriented overview of an IHE Profile that is in Final Text, Trial Implementation or perhaps Public Comment.  Delete text in italics and replace it with your material. Don't forget to delete the double quotes too.''
+
There is a need for interoperability between hospitals and Emergency Medical Service (EMS) systems. When a hospital patient is discharged, there is no standard for documentation provided to the EMS transport team that informs them of important patient care information. This profile provides a methodology for that gap.
 +
__TOC__
  
''Your page name should simply be Full Profile Name with spaces, with capitals, without the acronym. e.g. Scheduled Workflow. so it provides a title to the page. You can redirect the acronym to the full named page if you like for bonus points.''
+
==Summary==
  
 +
''[[File:IHE_PCC_RIPT_Picture.png]]''
  
''<IN ONE LINE, tell a user what the profile is about (including the acronym) so they can decide if they're on the right page.  Basically this should be the same sentence that appears on the [[Profiles]] catalog page>''
 
  
''e.g. Scheduled Workflow (SWF) integrates ordering, scheduling, imaging acquisition, storage and viewing for Radiology exams.''
+
Transport organizations must record information about patients being transferred under their care so that the organizations can minimize errors in their patient care record and the patient can have accurate and an appropriate level of care for their condition. This information is either gathered verbally through nursing staff or by perusing extensive paperwork to find the information needed for the transport patient care record. Once the transport is completed, the same information is also communicated as part of the transport summary. While the transfer of patient information is often done in electronic information systems today, a lack of standards means that duplicate entry is commonplace, leading to a higher chance for data entry errors by transport staff. With this profile the transport team’s time spent gathering information in the facility can be greatly reduced, accurate data is received and sent, and the team can spend quality time providing care to the patient.
 
+
__TOC__
+
 
+
==Summary==
+
Transport organizations must record information about patients being transferred under their care so that the organizations can minimize errors in their patient care record and the patient can have accurate and an appropriate level of care for their condition. This information is either gathered verbally through nursing staff or by perusing extensive paperwork to find the information needed for the transport patient care record. Once the transport is completed, the same information is also communicated as part of the transport summary. While this is often done in electronic information systems today, a lack of standards means that duplicate entry is commonplace, leading to a higher chance for data entry errors. While the transfer of patient information is often done in electronic information systems today, a lack of standards means that duplicate entry is commonplace, leading to a higher chance for data entry errors by transport staff. With this profile the transport team’s time spent gathering information in the facility can be greatly reduced and the team can spend more time providing care to the patient.  
+
 
+
''<See [[Help:Contents#Tips_.26_Tricks| Help - Tips and Tricks]] for details on inserting an image/graphic.>''
+
  
 
==Benefits==
 
==Benefits==
The time transport team’s spend gathering information in the hospital can be greatly reduced and decreasing duplicate data entry lessens the chance of data entry errors. This allows more time to be spent providing care to the patient, rather than spending prolonged periods of time searching for, and manually re-entering needed data. Another benefit is improved throughput for Emergency Departments (ED) which increases inpatient bed availability, by creating a faster turnover rate for hospital discharges.
+
The time transport team’s spend gathering information in the hospital can be greatly reduced and decreasing duplicate data entry lessens the chance of data entry errors. This decreases the potential for patient care errors and allows more time to be spent providing care to the patient, rather than spending prolonged periods of time searching for, and manually re-entering needed data. Another benefit is improved throughput for Emergency Departments (ED) and hospital care units which increases inpatient bed availability by creating a faster turnover rate for hospital discharges.
  
 
==Details==
 
==Details==
Line 24: Line 18:
 
==Systems Affected==
 
==Systems Affected==
  
* Transport System
+
* Transport systems patient record systems
* Hospital electronic record system
+
* Hospital electronic patient record systems
*
+
 
 +
 
 
'''Actors & Transactions:'''
 
'''Actors & Transactions:'''
  
''''
+
    [[Image: PCC Share Content Diagram.png | 350px]]
 +
 
 +
''[[File:RIPT_Actors.png]]''
 +
 
 +
 
 +
''[[File:RIPT_Actor_Transactions.png]]''
  
 
==Specification==
 
==Specification==
  
'''Profile Status:''' [[Comments| Trial Implementation]]   
+
'''Profile Status:''' [[Comments| Trial Implementation]]  
 +
   
 +
 
 +
'''Documents:'''
 +
 
 +
[http://www.ihe.net/Technical_Framework/index.cfm# Patient Care Coordination (PCC) IHE PCC Technical Framework:]
 +
:* https://www.ihe.net/uploadedFiles/Documents/PCC/IHE_PCC_Suppl_RIPT.pdf
  
  
 
'''Underlying Standards:'''
 
'''Underlying Standards:'''
  
''<list all the standards on which the profile is based; if possible with links to sources>''
 
 
:* HL7 FHIR STU3 http://hl7.org/fhir/STU3
 
:* HL7 FHIR STU3 http://hl7.org/fhir/STU3
 
:* HL7 CDA Release 2.0 and Reference Information Model
 
:* HL7 CDA Release 2.0 and Reference Information Model
Line 44: Line 49:
 
==See Also==
 
==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.>''
+
The IHE PCC Interfacility Transport Summary (ITS) profile is referenced in the RIPT profile, but the ITS profile is transporting the patient to the hospital, as compared to transporting the patient from the hospital to another facility as in the RIPT profile.  
 
+
 
+
 
'''Related Profiles'''
 
'''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.>''
+
* Interfacility Transport Summary [http://wiki.ihe.net/index.php/Interfacility_Transport_]''
  
* ''[[Reporting Workflow]] [RWF] may use Evidence Documents as inputs to the reporting process.''
 
* ''[[Simple Image & Numeric Reports]] [SINR] may include data copied from Evidence Documents.''
 
* ''[[Cross-enterprise Document Sharing for Imaging]] [XDS-I] can be used to share Evidence Documents between sites over a network.''
 
* ''[[Portable Data for Imaging]] [PDI] can store Evidence Documents on media such as CDs.''
 
* ''[[Import Reconciliation Workflow]] [IRWF] can fix patient ids, etc. of Evidence Documents when importing.''
 
  
 
+
[[Category:Profiles]][[Category:Patient Care Coordination]]
'''Consumer Information'''
+
[[Category:DocShare]]
 
+
[[Category:FHIR]]
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. >''
+
 
+
[[Category:Profiles]]
+
 
+
This page is based on the [[Profile Overview Template]]
+
 
+
[[Category:Template]]
+
<noinclude>''<'''Delete this Category Templates line''' since your Profile page is no longer a template.>'' </noinclude>
+
 
+
<!--
+
Categorize the Domain of your Profile with one of the following (delete the rest):
+
[[Category:CARD Profile]]
+
[[Category:DENT Profile]]
+
[[Category:ENDO Profile]]
+
[[Category:EYECARE Profile]]
+
[[Category:ITI Profile]]
+
[[Category:PaLM Profile]]
+
[[Category:PCC Profile]]
+
[[Category:PCD Profile]]
+
[[Category:PHARM Profile]]
+
[[Category:QRPH Profile]]
+
[[Category:RO Profile]]
+
[[Category:RAD Profile]]
+
 
+
Categorize key standards used in your Profile with one or more of the following (delete the rest):
+
 
[[Category:CDA]]
 
[[Category:CDA]]
[[Category:FHIR]]
+
[[Category:FHIR-Doc]]
[[Category:DICOM]]
+
[[Category:EMS]]
[[Category:DICOMweb]]
+
[[Category:HL7v2]]
+
[[Category:XDW]]
+
[[Category:DocShare]]
+
 
+
And if people forget to do this, we'll comment this out and you can forget to opt-in. :-)
+
-->
+

Latest revision as of 09:52, 1 June 2021

There is a need for interoperability between hospitals and Emergency Medical Service (EMS) systems. When a hospital patient is discharged, there is no standard for documentation provided to the EMS transport team that informs them of important patient care information. This profile provides a methodology for that gap.

Summary

IHE PCC RIPT Picture.png


Transport organizations must record information about patients being transferred under their care so that the organizations can minimize errors in their patient care record and the patient can have accurate and an appropriate level of care for their condition. This information is either gathered verbally through nursing staff or by perusing extensive paperwork to find the information needed for the transport patient care record. Once the transport is completed, the same information is also communicated as part of the transport summary. While the transfer of patient information is often done in electronic information systems today, a lack of standards means that duplicate entry is commonplace, leading to a higher chance for data entry errors by transport staff. With this profile the transport team’s time spent gathering information in the facility can be greatly reduced, accurate data is received and sent, and the team can spend quality time providing care to the patient.

Benefits

The time transport team’s spend gathering information in the hospital can be greatly reduced and decreasing duplicate data entry lessens the chance of data entry errors. This decreases the potential for patient care errors and allows more time to be spent providing care to the patient, rather than spending prolonged periods of time searching for, and manually re-entering needed data. Another benefit is improved throughput for Emergency Departments (ED) and hospital care units which increases inpatient bed availability by creating a faster turnover rate for hospital discharges.

Details

Patient discharge is shown using FHIR transactions and CDA documents to make the flow of the patient information from the hospital to the transport team paperless.

Systems Affected

  • Transport systems patient record systems
  • Hospital electronic patient record systems


Actors & Transactions:

    PCC Share Content Diagram.png

RIPT Actors.png


RIPT Actor Transactions.png

Specification

Profile Status: Trial Implementation


Documents:

Patient Care Coordination (PCC) IHE PCC Technical Framework:


Underlying Standards:

See Also

The IHE PCC Interfacility Transport Summary (ITS) profile is referenced in the RIPT profile, but the ITS profile is transporting the patient to the hospital, as compared to transporting the patient from the hospital to another facility as in the RIPT profile.

Related Profiles

  • Interfacility Transport Summary [1]