MajwareMAJWARE
HL7 v2.x Reference

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.

19
Codes documented
AA · AE · AR · CA · CE · CR
Acknowledgment codes
0 · 100–103 · 200–207
Error condition codes

Acknowledgment Codes (MSA-1, Table 0008)

The acknowledgment code in MSA-1 tells the sender whether the message was accepted, errored, or rejected.

Error Condition Codes (ERR-3, Table 0357)

The error condition code (ERR-3 in current versions) pinpoints why a message could not be processed.

0Message accepted

Error condition code 0 means success — no error.

100Segment sequence 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.

101Required field missing

Code 101 means a field the receiver requires was empty.

102Data type error

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.

103Table value not found

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.

200Unsupported message type

Code 200 means the message type in MSH-9 (e.

201Unsupported event code

Code 201 means the message type is supported but the specific trigger event (the second component of MSH-9, e.

202Unsupported processing id

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.

203Unsupported version id

Code 203 means the HL7 version in MSH-12 (e.

204Unknown key identifier

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.

205Duplicate key identifier

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.

206Application record locked

Code 206 means the transaction could not be performed because the target record was locked by another process.

207Application internal error

Code 207 is the catch-all: the receiving application hit an internal error that does not map to a more specific code.