Clinical software built from inside the workflow
Lumen was founded by Anthony Narine, a vascular technologist and software engineer with 17 years of experience inside vascular diagnostics. He is designing and engineering Lumen as a modern clinical platform for diagnostic reporting, imaging workflow, protocol management, interoperability, and clinical operations.
Anthony Narine
Founder & Clinical Software Engineer
17 years in vascular diagnostics · Full-stack engineering · Clinical systems architecture
17 years in vascular diagnostics. Now building the clinical infrastructure I wished we'd had.
After years of performing studies, working through complex protocols, training technologists, and using reporting systems that often made clinical workflows harder than they needed to be, Anthony began building the infrastructure he wished vascular labs already had.
“I didn't learn the vascular workflow by interviewing clinicians. I spent years inside it. Lumen started with a simple question: what would this software look like if it were built by someone who actually had to use it?”
Built to cause the least friction, for both sides of the report
A technologist and a physician want different things from the same exam. Lumen wasn't shaped by one opinion — Anthony built it by taking questions and friction points directly from coworkers on the technologist side and the physicians reviewing their studies, and designing toward whichever answer reduced friction for both, not just one.
Lumen takes a different approach. Clinical measurements, protocols, diagnostic criteria, workflows, facilities, users, reporting rules, and integrations are modeled as explicit parts of the platform, so Lumen can support the realities of an individual laboratory while still operating as a larger enterprise system.
“After enough years using clinical software, you start seeing the same problems repeatedly. The workflow is complicated, but the software doesn't have to make it more complicated.”
Clinical infrastructure underneath the workflow
What clinicians see is only one part of Lumen. Anthony's work spans the full product stack — from the clinical workflow clinicians see to the infrastructure required for healthcare systems to operate securely behind it.
That shows up across the platform: identity kept separate from clinical authority and tenant boundaries enforced structurally (see Security), a reporting engine built around explicit clinical state (see Product), imaging treated as part of the clinical workflow rather than a separate system (see Imaging), and integration designed in from the start (see Interoperability). Lumen is not built around technology for technology's sake — every engineering decision starts with the clinical workflow.
Explain clinical truth. Never invent it.
Lumen uses AI differently from many healthcare products. The model is not the source of clinical truth — approved protocols, diagnostic criteria, institutional configuration, and clinical records remain authoritative.
“AI should make clinical knowledge easier to access. It should never quietly become the authority.” See how Lumen's AI clinical knowledge layer works.
Not something added before deployment
Clinical systems protect real patient information and real clinical workflows. Lumen therefore treats security as part of the underlying architecture — identity, tenant isolation, facility boundaries, permissions, auditability, observability, and controlled system changes are designed in from the beginning.
Lumen also works alongside Gait, a separate identity and security platform built specifically to protect Lumen — it monitors authentication and security controls, investigates findings, validates repairs, and preserves human authority over production changes. Read more about Lumen's security architecture.
Intelligence can recommend. Authority remains explicit.
Build diagnostic software clinicians actually want to use
Lumen begins with vascular diagnostics. The larger goal is to build modern infrastructure for diagnostic medicine: systems that understand clinical workflows deeply, integrate cleanly with hospital environments, protect patient information, and remain adaptable as medicine changes. Anthony is building Lumen from both sides of that problem — the exam room and the engineering desk.
Talk with the person building Lumen
Bring your workflow, your protocols, or just your skepticism — the conversation is with the engineer, not a sales script.