Invalid Message Type and Trigger Event Combination
MSH-9 carries the message type and trigger event (for example ADT^A01). The combination supplied does not exist in the declared HL7v2 version, so no structure can be resolved to validate against.
HL7v2 · Error
The error
is not a valid message type/event combination in this HL7v2 versionWhy it happens
A typo in MSH-9, a trigger event that belongs to a different message type, or a version mismatch where the event exists in a newer or older release than the one in MSH-12.
How to fix it
Set MSH-9 to a valid type^event pair for your version, such as ADT^A01 or ORU^R01. The third component (message structure, e.g. ADT_A01) should agree with the first two.
Example
The snippet below triggers the error:
MSH|^~\&|S|S|R|R|20240115||ADT^A99|M1|P|2.5The corrected version:
MSH|^~\&|S|S|R|R|20240115||ADT^A01|M1|P|2.5Frequently asked questions
What goes in MSH-9?
MSH-9.1 is the message type (ADT, ORU, ORM), MSH-9.2 is the trigger event (A01, R01), and MSH-9.3 is the message structure. The first two together must be a recognized combination for the version in MSH-12.