HL7 201 — Unsupported event code
Code 201 means the message type is supported but the specific trigger event (the second component of MSH-9, e.g. the A04 in ADT^A04) is not.
When you see 201 (Error Condition Code)
Raised when the receiver handles the message family but not that particular event — for example it accepts ADT^A01 but not ADT^A04.
Common causes
- Sending a trigger event the receiver does not implement (e.g. A05 pre-admit when only A01/A03 are configured).
- Wrong or missing event code in MSH-9 component 2.
- Receiver maps only a subset of an event family.
How to fix it
- 1Check MSH-9's trigger event against the list the receiver supports for that message type.
- 2If the event is needed, request the receiver enable it, or remap to a supported equivalent event where clinically appropriate.
- 3Confirm the interface spec documents exactly which trigger events flow on this interface.
Example ACK message
A representative acknowledgment carrying ERR-3 = 201. Open it in the HL7 Viewer to inspect every field.
1MSH||^~\&|RECEIVER|HOSP|SENDER|HOSP|20260310143450||ACK^A05^ACK|ACK00021|P|2.5.1 2MSA||AR|MSG00001|Unsupported event code 3ERR||||201^Unsupported event code^HL70357|E|||MSH.9 trigger event 'A05' not supported
Related codes
Frequently asked questions
What is the difference between HL7 error 200 and 201?
Code 200 (Unsupported message type) means the whole message family (e.g. ADT) is not supported. Code 201 (Unsupported event code) means the family is supported but the specific trigger event (e.g. A05) is not. 201 is narrower.
Debug your ACK in the viewer
Paste the ACK (or original message) and get instant segment parsing, MSA/ERR decoding, and validation. Free, client-side, no signup.
Open HL7 Message Viewer →All HL7 error & ACK codes
Browse every acknowledgment code (Table 0008) and error condition code (Table 0357) with causes, fixes, and examples.
HL7 Error Code Reference →