The general order message is transmitted using HL7 ORM-O01 message function. It should be noted that there is only one type of ORM message - the ORM - O01 message.

New orders, cancellations, information updates, discontinuation etc. are the trigger events for ORM - O01message. The most extensively used message type in HL7 standard is the ORM message.

Get to know how Corepoint Health enables customer HL7 initiatives.
The order is defined as a “request for service” that is sent between applications, or in few cases within a single application (an application can send orders to itself). The ORM is made of segments and groups of segments, each of which may be required, optional, repeatable, or a combination of these (HL7 cardinality.

The ORM - O01 message with segments and groups of segments will include the following:

Similar to the ADT messages, ORM messages also have a PID segment for patient identification information. Difference is that in ORM message, this segment is only necessary in the case of new orders and only if the new order pertains to a particular patient. Only if both the conditions are met will the PID segment be included in the message.

Another segment that has a unique function in the ORM message is the OBX (Observation) segment in comparison to its use in other message types, such as ORU (Observational Report - Unsolicited) message. In the ORM message, the OBX segment forms the integral part of an optional and repeatable group called Observation group. The OBX segment carries the clinical information that might be required by the recipient system to interpret the observation that is made, rather than just information about observations and results (as in ORU message).

The Immunization Information System (IIS) is a versatile tool to augment and sustain high vaccination coverage. This is done by consolidating vaccination records of children and adults from variety of providers, forecasting the next dose, past due and the next due which will support the reminder and recall of vaccination notices for each individual. It also makes available official vaccination forms and vaccination outreach assessments. This is in line with the national health objective of increasing upto 95% the proportion of children aged <6 years who have data in the fully operational population based IIS. These are catchment area children less than 6 years of age with 2 or more immunization administered according to ACIP recommendations.

The children are entered into the IIS at birth, especially in a population based IIS, this is done through the electronic birth records. The IIS record is initiated by a health provider at the time of child’s first immunization. If the IIS enters the data of all children in a given area and providers report immunization information, it will be able to provide single data source for all community immunization partners. This helps in providing effective immunization strategies like reminder, recall, AFIX and WIC linkage. The same IIS can be used for adult immunization coverage also.

The management of medical records by transmitting new or updated documents or by transmitting important status information and updating records can be easily done using HL7 MDM. Trigger events and messages can be one of the two categories: either they convey the status of the document, or they produce the status of the document and contain the document contents. MDM messages are generated in relation to an order or independently of them.

The HL7 MDM has 11 different trigger events for the MDM message type as a standard. The commonly used MDM message is MDM T02 because it acts like an ORU or Result message. The MDM T-02 message notifies a system of creation of a document and includes the document contents.

An important part of the MDM message is the OBX segment. It contains document contents, because it is used to separate the body contents where headings or other separations may occur. Allthe MDM message will have the same structure except the OBX segment. When the message type contains document content then it is quite longer, many may also have repeating OBX segments based on how much of data has to be transmitted.

The HL7 MDM message helps manage medical records by transmitting new or updated documents, or by transmitting important status information and/or updates for the record. Trigger events and messages can be one of two categories: they can either describe the status of the document, or they can describe the status of the document AND contain the document contents. MDM messages can be created in relation to an order or independently of them.

There are 11 different trigger events for the MDM message type provided in the HL7 standard. The most commonly used MDM message is the MDM-T02 (Original document notification and content) because it acts like an ORU (Result) message. By definition, the MDM-T02 message notifies a system of creation of a document and includes the document contents.

The OBX segment is an important part of MDM messages that contain document contents, because it is used to separate the body contents along places where headings or other separations might occur. All MDM messages have the same message structure with the exception of the OBX segment. Message types that contain document contents are significantly longer, and may have repeating OBX segments depending on how much data needs to be conveyed.

The segments in the MDM-T02, T04, T06, T08 and T10 (which all contain document contents) are as follows:

The segments in the MDM-T01, T03, T05, T07, T9 and T11 (which do not contain document contents) are as follows: