Use a covered Claude surface only, then add technical controls that stop PHI before submission. A signed BAA governs the processor, but it does not enforce minimum necessary use or redact user input. The practical pattern is to combine the right deployment path, strict workspace controls, and upstream DLP so PHI never reaches Claude in prompts, uploads, or connected data sources.
What “covered Claude surface” means in a HIPAA deployment
A safe HIPAA implementation starts by choosing the deployment path that your agreement and controls actually cover, then constraining what reaches the model. The key distinction is between vendor-side obligations and your own intake controls: a BAA can govern how the processor handles data, but your team still owns minimum necessary use, source selection, and prompt hygiene before PHI is ever submitted.
That means the security question is not simply “is Claude allowed here?”, but “which Claude surface, connected systems, and user roles are inside the approved boundary?” If a workflow can ingest PHI from chat, file upload, retrieval connectors, or copied text, it needs the same review as any other system that handles ePHI.
The most reliable design pattern is to keep Claude at the edge of the workflow, not in the middle of raw clinical data flow. Use structured tasks, redacted inputs, and constrained data sources so the model sees the minimum viable context needed to produce a useful answer.
How to keep PHI out of prompts, uploads, and connectors
The practical control stack is upstream filtering plus workspace governance. DLP or equivalent content inspection should block PHI before submission, while workspace settings should limit who can connect data sources, create custom tools, or share outputs externally. That prevents accidental exposure even when a user is trying to be helpful.
For clinical teams, the highest-risk paths are usually copy-paste, document uploads, and retrieval connections into EHR-adjacent repositories. Those channels are attractive because they feel operationally convenient, but they also bypass the normal discipline of application-level field controls unless you deliberately interpose redaction or allowlisting.
When the use case requires patient context, prefer structured extraction over free-form narrative. Strip direct identifiers, swap them for local case IDs, and keep the lookup key outside the model boundary wherever possible. That preserves utility without turning the model into a repository for raw PHI.
Where Claude connects to internal systems, treat each connector as a separate trust decision rather than a generic productivity feature. The team should define exactly which repositories are permitted, what query scope is allowed, and what content types are excluded by policy before the connector is enabled.
Operational guardrails for healthcare teams
Successful implementations usually fail because of workflow design, not model behavior. The strongest control is a clear decision rule: if the prompt contains PHI, the user either redacts it, routes it through an approved minimization step, or uses a non-model workflow for that task.
Teams should also define who owns the approval path for clinical, revenue-cycle, and operations use cases. A security review alone is not enough if business owners are not accountable for what data the workflow may touch and what outputs may be acted on without verification.
Logging and review should focus on exposure points, not just usage volume. You want evidence that restricted fields were blocked, connectors were scoped correctly, and high-risk prompts were intercepted or remediated, because those are the controls that show whether PHI is actually being kept out.
Risk and Threat Considerations
PHI leakage can happen even when the vendor relationship is contractually covered, because the main failure mode is often user-side disclosure into the model boundary. The risk increases when prompts are copied from clinical systems, when uploads include charts or lab reports, or when connected sources are broader than the task requires.
Failure mechanism: A user or connector passes PHI into Claude before redaction, so the data is processed in a place the workflow did not intend, and the organisation loses control over minimum necessary handling.
Impact: The result can be unauthorized disclosure, policy violation, incident escalation, and avoidable breach response work, even if the organisation believed the deployment was “covered” by contract.
Standards & Framework Alignment
This section maps relevant standards and security frameworks to the operational risks and controls described in this guidance.
CSA Cloud Controls Matrix and NIST SP 800-53 Rev 5 set the technical controls, while ISO/IEC 27001:2022 defines the regulatory obligations.
| Framework | Control / Reference | Relevance |
|---|---|---|
| CSA Cloud Controls Matrix | IAM — Identity & Access Management | Controls who can connect sources and use Claude in the healthcare workspace. |
| Recommendation — Restrict workspace access and connector approvals to approved healthcare roles. | ||
| NIST SP 800-53 Rev 5 | AC-6 — Least Privilege | Limits who can submit sensitive data or enable data sources to the model. |
| AU-2 — Event Logging | Supports review of PHI-blocking events and high-risk data access attempts. | |
| Recommendation — Apply least privilege to prompt, upload, and connector permissions. Log blocked submissions and connector activity for PHI exposure review. | ||
| ISO/IEC 27001:2022 | A.5.12 — Classification of information | Requires classifying PHI so redaction and handling rules can be enforced before model use. |
| A.8.12 — Data leakage prevention | Directly supports preventing PHI from reaching Claude through prompts or uploads. | |
| Recommendation — Classify PHI and enforce handling rules before any AI submission. Deploy DLP controls to stop PHI before it is submitted to Claude. | ||
Practitioner Guidance
What to verify: Confirm the exact Claude surface in use, then test the full path for PHI ingress, including copy-paste, file uploads, and every enabled connector. If any of those paths can accept unfiltered PHI, the deployment is not yet safe enough for production use.
Decision rule: If the workflow needs PHI to function, redesign the workflow so Claude receives a redacted or tokenized version first; if that is not possible, keep the task outside the model and use a different process.
What good looks like: Clinicians and operational users can complete the task with de-identified or minimized inputs, while security can demonstrate blocked submissions, scoped access, and clear ownership for every data source attached to the workspace.
Practitioner takeaway: Treat the BAA as the contractual floor, not the control boundary, and design the workflow so PHI is removed before Claude ever sees it.
Related resources from NHI Mgmt Group
- Guide: HIPAA Security Rule Guide
- Environment
- How should healthcare-adjacent SaaS teams implement SOC 2 and HIPAA together without creating duplicated controls?
- How should security teams implement PHI monitoring in Slack without slowing down healthcare workflows?
- How should healthcare teams implement HIPAA controls for PHI stored in Box?
Deepen Your Knowledge
Free weekly newsletter
Subscribe to the NHI & AI Identity Journal
The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.
Bonus 33% off our NHI Course when you subscribe.
Reviewed and updated by the NHIMG editorial team on October 31, 2026.
NHI Mgmt Group — the #1 independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org