Security & compliance
How we protect patient data.
Prior authorization touches the most sensitive data in healthcare. Our architecture is designed around the HIPAA Privacy and Security Rules, least-privilege access, and a complete audit trail.
Controls
Security controls.
Business Associate Agreements
We sign a BAA with every customer and maintain BAAs with every subprocessor that touches PHI, including model providers.
Tenant isolation
Each customer's PHI lives in a logically isolated tenant with its own encryption keys; no cross-tenant data access paths exist.
Encryption
TLS 1.2+ in transit; AES-256 at rest; field-level encryption for direct identifiers; keys managed in a cloud KMS with rotation.
Minimum necessary
FHIR scopes and prefetch templates request only the resources a policy needs; note retrieval is bounded by encounter and date window.
Zero-retention AI
Model inference runs under BAA with zero data retention. PHI is never used to train or fine-tune shared models.
Audit logging
Every FHIR read, model call, human edit, attestation, and submission is written to an append-only audit log, exportable to your SIEM.
Access control
SSO via SAML/OIDC, role-based access, just-in-time elevation for support, and session recording for privileged actions.
Human accountability
Clinical attestations are captured from licensed users only. The system cannot submit on its own authority.
Responsible AI
Where software stops and people decide.
Payers decide, clinicians attest
AI assembles evidence. It does not render coverage determinations and does not attest on a clinician's behalf.
Grounded or blocked
Generated text that cannot be traced to a source span in the record is blocked at the verifier.
Transparent rationale
Reviewers see each criterion, its status, the evidence span, and the policy version that produced it.
Measured, not assumed
Model changes ship only after passing per-task evaluation gates; performance is monitored per payer and service line.