|Submitted By: Adam Bazer, MPD / Integrating the Healthcare Enterprise USA (IHE USA)|
|Data Element Information|
|Use Case Description(s)|
|Use Case Description||This use case pertains to the adoption of all of the defined data elements to be used as in the following use case.
a 28-year-old female, is going home from the hospital after having an infection due to systemic fibrosis. The doctors prescribed oxygen after treatment, and call a transport company to take her to a rehabilitation center. Alison is a paraplegic and is wheelchair bound. Due to the prescribed oxygen, there needs to be monitoring for her transport. The hospital creates a referral for her transport. The reasons for referral are heavily used to justify her transport for billing and payment. The referral requestor is used to identify who is requesting the service. The referral coverage includes the insurance information that may be needed to cover the event. The referral code indicates what type of service is being requested, in this case interfacility transport.
|Estimated number of stakeholders capturing, accessing using or exchanging||This data class would utilized by emergency responders and ambulance systems that are used for interfacility transport. It will also be of interest for any provider engaged in continuity of care referrals.|
|Link to use case project page||https://www.ihe.net/uploadedFiles/Documents/PCC/IHE_PCC_Suppl_RIPT.pdf|
|Maturity of Use and Technical Specifications for Data Element|
|Applicable Standard(s)||Routine Interfacility Patient Transport (RIPT) - https://www.ihe.net/uploadedFiles/Documents/PCC/IHE_PCC_Suppl_RIPT.pdf
|Additional Specifications||Routine Interfacility Patient Transport (RIPT) - https://www.ihe.net/uploadedFiles/Documents/PCC/IHE_PCC_Suppl_RIPT.pdf
|Current Use||This data element has been used at scale between multiple different production environments to support the majority of anticipated stakeholders|
360 Exchange Closed Loop Referral (360X) Connecathon testing in 2019
Used in multiple HIMSS Demos
|Number of organizations/individuals with which this data element has been electronically exchanged||5 or more. This data element has been tested at scale between multiple different production environments to support the majority of anticipated stakeholders.|
|Restrictions on Standardization (e.g. proprietary code)||none|
|Restrictions on Use (e.g. licensing, user fees)||none|
|Privacy and Security Concerns||none|
|Estimate of Overall Burden||I anticipate that this may have a low burden for implementation since this data class and elements exist in FHIR and CDA for medical referrals, which has a large populations of stakeholders that already use this data class.|
|Other Implementation Challenges||none|
Information from the submission form
|Reason for referral||
An explanation or justification for why this service is being requested in coded or textual form. This is often for billing purposes.