Luminare

Artificial intelligence is claimed and the patented method is rules. Luminare's How It Works page says the product uses "artificial intelligence and our patented patient phenotyping algorithm", and the home page describes a patented phenotyping algorithm that "harmonizes automated monitoring and communication with clinical observation and input".

The company's patent for the screening method (US 10,592,637, granted March 2020) describes determining the presence of systemic inflammatory response syndrome and then whether end organ damage from infection is likely, which is criteria based screening; its other two patents are user interface designs. No learned component is described on the company's pages or in the patent.

Structurally, the human is an input, not an overseer. Most sepsis tools compute a risk score from data and present it to a clinician who may or may not read it. Luminare requires the nurse's assessment as part of the screen, so the system cannot produce an output that a clinician passively ignores. That inverts the usual automation bias problem, and a nurse quoted in the company's own materials makes the point that it does not override her judgment. Nothing is auto closed, auto escalated or suppressed, and there is no low risk output to create an invisible failure mode.

The counterweight is real. This design adds work rather than removing it, its value depends entirely on nurses completing screens every shift, and a checklist completed under time pressure can be completed carelessly. That is why the company's headline metric is compliance.

No false negative behavior, threshold or override analysis is published.

You can tell exactly what this product does, which places it at the transparent end of the sepsis tool market. The screening basis is a named, published clinical standard in SIRS criteria, the second input is the nurse's documented assessment, and the action taken is the hospital's own sepsis protocol rendered in SBAR format. A clinician can trace any output back to a criterion they already know and to their own institution's protocol, and can disagree with either.

The weak point is the enhancement to standard SIRS screening, which is asserted rather than specified, so the one component that differentiates it from a paper checklist is undisclosed. No operating characteristics of the screen are published anywhere.

The substance here is a condition normally left to the contract, disclosed in public instead. The published grant program states plainly that qualifying hospitals receiving free deployments must share data with the company, alongside focus group participation and testimonials. Naming the price of a free deployment in public lets a hospital weigh the trade before entering a sales process rather than discovering it in a redline. What is absent is any definition of what that means.

No privacy policy, data processing statement, retention period, deidentification method or training use disclosure is published, so the scope, duration and purpose of the sharing are unestablished, as is whether the obligation survives the grant period or whether data already contributed can be withdrawn.

A hospital on the grant tier is in a weaker negotiating position than a paying customer by construction, and it is likely to be a smaller or more constrained institution, which is precisely the buyer least able to negotiate terms. Nothing else is named either: no model, hosting arrangement or sub processor list.

Named customers and figures without method. The How It Works page claims nurses save more than 25 minutes per sepsis patient, a sevenfold improvement in clinical reassessment rate, and sets a "30-50% Mortality Rate" before Luminare against "Saved Lives" after, with no source, denominator, comparison group or time period for any of them. Cedars-Sinai is named as a customer.

The one peer reviewed publication, Ferreira, McCants and Velamuri (Journal of Healthcare Quality Research, 2023), is a literature review of machine learning and process improvement in sepsis co-authored by Luminare's chief executive; it argues that prediction alone has not improved outcomes because staff fail to act on alerts, and it does not evaluate Luminare's product. No sensitivity, positive predictive value, alert burden or lead time is published. C.

One disclosure of substance and no governing documentation around it. The published grant program states plainly that qualifying hospitals receiving free deployments must share data with Luminare, alongside focus group participation and testimonials. Disclosing that condition publicly counts in the company's favor.

But no privacy policy, data processing statement, retention period, deidentification method or training use disclosure is published, so what data sharing means in scope and duration is not defined anywhere. It is not stated which data is covered, for what purpose, or whether the arrangement outlasts the grant period.

No statement on business associate agreements, execution terms, cost or subprocessor disclosure is published. Named hospital deployments including a major academic medical center mean agreements very likely exist, and nothing about them is published.

One structural point matters. The company has run two quite different lines of business, and they sit under different relationships. Sepsis detection inside a hospital is ordinary business associate territory: the hospital is the covered entity and the vendor processes its records. The public health products, screening and vaccination management deployed for city and county authorities, are not the same. A public health department operates under its own statutory authority, state public health reporting law applies alongside the federal privacy rule, and records generated there may be public health records rather than treatment records.

Nothing published says which terms govern which line.

Public company databases carry inconsistent signals about its corporate status, while its own materials and recent program participation indicate continuing activity. Nothing published says which legal entity signs, or what happens to data and to the agreement on a change of control.

No attestation, trust center or report request path is published.

Its public sector work is the most useful lead, because those environments generate assurance artifacts by requirement rather than by choice. The company deployed screening and vaccination management products for municipal and county public health customers, and is itself based in Texas serving Texas cities. Texas state agencies and institutions operate a state cloud security authorization program modeled on the federal one, and any federal work of the kind referenced would carry its own authorization requirements. Where such an authorization exists, a documented system security plan and defined boundary exist with it.

So the ask is specific rather than general: which public sector authorizations has the company held, for which products, and can the boundary documentation be shared.

