Fluent Care, connected. Talk with our team ↗
Menu

New federal health IT awards put workflow control and lab data quality in focus.

Labeled blood-sample vials at the NIH Clinical Center.
Blood-sample vials photographed at the NIH Clinical Center. This photograph does not depict the funded projects. Photo: Daniel Sone / National Cancer Institute / Unsplash.

Two new projects address different parts of the same problem: how software takes an authorized next step, and whether the data supporting that step can be used reliably.

Two awards, two concrete problems

On October 6, ONC announced two LEAP in Health IT awards totaling $1.5 million. One supports work on patient-controlled, verifiable clinical AI workflows. The other addresses laboratory terminology and interoperability gaps in small, independent laboratories.

The announcement describes projects to develop and evaluate approaches. It is not evidence that a finished clinical AI system has improved outcomes or that laboratory data problems have been solved.

An available result is not always usable data

The laboratory project plans to assess readiness, identify terminology problems, apply targeted improvements and validate the implementation. For a receiving workflow, a result needs enough consistent meaning to be interpreted in context. Merely delivering a document into another system does not settle that question.

The clinical AI project, meanwhile, puts control over execution and verification of actions at the center of its design. These are useful research questions for any system expected to do more than generate a response.

What to carry into an integration pilot

Our editorial recommendation is to test three distinct things: what information arrived, how it was interpreted and what action was permitted. Keep the source record available to the reviewer. Treat ambiguous mappings as unresolved work rather than silently choosing a meaning.

For a synthetic follow-up case, the team should be able to explain why a task exists, who authorized the next step and what happens when the source changes. Those questions are useful before selecting a model or adding another integration. The new awards make the development priorities visible; their results still need to be evaluated.

Sources & reporting notes

Reporting checked October 26, 2026. Source facts are linked above; operational recommendations are Fluent’s editorial analysis.

Related articles

Discover how healthcare teams are transforming patient access with Fluent.

A doctor writing in a clinical chart.

October 26, 2026 · Insurance operations

An October 21 CMS and Labor Department announcement brings self-funded employers into the prior authorization reform effort. What clinics should verify before changing their process.

A physician reviewing paperwork in a hospital.

October 26, 2026 · Clinical operations

A September 30 ONC update separates documentation burden from prior authorization and external-record retrieval. Why a single time-saved number misses the workflow.

A clinician reading medical documents.

October 25, 2026 · Clinical documentation

An October 12 paper proposes a framework for reviewing AI-generated clinical notes. What changed, what the research does not establish, and why it matters for medical documentation.

A wheelchair in a clinical building.

October 25, 2026 · Insurance operations

Medicare’s probationary prior authorization process began October 15, 2026 for certain DMEPOS suppliers. Why supplier, item and enrollment context matter at intake.

A clinician and patient discussing information during a consultation.

October 25, 2026 · Industry news

A new NHS ambient voice technology adoption programme launched in October 2026. Why clinical workflow, local assurance and evidence matter throughout an AI scribe rollout.