Understanding HL7 v2 MSH-6: Receiving Facility in Practice
MSH-6 is easy to treat as a formality, but in health systems that route messages between facilities — a shared lab serving several clinics, for example — it is the field that tells the receiving side which site a result or order is actually meant for.
MSH-6 is the sixth field of the MSH segment — an identifier naming the facility the message is intended to reach, paired with MSH-5 the way MSH-4 pairs with MSH-3.
What this field contains
Example
The 6th field, HOSP, identifies the receiving facility as the main hospital campus. Synthetic message — not a real transmission.
Where this trips people up
When a shared application serves several facilities and downstream logic branches on MSH-6 to decide which chart or which billing entity a message belongs to, an interface built or tested against a single-facility deployment often leaves this field blank or hardcoded — a shortcut that works until the same interface gets reused for a second site and messages start landing in the wrong facility's queue.