HL7 MDM

Medical Document Management

The Medical Document Management (MDM) message provides information about new or updated notes or documents. An MDM message can be created in relation to or independently of an order. There are 11 different MDM message trigger events. These events always include the status of the document and can also include the accompanying document itself:

      • MDM^T01 - Original Document Notification
      • MDM^T02 - Original Document Notification with Content
      • MDM^T03 - Document Status Change Notification
      • MDM^T04 - Document Status Change Notification with Content
      • MDM^T05 - Document Addendum Notification
      • MDM^T06 - Document Addendum Notification with Content
      • MDM^T07 - Document Edit Notification
      • MDM^T08 - Document Edit Notification with Content
      • MDM^T09 - Document Replacement Notification
      • MDM^T10 - Document Replacement Notification with Content
      • MDM^T11 - Document Cancel Notification

MDM messages are typically used by Radiology departments to communicate provider transcriptions, order information and document contents. These messages either update other healthcare systems to identify available reports in the transcription system and can also provide the documents contents. The most commonly used MDM message is the MDM-T02, similar to an HL7 ORU Result Message, notifying a system of the creation of a document and providing the document contents.

[[Diagram or video of Iguana feeding Transcription MDM to an EMR]]

 

Below is an example of an HL7 version 2.3 MDM^T02 message:

MSH|^~\&|MESA_OP|XYZ_HOSPITAL|iFW|ABC_HOSPITAL|20090130123||MDM^T02|20090130123|P|2.3|||NE|
EVN|T02|200901301235|
PID|||||DOE^JOHN||19920115|M||||||||||G83186|005729288| PV1||1|CE||||12345^WILLIS^LAYLA^H|||||||||||
TXA|1|HP^History & Physical|TX|200901151010|||||||||||||DO||AV|
OBX|1|TX|||
OBX|2|TX|||
OBX|3|TX|||
OBX|4|TX|||Name: TEST,TEST
OBX|5|TX|||MR #: 123006
TEST HOSPITAL||||||P|||||| Morrisville, Vermont 05661||||||P||||||
OBX|6|TX|||Physician:JAMES CLEA DOB:
Date:01/13/09||||||P||||||
Sex: M Age: 19
HISTORY & PHYSICAL||||||P||||||
Room #: 039A||||||P||||||
Acct. #: G8318||||||P 07/13/1989 Admit
OBX|7|TX|||Physician: KAEDING J Stay Type: I/P D/C||||||P||||||
OBX|8|TX|||Physician: KEITH P||||||P||||||
OBX|9|TX|||CC: Dizziness and weakness with elevated sugars.||||||P|||
OBX|10|TX|||HPI: This is a 19-year-old man with multiple admissions for poorly controlled||||||P||||||

 

Segment

Description

MSH

Message Header. This segment is a mandatory part of an MDM message, and contains information about the message sender and receiver, the date and time that the message was created. This segment is required.

EVN

Event Type. Communicates the event that occurred in order for the message to be generated. This segment is a crucial part of the data flow, as it indicates where and when a message is sent based on the type of event. This is a required segment.

PID

Patient Identification. An MDM message is a patient-specific message type, and must be linked to a particular patient. Therefore, patient information such as the patient identifier, name, date of birth, etc. must be included in an MDM. This segment is required.

PV1

Patient Visit. Contains information about patient visit details such as servicing facility, attending doctor, and visit ID. This segment is required.

TXA

Document Notification. Communicates information specific to a transcribed document as a result of a status change. This segment does not include the document contents and is required.

 

{OBX}

Observation Segment. Contains the document contents. This segment is required and is often repeating segments in an MDM.

[ ] = optional, { } = repeating

 

For more information on implementing various HL7 message types, please refer to the HL7 Messaging Standard Implementation Guides corresponding to your required version. 

 


 

 

Other HL7 Message Types:

      • HL7 ADT (Admit, Discharge and Transfer)
      • HL7 ORM (Order Entry)
      • HL7 ORU (Observation Result)
      • HL7 MDM (Medical Document Management)
      • HL7 DFT (Detailed Financial Transactions)
      • HL7 BAR (Billing Account Record)
      • HL7 SIU (Scheduling Information Unsolicited)
      • HL7 RDS (Pharmacy/treatment Dispense)
      • HL7 RDE (Pharmacy/Treatment Encoded Order)
      • HL7 ACK (Acknowledgement Message)

 

Integration with HL7

HL7 is great standard, but anyone with first hand experience knows it's not without its challenges. We're here to help!

Let's talk
icon-HL7

The ''non-standard" Standard

In practice, you'll find that everyone formats HL7 messages slightly different, even though it has a standard structure in place. With iNTERFACEWARE's integration engine, you can ensure that all data is normalized as intended for full compliance.

icon-HL7

Version Compatiblity

What happens when the source destination is sending one version of HL7, while the recipient's system can only handle an older version of HL7? With Iguana you can convert HL7 versions on the fly.

icon-HL7

Data Extraction

As you've seen, HL7 messages can contain a lot of information -- sometimes much more than you need. Simplify things using Iguana, by extracting the data from the specific HL7 fields you need. 

icon-HL7

Future Proofing

The HL7 organization is always working on improving the standard and new versions will keep coming in the future. Ensure that your data always remains compatible with iNTERFACEWARE's integration engine, Iguana.