What can a medical or dental office do with Claude without touching PHI?
A medical or dental office can use Claude for most of the work that is not about a specific patient: policies, procedures, patient education handouts, job posts, website and newsletter copy, staff training, vendor comparisons and letter templates with blanks where the patient details go. That work fits on Claude Team, which has no BAA, as long as the office holds one line: no information that identifies a patient goes in, ever. Our page on Claude for medical and dental practices covers the setup that keeps that line in place.

What the rules and Anthropic actually publish
The follow-up questions owners ask
What PHI-free Claude work can a medical front desk do?
Drafting the new-patient welcome letter, a missed-appointment policy, a phone script for insurance questions, a post-procedure care handout for a common procedure, an office manager job post, a staff handbook section, or a comparison of three phone systems. A useful test: if the document would make sense to hand to any patient, or to no patient, it is usually PHI-free.
Can staff remove the patient name and paste a chart note into Claude?
That is where offices get into trouble. Safe Harbor means removing all 18 identifiers, and dates of service, ages over 89, ZIP codes and record numbers are easy to miss. In a small town, a rare condition plus a visit month can point to one person, and Safe Harbor fails if you know that. Our rule for small offices is simpler: no chart notes, no patient messages, no images of patients in Claude Team, even “cleaned up.”
Can Claude draft insurance appeals and referral letters without PHI?
Build the template in Claude with placeholders such as [Patient name] and [Date of service], then fill in the patient details in your EHR or word processor outside Claude. You get the time savings on the writing without the patient data going in.
Does connecting Claude to email or files change this?
Yes. A connector to an inbox or a shared drive that holds patient messages or records puts PHI within reach, even if nobody pastes it. On Team, keep connectors and Cowork folder access away from anything that holds patient information, and write that down.
What this means for your rollout
In the practices I set up, the PHI-free list is longer than owners expect, and it is where most of the time savings are anyway: the writing nobody has time for. I would rather a practice start with a firm line and a useful list of approved uses than a loose rule that depends on staff de-identifying records correctly at 4:45 on a Friday. If the office later needs Claude for patient work, we plan that separately and on the right plan.
Related services and tools
Get the plan before you buy the seats
The plan choice is the easy part. Configuration, governance and training are where firms get it wrong. The Claude Build Plan is two working sessions with Michael Robichaud, then a written plan: architecture, plan choice with the reasons, your firm’s custom Claude plugin scoped, rollout timeline and cost. A fixed , and the plan is yours to keep.
Related questions
Sources
- HHS, Guidance Regarding Methods for De-identification of PHI: https://www.hhs.gov/hipaa/for-professionals/special-topics/de-identification/index.html
- eCFR, 45 CFR 160.103 Definitions: https://www.ecfr.gov/current/title-45/subtitle-A/subchapter-C/part-160/subpart-A/section-160.103
- HHS, Guidance on HIPAA and Cloud Computing: https://www.hhs.gov/hipaa/for-professionals/special-topics/health-information-technology/cloud-computing/index.html
- Anthropic, HIPAA-ready Enterprise plans: https://support.claude.com/en/articles/13296973-hipaa-ready-enterprise-plans
- Anthropic, Is my data used for model training?: https://privacy.claude.com/en/articles/7996868-is-my-data-used-for-model-training
Strategized.ai is independent and not affiliated with or endorsed by Anthropic. Claude is a trademark of Anthropic, PBC.