This application role is responsible for notifying applications when a tracked patient, a tracked provider and a tracked device move to the same location (as defined by local business rules) in a facility.

This application role is responsible for notifying applications when a tracked patient and a tracked provider move to the same location (as defined by local business rules) in a facility.

This application role is responsible for notifying applications when tracked resources (patients, providers, devices) move to the same location (as defined by local business rules) in a facility.

This application role is responsible for notifying applications when a tracked device changes location.

This application role is responsible for notifying applications when a tracked patient changes location.

This application role is responsible for notifying applications when a tracked health care practitioner changes location.

This application role receives notifications sent when a tracked patient, a tracked provider and a tracked device move to the same location (as defined by local business rules) in a facility.

This application role receives notifications sent when a tracked patient and a tracked provider move to the same location (as defined by local business rules) in a facility.

This application role receives notifications sent when tracked resources (patients, providers, devices) move to the same location (as defined by local business rules) in a facility.

This application role receives notifications sent when tracked devices change location.

This application role receives notifications sent when tracked patients change location.

This application role receives notifications sent when tracked health care practitioners change location.

This application role is responsible for notifying applications when a real time location system tracking tag is assigned or unassigned to a device.

This application role is responsible for notifying applications when a real time location system tracking tag is assigned or unassigned to a patient.

This application role is responsible for notifying applications when a real time location system tracking tag is assigned or unassigned to a health care practitioner.

This application role receives notifications sent when health care devices are assigned or unassigned real time location system tracking tags.

This application role receives notifications sent when patients are assigned or unassigned real time location system tracking tags.

This application role receives notifications sent when health care practitioners are assigned or unassigned real time location system tracking tags.

This application role is responsible for notifying applications when a real time location system tracking tag is assigned or unassigned to a health care resource (patient, provider or device).

This application role receives notifications sent when real time location system tracking tags are assigned or unassigned to health care resources (patients, providers or devices).

This trigger event signals that a patient and provider are now in the same location. Locally defined business rules determine which locations are of interest and how long the tracked resources need to be in that location to initiate this trigger event.

This trigger event signals that a patient, a provider and a piece of equipment are now in the same location. Locally defined business rules determine which locations are of interest and how long the tracked resources need to be in that location to initiate this trigger event.

This trigger event signals that a tracking tag has moved to a new location. Locally defined business rules determine which locations are of interest and how long the tracked resource needs to be in that location to initiate this trigger event.

The Tag Assignment information model defines the payload message used when informing systems about the assignment of a real time location tracking tag to a resource playing the role of patient, provider or device.

The entry point to this payload message is the IdTag role played by a physical tracking tag (ManufacturedMaterial) that is Held by a particular Person, NonPersonLivingSubject, or Device. A Person holding the IdTag must play the role of an identified HealthCareProvider or an identified Patient. A NonPersonLivingSubject holding the IdTag must play the role of an identified Patient.

The specifics of the assignment action are conveyed in the Master File / Reg Event Notification Control Act (MFMI_RM700700UV) control act:

• Assign a tracking tag to a resource -- the RegistrationEvent.statusCode is set to active and the starting time of the RegistrationEvent.effectiveTime interval is populated.
• End assignment of a tracking tag to a resource -- the RegistrationEvent.statusCode is set to completed and the ending time of the RegistrationEvent.effectiveTime interval is populated.
• Cancel an erroneously reported assignment of a tracking tag to a resource -- the RegistrationEvent.statusCode is set to nullified .

The Tag Location information model defines the payload message used when informing systems about the location of a real time location tracking tag assigned to a patient, provider or device.

The entry point to this payload message is the PositionObservationEvent representing the act of observing the position of a tracking tag. The required statusCode attribute conveys the status of the observation event; the default value is completed. The required effectiveTime attribute is the time the tracking tag was observed at the reported location. The priorityCode conveys the relative urgency for reporting this location observation. The confidentialityCode contains values that control disclosure of this location observation.

The PositionObservationEvent has a mandatory location association to exactly one ServiceDeliveryLocationRole.

The PositionObservationEvent has a mandatory subject association to exactly one IdTag which has an optional association to the Person, NonPersonLivingSubject, or Device holding the tag. A Person can be identified as either a Patient or a HealthCareProvider. A NonPersonLivingSubject can be identified as a Patient.

The Co-Located Tags information model defines the payload message used when informing systems that two or more real time location tracking tags are in close proximity to one another.

The entry point to this payload message is the PositionObservationEvent representing the act of observing the position of the tracking tags. The required statusCode attribute conveys the status of the observation event; the default value is completed. The required effectiveTime attribute is the time the tracking tags were observed at the reported location. The priorityCode conveys the relative urgency for reporting this location observation. The confidentialityCode contains values that control disclosure of this location observation.

The PositionObservationEvent has a mandatory location association to exactly one ServiceDelvieryLocationRole.

The PositionObservationEvent has a mandatory subject association to two or more IdTags each which has an optional association to the Person, NonPersonLivingSubject, or Device holding the tag. A Person can be identified as either a Patient or a HealthCareProvider. A NonPersonLivingSubject can be identified as a Patient..

This HMD defines the payload message used when informing systems that two or more real time location tracking tags are in close proximity to one another.

Base Hierarchical Message Description   

Message Type List

Tags Co-located

PRRG_MT801003UV01

Description 

This notification is sent from an EMR or medical logistics system to a real time location tracking system to convey that a specific tracking tag has been assigned to a specific piece of equipment.

Description 

This notification is sent from an EMR or registration system to a real time location tracking system to convey that a specific tracking tag has been assigned to a specific patient.

Description 

This notification is sent from an EMR or registration system to a real time location tracking system to convey that a specific tracking tag has been assigned to a specific healthcare practitioner.

Description 

This notification is sent from an EMR or medical logistics system to a real time location tracking system to convey that a specific tracking tag is no longer assigned to a specific piece of equipment.

Description 

This notification is sent from an EMR or registration system to a real time location tracking system to convey that a specific tracking tag is no longer assigned to a specific patient.

Description 

This notification is sent from an EMR or registration system to a real time location tracking system to convey that a specific tracking tag is no longer assigned to a specific provider.

Description 

This notification is sent from a real time location tracking system to convey that a patient, a provider and a device are now in the same location. Locally defined business rules determine which locations are of interest and how long the resources need to be in that location to trigger this interaction.

In this interaction the PositionObservationEvent has three subject participations -- one to Device, one to Person playing the role of HealthCareProvider and one to LivingSubjectChoice with either Person or NonPersonLivingSubject playing the role of Patient.

Description 

This notification is sent from a real time location tracking system to convey that a patient and a provider are now in the same location. Locally defined business rules determine which locations are of interest and how long the resources need to be in that location to trigger this interaction.

Description 

This notification is sent from a real time location tracking system to convey that a tracked device has moved to a different location. Locally defined business rules determine which locations are of interest and how long the tracked resource needs to be in that location to trigger this interaction.

Description 

This notification is sent from a real time location tracking system to convey that a tracked patient has moved to a different location. Locally defined business rules determine which locations are of interest and how long the tracked resource needs to be in that location to trigger this interaction.

Description 

This notification is sent from a real time location tracking system to convey that a tracked healthcare practitioner has moved to a different location. Locally defined business rules determine which locations are of interest and how long the tracked resource needs to be in that location to trigger this interaction.