 ANSI/HL7 V3 RXMDSVNT, R1-2012 HL7 Version 3 Standard: Pharmacy; Medication Dispense and Supply Event, Release 1 3/23/2012 |
Content Last Edited: 2012-03-06T13:34:34
3.2 Application Roles
3.3 Trigger Events
3.4 Refined Message Information Models
3.5 Hierarchical Message Descriptions
3.6 Interactions
This topic covers the issuing of medication to a patient or representative, as well as bulk supplies of medication.
|
||||||||||||
|
For details on the interpretation of this section, see the discussion of application roles and their relationships in the Version 3 Guide.
This is a system which supports a clinician with dispensing authority. This role specifically captures those interactions pertaining to dispense processing.
A system which support receiving medication dispense event notifications.
This a system which supports the sending of a request to another system for the puropse of recording a dispense in the patient record.
This is a system which can record a dispense in the patient record.
|
||||||||||||||||||||||
|
For details on the interpretation of this section, see the discussion of trigger events in the Version 3 Guide.
| Type: | User request |
User attempts to record that a medication dispense has been processed against a prescription (checked for contraindications and packaged for pickup).
| Type: | User request |
The request to record that a medication dispense has been processed (checked for contraindications and packaged for pickup) against a prescription has been refused.
| Type: |
A medication dispense has been processed (checked for contraindications and packaged for pickup).
| Type: | User request |
User requests that a bulk quantity of drugs be dispensed to a location.
| Type: | User request |
A request for a bulk dispense of drug products to a location has been refused.
| Type: |
A bulk quantity of drugs has been dispensed to a location.
| Type: | User request |
A quantity of drug has been processed (checked for contraindications and packaged) and been picked up.
| Type: | User request |
A request to record that a quantity of drug has been processed (checked for contraindications and packaged) and been picked up has been refused (e.g. contraindication, no permission, etc.)
| Type: |
A quantity of drug has been processed (checked for contraindications and packaged) and been picked up.
|
||||||||||||
|
For details on the interpretation of this section, see the description of RMIMs in the Version 3 Guide.
| Parent: | Pharmacy (PORX_DM000000UV) |
Returns the created dispense id as well as the (potentially created) prescription id
| Parent: | Pharmacy (PORX_DM000000UV) |
Records a dispense to a clinic/department with no patient or dose instructions specified
| Parent: | Pharmacy (PORX_DM000000UV) |
Captures information about the time of pickup and potentially who picked up the medication
|
||||||||||||
|
For details on the interpretation of this section, see the description of HMDs in the Version 3 Guide.
Captures information about the time of pickup and potentially who picked up the medication
The dispense pickup message is separate and distinct from the dispense processing message as pharmacy workflow usually supports processing the dispense soon after receiving the order but the pickup can occur over an extended period of time, sometimes many days after the processing. When reviewing a patient's current profile, it is clinically important for a health care provider to know if a dispensed product remains in the pharmacy or if the product is in the hands of the patient.
The core class in the Dispense Pickup Model is the SupplyEvent.
R_Patient identifies the patient for whom the dispense applies.
R_AssignedPerson identifies the individual who physically received the dispense, if other than the patient.
Further breakdown of the model attributes are listed in the attributes table.
Returns the created dispense id as well as the (potentially created) prescription id.
This message model represents data and associations involved in responding to a request to record a dispense in a repository.
Some system architectures are constructed as a request - response pairing. The response can be a refuse to record e.g. a significant drug interaction or an acceptance of a request to record. In the request - response architecture, a Point-of-service System assembles a draft dispense record which it asks the repository to record.
It may fall to the repository to assign a dispense identifier once it accepts the record. This message supports sending that dispense identifier to the initiating Point-of-Service system. Alternately it could mirror back an identifier assigned by the dispensing Point-of-Service system. In addition, a dispense based on a paper prescription may result in a repository creating an electronic inferred prescription. This message provides a mechanism to provide that order identifier to the originating Point-of-Service system.
The core classes in the Dispense Response Model are the: * Supply Event and the * Combined Medication Request.
The SupplyEvent carries the dispense identifier.
The CombinedMedicationRequest identifies the prescription order number that the dispense fulfills.
Further breakdown of the model attributes are listed in the attributes table.
Records a dispense to a clinic/department with no patient or dose instructions specified
This message model represents data and associations involved in recording the provision of a bulk supply of medication to an assigned entity e.g. a physician's office. It is not intended to record medication supplied to a specified patient and as such does not support administration instructions. The office supply includes content/concepts related to the supply, the product and the individual that requested the supply.
Information recorded by this message would most often be used by a regulatory authority to monitor the medications being supplied to an individual or an office, designated for office use. The information would be retrieved by the regulatory authority or the repository manager using a non-HL7 data base query.
The core classes in the Office Supply Model are the: * Supply Event and * Supply Request.
The SupplyEvent is the office supply entry point. Associated with the SupplyEvent are acts and participations capturing the parties involved in the supply of a medication, the product supplied, who received the medication and who requested it.
The SupplyRequest identifies who requested the medication as an office supply.
R_AdministerableMedication identifies the product being supplied to the office.
A_Annotation records observations or other notations related to the office supply record.
R_ServiceDeliveryLocation identifies the origin of the supplied product if other than the recording location, as well as where the product is being delivered to.
R_AssignedEntity identifies who made and is responsible for the order, as well as the entity that received the office supply.
Further breakdown of the model attributes are listed in the attributes table.
Use to record a medication dispense.
This message model represents data and associations involved in recording in the patient record that the medication dispense processing (drug preparation, packaging and contraindication checking) for a particular quantity of medication against a prescription has been performed and the medication is awaiting pickup. The dispense process includes content/concepts related to the dispensing (supply) and administration of prescribed items and may include information related to the order.
The medication dispense processing message is separate and distinct from the pickup as pharmacy workflow usually supports processing the dispense soon after receiving the order but the pickup can occur over an extended period of time, sometimes many days after the processing. When reviewing a patient's current profile, it is clinically important for a health care provider to know if a dispensed product remains in the pharmacy or if the product is in the hands of the patient.
The core classes in the Medication Dispense Model are the: * Combined Medication Dispense * Supply Event * Substance Administration Request.
The CombinedMedicationDispense is the medication dispense entry point. Associated with the CombinedMedicationDispense are acts and participations capturing the parties involved in the dispensing of a medication, the recipient of the medication, any substitutions made, information on the medication supplied and other dispense related parameters.
The SupplyEvent is a component of the medication dispense and provides details concerning the dispensing of the medication. Dispensing parameters include time parameters associated with the dispense function, the quantity dispensed, the number of refills, who received the dispensed medication, where the medication was dispensed to, and other related parameters. The dispensed medication is a direct target of the SupplyEvent.
The SubstanceAdministrationRequest is a component of the CombinedMedicationDispense providing information on how, when, where, how much and under what conditions the medication should be administered.
CombinedMedicationDispense related entities review the order in relation to the patient and undertake the dispense process.
A_Supporting Clinical Information provides additional information relevant to the order.
A_Annotation records observations or other notations related to the dispense record.
A_MedicationOrder allows information concerning the original order to be included with the dispense record e.g. the order author. This is only relevant when the dispense is not a result of an electronic order e.g. the order is in a paper format.
The WorkingList is used to group like orders together e.g. acute, PRN
SubstitutionMade describes any substitution made to the original order, why it was made, and who was responsible for the decision to substitute.
Further breakdown of the model attributes are listed in the attributes table.
|
||||||||||||||||||||||||||||
|
For details on the interpretation of this section, see the definition of Interactions in the Version 3 Guide.
Indicates that dispense processing (drug preparation, packaging and contraindication checking) has been performed for a particular quantity of medication against a medication prescription and the dispensed medication is awaiting pickup.
| Trigger Event | Med dispense processed | PORX_TE020190UV01 |
| Transmission Wrapper | Send Message Payload | MCCI_MT000100UV01 |
| Control Act Wrapper | Trigger Event Control Act | MCAI_MT700201UV01 |
| Message Type | Medication Dispense | PORX_MT020070UV01 |
| Sender | Medication Dispensing System | PORX_AR890010UV01 |
| Receiver | Medication Dispense Event Tracker | PORX_AR990420UV01 |
| Trigger Event | Request to record med dispense prep | PORX_TE020220UV01 |
| Transmission Wrapper | Send Message Payload | MCCI_MT000100UV01 |
| Control Act Wrapper | Trigger Event Control Act | MCAI_MT700201UV01 |
| Message Type | Medication Dispense | PORX_MT020070UV01 |
| Reason | Trigger Event | Interaction |
| Medication dispense processed and recorded n the patient record. | PORX_TE020190UV01 | PORX_IN020130UV01 |
| PORX_IN020140UV01 | ||
| The request to record dispense information on the patient record has been refused | PORX_IN020190UV01 |
| Sender | Medication Dispense Recorder Request | PORX_AR890020UV01 |
| Receiver | Medication Dispense Recorder Fulfiller | PORX_AR890030UV01 |
Indicates that the requested medication dispense processing information has been successfully recorded in the patient's record.
| Trigger Event | Med dispense processed | PORX_TE020190UV01 |
| Transmission Wrapper | Application Level Acknowledgement | MCCI_MT000300UV01 |
| Control Act Wrapper | Trigger Event Control Act | MCAI_MT700201UV01 |
| Message Type | Dispense Response | PORX_MT020030UV01 |
| Reason | Trigger Event | Interaction |
| PORX_TE020190UV01 | PORX_IN020130UV01 |
| Sender | Medication Dispense Recorder Fulfiller | PORX_AR890030UV01 |
| Receiver | Medication Dispense Recorder Request | PORX_AR890020UV01 |
The request to record dispense information on the patient record has been refused.
| Trigger Event | Decision to reject med dispense prep request | PORX_TE020270UV01 |
| Transmission Wrapper | Application Level Acknowledgement | MCCI_MT000300UV01 |
| Control Act Wrapper | Trigger Event Control Act | MCAI_MT700201UV01 |
| Reason | Trigger Event | Interaction |
| Sender | Medication Dispense Recorder Fulfiller | PORX_AR890030UV01 |
| Receiver | Medication Dispense Recorder Request | PORX_AR890020UV01 |
Indicates that a particular quantity of medication has been dispensed against a medication prescription and picked up by the patient. The prescription may or may not have been previously recorded. Pickup and preparation time are not distinguished.
| Trigger Event | Med dispensed and picked up | PORX_TE020210UV01 |
| Transmission Wrapper | Send Message Payload | MCCI_MT000100UV01 |
| Control Act Wrapper | Trigger Event Control Act | MCAI_MT700201UV01 |
| Message Type | Medication Dispense | PORX_MT020070UV01 |
| Sender | Medication Dispensing System | PORX_AR890010UV01 |
| Receiver | Medication Dispense Event Tracker | PORX_AR990420UV01 |
Indicates that a quantity of medication has been issued without accompanying administration instructions. This is generally used for bulk-supply or ward-stock dispenses.
| Trigger Event | Bulk supply of medication | PORX_TE020010UV01 |
| Transmission Wrapper | Send Message Payload | MCCI_MT000100UV01 |
| Control Act Wrapper | Trigger Event Control Act | MCAI_MT700201UV01 |
| Message Type | Office Supply | PORX_MT020050UV01 |
| Sender | Medication Dispensing System | PORX_AR890010UV01 |
| Receiver | Medication Dispense Event Tracker | PORX_AR990420UV01 |
Requests that the dispensing of a particular quantity of medication against a medication prescription and the associated pickup be recorded in the patient's record. Pickup and preparation time are not distinguished.
| Trigger Event | Request to record med dispense | PORX_TE020230UV01 |
| Transmission Wrapper | Send Message Payload | MCCI_MT000100UV01 |
| Control Act Wrapper | Trigger Event Control Act | MCAI_MT700201UV01 |
| Message Type | Medication Dispense | PORX_MT020070UV01 |
| Reason | Trigger Event | Interaction |
| To indicate that a rquest to record dispense information in a patient record has been refused. | PORX_IN020171UV01 | |
| To indicate that a reuest to record dispense information in a patient record has been completed. | PORX_IN020173UV01 |
| Sender | Medication Dispense Recorder Request | PORX_AR890020UV01 |
| Receiver | Medication Dispense Recorder Fulfiller | PORX_AR890030UV01 |
Requests that a bulk supply of a medication to a facility be recorded.
| Trigger Event | Request to record bulk supply of medication | PORX_TE020130UV01 |
| Transmission Wrapper | Send Message Payload | MCCI_MT000100UV01 |
| Control Act Wrapper | Trigger Event Control Act | MCAI_MT700201UV01 |
| Message Type | Office Supply | PORX_MT020050UV01 |
| Reason | Trigger Event | Interaction |
| A request to record a bulk supply has been refused. | PORX_IN020210UV01 | |
| A bulk supply of a medication to a facility has been recorded. | PORX_IN020210UV01 | |
| Bulk supply of medication | PORX_TE020010UV01 | PORX_IN020220UV01 |
| Sender | Medication Dispense Recorder Request | PORX_AR890020UV01 |
| Receiver | Medication Dispense Recorder Fulfiller | PORX_AR890030UV01 |
The request to record a medication dispense in the patient record as been accepted.
| Trigger Event | Request to record med dispense | PORX_TE020230UV01 |
| Transmission Wrapper | Send Message Payload | MCCI_MT000100UV01 |
| Control Act Wrapper | Trigger Event Control Act | MCAI_MT700201UV01 |
| Message Type | Medication Dispense | PORX_MT020070UV01 |
Indicates the requested bulk supply of a medication to a facility has been recorded.
| Trigger Event | Bulk supply of medication | PORX_TE020010UV01 |
| Transmission Wrapper | Send Message Payload | MCCI_MT000100UV01 |
| Control Act Wrapper | Trigger Event Control Act | MCAI_MT700201UV01 |
| Message Type | Dispense Response | PORX_MT020030UV01 |
| Sender | Medication Dispense Recorder Fulfiller | PORX_AR890030UV01 |
| Receiver | Medication Dispense Recorder Request | PORX_AR890020UV01 |
The request to record a medication dispense in the patient record has been refused.
| Trigger Event | Decision to reject med dispense record | PORX_TE020240UV01 |
| Transmission Wrapper | Send Message Payload | MCCI_MT000100UV01 |
| Control Act Wrapper | Trigger Event Control Act | MCAI_MT700201UV01 |
| Message Type | Medication Dispense | PORX_MT020070UV01 |
Indicates that the request to record a bulk supply of a medication to a facility has been refused.
| Trigger Event | Request to record bulk supply of medication | PORX_TE020130UV01 |
| Transmission Wrapper | Send Message Payload | MCCI_MT000100UV01 |
| Control Act Wrapper | Trigger Event Control Act | MCAI_MT700201UV01 |
| Reason | Trigger Event | Interaction |
| Sender | Medication Dispense Recorder Fulfiller | PORX_AR890030UV01 |
| Receiver | Medication Dispense Recorder Request | PORX_AR890020UV01 |
| Return to top of page |