HL7 Integration

RADPAIR and HL7 Integration Overview

RADPAIR supports many integration methods. RADPAIR supports HL7, recognizing the critical role of incoming metadata from various healthcare systems. The following outlines how RADPAIR handles the reception of HL7 orders and the transmission of radiology reports:

HL7 Message Handling

RADPAIR employs an integration layer to receive HL7 ORM (Order) messages and send HL7 ORU (Observation Result) messages. Since HL7 does not natively support encrypted transmissions, RADPAIR offers clients the option to install an on-premise edge node device. This device securely manages transmissions between the client environment and RADPAIR’s cloud infrastructure.

For clients who prefer not to use the edge node, alternative secure integration options are available, such as HL7 FHIR, AWS S3, and others. Please contact RADPAIR for more details.

Order Message Metadata and Pre-Population

HL7 order messages often contain key clinical metadata that clinicians expect to see reflected in the final radiology report. Examples of such metadata include:

• Study description

• Laterality

• Reason for exam

RADPAIR can ingest this information and use it to pre-populate the radiology report, allowing the radiologist to make modifications or sign it as appropriate. This reduces manual entry and improves accuracy and efficiency.

Pre-Caching Capability

HL7 order messages also enable pre-caching, a feature that allows RADPAIR to generate a preliminary version of a report in advance. Pre-caching significantly reduces latency and enhances the overall experience for radiologists by streamlining their workflow.

Report Delivery via HL7 ORU

For many clients, the HL7 ORU message is the preferred method for receiving signed radiology reports. When a radiologist signs a report in RADPAIR, an HL7 ORU message can be automatically triggered and transmitted to the client’s EMR, HIS, or RIS system.