HL7 v2 MSH-5 Field Guide: Receiving Application Codes and Common Mistakes
MSH-5 names where a message is supposed to end up, but very few interface engines actually validate that the message reached the system it claims to be addressed to — so a mismatch here tends to surface only after someone notices data is missing on the receiving end.
MSH-5 is the fifth field of the MSH segment — a short identifier naming the application system the message is intended for.
What this field contains
Example
The 5th field, BILLSYS, identifies the receiving application as the billing system. Synthetic message — not a real transmission.
Where this trips people up
MSH-5 is descriptive metadata, not an actual routing instruction — the interface engine decides where the message physically goes based on its own configuration, not on what this field says. When the two drift apart, usually after a system is decommissioned or replaced, messages keep flowing to the real destination while MSH-5 still names a system that no longer exists, which confuses anyone debugging the interface later by log alone.