GatewayDocsOpen workspace ↗
Developer preview · Synthetic data only Launch status ↗
Documentation/Healthcare & trust

Healthcare access & BAAs

How the intended one-BAA service works, and what must be verified before PHI.

Current PHI status

The production design is one customer BAA with Accountable, with Accountable responsible for the approved downstream provider relationships. The customer does not negotiate a separate BAA for each model made available through that offering.

Check access in your workspace

Open HIPAA & privacy in the dashboard to review your Accountable agreement, PHI-eligible models and API-key access. The page distinguishes your next step from reviews Accountable must complete.

Use Check model access to select a model, data type and optional workspace API key. The check sends no prompt, calls no model and consumes no credits. Workspace eligibility checks the account and route; choosing a key also checks its model permissions, data scope and revocation status. A positive result does not reserve credits or bypass normal request validation, rate limits or budgets.

Healthcare activation

  1. Verify your account and identify the organization and authorized signer.
  2. Review and accept Accountable’s current approved BAA and service terms, and acknowledge the privacy notice and provider disclosure. The saved record contains each document’s exact text, version and hash, the signer, the customer role and acceptance time. A preview practice signature has no legal effect.
  3. Use a route whose downstream agreements, retention, regional processing, commercial permissions, and infrastructure reviews are active.
  4. Receive an eligible healthcare key after the server verifies the prerequisites.

These are platform-enforced prerequisites. An organization name, browser checkbox, or data_classification parameter cannot make an ineligible route healthcare-ready.

PHI on an activated key

A healthcare key treats every payload as potentially containing PHI. The gateway does not require the customer to remove patient identifiers from a properly activated healthcare workflow. Labeling such a request synthetic does not bypass the healthcare checks.

The current supported purposes are administrative_support and document_summarization. This service does not provide a clinical assessment or clinical validation guarantee.

Your application’s responsibility

Design your own authentication, authorization, consent, record handling, client logging, and data lifecycle around your obligations. A provider BAA or a gateway configuration is not a certification of your application’s HIPAA compliance. HHS describes the shared obligations of customers and cloud providers in its cloud-computing guidance.

For request behavior, see data retention and classification and use cases.

Search documentation

Search all 25 guides and references.