HL7AI Integration Agent
An HL7 hub that routes your messages to your integration engines (Mirth, Rhapsody…) and applications — with a local AI that, per channel and per message type, fills documents, summarizes and extracts information. Every generated output is clearly marked as AI.
A central hub that routes to all your engines
Receive once, route everywhere: the Integration Agent dispatches each message to the right engines (Mirth Connect, Rhapsody…) and applications, by channel and message type.
Routing: sources → channels → engines
Daily volume · thickness ∝ message countReceive → AI → route, in milliseconds
Receive
MLLP listening, automatic ACK (V2.x, V3, FHIR, DICOM).
Validation
Conformance, identifier normalization (NAM/NIM/IPM).
Channel routing
Rules by facility, source system and message type.
AI by type
Fill, summarize, extract, classify — by message type.
Delivery
Mirth, Rhapsody, FHIR server, EHR, BI warehouse.
Each channel has its destinations, transform and AI task
| Channel | Message type | Destinations | IA |
|---|---|---|---|
| Laboratory | ORU^R01 |
MirthFHIRBI | Critical-result summary |
| Radiology | ORM^O01 ORU^R01 |
RhapsodyFHIR | Report summary |
| Admission | ADT^A01/A02/A03 |
MirthDPIBI | Patient-duplicate detection |
| Pharmacy | RDE^O11 |
MirthDPI | Interaction check |
| Microbiology | ORU^R01 |
MirthFHIR | Extraction & coding (LOINC/SNOMED) |
| Documents | MDM^T02 |
DPIArchive | Document fill & summary |
A specialized local AI for each flow
You ask HL7AI to fill a document, summarize a stay or extract data — the task is applied automatically to the right channel and message type.
AI task distribution
- Fill documents 34%
- Summarize 28%
- Extract & classify 22%
- Normalize & code 16%
Fill documents
Generates reports, CDA and FHIR DocumentReference from messages.
Summarize
Summary of a stay, a chart or a batch of results.
Extract & classify
Spots critical values, codes to LOINC/SNOMED, categorizes.
Normalize
Reconciles identifiers and terminologies across standards.
Fill a document from an HL7 message
A lab result (ORU^R01) arrives; the AI drafts the report, clearly tagged "AI-generated".
Report — Lipid panel
AI-generatedTREMBLAY, Jean · NAM TRJE 8203 1517 · ICU
Abnormal lipid panel suggesting high cardiovascular risk: elevated total cholesterol (6.8 mmol/L), high LDL (4.6 mmol/L) and low HDL (0.9 mmol/L).
Suggestion: consider a statin and reassess at 3 months.
Summarize a stay from multiple messages
The AI aggregates a patient's messages (joined on the key) and produces a traceable summary.
Stay messages
12 HL7 messages · 36 h · NAM TRJE 8203 1517ADT^A01 ER admissionORU^R01 Troponine 0,92 µg/LORU^R01 Abnormal ECGORM^O01 AngiographyADT^A02 Transfer to ICUStay summary
AI-generatedPatient admitted to ER for chest pain, then transferred to ICU.
Elevated troponin (0.92 µg/L) and abnormal ECG suggesting acute coronary syndrome; angiography performed.
Plan: continuous monitoring, dual antiplatelet therapy.
AI-generated content is always identified
No ambiguity between source data and AI output: each result carries its provenance and stays under human control.
"AI-generated" label
A visible badge marks every AI output in the UI and documents.
Full provenance
Local model, version, timestamp, confidence score and source HL7 segments.
Human validation
Mandatory "to validate" status before clinical delivery (human-in-the-loop).
Traceability
Every output links back to the exact HL7 messages and fields that produced it.
100% local AI
Models run on-premise; no patient data is sent to the cloud.
Audit log
Every AI task is logged (who, what, when, on which source).
Even more powerful with FHIR BI
Transform and route with the Integration Agent, then analyze everything in FHIR BI.