HL7 MDM_T08 Document Edit Notification and Content

An unavailable document was edited before it became available for patient care, and the edited content is included.
HL7 message structure MDM_T02 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_T02.COMMON_ORDER
 Common Order group No Yes
ORC
 Common Order Yes No
MDM_T02.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_T02.OBXNTE_SUPPGRP
 Obxnte Suppgrp group Yes Yes
OBX
 Observation/Result Yes No
NTE
 Notes and Comments No Yes

MDM_T08 is the document edit notification with content. It is used when a document has been edited and the new content is being sent, usually before the document has been made available for patient care. This is a narrower workflow than "replace a final report" or "add an addendum."

On the wire this is normally MDM^T08^MDM_T02. T08 is the edit event; MDM_T02 is the shared content-bearing document structure with required TXA and OBX content.

A small MDM_T08 example

MSH|^~\&|DOCSYS|CITYHOSP|EHR|CITYHOSP|20260716114500||MDM^T08^MDM_T02|MDM080001|P|2.5.1 EVN|T08|20260716114300 PID|1||123456^^^CITYHOSP^MR||Smith^Jane^Anne^^Ms^^L||19800314|F PV1|1|O|CARD^ECHO^^CITYHOSP||||55555^Reader^Riley TXA|1|ECHORPT^Echo Report^L|TX|20260716100000|55555^Reader^Riley|20260716111000|20260716114300|55555^Reader^Riley||||DOC20260716003|ORD449100^EHR|ECHO771100^CARD|UN OBX|1|TX|REPORT^Edited report text^L||Edited draft: Left ventricular function is normal. Final authentication is pending.||||||P

What systems do with it

The sender is usually a document/transcription system or departmental reporting system. The receiver updates a document that it already knows about, or stores the edited draft content until it becomes available or authenticated. This is often a back-office document lifecycle event rather than a clinical "new final result" event.

TXA identifies the document and its current status. OBX carries the edited content. If the receiver has already released the document to patient care, T08 may be the wrong event; replacement or addendum workflows are usually safer for released documents.

How to read the structure

T08 uses the MDM_T02 structure because content travels with the notification. The core is MSH, EVN, PID, PV1, optional order context, TXA, and one or more OBX/NTE content groups. In practice, the document ID in TXA is what lets the receiver update the existing draft document.

OBX-5 may carry text, formatted text, or encoded content depending on the profile. For draft/edit workflows, receivers should be especially clear about whether the content replaces the previous draft content or adds a new revision entry.

Implementation traps

The common trap is using T08 after a document is already available to clinicians. HL7 guidance treats edit notifications as valid for documents whose availability status is unavailable. Once a document has been made available, replacement or addendum workflows preserve the record more cleanly.

Another trap is sending edited content without a stable document identifier. A receiver cannot safely update a draft report just by matching patient, date, and document type.

Reference notes

HL7 Chapter 9 describes T08 as an edit notification with content, and notes that the edit trigger applies to documents whose availability status is unavailable. Caristix gives the same practical scenario: errors are found in a document and corrected, with edited content sent. iNTERFACEWARE's MDM overview frames MDM as document notification plus optional document contents.