HL7 MDM_T11 Document Cancel Notification

A document should be canceled or removed from general access, but the document body is not included.
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_T11 is the document cancel notification. It is used when an original document should be canceled, usually because it should not stand as available for the patient record it was associated with. A common example is a document dictated or filed against the wrong patient before it should have become generally available.

T11 normally uses MDM^T11^MDM_T01. The trigger event is the cancel notification, while the MDM_T01 structure carries the no-content document-notification layout: MSH, EVN, PID, PV1, optional order context, and TXA.

A small MDM_T11 example

MSH|^~\&|DOCSYS|CITYHOSP|EHR|CITYHOSP|20260716170000||MDM^T11^MDM_T01|MDM110001|P|2.5.1 EVN|T11|20260716165800 PID|1||123456^^^CITYHOSP^MR||Smith^Jane^Anne^^Ms^^L||19800314|F PV1|1|O|RAD^XRAY^^CITYHOSP||||55555^Reader^Riley TXA|1|RADRPT^Radiology Report^L|TX|20260716130000|55555^Reader^Riley|20260716133000|20260716165800|55555^Reader^Riley||||DOC20260716020|ORD449300^EHR|LAB778899^RAD|UN

What systems do with it

The sender is usually a document-management or reporting system. The receiver finds the document by its TXA identifiers, updates its availability/status, removes it from general clinical access if appropriate, and records the cancellation for audit.

Unlike MDM_T10, T11 does not send replacement content. If the correct patient needs a correct document, that should normally arrive as a separate creation or replacement workflow with the correct patient identifiers.

How to read the structure

The generated panel shows MDM_T01 because T11 is a no-content notification. The core is MSH, EVN, PID, PV1, optional ORC/OBR order context, and TXA. There is no required OBX content group.

The document identity in TXA is the thing the receiver must trust. If the message cannot uniquely identify the document being canceled, it should not guess based on patient/date/type alone.

Implementation traps

The biggest trap is using T11 to cancel a document that has already been made available for patient care when replacement is the safer process. HL7 guidance points implementers toward replacement for available documents, with the erroneous original retained historically and marked obsolete.

The second trap is leaking the correct patient's identity into a cancellation message for the wrong patient. If the document was filed to the wrong chart, the cancellation message should remove or restrict the erroneous document without exposing the intended patient's identifiers in the wrong record.

Reference notes

HL7 Chapter 9 describes T11 as document cancellation and notes the wrong-patient scenario, including the privacy reason not to put the correct patient's identity into the erroneous record. Caristix summarizes T11 as a cancellation notification for an original document with unavailable status. Rhapsody separates T11 into the MDM events that do not carry document body content.