Claude Project: Build an AI-Powered Practice Policy Assistant

What This Builds

Instead of searching through a binder or asking you the same question for the tenth time, your staff will be able to query an AI assistant that already knows your practice's policies, procedures, and key operational details. You build it once — loading your SOPs, policies, and HR handbook into a Claude Project — and then you and your team can ask it questions in plain English and get accurate, specific answers based on your actual documentation.

Prerequisites

• Comfortable using Claude for basic drafting (Level 3)
• Claude Pro subscription ({{tool:Claude.price}}/month) — Projects require Pro
• A collection of at least 3–5 existing policy/SOP documents in text or Word format
• 1–2 hours for the initial setup session

The Concept

A Claude Project is like hiring a new office coordinator who has read every policy document you've ever written, memorized your staff handbook, and can answer "what's our protocol for [X]?" in seconds — without interrupting you. You set it up once by loading your documents and writing a brief instruction set. After that, it's available 24/7 for you and, if you share access, your front desk leads and senior staff.

The key difference from regular ChatGPT: Claude Projects maintain persistent memory of the documents you load. Each new conversation starts with that knowledge already loaded — you don't need to re-paste documents every time.

Build It Step by Step

Part 1: Collect and Prepare Your Source Documents

You need to gather your existing policy documents. If you don't have many yet, spend 30 minutes generating the most important ones using ChatGPT first (see Level 3 guide).

Minimum documents to start:

• Patient scheduling and no-show policy
• Billing and copay collection policy
• Staff attendance and tardiness policy
• HIPAA privacy practices summary
• Patient complaint handling procedure
• After-hours and emergency coverage procedure

Save each as a plain text or Word document. Remove any specific patient names or PHI — the policies themselves should be generic procedures, not case examples.

How to convert: In Word, go to File → Save As → Plain Text (.txt). Or simply copy-paste the policy text.

Part 2: Create Your Claude Project

1. Log in to claude.ai with your Pro account
2. Click Projects in the left sidebar
3. Click New Project
4. Name it: "[Practice Name] Policy Assistant"
5. Add a project description: "Answers staff questions about practice policies and procedures based on loaded documents."

What you should see: A new project workspace with a files panel on the left and a chat area.

Part 3: Load Your Documents

In the project, click the + button in the Files panel (or "Add content"). Upload each of your policy documents. Claude will read and index them automatically.

What you should see: Each document appears in the files list. Claude has now "read" everything in them.

Part 4: Write Your Project Instructions

Click Edit project instructions (or similar settings option). This is where you tell Claude how to behave in this project. Copy and customize:

You are the Practice Policy Assistant for [Practice Name]. Your job is to answer staff questions about practice policies, procedures, and operational guidelines based on the documents loaded in this project.

Rules:
1. Only answer based on what's in the loaded policy documents. If you don't know, say "This isn't covered in our current policies — please ask [manager name]."
2. Always cite which policy document your answer comes from.
3. Keep answers brief and practical — staff need quick, clear guidance.
4. Never make up policies or procedures — always work from the loaded documents.
5. If a question involves a patient complaint, billing dispute, or HR issue, always recommend escalating to [manager name] regardless of what the policy says.

Tone: Helpful, clear, professional. Like a knowledgeable colleague, not a legal document.

What you should see: Instructions saved. Now every conversation in this project will follow these rules.

Part 5: Test It Thoroughly

Ask 10–15 questions that your staff commonly ask you. For example:

• "What's our no-show fee policy?"
• "How many unexcused absences trigger a written warning?"
• "A patient is refusing to pay their copay — what's the procedure?"
• "Can I reschedule a same-day cancellation for the same week?"
• "When do we send a patient account to collections?"

For each answer, verify: Is it accurate? Does it cite the right policy? Is it missing context that's important?

If anything is wrong, check your source document — the AI can only be as accurate as what you loaded.

Part 6: Share Access (Optional)

You can share your Claude Pro project with team members. Go to project settings and look for sharing options. Consider starting by sharing with your most senior front desk coordinator — have them use it for one week and report back on accuracy and helpfulness before wider rollout.

Real Example: Handling a Patient Dispute

Setup: You've loaded your billing policies, patient financial agreement, and collections procedure.

Input: Front desk coordinator asks: "A patient is arguing that we charged them wrong — they say their plan covers the visit at 100%. What do I do?"

Output: The assistant responds: "Per our Billing Dispute Policy (Patient Financial Policy, Section 4): First, tell the patient you'll research the claim and call them back within 1 business day. Pull up their EOB in the billing module and compare it to what we billed. If there appears to be a billing error, escalate to [manager name]. If the EOB shows patient responsibility as we charged, provide the patient with the EOB and advise them to call their insurance to dispute the coverage determination. Do not adjust charges without manager approval. Note the interaction in the PM system under the patient's account."

Time saved: The coordinator didn't have to interrupt you, didn't guess, and got a specific, accurate answer in 10 seconds.

What to Do When It Breaks

• Answer contradicts actual policy → Check the source document you loaded; update the policy text and re-upload the file
• Assistant makes up a policy → Your Project Instructions may need strengthening; add "If no policy exists for this situation, say 'No policy found — please ask [manager name]'"
• Answer is too vague → The source policy itself may be too general; revise the policy document and re-upload
• Staff stop using it → Likely because they got one wrong answer; audit accuracy monthly and fix source docs

Variations

• Simpler version: Skip the Project setup and just keep a Google Doc with all policies pasted in, then paste that doc into Claude when you need to answer a specific question — slower but free
• Extended version: Add your physician contracts summary (redacted), insurance panel list, and payer-specific billing rules to the project — becomes a comprehensive practice knowledge base

What to Do Next

• This week: Load your 5–6 most-frequently-referenced policies; test with 20 questions; fix anything wrong
• This month: Add remaining policies; share with 1–2 senior staff; track how many times it's used vs. how many times staff come to you with the same question
• Advanced: Add a section for common vendor contacts and a troubleshooting guide for your EHR's most common error messages

Advanced guide for Medical Office Manager professionals. These techniques use more sophisticated AI features that may require paid subscriptions.