Claude Project: Build a Persistent RCM Operations Assistant

What This Builds

Instead of re-explaining your payer mix, billing policies, denial patterns, and organizational context every time you use Claude, you'll build a Claude Project that holds all of that context permanently. Every conversation starts with your payer contracts, denial code reference, appeal templates, and billing SOPs pre-loaded. You spend zero time on setup and go straight to the actual work — drafting appeals, analyzing data, translating policies — for your specific organization.

Prerequisites

• Comfortable using Claude for single-session analysis tasks (Level 3)
• Claude Pro account ($20/month at claude.ai)
• Key reference documents to upload: payer summary, common denial codes, appeal templates, billing SOPs
• 1–2 hours for initial build; minimal time for ongoing use

The Concept

A Claude Project is like hiring a medical billing consultant who has read all your contracts, knows all your payer relationships, and remembers everything from your last conversation. You write a set of instructions (the "system prompt") that tells Claude about your organization, your payer mix, your billing standards, and how you like things done. You upload reference documents as project knowledge. Every conversation in the project starts from this shared understanding — no re-explaining, no context-loading, just work.

Build It Step by Step

Part 1: Set up the Claude Project

1. Go to claude.ai → click Projects in the left sidebar
2. Click New Project → name it "RCM Operations — [Your Organization Name]"
3. Click Edit Project Instructions → write your system prompt

System prompt template for an RCM Operations project:

You are an expert revenue cycle management advisor for [Organization Name],
a [hospital system / physician group / specialty practice] that provides [specialty/service area].

## Organizational Context
- Payer mix: [list your top 5 payers by volume percentage, e.g., "Medicare 35%, United Healthcare 20%, BCBS 18%, Medicaid 15%, Commercial other 12%"]
- Primary practice management system: [Epic / Cerner / Athena / other]
- Clearinghouse: [Availity / Change Healthcare / other]
- Specialties billed: [list]
- Geographic service area: [state(s)]

## My Role
I am the Revenue Cycle Manager. I oversee billing, coding, denial management, and AR reporting.
My team includes: [brief description of team structure].

## How to Help Me
- Draft denial appeal letters without including patient PHI in your outputs
- Analyze aggregate denial data and identify root causes
- Translate payer bulletins into specific billing procedure updates
- Write professional communications to payer representatives
- Summarize long policy documents into actionable guidance for billing staff
- Generate training materials for new billing and coding staff

## Communication Standards
- Use standard revenue cycle terminology (days in AR, CARC/RARC codes, clean claim rate, etc.)
- When drafting appeals, use formal, clinical-appropriate language
- When writing staff communications, use plain, direct language
- Always flag when advice may be jurisdiction-specific or require verification against current CMS/payer guidelines

## Things I Cannot Share with You (and you should not ask for)
- Individual patient names, dates of birth, or claim-level identifiers
- We work with aggregate data and de-identified summaries only

Click Save Instructions.

Part 2: Upload reference documents as project knowledge

Click Add Content → Upload Files → upload your most important reference documents:

High-value uploads:

1. Payer contract summary — A one-page summary of key terms for each major payer (you can create this using the Level 3 contract analysis guide first)
2. Common denial code reference — Your denial code guide with payer-specific meanings and standard resolution steps
3. Appeal letter templates — Your approved appeal templates for medical necessity, timely filing, authorization, and technical denials
4. Current billing SOPs — Your most frequently referenced billing procedures
5. Payer-specific PA requirements — Your prior authorization matrix by payer and service type

What you should see: Uploaded documents listed in the project's knowledge section. Claude reads these before every conversation.

Part 3: Test the project with real tasks

Start a new conversation inside the project → test with actual work:

Test 1: Denial appeal drafting

Check: Does Claude use your organizational context? Does it reference your UHC payer information? Is the language appropriate for your specialty?

Test 2: Policy translation

Check: Is the guidance specific enough for your billing staff? Does it use appropriate terminology?

Test 3: KPI narrative

Check: Does it use plain language appropriate for a non-billing executive?

Part 4: Refine based on test results

If outputs aren't right, update the project instructions with more specific guidance. Common refinements:

• Add specific payer-quirks you know: "United Healthcare in our region has a specific modifier 25 policy — always note this when drafting E&M + procedure appeal letters"
• Add style preferences: "Appeal letters should open with the claim information in a standard header format before the narrative argument"
• Add scope limits: "Only provide appeal strategy for the denial types listed in our uploaded template library"

Real Example: Weekly Denial Management Workflow

Setup: You've configured the project with your payer summary, appeal templates, and SOP library.

Monday morning, in your RCM Operations project:

You: "Here is our weekly denial summary [paste de-identified aggregate table]. What patterns should we prioritize this week, and what's the fastest path to recovery for each?"

Claude: "Based on your data and your payer mix:

1. The Aetna medical necessity denials (47 claims, $83,000) are your highest-priority recovery opportunity — based on your appeal template, these can typically be resolved within 30 days with a well-documented medical necessity argument. I recommend starting appeals this week.
2. The Medicare timely filing denials (12 claims, $22,000) have a filing deadline approaching — check each claim date now; those within the 90-day limit can still be appealed.
3. The United Healthcare modifier 25 pattern (31 claims, $28,000) looks like a systemic issue rather than individual claim errors — you'll want to investigate whether this is a coding pattern or a payer algorithm change. Here's how to determine which: [guidance specific to your UHC context]..."

Time saved: 60–90 minutes of manual triage reduced to 10–15 minutes of AI-assisted prioritization; every follow-up conversation builds on the same organizational context.

What to Do When It Breaks

• Claude doesn't reference uploaded documents → Remove and re-upload the documents; check that each file is under 10MB
• System instructions are being ignored → Move the most important rules to the top of your instructions; Claude weighs earlier instructions more heavily
• Appeal drafts are too generic → Add more specific examples to the instructions: "For UHC medical necessity appeals, always lead with the InterQual criteria relevant to the clinical scenario"

Variations

• Simpler version: Use Claude's Custom Instructions (Settings → Custom Instructions) to set basic organizational context without managing a full project — less powerful but zero setup time
• Extended version: Create a separate project for each major payer, uploading that payer's full contract and all payer-specific bulletins as knowledge — enables extremely specific payer guidance

What to Do Next

• This week: Set up the project with your payer summary and top 3 appeal templates; run one real denial appeal through it
• This month: Add your most commonly referenced billing SOPs and have billing leads test it as a reference tool before coming to you with questions
• Advanced: Combine this project with your Notion AI knowledge base (Level 3 guide) — use Notion for staff self-service and Claude Project for manager-level analysis and drafting

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