Claude Project: Your Personalized Pharmacy Knowledge Base

What This Builds

Instead of using Claude as a generic AI that knows nothing specific about your pharmacy, you'll build a Claude Project — a persistent AI assistant that knows your pharmacy's formulary, your most common PA appeal templates, your local patient population's characteristics, and your preferred clinical workflows. Every conversation starts from this shared context, so Claude's answers are specific to your situation rather than generic.

Think of it like hiring a clinical pharmacist consultant who has already read your operations manual, knows your patient demographics, and has your formulary memorized. You don't re-explain context every time — they already know it.

Prerequisites

• Claude Pro subscription — {{tool:Claude.price}}/month ({{tool:Claude.plan}}) at {{tool:Claude.url}}
• Your pharmacy's formulary (PDF, spreadsheet, or document)
• 3–5 of your best prior authorization appeal letters (past successes)
• Basic familiarity with using Claude for clinical questions (Level 3)

The Concept

A Claude Project is a workspace where you upload documents and write a custom system instruction that persists across all conversations in that project. When you open the project and ask a question, Claude already has access to everything you uploaded and remembers your preferred approach.

Unlike a regular Claude conversation that starts blank every time, a Project is like a dedicated pharmacist's notebook that Claude has read and keeps as context.

Build It Step by Step

Part 1: Create the Project

1. Log into Claude at {{tool:Claude.url}} with your Pro account
2. In the left sidebar, click Projects (or look for a + New Project button)
3. Click Create project and name it: "My Pharmacy Assistant — [Your Name]"
4. You'll see a Project workspace with an Instructions field at the top and a Knowledge upload area

What you should see: A project dashboard with an empty chat area, an Instructions section, and a Knowledge section for document uploads.

Part 2: Write Your Custom Instructions

Click on the Instructions field and paste this customized template (edit the bracketed sections for your specific situation):

You are a clinical pharmacy assistant for a staff pharmacist working at [retail chain / independent pharmacy / hospital pharmacy].

About my practice:
- Typical patient population: [elderly Medicare patients / working-age adults / pediatrics / mixed]
- Most common conditions I manage: [type 2 diabetes, heart failure, hypertension, chronic pain — edit to match]
- My formulary: [PBM name] with [key coverage notes, e.g., "prefers generics, GLP-1s require PA"]
- State I practice in: [your state] — apply state-specific practice authority rules

For clinical questions:
- Always provide structured, prioritized output
- Flag major drug interactions (not minor/theoretical ones)
- Reference specific clinical guidelines when relevant (ADA, ACC, ASHP, etc.)
- Recommend monitoring parameters when discussing high-alert medications

For prior authorization letters:
- Use my successful letter templates as style guides
- Include specific clinical guideline citations
- Address the payer's stated denial reason directly
- Keep letters under 400 words unless clinical complexity requires more

For patient education:
- Default to 6th-grade reading level
- Use simple numbered lists, not paragraphs
- Include "when to call the pharmacy" in every patient-facing document

For drug information:
- Note when information may be approaching your knowledge cutoff and suggest verifying with current sources (Lexicomp, Micromedex, or Perplexity for recent approvals)

Click Save instructions.

Part 3: Upload Your Knowledge Documents

In the Knowledge section, click Add content or Upload files and add:

Document 1: Your formulary or coverage reference

• Export a PDF or spreadsheet of your most common drugs and their PA/step therapy requirements
• Or create a simple Word document listing: "Drug X → requires PA for [indication] → step therapy: [prior drugs required]"

Document 2: Your PA letter templates (3–5 examples)

• Copy your best, most successful PA appeal letters into a Word document
• Remove patient-identifying information first
• These teach Claude your preferred letter style and clinical argumentation approach

Document 3: Local clinical protocols (optional)

• Any internal pharmacy protocols, MTM workflows, or clinical pathways specific to your practice
• State board requirements or scope of practice documents

What you should see: Each uploaded document appears as a tile in the Knowledge section. Claude now has access to these documents in every conversation within this project.

Part 4: Test and Refine

Open a new conversation within the project. Test it with real questions you encounter:

Test 1 — PA letter: "Write a PA appeal letter for Jardiance (empagliflozin) for a patient with HFrEF EF 35%. The payer denied it requesting step therapy with other diuretics first."

Verify Claude's response references your uploaded letter style and your formulary context.

Test 2 — Drug information: "A patient is starting on Ozempic 0.25mg weekly for type 2 diabetes. What are my top 5 counseling points and are there any interactions with their current metformin 1000mg twice daily and atorvastatin 40mg?"

Test 3 — Polypharmacy review: "Review this medication list for a 78-year-old Medicare patient with [list of diagnoses]" + paste medications.

If responses are too generic, refine your Instructions to add more specificity about your patient population or preferred output format.

Real Example: PA Letter Workflow

Setup: Your Project has your pharmacy's formulary uploaded and 5 successful PA letters as style guides

Input: "Write a PA appeal for tirzepatide (Mounjaro) for a patient with type 2 diabetes, A1C 8.9% on metformin and glipizide for 2 years. Payer requires GLP-1 trial before tirzepatide. Patient had nausea with semaglutide (Ozempic) that led to 15lb weight loss — too much loss for this patient's oncology team."

Output: Claude generates a letter that:

• Matches the tone and structure of your uploaded letter templates
• Cites ADA 2025 Standards of Care for GLP-1/GIP dual agonist recommendations
• Addresses the step therapy requirement by documenting the semaglutide experience
• Includes your patient's oncology context as a mitigating factor
• Is formatted exactly as your previous successful appeals

Time saved: 60 minutes of research and writing → 8 minutes of editing

What to Do When It Breaks

• Claude doesn't reference my uploaded documents → Try asking "Based on the formulary I uploaded, what is the step therapy requirement for [drug]?" to explicitly invoke the knowledge
• Letter style doesn't match my templates → In your instructions, add: "Always use the style and structure of the PA letters I've uploaded as knowledge documents"
• Instructions reset between sessions → They don't — but if something seems off, click on the project name to verify your instructions are still saved
• Claude gives outdated drug information → Add to your instructions: "For drugs approved after 2024, note that information may be incomplete and recommend verifying with Perplexity or current FDA labeling"

Variations

• Simpler version: Skip document uploads and just write detailed instructions — still dramatically better than plain Claude without the project context
• Extended version: Create separate sub-projects for different patient populations (MTM patients, discharge counseling, staff training) each with their own tailored instructions and templates

What to Do Next

• This week: Upload your formulary and 2–3 PA templates; test the project on your next 5 real clinical questions
• This month: Add new templates as you create them; refine instructions based on where the output still needs improvement
• Advanced: Connect this workflow to the Level 4 Custom GPT guide to build a second parallel assistant for patient-facing tasks

Advanced guide for staff pharmacist professionals. Claude Projects require a paid subscription. Do not upload PHI or patient-identifiable information to AI platforms.