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

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

Artifacts Summary

Contents:

This page provides a list of the FHIR artifacts defined as part of this implementation guide.

Behavior: Capability Statements

The following artifacts define the specific capabilities that different types of systems are expected to have in order to comply with this implementation guide. Systems conforming to this implementation guide are expected to declare conformance to one or more of the following capability statements.

IHE FooBar Server

CapabilityStatement for Server Actor in the IHE IT Infrastructure Technical Framework Supplement IHE FooBar. See https://profiles.ihe.net/ITI/TF/Volume1/ch-38.html. The IHE Profile text is Normative, this conformance resource is Informative.
IHE FooBar client

CapabilityStatement for Client Actor in the IHE IT Infrastructure Technical Framework Supplement IHE FooBar. See https://profiles.ihe.net/ITI/TF/Volume1/ch-38.html. The IHE Profile text is Normative, this conformance resource is Informative.

Structures: Resource Profiles

These define constraints on FHIR resources for systems conforming to this implementation guide.

RIPT AllergyIntolerance

This profile represents the constraints applied to the AllergyIntolerance resource by the Refferal For Interfacility Patient Trasnport (RIPT) FHIR Implementation Guide: Within the AllergyIntolerance section the Content Creator SHALL be able to create an AllergyIntolerance entry to identify the patient’s medication and environmental/food allergies. Environmental/food allergies using SNOMED-CT SHOULD be used to identify the allergen.

Medication allergies use RxNorm SHOULD be used to only to identify an allergy as a specific drug. To indicate an allergy to a class of drug ICD-10 SHOULD be used.
RIPT Condition

This profile represents the constraints applied to the Condition resource by the Refferal For Interfacility Patient Trasnport (RIPT) FHIR Implementation Guide: Within the Problems section the Content Creator SHALL be able to create a Condition entry to identify Medical/surgical History conditions and findings for the patient being transported. Including behaviors that may affect transport personnel (e.g., combativeness).
RIPT Procedures

This profile represents the constraints applied to the Procedures resource by the Refferal For Interfacility Patient Trasnport (RIPT) FHIR Implementation Guide.
Refferal For Interfacility Patient Transport

composition of the FHIR elements that are used to build the FHIR Document for the Refferal For Interfacility Patient Transport document. the following cardinalities follow the documentation in the RIPT profile:

  • RE 0..1 IPS Advance Directives
  • R 1..1 IPS Allergies and Intolerances
  • R 1..1 IPS Medication Summary
  • RE 0..1 IPS History of Past Illness
  • R 1..1 IPS Functional Status
  • RE 0..1 IPS History of Procedures
  • O 0..1 Immunizations
  • O 0..1 IPS Medical Devices
  • RE 0..1 IPS Problems
  • O 0..1 IPS Results
  • RE 0..1 IPS Vital Signs
  • RE 0..1 IPS History of Pregnancy
  • O 0..1 IPS Plan of Care
  • O 0..1 Payor
  • RE 0..1 Coded Reason for Referral
  • RE 0..1 Transport Instructions

Terminology: Value Sets

These define sets of codes used by systems conforming to this implementation guide.

AllergyIntolerance_PCS_VS

TBD
Condition_PCS_VS

TBD
Medical_Necessity_VS

Value set for Transport Reasons used to in Certificate of medical necesity entry
Procedures_PCS_VS

TBD
Reason_for_Interfacility_Transport_VS

Value set for Reason for Interfacility Transport used to in Certificate of medical necesity