An HL7 bridge and report builder for a diagnostics chain
A bridge carrying HL7 messages from laboratory instruments into a cloud platform, with a drag-and-drop report builder and generative AI assistance.
- Client
- A diagnostics chain
- Sector
- Diagnostics
- Shipped
- 2025
- Practice
- Business process automation
A cloud platform for a diagnostics operation, with an HL7 bridge that brings instrument messages in from the laboratory floor and serverless functions that process them. Report layouts are arranged by drag and drop rather than hard-coded, generative AI assists with drafting, and device fingerprinting is used to tie sessions to known machines.
The problem
Instruments spoke HL7 on the laboratory network while the platform the business wanted to run on was in the cloud. The two could not reach each other, and report layouts were changing often enough that every change becoming a development task was itself the bottleneck.
What we built
- 01
A bridge process on the laboratory network that receives HL7 messages locally and forwards them to the cloud, so instruments keep talking to something on their own segment.
- 02
Cloud functions to process the forwarded messages, so handling scales with volume instead of running on a machine in the laboratory.
- 03
A drag-and-drop report builder, so a layout change is an afternoon's configuration rather than a release.
- 04
Generative AI used for drafting inside the workflow, where it removes typing rather than adding a chat box.
- 05
Device fingerprinting to recognise the machines sessions come from.
What it does now
- Laboratory instruments feed a cloud platform without being exposed to the internet.
- Report layouts are changed by configuration, not by a deployment.
- Message processing scales with volume rather than with one machine's capacity.
What people ask about this work.
How do laboratory instruments connect to cloud software safely?
With a bridge on the laboratory network. Instruments send HL7 to a local process on their own network segment, and that process forwards messages outward to the cloud. The instruments are never exposed to the internet and nothing inbound has to reach the laboratory floor.
Should report layouts be configurable or coded?
Configurable, once they change more than occasionally. If every layout tweak is a development task and a release, the development queue becomes the bottleneck for a change that is really a business decision. A drag-and-drop builder moves that decision to the people who own it.
Related projects.
- Messaging reliability
A WhatsApp delivery service that survives disconnection
An Express service wrapping whatsapp-web.js with a persistent on-disk queue, so messages sent while WhatsApp is disconnected are delivered on reconnect.
Read it - Analyser integration
Middleware that reads a haematology analyser
Middleware for a Mindray BC-series haematology analyser, turning a printed slip and twenty retyped numbers into a result that arrives by itself.
Read it
