Scope, Honestly Stated
What We Don't Do
Lumenly is deliberately narrow. Understanding our scope is as important as understanding our capabilities.
In scope — what Lumenly handles
What we don't do — and why
Each of these is a deliberate decision, not a gap. Understanding the reasoning helps you evaluate whether Lumenly fits your scenario.
Charge capture and billing recovery
Charge recovery requires per-org CPT/procedure master mapping, and filing charges from a third party creates serious compliance liability. Hospitals already have manual charge recovery workflows post-downtime. We extract what was administered and documented — not what should be billed.
Physician order recovery
Order entry requires clinical decision support context, pharmacy interaction checking, and provider authentication that cannot be automated from paper. Orders must be re-entered directly by the ordering provider.
Ambient documentation (live patient encounters)
We solve the physical paper recovery problem — handwritten charts created during system outages. Ambient AI tools like Nuance DAX transcribe live clinical conversations. These are different problems, different pipelines, and different regulatory postures.
Lab result interpretation
We extract lab result values from paper requisitions and result printouts. We do not interpret results, generate clinical decision support alerts based on lab values, or interface with lab information systems. That is LIS territory.
ADT event management
Registration and ADT (admit/discharge/transfer) events during downtime require patient identity verification and bed management workflows. We assist with facesheet data extraction and patient record reconstruction — but live ADT event processing is your registration team's domain.
Fully automated EMR filing (no human review)
Every AI extraction requires clinician validation before export. We will not ship a black-box that writes directly to your EMR without human sign-off. This is a deliberate design choice — not a limitation. Regulatory defensibility requires a human in the loop.
Multi-EMR coexistence (two EMRs simultaneously)
Lumenly is built for Epic environments. Organizations running two EMRs in parallel (e.g. post-merger) would need separate configurations per system. Lumenly generates standard HL7 v2.x, so non-Epic environments are technically possible — contact us to scope before signing.
Replacement of your interface engine
Lumenly generates standard HL7 v2.x files. Your existing interface engine (Mirth Connect, Rhapsody, Cloverleaf) is still required to route messages to Epic. We work with your infrastructure — not around it.
Mobile app offline capture (not yet GA)
Offline mobile capture is on the roadmap. The current iOS/Android app requires connectivity. If your scenario requires fully disconnected capture during an active network outage, discuss this with us before signing.
Start free.
Upgrade when you need it.
The next outage isn't a matter of if. Generate your downtime kit now — no PHI, no credit card, no contract.