 HL7 V3 RXMSSEVNT, R1-2013 (Retired 2022) HL7 Version 3 Standard: Medication Statement and Administration Event, Release 1 Retired 11/18/2022 |
Content Last Edited: 2014-01-23T09:06:58
4.2 Storyboards
4.3 Application Roles
4.4 Trigger Events
4.5 Refined Message Information Models
4.6 Hierarchical Message Descriptions
4.7 Interactions
Medication Administration and Statement Topic
This topic provides interactions for exchanging information about medication use for individual patients. The interaction exchanges can be internal to systems within a single healthcare institution or healthcare enterprise, or across systems within a community setting, or some other mix of systems that crosses any of these boundaries. The specific types of interactions will include notification, request/response and query/response interactions. The content in this topic includes information about medication use constructed from:
Example sources of information:
- patient self reporting
- patient narratives gathered by health care professionals (physicians, pharmacists, nurses, etc.)
- institutional medication administration records
- an existing medication record (list) in an EHR system
- insurance (claims) records
Medication statements and administrations may include information about medication use where the medications have been prescribed or not prescribed.
Medication statements and administrations may include "negative" statements such as - the patient has not taken medication ABC, or the patient has not been administered medication XYZ at 10:00 AM on Oct 3, 2010.
The business process being modelled is this topic is only concerned with stating information about medication use; it does NOT cover any processes of medication order fulfillment or medication allergy documentation or clinical decision support.
Definitions
Medication List - A list of medications and associated information, pertaining to a specific patient, constructed for a specific purpose. There is more than one type of medication list, but for this documents purpose we will focus on medication lists as described below:
- A list of patient reported current medications. This list may include prescribed and over the counter medications the patient is currently taking.
- Discharge Medications list - the list of medications the patient will be taking after discharge from a healthcare institution.
- Admission Medication list - the list of medications the patient is using just before admission to a healthcare institution.
- The Medication Administration Record list - this is a list of all medications the patient has been administered during a specified period of time, which may be the duration of an in-patient stay. The record may also include details about dose, route, time of administration and who administered the medication.
- The list of medications as reported by a patient or significant other that a health care professional has documented during a patient history session or a patient profile session.
Medication History - A patient's medication history can be broadly defined as an organization of historical medication information. Medication History can also be presented as a list of medication prescriptions, and/or dispenses, and/or medication statements, and/or medication administrations. In this topic we are modeling the medication statements and the medication administrations.
|
||||||||
|
For details on the interpretation of this section, see the storyboard discussion in the Version 3 Guide.
The patterns of behavior for Medication Administration are very similar to those for Medication Statement and much of what follows is a repetition of that material changing Statement to Administration and providing new artefact IDs. The one difference is that Medication Administrations have a "complete" interaction. This is used when an administration (such as an infusion) runs for a significant period of time and has various starts and stops before it is entirely finished. The starts and stops can be dealt with by child administrations, but there is a need to mark the overall process as complete.
During a round at the cardiology ward, a patient is handed his scheduled medication by the attending nurse. This includes a tablet of 100mg Atenolol and 20 ml of Docusate Sodium in a unit-dose cup. Additionally, the patient gets an intramuscular injection of 10 ml of meperidine, with a strength of 5 mg/ml. For this last medication order, there is a protocol that requires the nurse to check the potassium level before administering. She checks the latest lab result for potassium, and notices that the value is outside the reference range. After consulting the resident doctor, it is decided to wait one hour and then still administer the injection. This results in the first two administrations being recorded in the nursing module of the hospital EHR system, with the nurse as the performer and the current time stamp. The third administration is rescheduled for an hour later, after which is also gets recorded [note that it can be recorded before, but it must be distingishable from an actual event].
These administration events are then sent as a notification to the prescribing system in which the original order originated (and/or any other systems that track administrations) (PORX_IN040110UV).
A patient arrives at the emergency room via ambulance. In the ambulance, an injection of meperidine was given to relieve the pain from several fractures. In the emergency room, another pain medication is injected, but also the patient receives an injection of 20 ml of metoprolol to help stabilize the heart rhythm. Both the administrations performed in the ambulance and the one from the ER are recorded in the ER system (being part of the overall hospital EHR system), each with the appropriate performer and (approximate) time stamp. PORX_IN040110UV
If at some later point, an interested system (that has the proper authorization) wants to know about the administrations for this patient, it issues a query (PORX_IN040150UV) which results in a query response that has all relevant administration events (depending on query parameters) (PORX_IN040152UV).
A patient has agreed to record each individual injection of Insulin (as part of ongoing treatment for diabetes type 1) in his PHR (Personal Health Record), which is accessed via a web portal. With each record that is entered, the patient includes the dose, the (approximate) time, and any special observations about the administration event.
These administration events are sent as a notification to any systems that track them (PORX_IN040110UV).
During a round at the cardiology ward, a patient is handed his scheduled medication by the attending nurse. This includes a tablet of 100mg metoprolol, which the patient refuses to take because it caused severe headaches the day before. After consulting the resident doctor, it is decided to skip this administration and see how the patient's condition develops. This results in a 'refused administration' being recorded in the nursing module of the hospital EHR system which includes the reason why the administration could not be performed. This refused administration is then sent as a notification to the prescribing system in which the original order originated (and/or any other systems that track administrations) (PORX_IN040110UV).
Adam Everyman is sent to the XRay department for a procedure while admitted to hospital. The nurse administered the patients morning dose of Amoxicillin 500mg capsules. The procedure was expected to take one hour however due to delays, the patient was not back on the ward in time for the mid-day dose.
The nurse records a 'missed administration' in the nursing module of the hospital medication administration record which includes the reason why the administration could not be performed. This missed administration is then sent as a notification to the prescribing system in which the original order originated (and/or any other systems that track administrations) (PORX_IN040110UV).
Adam Everyman has been admitted to hospital for a hip replacement. Dr. Patrick Pump orders that Adam's warfarin medication be held 1 day prior to his surgery.
The nurse records a 'held administration' in the nursing module of the hospital medication administration record which includes the reason why the administration could not be performed. This held administration is then sent as a notification to the prescribing system in which the original order originated (and/or any other systems that track administrations) (PORX_IN040110UV).
Medication Statements can be Created, Updated, Nullified and Queried. The following diagrams illustrate the content of each of the interactions and the subsequent narratives provide concrete examples that are tied back to specific interactions. The drawings illustrate a Simple Architecture in the upper section, and a more complex Hub Architecture (this is the pattern used in Canada) in the lower drawing. The principle difference between the architectures lies in the ownership of the data. In the Simple Architecture the data is owned by the originator of the data and they are allowed to do as they wish with the data. In contrast in the Hub Architecture the data is owned by the centre and records can only be added to this, updated, nullified etc if the Hub agrees.
The exception to this are the Query interactions - even in a Hub Architecture there is no need to seek permission to raise a query.
Adam Everyman has been to visit his local after hours clinic in the hospital and was given a supply of Maxalt, a new anti-migraine medication. His headaches have subsided. When he visits Dr. Fay Family, his family physician for his next appointment, Dr Family inquires if he has any changes to his current medication list, including any over the counter medications.
Adam tells Dr. Family of his visit to the hospital clinic and of receiving and taking the Maxalt. Adam tells Dr Family that he got quick relief from the medication and that he still has three tablets remaining. With Adams permission, Dr Family adds the Maxalt to Adam's current medication list (PORX_IN040010UV). Dr Family resolves any questions about the safety and long term use of the Maxalt with Adam.
Dr. Family then proceeds to examine Adam for his current concern of elevated blood pressure.
Adam Everyman, a senior retired citizen, is being admitted to the Blue Cross Hospital for operation on his prostate gland. As a standard procedure he is being interviewed on his medication usage. Adam has taken his daughter Dorothy along because his memory is not what it used to be. They are interviewed by the hospital pharmacist. Adam brought his pill box along to show them to the pharmacist. Beside the atenolol for his hypertension, Adam also uses Aspirin/ASA as a blood thinner. These medication are prescribed by his general practitioner. He also uses a mysterious ginseng product from the Chinese herbal drugstore to enhance his memory and an ointment for his eczema rash in his neck. This ointment was prescribed during his holiday in Egypt and works remarkably well for Adam. Dorothy explains to the pharmacist the reason, the origin and the frequency of the usage of the medication.
The pharmacist registers this information in the main EHR system of the Blue Cross Hospital and sends a copy of this information with the medication statement message to their separate institutional pharmacy system. (PORX_IN040010UV) in both cases.
Lucy Lindman has thrombosis. Her blood is examined every week by the blood lab and the lab sends in the results to thrombosis health service. The dosage of her blood thinner is adjusted according to the results of the coagulation factor tests. These instructions are sent to Lucy on her PHR. Lucy registers her daily dosage through her patient portal. Lucy also suffers from a migraine and uses aspirin to relieve the headache. She also registers the usage of this OTC medication, which she obtained from the neighbourhood drugstore. Her PHR system sends a daily message using a medication statement message to the EHR system of her GP. (PORX_IN040010UV)
In order to keep his records up-to-date, the GP (General Physician) of Adam Everyman pulls up a list of all known, active prescriptions and any associated dispenses (if present) for Mr. Everyman (these might be obtained from a central repository or via some form of transparent access to distributed sources). She then reviews that list with Mr. Everyman, to check his compliance with the prescriptions. In some cases, the screen will show that the prescribed medication was never picked up from a pharmacy, in others (where a dispense did occur) Mr. Everyman might confirm that he's using the medication as prescribed, but he might also state that he never started using the medication at all, or that he did, but stopped early, or that he used it with a different (possibly variable) dosage. For each of the prescribed medications, a medication statement is then recorded to capture the actual use of the medication (including the cases where there was no use). Depending on the architecture, this might lead to three different exchange methods:
- A notification is sent to any systems that are tracking medication statements. (PORX_IN040010UV)
- A request to record is sent to a central repository (PORX_IN040020UV), and then accepted (PORX_IN040033UV) or refused (PORX_IN040040UV).
- The medication statements are stored in the local database until a query comes in (PORX_IN040050UV), after which the relevant statements are returned as the query response (PORX_IN040052UV).
|
||||||||||||||||
|
For details on the interpretation of this section, see the discussion of application roles and their relationships in the Version 3 Guide.
A system that manages the access to the repository
A system that manages the access to the repository
This is a general clinical repository. In the context of this domain, the requirement for a shared repository of other medications to support EHRs reflects the core use case.
This is a general clinical repository. In the context of this domain, the requirement for a shared repository of other medications to support EHRs reflects the core use case.
This is a system which supports a clinician in recording or updating medication administrations. Would normally be part of an EHR or PHR or other clinical information system.
This is a system which supports a clinician in recording or updating medication statements.
Would normally be part of an EHR or PHR or other clinical information system.
|
||||||||||||||||||||||||||||||||||||||||||||||||||
|
For details on the interpretation of this section, see the discussion of trigger events in the Version 3 Guide.
| Type: | User request |
User asks central repository to record the completion of a Medication Administration
| Type: | User request |
User attempts to nullify a previously recorded Medication Administration record.
| Type: | User request |
User attempts to nullify a previously recorded Medication Statement record.
| Type: | User request |
User attempts to record a medication administration
| Type: | User request |
User attempts to record a medication statement
| Type: | User request |
User attempts to update a previously recorded Medication Administration record.
| Type: | User request |
User attempts to update a previously recorded Medication Statement record.
| Type: |
A request that the central repository mark a Medication Administration as complete is rejected. For example, due to an incomplete record or unrecognized id etc.)
| Type: |
An existing medication administration record has been nullified.
| Type: |
An existing medication statement record has been nullified.
| Type: |
A request to nullify an existing medication administration record has been refused. For example, no permission, record not found, etc.
| Type: |
A request to nullify an existing medication statement record has been refused. For example, no permission, record not found, etc.
| Type: | Interaction based |
Acknowledgement that a Medication Statement has been recorded.
| Type: |
Acknowledgement that a Medication Statement has been recorded.
| Type: | Interaction based |
A request to record a Medication Administration has been refused. For example, no permission, contraindications, etc.
| Type: |
Notify that a medication administratio n is now complete.
| Type: | Interaction based |
A request to record a Medication Statement has been refused. For example, no permission, contraindications, etc.
| Type: |
An existing medication administration record has been updated.
| Type: |
An existing medication statement record has been updated.
| Type: | Interaction based |
A request to update an existing medication administration record has been refused. For example, no permission, record not found, etc.
| Type: | Interaction based |
A request to update an existing medication statement record has been refused. For example, no permission, record not found, etc.
| Type: | User request |
User queries the Medications Administration Repository for specific information
| Type: | User request |
User queries the Medication Statement Repository for specific information
|
||||||||||
|
For details on the interpretation of this section, see the description of RMIMs in the Version 3 Guide.
| Parent: | Pharmacy (PORX_DM000000UV) |
This model is used to query for both medication statements and administrations, depending on the interaction that it is used in. It can be used to return a specific statement or administration as well as to search for a set of statements/administrations, depending on the query parameters that are used.
| Substance Administration Event Query | PORX_HD040030UV01 |
| Parent: | Pharmacy (PORX_DM000000UV) |
The main use of this structure is to communicate the administration of a medicine to a patient at a point in time or over a period of time. The main class is therefore the Substance Administration Event, whose attributes can describe all the key details of the administration, including the method, route and site of the administration, the dose quantity administered and the timing of the administration. This Substance Administration Event may itself be a part of a series of Substance Administration Events, which can be linked together using the Component relationship.
The medicine administered is described using the consumable participation to the R_ProductListed CMET.
The Patient is described using the subject participation; and any entry in their record using the recordTarget participation.
Various persons (parties) involved in the administration process can be described using the appropriate participations: author for the person authoring the administration information, performer for the person giving the medicine; both of these may be supervised by a responsible party. The record keeping process is also supported, with the dataEnterer and verifier participations. These persons may be variously the patient, a relation (R_RelatedParty) or a healthcare professional (R_AssignedEntity).
The location in which the administration(s) took place can be described if required using the location participation and the R_ServiceDeliveryLocation CMET.
Various activities related to the administration(s) can also be described; these include the usual activities of the medication process: prescribing (Prescription) and dispensing (DispenseEvent) the medicine administered, including any decision support information (A_DetectedMedicationIssue) or medicine substitution that took place (SubstitutionEvent), the healthcare consultation or admission that the administration was part of (EncounterEvent) and any additional information can be described using two generic constructs ObservationEvent and A_Annotation.
| Medication Administration | PORX_HD040020UV01 |
| Parent: | Pharmacy (PORX_DM000000UV) |
The main use of this structure is to communicate the statement (report) that a medicine has been administered to a patient at a point in time or over a period of time. The main class is therefore the Substance Administration Event, whose attributes can describe all the key details of the administration, including the method, route and site of the administration, the dose quantity administered and the timing of the administration. Any uncertainty about the veracity of the administration can be described using the uncertaintyCode.
The medicine administered is described using the consumable participation to the R_ProductUseExact CMET.
The Patient that the statement is about is described using the subject participation; and any entry in their record (EHR, PMR etc.) using the recordTarget participation.
Various persons (parties) involved in the making the medication statement process can be described using the appropriate participations: author for the person authoring the medication statement, dataEnterer and verifier for the persons involved in the record keeping process, and informant for the person providing the information with which to make the medication statement. Any of these may be supervised by a responsible party. These persons may be variously the patient, a relation (R_RelatedParty) or a healthcare professional (R_AssignedEntity).
The key activities related to the medication statement can also be described; these are the activities of the medication process: the prescribing that initiated the process (Prescription) and the dispensing (DispenseEvent) of the medicine. The healthcare consultation or admission that relates to the medication statement can be referenced using EncounterEvent and any additional information can be described using the generic construct A_Annotation.
| Medication Statement | PORX_HD040010UV01 |
|
||||||||||
|
For details on the interpretation of this section, see the description of HMDs in the Version 3 Guide.
This model is used to query for both medication statements and administrations, depending on the interaction that it is used in. It can be used to return a specific statement or administration as well as to search for a set of statements/administrations, depending on the query parameters that are used.
| Medication Statement Query | PORX_MT040030UV01 |  |
The main use of this structure is to communicate the administration of a medicine to a patient at a point in time or over a period of time. The main class is therefore the Substance Administration Event, whose attributes can describe all the key details of the administration, including the method, route and site of the administration, the dose quantity administered and the timing of the administration. This Substance Administration Event may itself be a part of a series of Substance Administration Events, which can be linked together using the Component relationship.
The medicine administered is described using the consumable participation to the R_ProductListed CMET.
The Patient is described using the subject participation; and any entry in their record using the recordTarget participation.
Various persons (parties) involved in the administration process can be described using the appropriate participations: author for the person authoring the administration information, performer for the person giving the medicine; both of these may be supervised by a responsible party. The record keeping process is also supported, with the dataEnterer and verifier participations. These persons may be variously the patient, a relation (R_RelatedParty) or a healthcare professional (R_AssignedEntity).
The location in which the administration(s) took place can be described if required using the location participation and the R_ServiceDeliveryLocation CMET.
Various activities related to the administration(s) can also be described; these include the usual activities of the medication process: prescribing (Prescription) and dispensing (DispenseEvent) the medicine administered or not administered, including any decision support information (A_DetectedMedicationIssue) or medicine substitution that took place (SubstitutionEvent), the healthcare consultation or admission that the administration was part of (EncounterEvent) and any additional information can be described using two generic constructs ObservationEvent and A_Annotation.
| R_PatientUniversal | COCT_MT050000UV02 |
| R_PatientPersonContact | COCT_MT050203UV07 |
| R_AssignedEntityContact | COCT_MT090003UV01 |
| R_ServiceDeliveryLocationContact | COCT_MT240003UV02 |
| A_DetectedMedicationIssueUniversal | COCT_MT260003UV01 |
| A_AnnotationUniversal | COCT_MT590000UV |
| R_RelatedPartyUniversal | COCT_MT910000UV |
| R_ProductListedUniversal | POCP_MT010100UV |
| Medication Administration Record Notification | PORX_MT040020UV01 | |
The main use of this structure is to communicate the statement (report) that a medicine has been administered to a patient at a point in time or over a period of time. The main class is therefore the Substance Administration Event, whose attributes can describe all the key details of the administration, including the method, route and site of the administration, the dose quantity administered and the timing of the administration. Any uncertainty about the veracity of the administration can be described using the uncertaintyCode.
The medicine administered is described using the consumable participation to the R_ProductUseExact CMET.
The Patient that the statement is about is described using the subject participation; and any entry in their record (EHR, PMR etc.) using the recordTarget participation.
Various persons (parties) involved in the making the medication statement process can be described using the appropriate participations: author for the person authoring the medication statement, dataEnterer and verifier for the persons involved in the record keeping process, and informant for the person providing the information with which to make the medication statement. Any of these may be supervised by a responsible party. These persons may be variously the patient, a relation (R_RelatedParty) or a healthcare professional (R_AssignedEntity).
The key activities related to the medication statement can also be described; these are the activities of the medication process: the prescribing that initiated the process (Prescription) and the dispensing (DispenseEvent) of the medicine. The healthcare consultation or admission that relates to the medication statement can be referenced using EncounterEvent and any additional information can be described using the generic construct A_Annotation.
| R_PatientUniversal | COCT_MT050000UV02 |
| R_PatientPersonContact | COCT_MT050203UV07 |
| R_AssignedPersonContact | COCT_MT090103UV01 |
| A_AnnotationUniversal | COCT_MT590000UV |
| R_RelatedPartyUniversal | COCT_MT910000UV |
| R_ProductUseExactUniversal | POCP_MT010600UV |
| Record Other Medication | PORX_MT040010UV01 | |
|
||||||||||||||||||||||||||||||||||||||||||
|
For details on the interpretation of this section, see the definition of Interactions in the Version 3 Guide.
Sender requests that the central repository adds the supplied record to the repository.
| Trigger Event | Request to Record a Medication Administration | PORX_TE040160UV02 |
| Transmission Wrapper | Send Message Payload | MCCI_MT000100UV01 |
| Control Act Wrapper | Trigger Event Control Act | MCAI_MT700201UV01 |
| Message Type | Medication Administration Record Notification | PORX_MT040020UV01 |
| Reason | Trigger Event | Interaction |
| Tell the requester that the request to add the record has been rejected. | PORX_TE040110UV02 | PORX_IN040140UV02 |
| Sender | Medication Administration Recorder | PORX_AR991410UV02 |
| Receiver | Medication Administration Record Request Fulfiller | PORX_AR991408UV02 |
Query repository for Medication Administration(s) that match a given set of parameters
| Trigger Event | Medication Administration Query Request | PORX_TE040150UV02 |
| Transmission Wrapper | Send Message Payload | MCCI_MT000100UV01 |
| Control Act Wrapper | Query Control Act Request : Query By Parameter | QUQI_MT021001UV01 |
| Message Type | Medication Statement Query | PORX_MT040030UV01 |
| Reason | Trigger Event | Interaction |
| Send the details of a Medication Administration to the originator of the query. | PORX_TE040130UV02 | PORX_IN040110UV02 |
| Sender | Medication Administration Record Request Fulfiller | PORX_AR991408UV02 |
| Receiver | Medication Administration Recorder | PORX_AR991410UV02 |
Send repository an update Medication Administration record with a request to apply this update to the copy held in the repository.
| Trigger Event | Request to Update a Medication Administration | PORX_TE040170UV02 |
| Transmission Wrapper | Send Message Payload | MCCI_MT000100UV01 |
| Control Act Wrapper | Trigger Event Control Act | MCAI_MT700201UV01 |
| Message Type | Medication Administration Record Notification | PORX_MT040020UV01 |
| Reason | Trigger Event | Interaction |
| Tell the requester that the record could not be updated as requested | PORX_TE040120UV02 | PORX_IN040180UV02 |
| Sender | Medication Administration Recorder | PORX_AR991410UV02 |
| Receiver | Medication Administration Record Request Fulfiller | PORX_AR991408UV02 |
Requests that a medication be recorded against the patient's record.
| Trigger Event | Request to Record a Medication Statement | PORX_TE040060UV02 |
| Transmission Wrapper | Send Message Payload | MCCI_MT000100UV01 |
| Control Act Wrapper | Trigger Event Control Act | MCAI_MT700201UV01 |
| Message Type | Record Other Medication | PORX_MT040010UV01 |
| Reason | Trigger Event | Interaction |
| Medication Statement could not be recorded - tell requesting system. | PORX_TE040010UV02 | PORX_IN040040UV02 |
| Sender | Medication Statement Recorder | PORX_AR990410UV02 |
| Receiver | Medication Statement Record Request Fulfiller | PORX_AR990408UV02 |
Query for Medication Statements
| Trigger Event | Medication Statement Query Request | PORX_TE040050UV02 |
| Transmission Wrapper | Send Message Payload | MCCI_MT000100UV01 |
| Control Act Wrapper | Query Control Act Request : Query By Parameter | QUQI_MT021001UV01 |
| Message Type | Medication Statement Query | PORX_MT040030UV01 |
| Reason | Trigger Event | Interaction |
| Returning the set of medication statements that were requested. | PORX_TE040050UV02 | PORX_IN040052UV02 |
| Sender | Medication Statement Tracker | PORX_AR990406UV02 |
| Receiver | Medication Statement Recorder | PORX_AR990410UV02 |
Send central repository details of an update and request that those details be applied to the specified record.
| Trigger Event | Request to Update a Medication Statement | PORX_TE040070UV02 |
| Transmission Wrapper | Send Message Payload | MCCI_MT000100UV01 |
| Control Act Wrapper | Trigger Event Control Act | MCAI_MT700201UV01 |
| Message Type | Record Other Medication | PORX_MT040010UV01 |
| Reason | Trigger Event | Interaction |
| Statement can't be recorded | PORX_TE040020UV02 | PORX_IN040080UV02 |
| Sender | Medication Statement Recorder | PORX_AR990410UV02 |
| Receiver | Medication Administration Record Request Fulfiller | PORX_AR991408UV02 |
Someone wishes to record administration of a medication
| Trigger Event | Medication Administration has been Recorded | PORX_TE040130UV02 |
| Transmission Wrapper | Send Message Payload | MCCI_MT000100UV01 |
| Control Act Wrapper | Trigger Event Control Act | MCAI_MT700201UV01 |
| Message Type | Medication Administration Record Notification | PORX_MT040020UV01 |
| Sender | Medication Administration Recorder | PORX_AR991410UV02 |
| Receiver | Medication Administration Tracker | PORX_AR991406UV02 |
Send a notification that a Medication Administration record has been updated.
| Trigger Event | Medication Administration Updated | PORX_TE040140UV02 |
| Transmission Wrapper | Send Message Payload | MCCI_MT000100UV01 |
| Control Act Wrapper | Trigger Event Control Act | MCAI_MT700201UV01 |
| Message Type | Medication Administration Record Notification | PORX_MT040020UV01 |
| Sender | Medication Administration Recorder | PORX_AR991410UV02 |
| Receiver | Medication Administration Tracker | PORX_AR991406UV02 |
Indicates that a medication has been recorded against the patient's record.
| Trigger Event | Medication Statement has been Recorded | PORX_TE040030UV02 |
| Transmission Wrapper | Send Message Payload | MCCI_MT000100UV01 |
| Control Act Wrapper | Trigger Event Control Act | MCAI_MT700201UV01 |
| Message Type | Record Other Medication | PORX_MT040010UV01 |
| Sender | Medication Statement Recorder | PORX_AR990410UV02 |
| Receiver | Medication Statement Tracker | PORX_AR990406UV02 |
Send a notification that a Medication Statement has been updated.
| Trigger Event | Medication Statement Updated | PORX_TE040040UV02 |
| Transmission Wrapper | Send Message Payload | MCCI_MT000100UV01 |
| Control Act Wrapper | Trigger Event Control Act | MCAI_MT700201UV01 |
| Message Type | Record Other Medication | PORX_MT040010UV01 |
| Sender | Medication Statement Recorder | PORX_AR990410UV02 |
| Receiver | Medication Statement Tracker | PORX_AR990406UV02 |
Provide a list of Medication Administrations that match the parameters specified.
| Trigger Event | Medication Administration has been Recorded | PORX_TE040130UV02 |
| Transmission Wrapper | Send Message Payload | MCCI_MT000100UV01 |
| Control Act Wrapper | Trigger Event Control Act | MCAI_MT700201UV01 |
| Message Type | Medication Administration Record Notification | PORX_MT040020UV01 |
| Sender | Medication Administration Recorder | PORX_AR991410UV02 |
| Receiver | Medication Administration Tracker | PORX_AR991406UV02 |
Provide a list of Medication Statements that match the parameters specified.
| Trigger Event | Medication Statement has been Recorded | PORX_TE040030UV02 |
| Transmission Wrapper | Send Message Payload | MCCI_MT000100UV01 |
| Control Act Wrapper | Trigger Event Control Act | MCAI_MT700201UV01 |
| Message Type | Record Other Medication | PORX_MT040010UV01 |
| Sender | Medication Statement Record Request Fulfiller | PORX_AR990408UV02 |
| Receiver | Medication Statement Tracker | PORX_AR990406UV02 |
Tell the requester that the record could not be placed in the repository
| Trigger Event | Reject Request to Record a Medication Admin | PORX_TE040110UV02 |
| Transmission Wrapper | Application Level Acknowledgement | MCCI_MT000300UV01 |
| Control Act Wrapper | Trigger Event Control Act | MCAI_MT700201UV01 |
| Sender | Medication Administration Record Request Fulfiller | PORX_AR991408UV02 |
| Receiver | Medication Administration Recorder | PORX_AR991410UV02 |
Indicates that the request to nullify the specified medication has been denied.
| Trigger Event | Reject Request to Nullify Medication Admin | PORX_TE040114UV02 |
| Transmission Wrapper | Application Level Acknowledgement | MCCI_MT000300UV01 |
| Control Act Wrapper | Trigger Event Control Act | MCAI_MT700201UV01 |
| Sender | Medication Administration Record Request Fulfiller | PORX_AR991408UV02 |
| Receiver | Medication Administration Recorder | PORX_AR991410UV02 |
Repository tells requester that it cannot mark the record identified as complete
| Trigger Event | Reject Request to Complete a Medication Admin | PORX_TE040115UV02 |
| Transmission Wrapper | Application Level Acknowledgement | MCCI_MT000300UV01 |
| Control Act Wrapper | Trigger Event Control Act | MCAI_MT700201UV01 |
| Sender | Medication Administration Record Request Fulfiller | PORX_AR991408UV02 |
| Receiver | Medication Administration Recorder | PORX_AR991410UV02 |
Tell sender that the update to the Medication Administration record cannot be made.
| Trigger Event | Reject Request to Update a Medication Admin | PORX_TE040120UV02 |
| Transmission Wrapper | Application Level Acknowledgement | MCCI_MT000300UV01 |
| Control Act Wrapper | Trigger Event Control Act | MCAI_MT700201UV01 |
| Sender | Medication Administration Record Request Fulfiller | PORX_AR991408UV02 |
| Receiver | Medication Administration Recorder | PORX_AR991410UV02 |
Indicates that the request to add the medication has been denied.
| Trigger Event | Reject Request to Record Medication Statement | PORX_TE040010UV02 |
| Transmission Wrapper | Accept Acknowledgement | MCCI_MT000200UV01 |
| Control Act Wrapper | Trigger Event Control Act | MCAI_MT700201UV01 |
| Sender | Medication Statement Record Request Fulfiller | PORX_AR990408UV02 |
| Receiver | Medication Statement Recorder | PORX_AR990410UV02 |
Indicates that the request to nullify the medication statement has been denied.
| Trigger Event | Request to Nullify Medication Statement Rejected | PORX_TE040014UV02 |
| Transmission Wrapper | Application Level Acknowledgement | MCCI_MT000300UV01 |
| Control Act Wrapper | Trigger Event Control Act | MCAI_MT700201UV01 |
| Sender | Medication Statement Record Request Fulfiller | PORX_AR990408UV02 |
| Receiver | Medication Statement Recorder | PORX_AR990410UV02 |
Tells the requester that updating of the Medication Statement as requested in not allowed.
| Trigger Event | Reject Request to Update a Medication Statement | PORX_TE040020UV02 |
| Transmission Wrapper | Application Level Acknowledgement | MCCI_MT000300UV01 |
| Control Act Wrapper | Trigger Event Control Act | MCAI_MT700201UV01 |
| Sender | Medication Statement Record Request Fulfiller | PORX_AR990408UV02 |
| Receiver | Medication Statement Recorder | PORX_AR990410UV02 |
| Return to top of page |