Sovereign by design, enterprise by default
Enterprise-grade clinical AI, owned and governed by your health system.
Criticalinsights™ puts a sovereign clinical-AI platform inside your health system's own boundary: one governed runtime that serves every member hospital, across every state you operate in. We hold no custody of patient data, hold no keys to your systems, and process nothing in the cloud. Your clinicians get sub-second decision support at the bedside; your enterprise keeps the keys, the policies, the audit trail, and the economics.
Engineered for the standards US healthcare runs on
- HL7 FHIR
- SNOMED CT
- LOINC
- ICD-10-CM
- National drug codes (NDC)
Sovereign by design, enterprise by default
What we deploy
One platform, four tiers, every member hospital
CRATON, the Criticalinsights™ sovereign stack
We build the platform from the bed space up to the enterprise, so a single governed runtime spans an entire health system. Each tier does a specific job, and nothing leaves your boundary.
Enterprise AI hub
The governing layer for the whole system. Enterprise policy, identity, model governance, and audit are set once by the system, and every member hospital inherits it, no matter how many states it spans. You govern; we serve the runtime.
Facility infrastructure
Compute inside each hospital, operated by your system IT under enterprise standards on a segmented network with no inbound internet exposure. Facilities keep local operation while inheriting enterprise policy.
Unit and department nodes
Local nodes running small and large language models we deploy and govern, sized to a clinical unit or department. Compact workstations and rack nodes rather than construction projects.
Edge AI at the point of care
Sub-second analysis at the bed space, with device-data gateways feeding the unit tier, the moment where governed AI meets the clinician.
What we do
Bring governed AI to every facility, without giving up control
We deploy single-tenant inside your system's boundary, on your premises, under your identity. Clinical processing never leaves your network, and we never become a custodian of your patient data.
- Designed to operate within HIPAA and applicable state law
- Single-tenant deployment inside the system's boundary, with zero data egress
- No business-associate data sharing with outside cloud services for clinical processing
- SSO/SAML against the system's identity provider, with role-based access
- System-held keys, policies, and a complete audit trail
The difference it makes
One system, many facilities, many states
Set enterprise governance once; every member hospital inherits it. Expand facility by facility on your timeline, with per-facility configuration where state law or local policy differs. The economics are owned-infrastructure, not per-user, so adoption can spread across your system without cost growing with every clinician.
- Enterprise governance set once, inherited by every member hospital
- Per-facility configuration where state law or local policy differs
- Data residency in the United States, in the system's own environment
- A scoped pilot at one unit, then expansion facility by facility on the system's timeline
Governance checklist
What your teams can verify before rollout
The four areas your compliance, security, and clinical teams review first, and the answers we give at a technical briefing. Bring this to your governance committee and mark it against your system’s own criteria.
Authority
The health system governs its own AI deployment, within state law. Enterprise policy binds every member facility, while remaining subject to the licensing and regulatory authority of each state in which a facility operates.
- Named enterprise owner and clinical sponsor at the system level
- Enterprise governance set once, inherited by each member hospital
- Per-facility configuration where state law or local policy differs
- One scoped unit pilot approved before any facility rollout
Residency and processing
Protected health information stays inside the system's own environment; no outside cloud service processes it.
- Single-tenant deployment inside the system's boundary, with zero data egress
- Compute runs on premises under the system's control
- Data residency in the United States, in the system's own environment
- Designed to operate within HIPAA and applicable state law
Identity and access
Enterprise identity already spans facilities and states, and remains the source of truth.
- SSO/SAML against the system's identity provider
- Role-based access consistent across facilities, with local overrides where required
- Encryption at rest and in transit, with system-held keys
- No business-associate data sharing with outside cloud services for clinical processing
Clinical oversight
Clinicians decide; the system informs. Evidence from one facility governs expansion to the next.
- Shadow-mode first, observing and logging only, before any workflow change
- No autonomous diagnosis, and clinician oversight at every step
- Complete audit trail on every interaction, held by the system
- Evaluation against the system's own criteria before facility-by-facility expansion
Why health systems choose us
Sovereign by design, enterprise by default
01 / Governed by your system
The health system governs its own AI deployment: enterprise policy, identity, and audit set once and inherited by every member hospital, within the law of each state in which a facility operates.
02 / Economics that scale
Owned infrastructure rather than token-based pricing, so adoption spreads across facilities without per-user cost growth. Your investment compounds as more units go live.
03 / No third-party control
No outside operator, custodian, key-holder, or licensor controls your system. Clinical processing never leaves your premises, and we never hold custody of patient data.
04 / Audit across the enterprise
Every action and every AI response is logged, versioned, and reviewable across the enterprise, the evidence your compliance and clinical teams need for facility-by-facility expansion.
Where to start
Products, as they land in a US health system
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: zero data egress, the clinician’s final say.
Explore SALVEA →TRIMPACT
The bedside critical-care platform, single-tenant inside the system's boundary with enterprise identity, policy, and audit.
Explore →CELSUS
Governed clinical reference aligned to system formulary and pharmacy-controlled content across member hospitals.
Explore →CECI
Grounded answering over the system's approved library, with a citation on every answer and no source found when the library is silent.
Explore →MINIM
Ambient documentation drafted on system compute, signed by a clinician before anything reaches the record.
Explore →FIGURA
Contact-free bedside sensing as geometry only, with no likeness produced and no imagery stored across member hospitals.
Explore →CHICKADEE
The family app, keeping families connected to their baby's journey across the admission.
Explore →Request a technical briefing. · held under NDA
Operating in Canada instead?
US operations: Dallas, Texas.