Healthcare · Clinical AI · HIPAA-enforced substrate

AI in clinical decisions
with HIPAA and protocol
enforced before each action runs.

Clinical AI touches life-safety decisions — a drug interaction flag, a device calibration, a patient identity match, a diagnostic suggestion. Every one of those proposals needs to be evaluated against the applicable clinical protocol and HIPAA authority before it reaches the care team. Not logged after. Not reviewed in a separate system. Evaluated before. Structurally.

Vertical Healthcare & MedTech Authority HIPAA · FDA 21 CFR Part 11 · HL7 FHIR Patents 3 issued, zero prior art Stage Spec library in development · Platform Q3 2026
Scroll

01 · The thesis

Clinical AI without a governed substrate is a diagnostic tool with no chain of custody.

Every hospital deploying AI in clinical workflows has the same problem: the AI output arrives in the clinical system without a verifiable chain of custody from the data that produced it. The physician sees a recommendation. They don't see the evidence, the authority under which it was generated, or any structural record that it was evaluated against the applicable clinical protocol before it appeared.

Essence changes that. The clinical AI proposal — drug interaction flag, device alert, diagnostic suggestion — is evaluated against the named protocol authority (the hospital formulary, the FDA 510(k) clearance, the applicable CPG) before it surfaces to the clinician. The clinician decides. The substrate records. The record is first-class: proposal, evaluation, surface, decision — a single governed chain of custody, not four separate systems trying to synchronize.

Detection, never determination. No Aptiv in the healthcare cluster diagnoses a patient, approves a treatment, or clears a device for use. Those determinations require a licensed clinician operating under the applicable standard of care. Essence makes that boundary structural — the substrate surfaces, the clinician decides, and the record makes the distinction unambiguous.
Clinical Workflow Governance

Protocol enforcement before the recommendation surfaces

Every AI recommendation in a clinical workflow — a drug interaction flag, a care pathway suggestion, a diagnostic alert — is evaluated against the hospital's formulary, the applicable CPG, and the HIPAA minimum-necessary standard before it reaches the care team. The clinician sees a governed surface, not a raw model output.

MedTech Device Integration

FDA clearance scope enforced in the substrate

Connected medical devices — infusion pumps, diagnostic imaging systems, remote monitoring platforms — operate under FDA 510(k) or PMA clearance scopes. Essence evaluates every device-generated AI output against the cleared indication before it informs a clinical decision. The device's AI is scoped to its clearance by the substrate, not by documentation.

Patient Identity (SecuriSync™)

Identity certainty before the record opens

Patient misidentification is the root cause of a significant fraction of serious preventable harm events. SecuriSync™ is an Aptiv — its behavior is described with Aptiv Specs that Synergy resolves into machine instructions. It governs the identity resolution chain — biometric correlation, MPI matching, HIPAA minimum-necessary access — before the patient record is opened or modified. The identity decision is a first-class substrate event, not a system login, not a middleware integration.

AIRS Physical Object ID

Surgical instrument and supply chain identity governance

Retained surgical items and counterfeit medical supplies are supply chain governance failures. AIRS (Autonomous Identity Resolution System) governs the physical object identity chain — UDI verification, sterilization record, lot tracking, provenance from manufacturer to point of use — as a substrate property, not a barcode scan and a separate tracking system.


02 · The gap

Clinical AI needs a substrate. HIPAA requires a chain of custody. Today there isn't one.

Every HIPAA-covered entity has compliance processes. None of them have a substrate that enforces those processes before an AI system proposes a clinical action. The PHI flows through the model, the recommendation emerges, the compliance documentation happens afterward — in a privacy office, in an audit system, in a HIPAA officer's quarterly review. The chain of custody is reconstructed from logs. Essence makes it structural.

Clinical AI today
AI recommendations surface in clinical decision support systems without a verifiable chain of custody from the data that produced them. The evidence is inside the model. The protocol evaluation is the physician's responsibility to perform independently.
Clinical AI today
HIPAA compliance is a process layer — privacy impact assessments, BAA documentation, minimum-necessary determinations made by humans before system configuration. When an AI system touches PHI in an unanticipated way, the documentation doesn't capture it.
Essence
Every clinical AI proposal is evaluated against the applicable protocol authority and HIPAA minimum-necessary standard before it surfaces. The chain of custody — data source, protocol authority, evaluation record, clinician decision — is structural, not reconstructed.
Essence
SecuriSync™ governs patient identity resolution as a substrate event. Device clearance scope is enforced before device AI outputs inform clinical decisions. The clinician always decides — and the substrate makes the boundary between AI surface and clinical determination unambiguous by construction.

03 · What's next

Healthcare spec library in development.

Clinical Workflow Governance, MedTech Device Integration, Patient Identity (SecuriSync™), and AIRS Physical Object ID are in active spec development ahead of Q3 2026 platform launch. Briefings available for health systems, MedTech manufacturers, and digital health platforms evaluating governed clinical AI infrastructure.