^T01
MDM^T01 — Original Document Notification
MDM^T01 notifies downstream systems that a new clinical document has been created, without transmitting the document content. It carries document metadata in the TXA segment, allowing the receiving system to index the document and request the content separately if needed.
When Is This Sent?
When a new transcribed document (dictation) is first received by a transcription system or when an EMR creates a new document that needs to notify other systems. The document metadata is sent but the content is transmitted separately via MDM^T02.
Real-World Usage
MDM^T01 is used in transcription workflows where the transcription system notifies the EMR that a new document is available for the patient. The EMR can then retrieve or request the content. In practice, many implementations skip T01 and go directly to T02 (with content). T01 is valuable when the document content is large or the workflow requires a two-step notification/retrieval pattern.
Message Structure
Segment names link to their field-level reference pages.
| # | Segment | Purpose in this message | Req | Repeat |
|---|---|---|---|---|
| 1 | MSH | Message header with MDM^T01 in MSH.9 | R | — |
| 2 | EVN | Event type with T01 trigger and document creation timestamp | R | — |
| 3 | PID | Patient demographics | R | — |
| 4 | PV1 | Visit context at time of document creation | R | — |
| 5 | TXA | Document metadata: type, creation time, authenticator, unique document number | R | — |
| 6 | OBX | Document content (if included; T02 is preferred for content delivery) | O | Yes |
Example Message
Realistic example with fake patient data. Paste into the HL7 Message Viewer to explore interactively.
1MSH||^~\&|TRANSCRIPTION|HOSPITAL_A|EPIC|HOSPITAL_A|20260310161000||MDM^T01^MDM_T01|MDM_T01_001|P|2.5.1 2EVN||T01|20260310161000 3PID||1||123456^^^HOSP_A^MR||Smith^John^M^^Mr.||19850315|M 4PV1||1|I|4A^201^1^^^HOSP_A||||1234^Ahmed^Dr.^Khalid 5TXA||1|DS|FT|20260310160000|5678^Wilson^Dr.^Sarah^R|||DOC20260310001^TRANSCRIPTION|||5678^Wilson^Dr.^Sarah^R|DOC20260310001|||||AV
Troubleshooting Scenarios
EMR receives T01 but document never appears in the chart
Cause
The EMR is not configured to process T01 notifications — it is only configured to receive T02 (document with content). T01 is indexed but no content ever arrives.
Fix
Either switch the transcription system to send T02 instead of T01, or configure the EMR to request document content after receiving T01. Confirm with the EMR vendor how T01 is handled in the document indexing workflow.
TXA document type code not recognized by receiving system
Cause
TXA.2 (document type) uses a local code that the receiving system's document type catalog doesn't contain.
Fix
Obtain the list of document type codes supported by the receiving system. Map the sending system's local document type codes to the receiving system's catalog in the interface engine. Common TXA.2 values: DS (Discharge Summary), HP (History and Physical), OP (Operative Note), RN (Radiology Note).
Common Confusions
MDM^T01 (notification only) vs MDM^T02 (notification with content). T01 tells the system a document exists; T02 delivers the actual document text. Most implementations use T02 exclusively. T01 is useful in hub-and-spoke architectures where a central repository notifies multiple systems. Also: MDM^T01 vs ORU^R01 — use MDM messages for narrative documents; use ORU^R01 for structured discrete results.
Related Message Types
Segment Reference
Paste this message into our viewer
Interactive HL7 parser. Decodes every field, validates structure, highlights errors. Free, no signup.
Open HL7 Message Viewer →Need mapping templates?
The HL7 Integration Toolkit includes field mapping worksheets and interface spec templates for every major HL7 message type including MDM^T01.
View HL7 Integration Toolkit →