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:

SEGMENT/ GROUPNAMEOPTIONAL/REPEATABLE?
MSHMessage headerRequired
EVNEvent typeRequired
PIDPatient identificationRequired
PV1Patient visitRequired
TXADocument notification segmentRequired
OBXObservation segmentRequired, Repeatable

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

SEGMENT/GROUPNAMEOPTIONAL/REPEATABLE?
MSHMessage headerRequired
EVNEvent typeRequired
PIDPatient identificationRequired
PV1Patient visitRequired
TXADocument notification segmentRequired

In HL7 pipe and hat format, the MDM-T01 (Original document notification) message would look like this:


MSH|^~\&|MedOne|FACILITY A|CARECENTER^HL7NOTES|HFH|20060105180000| D61AFEF1-B10E-11D5-8666-0004ACD80749|MDM^T01|20060105180000999999|T|2.3
EVN|T01|20060105180000
PID|1||1112388^BS||ESPARZA^MARIA
PV1|1|O|BS^15^15
TXA|1|GENNOTES|TX|200601051800|50041^SMITH^CHRIS^M|200601051800|200601051800|200601051800|||
SC^ROBINSON^JESSICA^A|1234567890||||FILE0001.TXT|PR

Register for an upcoming HL7: First Steps training class.

How Corepoint Integration Engine works with HL7

 

The #1 Integration Engine Nine Consecutive Years

Customers have confidence in Corepoint Health’s history of focusing on healthcare interoperability, as evident by our #1 KLAS® ranking nine years in a row. Discover the power Corepoint Integration Engine offers healthcare providers of all sizes and specialties.

 Print Friendly