Integrations
Standard HL7, zero new Epic work
Lumenly generates industry-standard HL7 v2.x messages validated against Epic's production interfaces. They import through your existing Mirth Connect or Rhapsody configuration — no new interfaces, no Epic project.
Primary Integration
Built and validated for Epic
Every HL7 message Lumenly generates is validated against Epic's production sandbox and Epic's Incoming Clinical Documentation Flowsheet interface.
AvailableEpic (2020 and later)
Full ADT, ORM, and ORU message support tested with Epic production environments at regional health systems. Uses Epic's existing inbound interfaces — no new interface builds required.
- ADT^A08 for encounter reconstruction
- ORU^R01 for vitals and lab results
- ORM^O01 for order recovery
- Incoming Clinical Documentation Flowsheet for structured flowsheet data
- Downtime MAR CSV import for medication recovery
Your Epic TC doesn't need to be involved
Lumenly uses interfaces your Epic environment already has active. The Incoming Clinical Documentation Flowsheet is standard for any organization running clinically-entered flowsheets. Mirth Connect or Rhapsody already handles inbound HL7 — we're just another feed.
No new interfaces to build
Uses existing inbound HL7 config
No Epic project required
No TC approval needed beyond confirming interface is active
No new Epic credentials
Messages delivered via your interface engine, not direct API
Standard import workflow
Imports exactly like any other HL7 feed
Running a non-Epic EMR?
Lumenly generates standard HL7 v2.x — if your EMR supports inbound HL7 interfaces, integration is technically feasible. Contact us to scope it.
Message Types
HL7 v2.x message types
Three message types covering the full scope of downtime documentation. All messages are validated before export.
Update Patient Information
Encounter & registration reconstruction
Used to restore visit records, patient demographics, admit/discharge/transfer events, and attending physician assignments.
Order Message
Medication orders, lab orders, imaging
Reconstructs orders placed during downtime — medications, lab work, imaging requests, and specialist referrals.
Observation Result
Vitals, lab results, clinical observations
Carries structured clinical data: vital signs, intake/output, nursing observations, and point-of-care lab values.
How it works
How integration works
No custom development required. Lumenly produces standard .hl7 files that your existing interface engine can import exactly as it does from any other source system.
Validate & Approve
Clinicians review and approve AI-extracted data in Lumenly. Every field is confirmed before export.
Download .hl7 File
Hospital IT downloads the .hl7 file from the Lumenly portal, or Lumenly delivers it via SFTP to your interface engine.
Import Through Your Interface Engine
Drop the file into Mirth Connect, Rhapsody, or any HL7 listener. It imports like any other inbound feed.
Compatible interface engines
Mirth Connect
Open source, most common
Rhapsody
Orion Health
Cloverleaf
Infor
Iguana
iNTERFACEWARE
Ensemble / HealthShare
InterSystems
Custom MLLP listener
Direct TCP delivery
No interface engine?
For facilities without an interface engine, Lumenly can deliver messages via direct SFTP or provide detailed import instructions for manual import using Epic's built-in HL7 tools.
Discuss your setup →Ready to test it?
See a live HL7 export
for your environment
In a demo we'll walk through a live HL7 export and show exactly how it imports through your interface engine. Bring your Epic TC or interface team.
Schedule a Technical Demo