Patient Location Tracking

The Patient Location Tracking (PLT) Integration Profile provides an integration solution to find the physical location (PL) of patients.

Summary

The Patient Location Tracking (PLT) Integration Profile provides an integration solution to find the physical location (PL) of patients. A physical location can be mapped to the service delivery location (SDL). An implementation may support SDL with this profile, e.g., using an appropriate code system of locations which relates PL to SDL. A PL may be shared by more than one SDL. It is up to an implementation to define their relationship if it decides to support SDL with this profile. IHE does not specify a mapping of PL to SDL.

Benefits

Quickly locate patients with a simple query.

Details

The Patient Location Tracking (PLT) Integration Profile supports collecting the patient location information in a facility, and providing his/her recently recognized location to other systems. PLT covers patient location tracking inside single facilities, not between two or more facilities.

There is no systemized mechanism that records the latest location of the patients in a hospital due to the lack of a standardized method to collect it. The Patient Location Tracking (PLT) Integration Profile standardizes the transactions, records patients' locations, and provides the latest information upon request from external subsystems.

Patient locations are recognized by Patient Location Tracking Suppliers, and received/managed by Patient Location Tracking Managers. Transaction [ITI-76] is used for a Patient Location Tracking Feed. Requests for a patient location are sent from Patient Location Tracking Consumers to Patient Location Tracking Managers using Patient Location Tracking Query [ITI-77].

Systems Affected

<List (in user terms) the types of systems they might expect to have implemented actors from this profile, e.g. RIS, PACS, HIS, CAD Workstation, etc. and for each, how it would participate.>

• PACS systems may store, manage, and/or display Evidence Documents.
• Display systems may query, retrieve and display Evidence Documents.
• Reporting workstations may retrieve, process and include details from Evidence Documents in reports

Actors & Transactions:

<Insert an actor-transaction diagram, and or list of Content Definitions>

Specification

Profile Status: Final Text <Replace "Final Text" with "Trial Implementation" or "Public Comment" as appropriate.>

Documents:

<Provide direct links to the specific volumes or supplements, and list the volume sections relevant to this profile. This is a simple inventory of official normative and informative text. If you would like to provide a reading guide or walkthrough of what is in each of the different sections for implementers or users, do that in the Profile FAQ or the Profile Implementation Page linked below. If the profile uses transactions from multiple Tech. Frameworks, repeat the structure below.>

IHE Radiology Technical Framework:

• Vol. 1 - Section 5 (SWF Profile)
• Vol. 2 - Sections 4.8 to 4.10, 4.14 to 4.19, and 4.23
• Vol. 3 - Appendix E

Underlying Standards:

<list all the standards on which the profile is based; if possible with links to sources>

• DICOM
• HL7
• ...

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.>

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.>

• 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.

Consumer Information

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. >

This page is based on the Profile Overview Template

<Delete this Category Templates line since your Profile page is no longer a template.>