IHE PCC - Routine Interfacility Patient Transport (RIPT)
2.0.0-draft - ci-build

IHE PCC - Routine Interfacility Patient Transport (RIPT), published by IHE Patient Care Coordination. This is not an authorized publication; it is the continuous build for version 2.0.0-draft). This version is based on the current content of https://github.com/IHE/PCC.RIPT/ and changes regularly. See the Directory of published versions

## RIPT Home

Official URL: http://profiles.ihe.net/PCC/RIPT/ImplementationGuide/ihe.pcc.ript | Version: 2.0.0-draft
Draft as of 2023-01-27 | Computable Name: IHE_PCC_RIPT

When a professional transport takes place, there is information that needs to be recorded into a transport organization’s patient record, needed for patient care that is not electronically available to the transport team. Much of the information is currently available in standard formats in electronic discharge summaries used in US, Canada and European healthcare settings using the HL7 CDA Release 2.0 Standard. Other standards, such as HL7 FHIR resources could also be used to communicate this information between the discharging facility and EMS transport company. The way that the transport company is contacted for the transport is out of the scope of this profile. The use of electronic transfer summaries benefits both hospitals and transport companies by decreasing staff time used to communicate such information, and hospitals will further benefit in reduced patient wait times for transfers and increase bed availability that could result from this time efficient transfer of this information. IHE is an excellent venue to solve this problem because it already has substantial experience with the standards that will be used and the necessary content and the knowledge of CDA-based discharge summaries (e.g., MS XPHR). IHE will also provide a mechanism for Transport system vendors and Hospital system vendors to establish and test a solution. Much of the content is already in the current, real world, EMR systems in hospitals and patient care facilities. This is regularly used when a patient is being transferred from a hospital into the rehab facility where the patient information is electronically sent to the facility that the patient is going to go into. This system can then be reused to fulfill transport system information needs.

Open and Closed Issues

### Organization of This Guide

This guide is organized into four main sections:

1. Volume I: Profiles
   1. Refferal For Interfacility Patient Transport (RIPT) Profile
   2. Overview
   3. Actors and Transactions
   4. Actor Options
   5. Actor Required Groupings
   6. Overview
   7. Security Considerations
   8. ​Cross Profile Considerations
2. Volume II: Transaction Detail
   1. Document Sharing [PCC-1]
3. Volume III: Content Modules
   1. [RIPT Content Modules]](volume-3.html)
   2. RIPT FHIR IG Build
4. Volume IV: National Extensions
   1. National Extensions for the United States of America (USA)
5. Appendix
   1. Test Plan
   2. [RIPT NEMSIS to CDA and FHIR Mapping]TODO: point to your appendix if you have them

Click on any of the links above, head on over the table of contents, or if you are looking for a specific artifact, check out the index.

You can also download:

- this entire guide,
- the definition resources in json, xml, ttl, or csv format, or
- the example resources in json, xml or ttl format.

The source code for this Implementation Guide can be found on TODO: Put your github repo here