Solutions
Governance first, then scale
Hospitals need role governance, escalation and an audit trail before any of the rest. Those pieces are in the pilot. The clustered on-site deployment is designed and not built; a single on-site hub exists.
In the pilot Pilot
- Hospital preset: all 36 pieces, dark interface, 14-character passwords.
- A server-enforced permission matrix of 23 role classes and 103 actions.
- Scheduling, coverage, billing, printing, decision support, e-prescribing and a patient portal, with the outside connections simulated.
- Four-level chain of command for alerts and escalation.
- Per-facility code catalog with propose-then-approve by a different person.
- Break-glass with mandatory privacy review; VIP flags.
- Two-person approval for privileged user changes.
Designed, not built Designed
- Clustered on-site servers with zones and a reserve.
- Federated ledger of hashes, consent records and audit events (patient records never go on it).
- Hardware-level hardening, such as a sealed read limiter.
- A real interface engine and live HL7, FHIR, DICOM and X12 connections (today these are simulated).
Hospital pricing is set with each hospital. Pricing.
Reality check
Hospitals will ask for security certifications, interfaces and uptime commitments. We make none of those claims. Every one of them appears in the help center with an honest answer.
Talk to us about hospitals
A short walkthrough on synthetic data. No patient information needed.