A hand holds a privacy screen over a laptop showing a conversation beside a closed folder.
HIPAAClaudeprivacypractice management

Is Claude HIPAA Compliant for a Therapy Practice?

Photo of Marcus Reilly
Marcus Reilly Practice Operations Editor 8 min read
Outline

Your team is testing with a wholly invented referral:

“Jordan Lee requests an appointment for sleep difficulty and work stress. The referring clinician asks for a summary of the stated concerns.”

You want a short summary, not a diagnosis or treatment recommendation. There is no actual client behind these details.

A clinician’s Pro account: Your clinician signs in to a personal Pro account and asks Claude to summarize the fictional referral. Pro cannot enable the HIPAA-ready Enterprise setting. Do not put the real identifiable referral there, even if the same clinician belongs to your practice’s Enterprise organization.

Your practice’s Enterprise organization: The clinician switches to the practice organization and uses an eligible chat feature only after your Primary Owner has accepted the BAA and enabled HIPAA. You still need to verify the actual organization, covered feature, settings, permissible purpose, and practice policy.

Compare it to the referral; the draft does not establish a diagnosis. An Enterprise label alone is not approval.

A vendor’s application built on the Claude API: A separate vendor offers a referral workflow using the API. Your practice’s Enterprise agreement does not cover that vendor’s application. Identify your contract with the vendor, its data flow and subcontractor arrangements, and the relevant API organization’s BAA, HIPAA activation, and eligible feature before considering real PHI. You have not inspected these for this hypothetical tool. If any boundary remains unclear, keep the referral in your approved system and summarize it there.

For a different task, see how Emosapien supports session documentation.

Record the decision for each destination: For the personal account, write “not approved for an identifiable referral.” The clinician can still practice with the invented Jordan example, but should not substitute a real referral or paste an excerpt into that account. Removing the person’s name alone does not establish de-identification; other details can identify someone. Do not treat a successful test as authorization to use real information.

For the practice organization, ask the Primary Owner to confirm the organization on screen and show that HIPAA is enabled. Record the approved feature and staff access, not a screenshot containing client information. Check whether the intended summary stays in that feature or is sent through a connector. If it goes to another destination, review that destination and its agreement separately. A clinician who changes accounts should check the organization again before starting work.

Ask the administrator to record the retention settings for the workspace and any project involved. A draft left in a project can follow a different retention rule from a regular chat. Decide who may see the summary, where the approved copy belongs, and who will remove unnecessary copies under the practice’s policy. Before the summary enters a record, compare it with the original referral and correct any detail the source does not support.

For the vendor application, ask the vendor to identify the contracting parties, the data recipients, and how it handles the referral and output. Verify its agreement with your practice and the relevant API organization’s activation and eligible features. Do not assume that the practice’s own Enterprise setting controls the vendor’s account. If the vendor cannot answer, mark the decision pending and use the existing approved system instead.

Finally, explain the proposed task and data flow to the client and obtain informed consent consistent with applicable professional guidance and law. Keep the approval card about the workspace and decision, not Jordan’s referral details. Assign an owner and a date to revisit approval when a feature, contract, or setting changes.

Review Your Referral Workspace

Use the Claude Referral Approval Card to record your account, feature, and decision without client details.

Free. We'll email the PDF link right away and add you to the therapist toolkit, sent every two weeks. Unsubscribe any time.

PlaceAgreement boundaryDecision for real referral
Personal ProNo HIPAA settingDo not enter PHI
Practice EnterprisePractice organizationVerify activation and feature
Vendor’s API toolSeparate vendor and API organizationReview both arrangements

Identify the organization and feature

Is Claude HIPAA compliant for this referral? Anthropic’s “HIPAA-ready Enterprise plans,” checked November 2026, says Enterprise organizations can enable the offering; individual plans and Team cannot. Only the Primary Owner can accept the BAA and enable HIPAA. Ask that owner to review the agreement and implementation guide, confirm the organization name and enabled status, and identify which staff may use the approved feature. Do not assume every feature is covered because it is visible.

Anthropic’s “Business Associate Agreements (BAA) for Commercial Customers,” checked November 2026, lists eligible Enterprise features and identifies exceptions. Cloud Cowork is not covered; sending information to third parties through connectors is not covered by Anthropic’s BAA. Check the implementation guide and your actual configuration before authorizing a feature or external destination. Review your agreement, feature configuration, and any downstream vendor contract.

Before authorizing staff, write down the exact organization and feature they should use, and who will verify them. Ask the owner to show you the enabled setting in the practice organization rather than relying on a subscription receipt or a screenshot from another account. Keep the approval record free of client details. If a clinician switches accounts or opens a separate vendor application, pause and check that destination independently.

