Security & Compliance
A straight answer on where things stand today, and what's on the roadmap before a pilot handles real patient data at scale.
Encryption, access control, audit logging
Data is encrypted in transit (TLS) and at rest in our Postgres database. Staff access to the clinical console requires an authenticated account with an explicit clinical role grant (nurse / physician / admin) — there is no shared login. Every action that touches patient data is written to an append-only audit log (who or what device, what action, when), independent of the record it's logging, so logging a failure never blocks real clinical work.
BAA availability and formal HIPAA assessment
We don't describe ourselves as "HIPAA compliant" — that's not a status a vendor self-declares, it's something assessed jointly with a covered entity, backed by a signed Business Associate Agreement. A BAA and a formal HIPAA security-rule assessment are both planned ahead of any pilot that handles real patient data outside of a sandboxed/synthetic environment, not something available today.
SOC 2
A SOC 2 Type II audit is on the roadmap but has not started. We'll update this page the moment that changes — not before.
Data residency
Data currently resides in a US-region database. Region-specific residency commitments for international deployments aren't yet formalized and would be scoped per site.
Our FDA approach
JegsMediScan is not FDA-cleared and does not provide a medical diagnosis — it is decision support, and a clinician's judgment is always the final word, not a suggestion from this product. Any path toward FDA clearance (most likely as Software as a Medical Device) would follow real-world shadow-mode validation first — see our evidence page for exactly where that validation stands today.