HL7 Error & Acknowledgment Codes
Got an MSA|AE or an ERR...101 back from an interface and need to know what it means? This is the complete reference for HL7 v2.x acknowledgment codes (MSA-1, Table 0008) and error condition codes (ERR-3, Table 0357) — each with what it means, why it happens, how to fix it, and an example ACK.
Acknowledgment Codes (MSA-1, Table 0008)
The acknowledgment code in MSA-1 tells the sender whether the message was accepted, errored, or rejected.
The receiving application successfully received, understood, and processed the message.
The receiving application understood the message but could not process it because of an error in the message content or an application-level failure.
The receiving application rejected the message and did not process it — typically because of a structural, version, or environmental problem the sender cannot fix by changing one field value.
In enhanced acknowledgment mode, CA confirms the message was successfully received and safely committed to storage by the receiver — but not yet processed by the application.
In enhanced acknowledgment mode, CE indicates an error occurred while the receiver attempted to accept and commit the message to storage.
In enhanced acknowledgment mode, CR indicates the receiver rejected the message at the accept (commit) level — typically because the message header or framing was unacceptable before any application processing.
Error Condition Codes (ERR-3, Table 0357)
The error condition code (ERR-3 in current versions) pinpoints why a message could not be processed.
Error condition code 0 means success — no error.
Code 100 means the segments arrived in an order the receiver did not expect, or a required segment was missing from its expected position in the message structure.
Code 101 means a field the receiver requires was empty.
Code 102 means a field contained a value of the wrong data type — for example text where a number or a properly formatted date/timestamp was expected.
Code 103 means a coded field contained a value that is not in the table the receiver uses for that field — for example an unrecognized gender, marital status, or facility code.
Code 200 means the message type in MSH-9 (e.
Code 201 means the message type is supported but the specific trigger event (the second component of MSH-9, e.
Code 202 means the processing ID in MSH-11 (P = production, T = training/test, D = debug) is not accepted by the receiver — commonly a test message hitting a production-only endpoint or vice versa.
Code 203 means the HL7 version in MSH-12 (e.
Code 204 means a key the receiver looked up — such as a patient identifier, visit number, or order number — was not found in the receiving system.
Code 205 means the receiver rejected a create because a record with the same key already exists — for example admitting a patient or creating an order that is already on file.
Code 206 means the transaction could not be performed because the target record was locked by another process.
Code 207 is the catch-all: the receiving application hit an internal error that does not map to a more specific code.