The practice can use a wholly invented referral while it works through those checks. If the owner cannot confirm the feature or destination, keep the real referral in the approved system. Record the unresolved question and who will follow up before staff revisit the decision. A familiar interface or an employee’s access to the tool is not proof that the referral can be sent there.

For first-party API use, Anthropic’s “API and data retention,” checked November 2026, requires a signed BAA and HIPAA-enabled API organization for eligible API features. A single agreement can cover both Enterprise and API if its terms do so; activation and feature coverage still need checking separately. The Claude Console interface itself is excluded for processing PHI even though the API setting can be enabled there. An outside application’s own agreement and data handling need separate review. For the different OpenAI tier question, see what a signed BAA covers for ChatGPT.

For a generic request such as a blank referral-summary outline, a general assistant can be enough. Use invented material, not a real referral with the name removed.

Is Claude HIPAA compliant without retention settings?

A BAA is not enough without the appropriate settings and your own safeguards.

Anthropic’s “Configure custom data retention controls for Enterprise plans,” checked November 2026, says covered Enterprise content is retained indefinitely by default unless a custom period is set, with a 30-day minimum. Project retention takes precedence over chat retention for chats inside that project. Activity can restart the clock, and deletion is not necessarily instantaneous. Ask your administrator to document the actual chat, project, and artifact rules, exceptions, and who can access the content.

Anthropic’s “How long do you store my organization’s data?”, checked November 2026, says standard API inputs and outputs are ordinarily deleted from its backend within 30 days, with exceptions including longer-retention services, different agreements, policy enforcement, and legal requirements. Your vendor may also retain a copy. A BAA is not a zero-retention setting, and a shorter API clock does not set the Enterprise workspace’s clock.

Anthropic’s “Is my data used for model training?”, checked November 2026, says commercial inputs and outputs are not used to train its models by default; explicit feedback or permission can change that where available. Do not treat that default as a deletion promise. Ask whether feedback is available in your configuration and what your policy permits. Keep these decisions distinct from the signed BAA.

When a referral summary is copied into your record, you remain responsible for comparing it with the source and correcting unsupported statements. For our documentation workflow, see how notes are drafted and reviewed.

Protect the person behind the referral

Removing a name is not HIPAA de-identification. HHS guidance describes Safe Harbor as removing 18 categories of identifiers concerning the individual and relatives, employers, or household members, with no actual knowledge that the remainder can identify the person alone or in combination with other information. Review free text and unusual combinations too. Expert Determination is a separate method. For a test, invent the entire case.

Explain the specific provider and task to the client: the referral-summary purpose, information sent, recipients and data flow, benefits and risks, who reviews the output, and the available choice or refusal under your policy and applicable law. Obtain informed consent consistent with APA health-service psychology guidance, and retain professional judgment. Consent does not legalize a prohibited use. An eligible product and a signed BAA alone do not satisfy HIPAA, professional duties, or state law.

Check the actual jurisdiction, provider, and task as well as the feature. Consult counsel about your facts; this information is not legal advice.

Is Claude HIPAA compliant in your practice’s workflow?

Keep the signed agreement, organization identity, activation evidence, approved feature and recipient, and the named decision owner. Record the referral task, flow to any vendor or subcontractor, retention settings and exceptions, access restrictions, and the date of review. Document the client’s communication, choice and consent as required by your policy and law, without putting clinical details in the approval record. Assign a review date and revisit the decision when the product, contract, configuration, or law changes. HHS cloud guidance explains that a BAA is one part of a broader risk analysis and management process.

Keep the clinical note under a signed BAA

A referral summary and a session note are different jobs. For the session-derived note, Emosapien’s Scribe Agent drafts a progress note for you to review, edit, and sign. Before entering PHI, confirm that your practice has a signed BAA covering the intended use. You retain responsibility for the note and the practice’s legal obligations.

Review the first session note under a signed BAA

Review and edit your draft before signing.

Create account
  • Clinician review
  • Edit before signing
Note review
Fictional session

Session detail

The client practiced a breathing exercise.

Draft for review

Progress note ready for clinician review.

Review your note… →

References

Free PDF: AI Assistant Workspace Approval Cards

Printable decision sheets for checking assistant accounts, features, copies, retention and clinician review before a workflow is approved.

  • Claude Referral Approval Card and Gemini Referral Desk Card
  • Copilot-to-chart worksheet and Psychiatric Referral Check
  • Research-session attachment and deletion worksheet and Chart Proofreading Field and Extension Checklist
  • Document workspace versus session-note trial scorecard

Free. We'll email the PDF link right away and add you to the therapist toolkit, sent every two weeks. Unsubscribe any time.

Ready to transform your practice?

Join 10,000+ therapists using Emosapien.