Clinical reporting.
Imaging.
AI-guided knowledge.
One connected workflow.
Lumen connects structured reporting, DICOM imaging, clinical criteria, physician interpretation, interoperability, and billing preparation in one configurable platform.
Vascular is where Lumen begins. It is not where Lumen ends.
The Vascular Reporting Engine
Vascular ultrasound is not one exam. It's a family of diagnostic workflows that share infrastructure but differ sharply in protocol, measurements, calculations, criteria, and reporting. Lumen runs all of them through a single exam reporting factory — each study plugs its own clinical rules into a shared pipeline and inherits the same security, tenancy, workflow state, auditability, imaging, and hospital integration underneath.
Domains on the engine
built and demonstrable todayThe vascular engine
One configuration layer. Not a separate application.
- Anatomy
- Rules
- Language
- Schema
Cerebrovascular
- Carotid
Peripheral arterial
- Lower-extremity arterial
- Upper-extremity arterial
Physiologic arterial
- ABI
- PVR / segmental pressures
Peripheral venous
- Lower-extremity venous
- Upper-extremity venous
- Venous reflux
Visceral vascular
- Renal
- Mesenteric
- Aortoiliac / aortic
- IVC
Dialysis access
- Hemodialysis access
Postoperative surveillance
- Bypass graft
- Pseudoaneurysm
- Targeted follow-up
One engine. Domain packs are configuration, not separate applications.
Why vascular first
Vascular is Lumen's first engine precisely because it is the specialty that breaks rigid reporting software: many exam types, facility-specific protocols, complex measurements, derived calculations, diagnostic criteria, imaging, and highly structured reports. An engine that survives vascular is an engine that generalizes.
Whose criteria
Diagnostic criteria belong to the lab, not to Lumen. Another facility loads its own criteria and the same engine grades the same velocities differently — and the reading physician still signs every report.
From an Epic order to storage
One packet. It is born in the EHR, scheduled, captured, measured, signed, then written back to Epic and PACS. Nothing forks off the line.
00 · Epic EHR
The exam does not start in Lumen. It starts as an order in Epic — accession, patient, modality, laterality, reason for exam. Lumen only accepts that packet. It never invents one.
The report and the images belong to the same study
Lumen doesn't treat imaging as an attachment. Stills, cine clips, and DICOM objects are captured, stored, and linked directly to the exam they document — so the report a physician signs and the images behind it are always the same record.
- Still image storage
- Cine clip storage
- DICOM object handling
- Study and series metadata
- Image-to-exam linkage
- DICOM ingestion and retrieval
- In-app viewing
- Designed for future PACS interoperability
Series: 2 · Instances: 6 · Modality: US
Linked exam segments: Right ICA, Left ICA, Bulb
Ask for the approved answer, not a guess
Lumen's AI layer retrieves and explains approved institutional protocols, procedures, and diagnostic criteria in natural language. It does not speculate: answers are drawn only from documentation your facility has approved, each one names the source it came from, and the same question returns the same answer every time. Facility-specific criteria stay clearly distinguished from system defaults — and nothing here replaces clinical judgment.
- Protocols
- Procedures
- Diagnostic criteria
- Measurement technique
- Reporting standards
- Accreditation requirements
- Workflow policy
No invented answers. If an answer isn't in approved documentation, Lumen says so — it does not fill the gap with a guess.
Deterministic by design. The same question returns the same answer, every time. Nothing is freshly generated per ask.
Always sourced. Every response names the document and version it came from, and whether it overrides a system default.
Synthetic example · not real patient data
This facility classifies a >70% ICA stenosis using a modified velocity criteria set: PSV greater than 230 cm/s, with ICA/CCA ratio and plaque estimate as supporting criteria.
Source: Facility protocol — Vascular Lab Criteria, v3 (overrides system default)Retrieved verbatim from approved documentation — not generated.
The in-stent renal artery protocol specifies the required sampling sites, the expected velocity ranges after stent placement, and the thresholds used to flag in-stent restenosis.
Source: Facility protocol — Renal Artery Studies, Post-Intervention sectionRetrieved verbatim from approved documentation — not generated.
The exam already has the answers. Billing prep should use them.
Because Lumen already understands the exam performed, the measurements taken, the findings recorded, and the diagnosis information in the final report, it can carry that record through billing prep as one continuous flow — not five disconnected features.
Lumen prepares structured information for human review. It does not perform autonomous billing or coding decisions — the checkpoints above surface gaps, a coder still makes the call.
Built to sit inside an existing health-system stack
Lumen is designed to connect outward, not replace what's already in place — wired into the systems a health system already runs on like a harness into an engine block.
From a solo practice to a multi-facility enterprise
Lumen's architecture separates organizations, facilities, and roles at every layer — from identity through data access — so clinical data stays scoped to the tenant and facility it belongs to, whether that's one physician's practice or a multi-site health system.
Built with HIPAA-aligned technical safeguards and designed to support HIPAA-compliant deployment across healthcare environments of every size.
- Centralized identity
- Organization isolation
- Facility scoping
- Authorization policy
- Auditability
- Secure image handling
- Tenant-aware data access
- Protected service communication
Beyond vascular: cardiac imaging
The same reporting engine that powers vascular ultrasound is designed to support cardiac imaging as a future specialty — new measurements and criteria configured on the existing platform, not a new application.
Cardiac imaging capabilities are planned expansion and designed to support future release — not part of Lumen's current production scope.
Vascular is where Lumen begins.
It is not where Lumen ends.
See how one configurable reporting engine connects imaging, AI-guided knowledge, and downstream workflow for your clinical environment.