Each job gets the AI that fits it.
Booking, intake, the visit and follow-up need different information and different checks. A job-specific engine takes on that difference.
AetherHeal Whitepaper v2.1 · 2026.09.13
The structure that connects work.
The boundaries that keep it accountable.
How can work prepared by several AI engines become one connected care workflow? This paper describes Clinical OS, the layer for shared patient state, and the Golden Clinical Loop, from physician review to evidence of completion. Clinical OS works beside the existing chart.
01 · Core proposition
Carrying unfinished work
through to accountable execution.
The chart records what finished. We handle what has not finished yet.
Purpose-built AI engines for each job in care, and a Clinical OS that keeps them on one patient state under one line of physician authority.
The paper explains how job-specific AI connects into one patient's work, and what the physician confirms inside Golden Clinical Loop.
02 · Three principles
One engine per job.
One patient state.
The physician confirms.
Patient state stays continuous.
Where the patient stands is visible in one place, together with evidence, authority, decisions, owner and completion.
The physician confirms the next action.
Proposal, confirmation, execution and verification are kept apart, and authority over clinical judgment, treatment, correction and exceptions stays with the physician.
03 · ΔC
A way to count finished cognitive work.
ΔC (DeltaC) is a metering concept we are developing to count healthcare cognitive work that carries the required checks, approvals and closing evidence. It is the unit that separates "AI produced an answer" from "the task is done". The definition and calculation are in the paper.
A synthetic workflow example is at the bottom of the products and platform page.
Whitepaper v2.1 · 2026.09.13
The full whitepaper is available as a file.
This page is the summary. The full text is below. Product status and anything else that carries a date lives in the evidence appendix, which is current as of August 18, 2026.
Edition record Whitepaper v2.1 · 2026.09.13 · Company description aligned to canonical wording, entry-wedge commercial form updated, evergreen paper and dated appendix kept separate.
05 · Library
Documents to read alongside.
Clinical safety document
What the physician confirms, the layers of responsibility, and the wording we use and do not use. Web summary.
Clinical safety →Research collaboration proposal
Which questions we can work on together, roles and data principles. Web summary.
Research collaboration →Evidence record
Status today per product and dated evidence.
Evidence record →
Evidence boundary
We use the present tense onlyfor what the evidence covers.
Per-product validation status, and the limits of what we say publicly, continue in the clinical safety document.
Read the clinical safety document