Skip to main content
Lumen
Vascular ultrasound reporting, built to expand

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.

Solo physician practiceMulti-facility enterprise health system

Vascular is where Lumen begins. It is not where Lumen ends.

Diagnostic pipeline

Live
  1. Order
  2. Exam
  3. Imaging
  4. Measurements
  5. Calculations
  6. Interpretation
  7. Report

Every stage is structured data — reusable across exam types and specialties.

The connected pipeline

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.

Idle
Order arrives
Lumen's clinical process8 stations, one line
Delivered downstream
Ordering clinician

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.

SourceServiceRequest / ORM
SystemEpic
AccessionACC-48219
MRN00491822
FHIR ServiceRequestaccessionMRN
Packet integrity0 / 8 stations
Where Lumen begins

Vascular ultrasound, done thoroughly

Lumen's first fully built specialty is vascular ultrasound — structured worksheets, facility-approved criteria, and automated calculations across the exam types that make up a vascular lab's daily volume.

CarotidRenalLower-extremity arterialVenousMesentericDialysis access

Representative measurements

PSVEDVICA/CCA ratioWaveform patternPlaque characteristics
Imaging and DICOM

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
Study 04821 · CarotidLinked
IMG 1
IMG 2
IMG 3
IMG 4
CINE
CINE

Series: 2 · Instances: 6 · Modality: US

Linked exam segments: Right ICA, Left ICA, Bulb

AI clinical knowledge

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 surfaces the applicable source and distinguishes facility-specific criteria from system defaults — it does not invent policy or replace clinical judgment.

  • Protocols
  • Procedures
  • Diagnostic criteria
  • Measurement technique
  • Reporting standards
  • Accreditation requirements
  • Workflow policy

Synthetic example · not real patient data

What criteria are we using for 70–99% internal carotid artery stenosis at this facility?

This facility uses a modified velocity criteria set for 70–99% ICA stenosis, requiring PSV > 230 cm/s with supporting ICA/CCA ratio and plaque estimate.

Source: Facility protocol — Vascular Lab Criteria, v3 (overrides system default)

What's our protocol for a renal artery study in a patient with a prior renal artery stent?

Retrieving the in-stent renal artery protocol: sampling sites, expected velocity ranges post-stent, and the criteria used to flag in-stent restenosis.

Source: Facility protocol — Renal Artery Studies, Post-Intervention section

Billing preparation

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.

The billing assembly line

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.

Interoperability

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.

LumenReporting & imaging core
EMRStructured report delivery
HL7ORU messaging
DICOMImaging objects & metadata
PACSDesigned for future integration
Interface enginesRouting and transformation
Billing systemsStructured revenue-cycle handoff
Healthcare security

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
Planned expansion

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.

Chamber measurementsDoppler valuesVentricular functionValve measurementsCalculated cardiac metricsPhysician interpretationImage and cine review

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.