Process an HL7v2 MDM^T02 medical document notification to ingest a clinical document

In-depth guide

Steps

1. Receive the MDM^T02 message (Medical Document Management — Original Document Notification with Content) via your MLLP listener; T02 indicates the document content is embedded in the message as opposed to T01 which is a pointer-only notification
2. Parse the EVN segment for event date/time and TXA segment for document metadata: document type code in TXA-2, activity date/time in TXA-4, originating provider in TXA-9, document status in TXA-17 (AU for authenticated, DI for dictated), and unique document ID in TXA-12
3. Extract the OBX segments that follow the TXA segment; for embedded documents OBX-2 will typically be 'ED' (encapsulated data) or 'TX' (text); for ED type, OBX-5 contains the document encoded as base64 (or plain text for TX) along with the encoding type and MIME type
4. Decode the document content from base64 if applicable; the document may be a CDA (Clinical Document Architecture) XML document, plain text, or a PDF depending on the sending system
5. Correlate the document to the patient using the PID segment in the MDM message and the visit using PV1 if present; store the document with appropriate indexing by document type, date, and provider
6. Send an ACK and, if your system requires document management workflow, track authentication status using TXA-17 — documents in dictated or transcribed status may need to be updated via subsequent MDM messages as they move through the authentication workflow