HL7 MDM_T01 Original Document Notification

A document exists, but the content is not riding along in this message.
HL7 message structure MDM_T01 groups and segments from HL7 v2.5.1 Hide structure

These are the generated groups and segments for the version selected at the top of the page. The article explains the workflow, and this panel follows the chosen HL7 version.

Message Structure

SegmentNameRequiredRepeatable
MSH
 Message Header Yes No
SFT
 Software Segment No Yes
EVN
 Event Type Yes No
PID
 Patient Identification Yes No
PV1
 Patient Visit Yes No
MDM_T01.COMMON_ORDER
 Common Order group No Yes
ORC
 Common Order Yes No
MDM_T01.TIMING
 Timing group No Yes
TQ1
 Timing/Quantity Yes No
TQ2
 Timing/Quantity Relationship No Yes
OBR
 Observation Request Yes No
NTE
 Notes and Comments No Yes
TXA
 Transcription Document Header UAC User Authentication Credential Segment Yes No

MDM_T01 is the original document notification message. It tells a receiving system that a new document has been created, dictated, transcribed, or otherwise entered into the document-management workflow, but it does not send the body of the document.

That distinction is the point. If the receiver needs the content in the same message, look at MDM_T02. T01 is for the header and lifecycle notification: this document exists, here is the patient and visit context, here is the document identifier, type, status, author/authenticator context, and enough information to track or retrieve it elsewhere.

A small MDM_T01 example

MSH|^~\&|TRANSCRIPTION|CITYHOSP|EHR|CITYHOSP|20260715131500||MDM^T01^MDM_T01|MDM010001|P|2.5.1 EVN|T01|20260715131500 PID|1||123456^^^CITYHOSP^MR||Smith^Jane^Anne^^Ms^^L||19800314|F PV1|1|O|CARD^ROOM1^1^CITYHOSP||||12345^Cardio^Casey TXA|1|CN|TEXT|20260715110000|12345^Cardio^Casey|20260715113000|20260715131500|||45678^Transcriber^Tina|DOC7788^TRANS|DOC7788^TRANS|AV|AU

What systems do with it

The sender is usually a transcription, radiology, cardiology, document-management, or EHR system. The receiver may be the enterprise EHR, a clinical repository, a document index, a results-review queue, or an integration engine. The receiver uses TXA as the document header and connects it to the patient and visit through PID and PV1.

Optional order context can appear through ORC, TQ1, TQ2, OBR, and NTE. That is useful when the document belongs to a specific order, imaging study, consult, or procedure.

How to read the structure

The required backbone is MSH, EVN, PID, PV1, and TXA. The common-order group is optional and repeating. There is no required OBX content group in T01, because the message is the notification without content.

That makes TXA especially important. TXA fields carry the document type, activity time, origination/transcription/edit times, unique document number, parent document relationship, availability status, and authentication status depending on profile. If the document ID in TXA is weak or unstable, downstream document tracking becomes painful quickly.

Implementation traps

The first trap is accidentally treating T01 as if it contained the report text. A receiver should not mark the document body as available from OBX unless the message event actually carries content. T01 can update a worklist or index, but the body comes from another message, repository, or retrieval workflow.

The second trap is using a local display title as the document identifier. Human titles change. Document identifiers should survive corrections, replacement, routing, and resend. If later T06, T08, T10, or T11 events depend on parent-child document relationships, weak identifiers make those workflows much harder.

Reference notes

The HL7 v2+ MDM_T01 page lists the original document notification structure. The HL7 v2.5.1 chapter 9 material describes MDM T01 as the original document notification event, and vendor references such as Rhapsody's MDM guide and iNTERFACEWARE's MDM overview frame MDM messages around document notifications, transcription, and document content workflows.