Automating Lab Results via HL7

The Problem: Human Middleware

A high-volume general practice relied heavily on a local regional lab that did not have a pre-built interface with the clinic's specific EMR. Consequently, the lab faxed results to the clinic. Medical Assistants (MAs) spent an average of 15 hours a week manually typing these PDF results into the EMR's discrete lab fields.

This process was not only expensive, it was dangerous. A single typo in a potassium level could alter a clinical decision.

The GP CTO Solution

We architected a secure, bi-directional HL7v2 interface using Mirth Connect (an open-source interface engine).

Phase 1: Order Routing (ORM)

When a physician orders a test in the EMR, Mirth intercepts the outbound order (ORM message). It translates the EMR's internal codes into the specific LOINC (Logical Observation Identifiers Names and Codes) standard required by the regional lab. This message is sent securely over a site-to-site IPsec VPN.

Phase 2: Results Processing (ORU)

When the lab completes the assay, they transmit an ORU (Observation Result) message back. Mirth validates the patient identifiers (MRN, DOB), maps the discrete values, flags any abnormal results based on the clinic's specific thresholds, and injects the data directly into the provider's inbox within the EMR.

The Results

Metric	Before (Manual)	After (HL7)
Time from lab completion to provider inbox	4-24 Hours	< 5 Minutes
Transcription Errors (Monthly)	~4 reported	0
Nursing Time Wasted	15 hrs/week	0 hrs/week

Frequently Asked Questions

What is Mirth Connect?

Mirth Connect (now NextGen Connect) is a powerful healthcare integration engine that routes, translates, and filters HL7, FHIR, XML, and JSON messages between disparate clinical systems.

Can any EMR connect to any Lab?

Technically, yes, if both systems support HL7 or API endpoints. However, many proprietary EMRs charge exorbitant "interface fees" to unlock their end of the connection.