Some of the default message types OnBase HL7 ships with are as follows:
The following table summarizes message descriptions from the HL7 specification document. These descriptions are provided for general background information only and are not intended as a comprehensive resource for configuration purposes. See the HL7 specification document for more information.
Message |
Description |
---|---|
ADT^A01 |
Admit / Visit notification An A01 event is intended for patients who are going through the admission process, including assigning a patient to a bed. This event marks the beginning of a patient's stay in a healthcare facility. |
ADT^A02 |
Transfer a patient This event indicates that patient is moved from the assigned physical location. |
ADT^A03 |
Discharge/End visit This event marks the end of a patient's stay in a healthcare facility. With this event, the patient's status will be changed to discharged, with the discharge date recorded. With this event, the person is no longer a patient in the healthcare facility. |
ADT^A04 |
Register a Patient This event indicates that a patient is checking in, but will not be assigned to a bed. |
ADT^A05 |
Pre-admit a Patient An A05 event signals patient pre-admission. Data is gathered in preparation for a patient's stay in a healthcare facility. |
ADT^A06 |
Change an Outpatient to an Inpatient An A06 event indicates a patient is being admitted to a healthcare facility after being evaluated in a non-admitted visit and found to be serious enough for admittance. An A06 event changes patient status from non-admitted to admitted. |
ADT^A07 |
Change an Inpatient to an Outpatient An A07 event indicates that an admitted patient has changed his/her status to "no longer admitted" but is still being evaluated for this episode of care in a non-admitted capacity. This event changes patient status from an "admitted" to "non-admitted.” |
ADT^A08 |
Update Patient Information An A08 trigger event indicates that any patient information has changed but no other trigger event has occurred. |
ADT^A11 |
Cancel Admit / Visit Notification For "admitted" patients, an A11 event signals that an A01 event has been canceled for one of two reasons:
For "non-admitted" patients, an A11 event signals that an A04 event has been canceled for one of two reasons:
|
ADT^A18 |
Merge Patient Information Event A18 is being retained for backward compatibility. an A18 event merges current and previous patient identification numbers:
An A18 event indicates the decision to combine the information under the new or old identifier(s). |
ADT^A28 |
Add Person Information An A28 event allows systems to exchange all information that is known about a person. For example, A28 may be used to send a person's demographic information to a system where the person is not yet a patient. |
ADT^A31 |
Update Person Information An A31 event allows for the updating of person information on an MPI. |
ADT^A34 |
Merge Patient Information - Patient ID Only An A34 event is intended for merging or changing patient identifiers. It is used to change patient identifiers on all of a patient's existing accounts. |
ADT^A35 |
Merge Patient Information - Account Number Only An A35 event indicates the decision to merge or change the account number only. |
ADT^A36 |
Merge Patient Information - Patient ID & Account Number An A36 event indicates the decision to merge or change the account number and the patient identification - internal. |
ADT^A38 |
Cancel Pre-admit The A38 event signals that an A05 event has been canceled for one of two reasons:
|
ADT^A40 |
Merge Patient - Internal ID An A40 event is used to signal a merge of records for a patient who was incorrectly filed under two different internal IDs. |
ADT^A41 |
Merge Account - Account Number An A41 event is used to signal a merge of records for an account that was incorrectly filed under two different account numbers. |
BAR |
BAR messages add or change billing account information. |
MDM^T01 |
Original document notification MDM^T01 is a notification of the creation of a document without the accompanying content. |
MDM^T02 |
Original document notification and content MDM^T02 is a notification of the creation of a document with the accompanying content. |
MFN^M02 |
Master File - Staff Practitioner MFN^M02 can be used to transmit staff and practitioner master file information between systems. |
SIU |
SIU messages are used to notify auxiliary applications of modifications in a filler application's schedule, such as new appointments or modifications to existing appointments. |