HIPAA & BAA

If your calls touch Protected Health Information (PHI), OpenPhn supports a HIPAA mode that hardens PHI handling — but only once a Business Associate Agreement (BAA) is on file. The two are linked: HIPAA mode cannot be turned on without a signed BAA, and revoking the BAA turns HIPAA mode off in the same step.

Both live under Settings → Compliance and are owner-only.

1. Record the BAA

Attest to a counter-signed BAA. OpenPhn stores an audit reference (signer, date, document URL) — the file itself is not uploaded.

POST /v1/tenants/me/baa
{
  "baa_document_url": "https://docs.example.com/baa.pdf",
  "signed_by_email":  "legal@acme.test",
  "signed_by_name":   "Jane Counsel"
}

GET /v1/tenants/me/baa — read the current BAA state.
DELETE /v1/tenants/me/baa — revoke. This auto-disables HIPAA mode.

2. Enable HIPAA mode

PATCH /v1/tenants/me/hipaa_mode { "hipaa_mode": true }

With HIPAA mode on, OpenPhn:

Locks PII redaction on — it can't be turned off while HIPAA mode is active.
Quarantines PHI in telemetry — transcripts and analytics route through the quarantine path instead of standard logging.
Stamps per-call disclosure certificates with the BAA reference, so each call carries proof it ran under the agreement.

HIPAA mode is a mechanical enforcement layer, not a compliance program on its own. You remain responsible for your own policies, training, and the lawful basis for each call. Revoking the BAA is destructive — it immediately drops PHI enforcement for every call.

Availability follows your plan — see pricing.

1. Record the BAA

2. Enable HIPAA mode

On this page