In a multi-tenant radiology platform, one integration endpoint may serve many customer organizations and hundreds of facilities. Reliable routing requires separate, governed identifiers for the tenant, facility, message and order.
Use distinct identity layers
Do not overload a single HL7 field to represent both the customer tenant and the patient facility. Maintain a platform tenant identifier in the integration envelope or agreed sending-application namespace, and carry the actual facility identifier in the message location or organization fields defined by the interface specification.
- ✓Tenant ID: identifies the Comiere customer environment
- ✓Facility ID: identifies the patient care or imaging location
- ✓MSH-10: uniquely identifies the message instance
- ✓ORC-2 / OBR-2: preserves the placer order number from the EHR or HIS
- ✓ORC-3 / OBR-3: carries the filler order number assigned by the RIS or performing system
Resolve through a governed routing table
Use the combination of sending application, sending facility, tenant and facility mapping to resolve the destination. Reject ambiguous or inactive mappings instead of guessing. Version changes and retain an audit history.
Acknowledge with traceability
Return HL7 acknowledgements that reference MSH-10 and record the resolved tenant, facility, order identifiers, route and outcome. Operational teams should be able to move from an accession number or message control ID to the complete processing trail.
Protect tenant boundaries
Validate that each facility belongs to the resolved tenant before processing patient data. Apply authorization and observability at the tenant boundary and prevent cross-tenant fallbacks.
This insight is provided for general informational purposes. Architecture, clinical workflow and compliance decisions should be validated against your organization’s requirements.