Security & trust
Every tool is born onto the rails. None of them reinvent trust.
The expensive part of healthcare software was never the code. It was the trust: encryption, access control, audit, change control, and the paper trail that proves it all. Here that layer is the foundation every tool inherits on day one, not a checklist each tool starts over.
“Your EHR stays the system of record for the chart. Our tools keep the record of your program's work and the minimum patient identity they need; every stored copy of chart data is named, bounded, and switchable, on the record.”
Patient data
Your EHR stays the system of record.
The chart stays in your EHR, and tools read it there when they need it. What a tool keeps is the record of your program's work and the minimum patient identity that record needs. Where a tool keeps a copy of chart data, that copy is named field by field, justified, approved by your people on a recorded decision, encrypted, bounded by a retention window or a switch, and your compliance office can read the list any time. There is no shadow chart and no second source of truth: the footprint is the smallest that still does the job.
Said carefully, because precision matters here: this posture shrinks risk. It does not exit HIPAA. Displayed chart data is still protected health information in transit, and we treat it that way.
The rails
What every tool inherits.
Field-level encryption
Tamper-evident audit trail
Clinical-grade sessions
Role-gated access
The decision log
The documentation pack
Isolation
One instance per institution. Isolation by construction.
Your institution's tools run in one application that is yours alone: your own database, your own deployment, no other customer on it. Cross-institution isolation isn't a filter we promise to apply. It is the architecture. The platform surfaces we use to build and operate are kept separate from your instance and hold no patient data at all, ever.
The claim
The claim, said right.
Tools built here run on SOC 2-ready architecture implementing the HIPAA Security Rule's technical safeguards, and we maintain a compliance program to match. SOC 2 is an audit outcome and HIPAA compliance is a property of an operating organization. Anyone who tells you their codebaseis “HIPAA certified” is selling something. We give your auditors the architecture, the evidence, and the paper trail.
You'll notice this page makes no claims of certification. That is deliberate, and it is the same discipline that runs through every decision card in the product: plain claims, named exceptions, evidence over adjectives.
Change control
Change control your CAB will recognize.
Every tool moves Preview, then Pilot, then Live, and each gate is a recorded sign-off by your people: staged, recorded, and reversible. Updates ship on a scheduled release train with a separate emergency lane for security fixes, and your admins see a release log of what changed and when. Scrutiny scales with data sensitivity: a tool that stores nothing patient-linked can take the fast path; a tool holding named patient fields pilots mandatorily.
Exit
No hostages.
Your decision log is readable from day one, and if you ever leave, you take your data, every record and your complete decision logs, cleanly exported in open formats. Continuity beyond that is an escrow or exit-license arrangement. Platform-side operational records are erased on the agreement's deletion schedule. We keep customers by being worth keeping.