One further question follows from the company's own description of itself. The team is distributed, with staff outside the United States including in Europe. That is unremarkable for a software company and it does mean personnel security, access location and offshore support arrangements are live questions for a vendor whose product reads patient records inside hospitals. Nothing published says who can reach a customer environment or from where.

The company is small and early stage, and the gap is in what a counterparty can verify, not evidence that controls are absent.

Not FDA cleared, and the company has said it operates without clearance on the basis that it makes no claims about lives saved and issues no treatment recommendations, which is in substance a clinical decision support exclusion argument.

Two things are true. First, its exclusion argument is a strong one. The exclusion turns on whether a clinician can independently review the basis for the output, and here the basis is a published screening standard plus the hospital's own protocol, both fully reviewable. Second, there is visible tension between the stated basis and the marketing, since the product's advertised value is providing clear actionable intervention steps, and the site does publish mortality and outcome claims.

Whether the Cures Act exclusion applies is an open question for the vendor rather than a settled legal conclusion.

No subgroup performance, calibration or fairness analysis of any kind is published.

The specific governance exposure here is not algorithmic, it is an incentive structure, and the company states it openly enough to assess. Luminare markets a documented financial case built on increased sepsis capture: a 400 bed hospital coding 80 to 100 sepsis patients monthly is described as likely missing another 20, at $10,000 to $15,000 average reimbursement, framed as up to $3.6 million a year, alongside a clinical documentation improvement program said to lift case mix index by around 10 percent.

Identifying sepsis that was actually missed is the clinical goal, and being paid appropriately for care delivered is legitimate, so this describes a structure rather than an accusation. But a system that prompts staff to screen for and document sepsis, sold on the revenue from documenting more sepsis, points its clinical and commercial incentives in the same direction with no independent check. OmniMD and Droxi Unlock carry the same tight loop. Sepsis coding is already an area of established payer scrutiny, which sharpens rather than softens the question.

A clinician can trace every visible part of this product back to something they can already argue with. The screening basis is a named published criteria set rather than a proprietary score, the second input is the nurse's own documented assessment, and the action is the hospital's own sepsis protocol rendered in a standard clinical handoff format.

So an output points at a criterion the clinician knows, an assessment they wrote, and a protocol their institution authored, and any of the three can be disputed on its own terms. The published parts are the borrowed parts. The enhancement to the standard screen is asserted rather than specified, so the one component that differentiates this from a paper checklist is the one nobody can inspect, and if the enhancement is what suppresses or promotes an alert then it is also the component that decides what a clinician sees. No operating characteristics of the screen are published anywhere, and no warranty, indemnity or remediation commitment is stated.

Named partners rather than a generic integration claim: Microsoft, Cerner, CPSI and the American Heart Association Get With The Guidelines registry are all listed as interoperability partners, and the company presented at the HIMSS Epic Interoperability Showcase in 2021. Bedside data is written directly back into the EMR rather than held in a separate system, which is a two way integration.

CPSI matters more than its profile suggests here, because it serves community and rural hospitals, which is the segment this product is aimed at. Epic presence is showcase participation rather than a marketplace listing or partner review, no FHIR or SMART on FHIR capability is described, and the standalone tier explicitly requires no integration at all, so integration depth varies by tier in a way the pricing structure makes clear but the integration claims do not.

Publishes an implementation ladder with timelines attached: a standalone product needing no integration and offered on a 30 day trial, an Enterprise Lite tier deployable in a few weeks, and a full enterprise platform implemented over months.

For a small hospital, the standalone no integration option is the most practically useful part of the offer. Competing sepsis products require a real time data feed before anything works at all, which excludes facilities without the IT capacity to build one.

Named deployments include an enterprise agreement with Cedars-Sinai from 2023, two CHG hospitals and Cornerstone Specialty Hospitals Clear Lake. A separate onsite consulting workshop offering is described in three stages. Nothing is published on hosting architecture, data residency commitments or technical prerequisites.

A pricing basis is stated without figures. The home page says pricing is "based on a combination of your patient volume as well as your expected ROI", with return on investment typically in two to six months, so a hospital can see what drives the cost before contact.

Earlier company material described three tiers (a standalone product on a 30 day trial, a flat fee Enterprise Lite contract, and an enterprise platform priced per patient day) and a grant program offering free deployments to smaller facilities in exchange for data sharing, focus groups and testimonials; that material may no longer be current. No dollar figures are published.

Deliberately narrow: one condition, sepsis, in adult inpatient acute care. No pediatric or neonatal indication is stated, no ICU specific configuration is described, and no other clinical condition is covered. Narrowness is a strategic choice here rather than a gap, and specialization is arguably why the workflow is as specific as it is, but the coverage is still a single condition.

The wider company also sells products unrelated to sepsis screening, including a vaccination management platform, an emergency response system, a syndromic screening tool and a record abstraction product named Leonardo, with public sector customers including state health departments, FEMA and Department of Defense. Only the sepsis product is described here.