Security & compliance
Built like the data
matters. Because it does.
A clinical record is the most sensitive data a person has. This is not a page written after the fact, it describes the architecture itself, and it says plainly where we are today.
The posture
Six things that are true of the running system.
Encrypted everywhere
Data is encrypted at rest with managed keys and in transit with TLS, including every internal hop between the application and the database. There is no unencrypted path to the record.
Isolated by design
OmniEHR runs on dedicated, single-purpose infrastructure in its own private network, with per-tenant separation and per-tenant keys. The clinical datastore has no public address and accepts connections only from the application tier.
Consent in the data layer
HIPAA and 42 CFR Part 2 protections are enforced where the data lives. Segment-level consent is evaluated on every read, with audited break-glass and revocation, rather than being policed by each application screen.
A defensible audit trail
Every chart open, every clinical write, and every AI-assisted action is attributed and recorded to FHIR AuditEvent through OmniGuard, exportable for real investigations rather than compliance screenshots.
No silent overwrites
Chart-level locking coordinates concurrent clinicians with request, grant, deny, and audited takeover, so two people working the same chart is a negotiation the system records rather than a race one of them loses.
AI that answers to humans
Ambient documentation and agentic workflows operate behind human gates: drafts are reviewed, actions are attributed, and nothing enters the legal record without a clinician's attested signature.
Where we are today
OmniEHR is in active development on HIPAA-eligible cloud infrastructure under a Business Associate Agreement. The current environment runs synthetic data and is labelled as such inside the product. ONC Health IT certification is a funded milestone on the roadmap, not an assumption, and capabilities that depend on it, such as certified eCQM submission, are described that way wherever they appear.
We publish our posture plainly because trust in healthcare is earned with specifics. For security questions, disclosure reports, or due-diligence requests, reach us through the early access form and mark your role accordingly.