Simple Health Engine

Trust

Protected health information, protected from day one.

This page says what we do with patient data, in plain words, and how to get the documents behind it. A clinic, a pharmacy, a reviewer or a patient can read it in five minutes.

The short version

Your patients' records stay in your EMR. What we hold is protected the way the law expects.

Business associate agreements
We sign a BAA with every clinic, pharmacy, lab and partner that shares protected health information with us, and with every vendor that processes it on our behalf.
Where it runs
Google Cloud, in HIPAA-eligible services, in the United States only, inside a dedicated organisation with the controls that regulated healthcare requires.
Who can see it
Only the clinic's own users for their own patients. Our operators see counts and audit events, never a chart. Agents that run the platform never touch patient data or clinical decisions.
Encrypted, logged, reviewed
Encrypted in transit and at rest with keys we control. Every access is logged to a retention-locked audit trail. Access is reviewed on a schedule.
Records that hold up
Protocol versions, signatures, consents and registry entries are kept as 21 CFR Part 11 style records: who, what, when, and never edited in place.
The clinician decides
The engine proposes. A licensed clinician approves, edits, asks for a visit or declines. Every decision is signed and kept with the record. The software supports clinical decisions; it does not make them.

Safeguards, mapped to the HIPAA Security Rule

Administrative, physical and technical. Each with a control behind it.

AreaOur standardRule
Risk and governanceA written control matrix of 63 controls, each mapped to the rule and reviewed with every change; a threat model; a named security owner.164.308(a)(1)
Workforce and accessNamed operators only, least privilege by role (clinician, clinic admin, front desk, pharmacy, operator, auditor), access reviewed quarterly, removed on departure.164.308(a)(3), (a)(4)
Business associatesBAA with every covered entity and every subprocessor before any protected data flows; a register of agreements with dates.164.308(b), 164.314
Facility and devicesGoogle Cloud data centres (SOC 2, ISO 27001 audited); no protected data on laptops or removable media; operator consoles behind identity-aware access.164.310
Access control and authenticationPer-user accounts, one-time sign-in codes, session limits, tenant isolation enforced in the database, emergency access procedure documented.164.312(a)
Audit controlsEvery read and write of protected data is logged; logs kept in a retention-locked bucket for seven years in production; an alert fires if personal data ever appears in application logs.164.312(b)
IntegritySigned, versioned, append-only records; registry entries chained and anchored monthly so tampering is detectable.164.312(c)
Transmission securityTLS 1.2 or higher everywhere; private database networking; encryption at rest with customer-managed keys rotated on a schedule.164.312(e)
ContingencyDaily backups, point-in-time recovery, a restore drill on a schedule with the result recorded; a documented incident response procedure and breach notification process.164.308(a)(7), 164.400
Software supply chainEvery production release is built by our pipeline, scanned for critical vulnerabilities, signed, and only signed images can run.164.308(a)(1)(ii)(B)

Attestations and reports

What exists, what is scheduled, and what we will send you.

ItemStatusHow to get it
HIPAA Security Rule control matrixIn placeSummary on request under NDA.
Business associate agreementSigned before any data flowsOur standard BAA, or yours, before any data flows.
Google Cloud HIPAA eligibilityIn placeGoogle's own compliance reports cover the infrastructure.
21 CFR Part 11 record practicesIn placeDescribed in the control matrix summary.
Penetration testScheduled 2027Executive summary shared after remediation.
SOC 2 Type IReadiness, then audit after the first quarter in productionReport shared under NDA when issued. Until then we say "SOC 2 aligned controls", never "certified".
Subprocessor listIn placeGoogle Cloud (hosting), our sign-in code delivery providers, and the pharmacy and lab partners a clinic chooses. Full list on request.

Request documentation

Report a concern

If you find a security issue, tell us first.

Write to hello@simplehealthengine.com with "Security" in the subject. We acknowledge within two business days and do not pursue researchers who report in good faith. Our security contact is also published at /.well-known/security.txt.