HL7 MDM^T02 (Original Document Notification & Content)
MDM^T02 is an original document notification that also carries the document content. The TXA segment describes the document (type, status, author, dates) and OBX segments carry the report text.
When is MDM^T02 sent?
Sent when a new clinical document (discharge summary, operative note, transcription) is created and its content is distributed along with the notification.
Key segments
The segments below are the ones most relevant to MDM^T02. Real messages may carry additional optional segments depending on the sending system’s configuration.
| Segment | Usage | Role |
|---|---|---|
| MSH | Required | Message header: sending/receiving application & facility, message type, control id, version. |
| EVN | Required | Event type: the trigger event code and the date/time the event occurred. |
| PID | Required | Patient identification: identifiers (MRN), name, date of birth, sex, address, phone. |
| PV1 | Optional | Patient visit: patient class, assigned location, attending provider, admit/discharge details. |
| TXA | Required | Transcription document header: document type, content presentation, activity/edit dates, author, unique document id, availability status. |
| OBX | Required | Observation: carries the document content (e.g. report text) in repeating OBX segments. |
Example MDM^T02 message
A realistic, well-formed example. Segments are separated by carriage returns; fields by the pipe (|) delimiter.
MSH|^~\&|EMR|HOSP|REC|REC|20240115170000||MDM^T02|MSGCTRL8888|P|2.5.1
EVN|T02|20240115170000
PID|1||MRN12345^^^EPIC^MR||DOE^JOHN^A||19800101|M
TXA|1|DS^Discharge Summary^L|TX^Text|20240115163000|||20240115170000||||DOC123^SMITH^ALICE^MD||DOCID999||AU|||AV
OBX|1|TX|||Patient discharged in stable condition.|||||||FMapping MDM^T02 to FHIR
See the full field-by-field mapping of MDM^T02 to a FHIR DocumentReference — including the transforms and gotchas — on the MDM^T02 → US Core DocumentReference reference page. You can fork that template and run it in the Mapping Builder.
Frequently asked questions
What is an HL7 MDM^T02 message?
MDM^T02 is an original document notification with content. TXA carries the document metadata (type, status, author, dates) and the document text is carried in one or more OBX segments.
What is the difference between MDM^T02 and MDM^T01?
T01 is a notification only (the document exists), while T02 includes the document content itself in OBX segments. Other events (T04 status change, T08 edit) cover later updates.
How do I map MDM^T02 to a FHIR DocumentReference?
Map TXA-2 to type (LOINC), TXA-17 availability status to docStatus, TXA-9 author to author.display, TXA-4 to date, and the OBX content to content.attachment. The Interoperall template shows the rules.
How do I validate an MDM^T02 message?
Paste it into the HL7v2 validator to parse the TXA/OBX structure and confirm it is well-formed, entirely in your browser.