Routine Interfacility Patient Transport (RIPT)
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.
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.
<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 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 - Tips and Tricks for details on inserting an image/graphic.>
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.
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.
- Transport System
- Hospital electronic record system
Actors & Transactions:
Profile Status: Trial Implementation
<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 CDA Release 2.0 and Reference Information Model
<The following sections can be left out if there is nothing to point to. This is just to show where such information can go.>
<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.>
- 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.
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>
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>
<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 <Delete this Category Templates line since your Profile page is no longer a template.>