Viewing the Canadian model

Sovereign by design, enterprise by default

The full stack of sovereign clinical AI.

Criticalinsights, founded by clinicians and AI engineers, builds clinical AI that lives entirely inside the institution: the compute, the bedside intelligence, the governed clinical knowledge, and the connection to patients and families. Nothing leaves the boundary, and no third party holds the keys.

AI infrastructure · Governed platform · Clinical products

Criticalinsights builds the on-site AI computing hardware and software that lets a hospital run governed modern clinical AI without sending any patient data outside its walls.

In plain terms

What Criticalinsights actually does, in plain terms

The problem

Machines that don't talk, AI that sends data out

Hospitals have lots of machines and systems, bedside monitors, the electronic record, devices in the room, that don't talk to each other well. And most "AI" tools a hospital is offered send patient data out to someone else's cloud to do the thinking. That raises privacy, control, and cost questions.

What we do

The computing lives inside the hospital

The opposite. We install the computing inside the hospital itself, connect all those machines into one intelligent picture, and run the AI on the hospital's own hardware under the hospital's own rules. No patient information leaves the building, and no outside company holds the keys.

What sits on top

Tools clinicians actually use at the bedside

A handful of tools clinicians actually use at the bedside: a critical-care dashboard, a system that answers clinical questions from the hospital's own approved references, ambient documentation that drafts a note for the clinician to sign, contact-free sensing of the patient, and a family app that keeps relatives informed.

The governance part

The hospital sets the rules

The hospital sets the safety rules and the approvals, every AI suggestion stops at a clinician for a final decision, and every action is logged.

How it fits together

One sovereign foundation. Everything governed.

Criticalinsights builds the foundation. Clinical AI runs on top of it: ours, the hospital's own, or any vendor's, all governed the same way.

INSIDE THE HOSPITAL BOUNDARYNothing sits outside it.
Every tile above the line runs under the institution's policies. Ours or anyone's.
ExploreHover, tap, or tab to any part of the stack to see what it does.

Engineered for the standards North American healthcare runs on

  • HL7 FHIR
  • SNOMED CT
  • LOINC
  • ICD-10-CA / ICD-10-CM
  • National drug identifiers (DIN / NDC)
Human in the loop, by design

The safety property built into the platform, not a setting on top of it. A qualified human holds the judgement and the accountability: every model, agent, and workflow is designed to inform that person and stop at them.

A clinician decides

The system surfaces evidence, risk, and reasoning. It does not order, prescribe, or act on a patient. Every clinically consequential step waits on a named person with the authority to take it.

Approval before action

Anything sensitive routes to explicit human approval before it takes effect. The approval gate is enforced in the platform itself, not left to policy documents or user discipline.

Reasoning shown, not hidden

Every output carries what it drew on, what it was missing, and how it was formed, so the reviewing clinician can accept, question, or reject it on the evidence rather than on trust.

Accountability stays human

The operator, the custodian, the key-holder, and the approver are the institution's own people. Clinical accountability is never transferred to a model or to us.

Sovereign by design, enterprise by default

System architecture

The bedrock of sovereign healthcare AI.

CRATON, the Criticalinsights sovereign stack

Data residency follows stewardship at every tier. Patient information stays with the organization legally responsible for it; only structure and learning move between tiers.

Read the architecture in depth

Products

Clinical products on one sovereign foundation

Sovereign platform

SALVEA

The hospital's control layer for AI: one governed runtime for every assistant, agent, and workflow, deployed single-tenant inside the institution's boundary. The institution sets the boundaries, the safety rules, and the approvals; SALVEA enforces them everywhere with role-based access, human-in-the-loop sign-off, and a complete audit trail. Zero data egress, the clinician's final say.

Explore SALVEA

Critical care

TRIMPACT

The bedside critical-care platform: TRINITY, the intelligent bedside integration hub, and IMPACT, the clinical dashboard on top of it. Continuous capture from monitors, devices, and record systems, with risk computed on premises.

Explore the bedside platform

Clinical reference

CELSUS

The institution's own approved monographs, protocols, and guidelines: version-controlled, pharmacy-governed, and reachable by every clinician at the point of care. No patient information is entered, processed, or stored.

Explore CELSUS

Grounded answering

CECI

The answering agent for the approved library. Clinicians ask in plain language and get an answer cited to the institution's own document and version, or an explicit no source found when the library is silent.

Explore CECI

Documentation

MINIM

Ambient clinical documentation. The encounter that was going to happen anyway becomes a structured draft note on the unit's own compute, and reaches the record only when a clinician signs it.

Explore MINIM

Contact-free sensing

FIGURA

Posture, movement, and presence in the bedspace, read as geometry rather than imagery. Joints and limbs only: no face, no likeness, and no video stored or transmitted anywhere.

Explore FIGURA

Families

CHICKADEE

The family app. Families stay connected to their loved one's journey through the admission, with updates and family-readiness materials that build up over time, governed by the care team.

Explore CHICKADEE

TRIMPACT, CELSUS, CHICKADEE, MINIM, CECI, and FIGURA run on SALVEA and CRATON.

Governance architecture

Why institutions choose this model

01 / Residency

Processing happens on hardware inside the facility. Nothing is sent to a third-party cloud service, and no outside party processes clinical content.

02 / Economics

Institutional infrastructure rather than token-based pricing. Adoption can grow across the hospital without per-user costs growing with it.

03 / Control

Existing technology teams, and hospital-held keys and policies. The institution remains the information steward throughout.

04 / Audit

Every action and every AI response is logged, versioned, and reviewable, so clinical decision support stays accountable.

How adoption works

One unit at a time, governed from the start

  1. Step 01

    One unit opts in

    A scoped use case and a small clinical team, chosen by the site.

  2. Step 02

    Governed from the first day

    Policies, access, and audit are active before the first question is asked.

  3. Step 03

    Evaluated before it expands

    Results are reviewed against the site's own criteria, in shadow mode first.

  4. Step 04

    Expansion by invitation

    The site decides whether to widen the deployment, and on what timeline.

Common questions

What does this actually do to our hospital?

Plain answers to the questions hospital leaders ask first.

We connect what your hospital already has into one intelligent, governed environment: bedside devices and monitors, the record systems, contact-free sensing in the bed space, and the hospital's own clinical knowledge. Intelligence starts at a single bed and scales to the unit, the department, and the whole hospital, on compute the hospital owns and policies the hospital sets. Patient information stays inside, and your teams run it.

Governance & trust

Built for the privacy and security review that comes first

Encryption, SSO/SAML identity, role-based access, and a complete audit trail, with documentation available under NDA.

Read our governance posture

Bring sovereign clinical AI into your institution.

We work with clinical, privacy, and information-management leadership to scope a deployment your teams can absorb and operate. Briefings are held under NDA.

Request a technical briefing.