 HL7 PA, R2-2010 HL7 Version 3 Standard: Patient Administration, DSTU Release 2 Update February 2010 Update to DSTU Release 2 |
Content Last Edited: 2011-06-17T13:44:56
12.2 Storyboards
12.3 Application Roles
12.4 Trigger Events
12.5 Refined Message Information Models
12.6 Hierarchical Message Descriptions
12.7 Interactions
This topic covers messages about patient transfers from one assigned location to another during a patient encounter. This type of message would only be exchanged between systems that are closely coupled with respect to patient location assignments so the information model consists of little more than identifiers for the encounter, patient and locations (and any Accommodation Events associated with the locations) plus the time intervals for the patient location assignments. In HL7 version 2.x terms, these messages represent the ADT^A02 (transfer a patient) and the ADT^A12 (cancel transfer) events.
Note that these interactions are only for reporting changes. The initial participation is created by the interaction that begins the encounter and the final participation is completed by the interaction that ends the encounter.
The Patient Administration work group chose to limit scope in this release by:
- Limiting storyboards to the simplest cases
- Excluding order/request messages
- Including notification messages only for changes of assigned patient location (see diagram below; the unsupported states and transitions are grayed out in the diagram).
The Patient Administration Technical Committee invites implementers with additional requirements to submit content proposals for future releases of the standard.
This document was previously published as DSTU in 2007 and it is being issued as an updated DSTU again due to the lack of feedback from implementers. The Patient Administration work group wants to hear from implementers regarding the suitability for use of this content.
|
||||||||
|
For details on the interpretation of this section, see the storyboard discussion in the Version 3 Guide.
This storyboard demonstrates transferring a patient from one assigned location to another during an encounter.
| Patient Transferred to New Location |  PRPA_IN302011UV02 |
Mr. Adam Everyman was admitted on Monday to the Good Health Hospital Inpatient Unit for his hip replacement surgery and assigned to room 1016, bed A. Later that day a problem developed in the oxygen line to his room so Mr. Everyman was moved to room 1022, bed B [Interaction Patient Transferred to New Location].
This storyboard demonstrates canceling a reported transfer of a patient from one location to another.
| Patient Transfer to New Location Canceled | PRPA_IN302012UV02 |
Mr. Adam Everyman was an inpatient in the Good Health Hospital assigned to room 1016, bed A. A problem developed in the oxygen line to room 1016 so arrangements were made to move Mr. Everyman to room 1022, bed B. The clerk recorded the location change but before Mr. Everyman was moved the problem with the oxygen was fixed so the clerk reversed the location change [Interaction Patient Transfer to New Location Canceled].
|
||||||||
|
For details on the interpretation of this section, see the discussion of application roles and their relationships in the Version 3 Guide.
An Patient Location Assignment Change Informer sends notifications about changes in a patient's assigned location. It can also send cancellation notification if a reported change did not take place.
An Patient Location Assignment Change Tracker receives notifications about changes in a patient's assigned location. It can also receive cancellation notification if a reported change did not take place.
|
||||||||
|
For details on the interpretation of this section, see the discussion of trigger events in the Version 3 Guide.
| Type: | State-transition based |
| State Transition: | location2 (PRPA_RM302011UV02) |
| location1 (PRPA_RM302011UV02) |
This trigger event signals transfer of a patient from one assigned location to another during an encounter.
The Change Patient Location trigger event is most closely aligned with the HL7 2.4 ADT^A02 - transfer a patient event.
| Type: | State-transition based |
| State Transition: | location2 (PRPA_RM302011UV02) |
| location1 (PRPA_RM302011UV02) |
This trigger event signals that a previously-reported patient transfer from one assigned location to another did not take place. The previous Change Patient Location action was reversed.
The Cancel Change of Patient Location trigger event is most closely aligned with the HL7 2.4 ADT^A12 - cancel transfer event.
|
||||||||
|
For details on the interpretation of this section, see the description of RMIMs in the Version 3 Guide.
| Parent: | Patient Administration (PRPA_DM000000UV) |
The Assigned Patient Location Change R-MIM defines the message used to report that a patient has been transferred from one assigned location to another during an encounter.
EncounterEvent
The entry is the focal encounter, EncounterEvent. The R-MIM assumes encounter location change messages would be exchanged between systems that are closely coupled with respect to patient location assignments so the id and code attributes and the subject association to R_Patient [identified] CMET are included.
location1
The location1 participation is the active patient location assignment for the encounter. The attributes statusCode (default of "active") and time (populated with the assignment start date-time) are mandatory. The location is sent as a ServiceDeliveryLocation that has an optional association to an AccommodationEvent.
location2
The location2 participation is the patient's assigned location prior to the change action. The attributes statusCode and time are mandatory. The default statusCode is "completed" and the time attribute should contain the time range (starting and ending date-time) for the completed location assignment. The location is sent as a ServiceDeliveryLocation that has an optional association to an AccommodationEvent for the completed location assignment.
ServiceDeliveryLocation
ServiceDeliveryLocation is a role played by a place at which services may be provided. The types of services are characterized by the code attribute. Either ServiceDeliveryLocation.id or E_Place.name must be valued.
AccommodationEvent
A patient location assignment may be associated with one or more AccommodationEvents, that is, a service (usually billable) provided for a Person in which a place is provided for the subject to reside for a period of time. Commonly used to track the provision of ward, private and semi-private accommodations for a patient.
| Assigned Patient Location Change | PRPA_HD302011UV02 |
| Parent: | Patient Administration (PRPA_DM000000UV) |
The Assigned Patient Location Change Cancel R-MIM defines the message used to notify systems that a previous assigned patient location change notification was sent in error and has been reversed.
EncounterEvent
The entry point to the R-MIM is the focal encounter, EncounterEvent. The R-MIM assumes assigned patient location change messages would be exchanged between systems that are closely coupled with respect to patient location assignments so only the id and code attributes and the subject association to R_Patient [identified] CMET are included.
location1
The location1 participation is the correct patient location assignment for the encounter. The attributes statusCode (default of "active") and time (populated with the assignment start date-time) are mandatory. The location is sent as a ServiceDeliveryLocation that has an optional association to an AccommodationEvent.
location2
The location2 participation is the nullified (erroneously reported) patient location assignment for the encounter. Either the id or the time attribute must be valued so the receiving system knows exactly which patient location assignment is being nullified.
| Assigned Patient Location Change Canceled | PRPA_HD302012UV02 |
|
||||||||
|
For details on the interpretation of this section, see the description of HMDs in the Version 3 Guide.
| R_PatientIdentified | COCT_MT050001UV07 |
| E_OrganizationIdentified | COCT_MT150001UV01 |
| E_PlaceUniversal | COCT_MT710000UV07 |
| Assigned Patient Location Change Canceled | PRPA_MT302012UV02 | |
This HMD defines the message used report that a patient was transfered to a new assigned location during an active encounter.
| R_PatientIdentified | COCT_MT050001UV07 |
| E_OrganizationIdentified | COCT_MT150001UV01 |
| E_PlaceUniversal | COCT_MT710000UV07 |
| Assigned Patient Location Changed | PRPA_MT302011UV02 | |
|
||||||||
|
For details on the interpretation of this section, see the definition of Interactions in the Version 3 Guide.
This interaction occurs after a patient is transferred from one assigned location to another. An informer sends to a tracker a small message identifying the encounter, the patient, the previous location and assignment time range, the new location and start time, and any related Accommodation events.
| Trigger Event | Patient Location Transfer | PRPA_TE302011UV02 |
| Transmission Wrapper | Send Message Payload | MCCI_MT000100UV01 |
| Control Act Wrapper | Trigger Event Control Act | MCAI_MT700201UV01 |
| Message Type | Assigned Patient Location Changed | PRPA_MT302011UV02 |
| Sender | Patient Location Assignment Change Informer | PRPA_AR302011UV02 |
| Receiver | Patient Location Assignment Change Tracker | PRPA_AR302012UV02 |
This interaction occurs after a previously reported transfer of a patient from one assigned location to another is canceled. An informer sends to a tracker a small message identifying the encounter, the patient, the location assignment to be reactivated, and location assignment to be nullified.
| Trigger Event | Patient Location Transfer Canceled | PRPA_TE302012UV02 |
| Transmission Wrapper | Send Message Payload | MCCI_MT000100UV01 |
| Control Act Wrapper | Trigger Event Control Act | MCAI_MT700201UV01 |
| Message Type | Assigned Patient Location Change Canceled | PRPA_MT302012UV02 |
| Sender | Patient Location Assignment Change Informer | PRPA_AR302011UV02 |
| Receiver | Patient Location Assignment Change Tracker | PRPA_AR302012UV02 |
| Return to top of page |