Short answer. A BAA is required when a business associate creates, receives, maintains or transmits protected health information (PHI) for a covered entity. Plugsky's current security page states that a BAA is available for healthcare workloads. Whether it covers your use case, subprocessors and deployment topology requires review of the executed BAA and counsel sign-off. This is a diligence checklist, not legal advice.
When a BAA is required and what it must contain
The Privacy Rule requires a written contract before a covered entity discloses PHI to a business associate, and before a business associate discloses PHI to a subcontractor. The contract must establish the permitted and required uses and disclosures, require appropriate safeguards, require reporting of uses or disclosures not provided for (including breaches), flow the same restrictions down to subcontractors, make PHI available for access, amendment and accounting, and return or destroy PHI at termination where feasible. It must also authorize termination for a material breach. See 45 CFR 164.504(e).
Scope is where most reviews go wrong. Does the BAA cover the API only, or also the console, logs, RAG storage, agents and support access? Every model, or only named models? Production, staging and sandbox? A VPC, on-premises or air-gapped deployment? A BAA that covers the hosted API but not the observability pipeline is not aligned with the data flow.
Map the PHI flow before you sign
Draw the path from the patient or clinician to the model and back. Label every hop with the data class, encryption, retention and the entity that touches it. A blank cell is a question for the vendor.
| Hop | PHI? | What to verify |
|---|---|---|
| User browser or clinical app → your application | Often | Consent, TLS, client-side logging, screen capture, retention |
| Your application → Plugsky API | Often | BAA scope, region, TLS, request size, model routing |
| Plugsky → underlying model provider | Possible | Subprocessor BAA, retention, training use, location |
| Logs, traces and audit events | Possible | Payload capture on/off, access, retention, SIEM export |
| RAG index, vector store and object storage | Possible | Tenant isolation, encryption, deletion, backups |
| Backups, exports and support tickets | Possible | Retention, location, who can access, deletion proof |
Plugsky routes requests to underlying model providers; the current Terms name opencode.ai, NVIDIA NIM and others. The BAA and subprocessor list should identify every entity that can access PHI. If a provider processes PHI without a BAA or equivalent written assurance, the flow is not covered.
Subprocessors, retention and encryption
Flow-down is explicit: subcontractors that create, receive, maintain or transmit PHI must agree to the same restrictions as the business associate. Ask for the subprocessor list, services, countries, notice period and your right to object. Ask what happens if a model provider changes retention or training terms mid-term.
Retention is not one number. Prompts, completions, request logs, audit logs, embeddings, backups and support attachments can each differ. Plugsky's security documentation says audit logs default to 90 days and can extend to seven years on Enterprise, but that is not PHI retention. Ask for each data type's schedule, deletion method, backup tail and certificate.
Encryption should be explicit: AES-256 at rest with per-region keys and TLS 1.3 in transit, as the current security documentation states. Ask who holds the keys, whether BYOK or HSM custody is available, how rotation works and whether the vendor can read the data. Encryption is necessary but not sufficient.
Access, audit and incident notice
The Security Rule's technical safeguards cover access control, audit controls, integrity, authentication and transmission security (45 CFR 164.312). Map each to evidence: unique IDs, RBAC, MFA or SSO, least-privilege admin, audit coverage, log integrity, encryption and a tested incident process. Ask whether SCIM deprovisions access and how long a disabled user keeps API keys.
Breach notification has a clock: without unreasonable delay and no later than 60 calendar days after discovery (45 CFR 164.410). The BAA should say who notifies whom, in what form, with what content, at whose cost, and how law-enforcement delays work. It should also cover suspected incidents, because you need early warning. Test the path with a tabletop exercise.
What a BAA does not cover
A BAA does not make a vendor “HIPAA certified” — HHS does not issue that certification. It does not cover your own obligations, notice of privacy practices, consent, minimum-necessary decisions or risk analysis. It does not automatically cover de-identified data, state consumer health law or GDPR. It does not guarantee clinical accuracy. Counsel review is required.
Questions to send before signing
- Which services, models, environments and deployment topologies does the BAA cover?
- Which subprocessors can access PHI, where are they located, and what is the notice and objection process?
- What is the retention schedule for prompts, completions, logs, embeddings, backups and support tickets?
- Who can access PHI for support or operations, under what approval, and is that access logged?
- What is the security-incident notification clock, and how does it interact with the 60-day breach rule?
- What audit evidence will you provide: SOC 2 report, penetration-test summary, access review, deletion proof?
- What happens at termination: export, deletion, certificate and retention of backups?
For the deployment context, see healthcare private LLM and private RAG for sensitive data. The current Terms govern the service; the BAA and DPA govern PHI. Have counsel review all three together.
FAQ
Does Plugsky offer a BAA?
Plugsky's current security page states that a BAA is available for healthcare workloads. Confirm the scope, covered services, subprocessors, retention and deployment topology in the executed BAA; this page is not a claim that a specific workload is covered.
Is a BAA enough to make an AI API HIPAA-compliant?
No. A BAA is one contract in a compliance program. You still need a risk analysis, access controls, audit logging, incident response, training and policies. Counsel review is required.
What has to be in the BAA?
Permitted uses, safeguards, breach reporting, subcontractor flow-down, access and amendment, accounting of disclosures, return or destruction at termination, and termination for material breach. See 45 CFR 164.504(e).
How fast must a business associate report a breach?
Without unreasonable delay and no later than 60 calendar days after discovery of a breach of unsecured PHI. The BAA should define the notice path, content, costs and cooperation before an incident.
Does the BAA cover model providers and subprocessors?
Only if those entities are in scope and bound by the same restrictions. Ask for the subprocessor list, locations, flow-down terms and notice process, and verify that no PHI reaches a provider without a BAA or equivalent assurance.
Sources
Primary sources checked 20 November 2026. Provider terms, limits and prices change; verify the current version before you commit.
- 45 CFR 164.504 — business associate contracts — sets the required contract terms, including permitted uses, safeguards, breach reporting, subcontractor flow-down and return or destruction of PHI.
- 45 CFR 164.410 — notification by a business associate — requires notice to the covered entity without unreasonable delay and no later than 60 calendar days after discovery.
- NIST SP 800-66 Rev. 2 — is a cybersecurity resource guide for implementing the HIPAA Security Rule, including risk analysis and technical safeguards.
Reviewed 20 November 2026. This page is a diligence checklist, not legal advice. HIPAA obligations depend on your role, data and deployment. Have counsel review the BAA, DPA and data flow before processing PHI.