MDM: Medical Document Management

MDM moves clinical documents and their status: a dictated note becoming available, a transcription being edited, a document being replaced. The document itself travels in OBX segments beneath a TXA header.

Recognising MDM messages

MDM announces itself in MSH-9 like this:

How to use these specifications explains MSH-9 in full, with a worked example.

Message structures

MDM takes 2 structures.

MDM_T01: Original Document Notification

6 different trigger events send this structure:

• T01Original Document Notification
• T03Document Status Change Notification
• T05Document Addendum Notification
• T07Document Edit Notification
• T09Document Replacement Notification
• T11Document Cancel Notification

You must always send: MSH, EVN, PID, PV1, TXA. Everything else is optional, or required only inside a group you chose to send.

R inside a group means required of that group. Send the group and you must include that segment; leave the group out and it never appears. This structure has 2 such groups: COMMON_ORDER, TIMING.

MDM_T02: Original Document Notification and Content

5 different trigger events send this structure:

• T02Original Document Notification and Content
• T04T04
• T06Document Addendum Notification and Content
• T08Document Edit Notification and Content
• T10Document Replacement Notification and Content

You must always send: MSH, EVN, PID, PV1, TXA, OBX. Everything else is optional, or required only inside a group you chose to send.

R inside a group means required of that group. Send the group and you must include that segment; leave the group out and it never appears. This structure has 3 such groups: COMMON_ORDER, TIMING, OBSERVATION.

Trigger events

The trigger event is the real-world thing that made the message get sent. MDM defines 11.

Related

• MSHthe header carrying MSH-9, where the type and event are declared
• All message typesthe complete list