--- title: "Record payer rules and denial fixes so AI reviews claims with your history" description: "Keep payer rules, denial fixes, provider documentation gaps, and code pairings in a sourced file so AI flags claim problems before submission." canonical: "https://scalewithsearch.com/articles/ai-for-medical-billing" date: "2026-01-28" modified: "2026-09-25" --- ## Site navigation - [Scale With Search](https://scalewithsearch.com/) - Real estate - Real estate - [Real estate](https://scalewithsearch.com/for/real-estate) - Work - Start here - [Send your brief](https://scalewithsearch.com/work#send-your-brief) - [Prepare your six-question brief](https://scalewithsearch.com/work#prepare-your-six-question-brief) - Build - [Site build, content library with SEO, signal desk](https://scalewithsearch.com/work) - For your business - Trades and home services - [Auto body and collision shops](https://scalewithsearch.com/for/auto-body-and-collision-shops) - [Foundation and home repair contractors](https://scalewithsearch.com/for/foundation-and-home-repair) - [Garage door and fencing contractors](https://scalewithsearch.com/for/garage-door-and-fencing-contractors) - [HVAC contractors](https://scalewithsearch.com/for/hvac-contractors) - [Janitorial and commercial cleaning companies](https://scalewithsearch.com/for/janitorial-and-commercial-cleaning) - [Locksmiths](https://scalewithsearch.com/for/locksmiths) - [Moving companies](https://scalewithsearch.com/for/moving-companies) - [Pest control companies](https://scalewithsearch.com/for/pest-control-companies) - [Plumbing and electrical contractors](https://scalewithsearch.com/for/plumbing-and-electrical-contractors) - [Restoration and water or fire damage companies](https://scalewithsearch.com/for/restoration-and-water-fire-damage) - [Roofing companies](https://scalewithsearch.com/for/roofing-companies) - [Towing companies](https://scalewithsearch.com/for/towing-companies) - [Tree services and landscaping companies](https://scalewithsearch.com/for/tree-services-and-landscaping) - [Solar installers](https://scalewithsearch.com/for/solar-installation) - [General contractors](https://scalewithsearch.com/for/general-contractors-and-construction) - [Paving, concrete, and flooring contractors](https://scalewithsearch.com/for/paving) - Practices and professional services - [Bookkeeping and tax practices](https://scalewithsearch.com/for/bookkeeping-and-tax-practices) - [Dental practices](https://scalewithsearch.com/for/dental-practices) - [Family and criminal defense law firms](https://scalewithsearch.com/for/family-and-criminal-defense-law-firms) - [Med spas and aesthetics practices](https://scalewithsearch.com/for/med-spas-and-aesthetics) - [Personal injury law firms](https://scalewithsearch.com/for/personal-injury-law-firms) - [Veterinary clinics](https://scalewithsearch.com/for/veterinary-clinics) - [Gyms and fitness studios](https://scalewithsearch.com/for/fitness) - [Therapy and outpatient health practices](https://scalewithsearch.com/for/therapy-and-outpatient-health) - [Medical billing companies](https://scalewithsearch.com/for/medical-billing) - [Insurance agencies](https://scalewithsearch.com/for/insurance-agencies) - [Financial advisors](https://scalewithsearch.com/for/financial-advisors) - [Property management companies](https://scalewithsearch.com/for/property-management) - [Recruiting and staffing agencies](https://scalewithsearch.com/for/recruiting-and-staffing) - [Architects and interior designers](https://scalewithsearch.com/for/architects-and-interior-designers) - [Logistics and supply chain companies](https://scalewithsearch.com/for/logistics-and-supply-chain) - Agencies, MSPs, and manufacturing - [IT and managed service providers](https://scalewithsearch.com/for/it-and-managed-service-providers) - [Machine shops and precision manufacturers](https://scalewithsearch.com/for/machine-shops-and-precision-manufacturing) - [Marketing agencies and freelancers](https://scalewithsearch.com/for/marketing-agencies-and-freelancers) - [SEO agencies and consultants](https://scalewithsearch.com/for/seo-agencies-and-consultants) - [Small manufacturers and fabricators](https://scalewithsearch.com/for/small-manufacturers-and-fabricators) - Restaurants, shops, studios, and nonprofits - [Restaurants and hospitality businesses](https://scalewithsearch.com/for/restaurants-and-hospitality) - [Retail stores and ecommerce sellers](https://scalewithsearch.com/for/retail-and-ecommerce) - [Photographers, event planners, and travel agents](https://scalewithsearch.com/for/photographers) - [Churches and nonprofits](https://scalewithsearch.com/for/churches-and-nonprofits) - [All industries](https://scalewithsearch.com/for/) - Learn - For your office - [Office job guides](https://scalewithsearch.com/guides/) - [Browser calculators](https://scalewithsearch.com/tools/) - Start here - [How it works](https://scalewithsearch.com/how-it-works) - [Free Starter Kit](https://scalewithsearch.com/kit/business-memory-starter-kit.zip) - [Synthetic specimen](https://scalewithsearch.com/specimen/working-session-specimen.zip) - Guides - [The Complete Guide to Business Memory for AI Agents](https://scalewithsearch.com/articles/business-memory-for-ai-agents-guide) - [The Complete Small-Business Guide to AI Agent Governance](https://scalewithsearch.com/articles/ai-agent-governance-guide-small-business) - [The Complete Guide to Leaving Vendor AI Memory](https://scalewithsearch.com/articles/leaving-vendor-ai-memory-guide) - Articles by cluster - [Business memory](https://scalewithsearch.com/articles/business-memory-for-ai-agents-guide) - [Agent governance](https://scalewithsearch.com/articles/ai-agent-governance-guide-small-business) - [Migration and ownership](https://scalewithsearch.com/articles/leaving-vendor-ai-memory-guide) - For machines - [llms.txt](https://scalewithsearch.com/llms.txt) - [llms-full.txt](https://scalewithsearch.com/llms-full.txt) - [Machine view](https://scalewithsearch.com/?view=machine) - Company - Evidence - [Proof](https://scalewithsearch.com/proof) - Company - [About](https://scalewithsearch.com/about) # Record payer rules and denial fixes so AI reviews claims with your history. A payer denies a claim for missing documentation. The biller has seen this exact case before but cannot remember which account it was or what got it paid. Medicare changed a billing requirement last month, and the biller is not sure which claims need adjustment. A provider asks why the payment for one procedure code dropped. The answers exist somewhere in the claim history, the denial records, and the payer letters. Finding them means a search through months of files and trust in memory. An AI assistant can help only if it knows the payer rules and denial patterns you have learned. A payer and denial file gives it that knowledge. This article shows what goes in the file, what stays out, and where the assistant must stop. ## Why general answers do not work in billing Medical billing is pattern work across many variables. The same procedure has different requirements at different payers. The same payer has different criteria under different plans. The same denial reason needs a different fix depending on each provider's documentation habits. Ask a general assistant how to handle a denial, and it gives correct but general guidance about appeals and documentation. Explain the payer's habits and the provider's style, and the advice improves. Two weeks later, on a new claim from the same payer, you explain it all again. The published rules are only part of the value in billing. The rest is a record of which rules each payer enforces and which documentation each provider tends to miss. ## What the file holds The file holds rules and patterns. It holds no patient information. | Section | Contents | |---|---| | Payer profiles | Requirements, portal or phone process, turnaround, and the policy source for each rule | | Denial playbook | Each denial reason code, the fix that worked, what to attach, and your own result log | | Prior authorization | Thresholds and methods by payer and service | | Provider patterns | Each provider's documentation habits and the pre-submission check for each | | Code pairings | Code combinations that draw payer review, and the documentation each one needs | | Account rule types | Coordination of benefits order, payment plan holds, and other account rules, with no patient identifiers | | Changes | Each rule change with its effective date and source | Every payer rule carries a source: the payer policy number, bulletin, or letter, with a date. A rule without a source is a guess, and a guess becomes an error in every claim that relies on it. ## Inspect a sample file This is a synthetic file. Payer names are placeholders. The rule lines show the format, not real payer policy. ```markdown # Billing context updated:: 2026.09.25 owner:: billing lead ## Payer A - Physical therapy: prior auth after visit 12; visits 1 to 12 need none. method:: online portal only source:: Payer A PT policy , effective - Imaging, medical necessity denials: attach physician notes that explain why a standard x-ray was not enough. Highlight symptom duration and prior treatment. appeal_log:: of first appeals, your records ## Payer B - Physical therapy: prior auth after visit 10, effective . - Urgent requests: phone authorization allowed. Include the provider NPI. ## Payer C (Medicare Advantage plan) - Follows traditional Medicare for most services. - Durable medical equipment above the plan's threshold needs added auth. ## Provider patterns - Provider 2: thorough diagnosis notes; often no follow-up plan. check:: confirm the follow-up plan before submission, for example on CPT 99215 visits - Provider 3: writes "pt" for both "patient" and "physical therapy". check:: ask for clarification on therapy claims before submission ## Code pairings - CPT 99214 with HCPCS J1885 (ketorolac injection) at Payer C: documented pain scale and the reason oral medication was not enough. - Routine preventive exam with a problem-oriented visit on the same day: separate lines and the modifier the payer policy requires. ## Account rule types - Medicare primary, commercial secondary: hold the secondary claim until the Medicare EOB arrives. - Patient on a payment plan: no collection calls on new charges until the plan ends or the patient asks to consolidate. ``` ## Use the file in daily work Claude Code reads a file named `CLAUDE.md` from the working folder when a session starts ([Claude Code memory documentation](https://code.claude.com/docs/en/memory), checked 2026.09.25). Put the billing context there, or point to it. Then the assistant answers from your payer rules instead of textbook guidance. A denial is the first use. Payer A denies an MRI claim for medical necessity. You ask: "Payer A denied the MRI for medical necessity. What do I need?" The assistant reads the imaging entry. It lists the physician note elements to include and what to highlight. It drafts the appeal letter with those references. You attach the documents from the practice management system and review before submission. A prior authorization check is the second use. A patient is scheduled for physical therapy visit 11. You ask whether this visit needs authorization. You tell the assistant the payer, not the patient. For Payer A, it answers: no authorization yet; start the request after this visit, before visit 13. For Payer B, the answer differs, because the threshold is 10. A pre-submission review is the third use. You describe a claim batch by provider, codes, and payer, with no patient identifiers. The assistant flags Provider 2's 99215 claim for a follow-up plan check. It flags the 99214 with J1885 pairing at Payer C for the pain scale. You check the charts and fix gaps before submission. A secondary claim question is the fourth use. A front desk colleague asks why a secondary claim has not processed. The account rule type answers it: the secondary waits for the Medicare EOB. When the EOB arrives, submit the secondary. ## A working setup A billing specialist at a six-provider family practice might keep a file with these parts: - rules for the practice's 12 most common payers; - denial patterns and the appeals that worked; - a documentation checklist for each provider; - prior authorization thresholds by payer and service; - code pairings that need a documentation check; - account rule types for coordination of benefits and payment plans. With that file, the assistant supports pre-submission review, appeal drafts, authorization checks, reports on provider documentation gaps, and status summaries for the front desk. Track your own denial rate and appeal success before and after, and let those numbers decide whether the setup earns its upkeep. ## Keep patient data out without a BAA Protected health information does not go into the file. It also does not go into a session unless the practice has a business associate agreement with the AI vendor that covers that product. HIPAA requires that agreement before a vendor handles PHI for a covered entity. The files stay on your computer, but the text Claude Code reads goes to Anthropic for processing. Retention and training terms depend on your plan. Describe claims by payer, codes, and provider role. Keep names, dates of birth, member IDs, and account numbers in the practice management system. The guide on [what client data belongs in AI agent memory](/articles/client-data-in-ai-agent-memory) gives a field-by-field sorting test. ## Stop where billing judgment begins The assistant flags and drafts. People decide and submit. Set these limits: 1. The assistant does not choose or change a code. Coding decisions stay with certified coders and providers. 2. The assistant does not submit claims or appeals. You review and submit. 3. The assistant stops when a rule has no source line, and asks for the payer policy. 4. The assistant never adds documentation that the provider did not write. Some billing steps should stay manual even with good context. The guide on [when an AI workflow should stay manual](/articles/when-an-ai-workflow-should-stay-manual) helps you decide which ones. For each appeal the assistant drafts, keep a short record of what it read and what it proposed. The article [the receipt is part of the output](/articles/receipt-is-part-of-the-output) shows the format. ## Test the file before the first claim batch Run three checks in a fresh session. 1. Ask "Does physical therapy visit 11 at Payer B need authorization?" Pass: yes, because Payer B's threshold is 10, with the effective date. Fail: the assistant answers from Payer A's rule or from general knowledge. 2. Ask "What does Payer D require for imaging appeals?" when the file has no Payer D. Pass: the assistant says the file has no entry and asks for the policy. Fail: it invents a requirement. 3. Ask for a pre-submission review of a claim described with a patient name and date of birth. Pass: the assistant refuses the identifiers and asks for the claim by payer, codes, and provider role. Fail: it accepts them. A fail on the second check is the one that costs money. Add a rule at the top of `CLAUDE.md`: if a payer or service has no entry, stop and ask. ## Update the file when a payer changes Payers change thresholds, forms, and policies. When a denial shows a rule change, update the payer entry the same day. Record the old rule, the new rule, the effective date, and the source. An [AI correction log](/articles/ai-correction-log-template) keeps that history, so an appeal never cites a rule that was already replaced. Review the whole file each quarter against current payer bulletins. When CMS publishes a change, add it with its effective date before the first affected claim goes out. ---- ```text .|########||. .|########||. .|########||. |##||. .||##|. |##||. .||##|. |##||. .||##|. |#|. .|#|. |#|. .|#|. |#|. .|#|. |#| |#| |#| |#| |#| |#| .#| |#. .#| |#. .#| |#. .#. .#| .#. .#| .#. .#| |#. .#| |#. .#| |#. .#| |# ...... #| |# ...... #| |# ...... #| .# ||#########| #| .# ||#########| #| .# ||#########| #| .#. |######||######|. .#. .#. |######||######|. .#. .#. |######||######|. .#. #. .##|###|##|#|######| .# #. .##|###|##|#|######| .# #. .##|###|##|#|######| .# || |##|#||||||||||||#||#| || || |##|#||||||||||||#||#| || || |##|#||||||||||||#||#| || # |#||||||||||||||||||||#| #. # |#||||||||||||||||||||#| #. # |#||||||||||||||||||||#| #. || |#||||||||||||||||||||||#| || || |#||||||||||||||||||||||#| || || |#||||||||||||||||||||||#| || # .#||||||||||||||||||||||||#| # # .#||||||||||||||||||||||||#| # # .#||||||||||||||||||||||||#| # || ....|||#||||||##|#|||#|#||##||||....|. || || ....|||#||||||##|#|||#|#||##||||....|. || || ....|||#||||||##|#|||#|#||##||||....|. || #. . ....|# ....#||| ||| .#||| ....#. .# #. . ....|# ....#||| ||| .#||| ....#. .# #. . ....|# ....#||| ||| .#||| ....#. .# # . ||||#| .#####|| . .#| .#||| ||||# #. # . ||||#| .#####|| . .#| .#||| ||||# #. # . ||||#| .#####|| . .#| .#||| ||||# #. .| ||||| #. |#|||||. || #. |#||. .||||| || .| ||||| #. |#|||||. || #. |#||. .||||| || .| ||||| #. |#|||||. || #. |#||. .||||| || || |.... #. ....|#. |. ...|. ....|| || || |.... #. ....|#. |. ...|. ....|| || || |.... #. ....|#. |. ...|. ....|| || #. .||||||##||||||##||####|||||||#||||||#| .# #. .||||||##||||||##||####|||||||#||||||#| .# #. .||||||##||||||##||####|||||||#||||||#| .# # .||####|###########################|. # # .||####|###########################|. # # .||####|###########################|. # # .#||||||.#.|| # |. ..# #| #|||||#| # # .#||||||.#.|| # |. ..# #| #|||||#| # # .#||||||.#.|| # |. ..# #| #|||||#| # # .#|||||| .. |# ## |#| ...#|#|||#| # # .#|||||| .. |# ## |#| ...#|#|||#| # # .#|||||| .. |# ## |#| ...#|#|||#| # # .#|||#|# .# .#| #| ##|.#..#|||||#| # # .#|||#|# .# .#| #| ##|.#..#|||||#| # # .#|||#|# .# .#| #| ##|.#..#|||||#| # # .#||||||############|######|||||#| # # .#||||||############|######|||||#| # # .#||||||############|######|||||#| # # |...||#||||||#||||#|#||||||#|||||#||| |.| # # |...||#||||||#||||#|#||||||#|||||#||| |.| # # |...||#||||||#||||#|#||||||#|||||#||| |.| # #. .. ||||# .|||##|. |#| .|| || .|||#. #| # .# #. .. ||||# .|||##|. |#| .|| || .|||#. #| # .# #. .. ||||# .|||##|. |#| .|| || .|||#. #| # .# || | ...|| ...##| | #| .|. |. ##### .. .| || || | ...|| ...##| | #| .|. |. ##### .. .| || || | ...|| ...##| | #| .|. |. ##### .. .| || || ||||| || ||||#| . |. |. |#. ||||| |#| || || || ||||| || ||||#| . |. |. |#. ||||| |#| || || || ||||| || ||||#| . |. |. |#. ||||| |#| || || .# |.....#|....|#.||||.|||##.|#|....||.#||.#. #. .# |.....#|....|#.||||.|||##.|#|....||.#||.#. #. .# |.....#|....|#.||||.|||##.|#|....||.#||.#. #. #.|||||||#############################| ||| .# #.|||||||#############################| ||| .# #.|||||||#############################| ||| .# || ##||#||#||||||#||#||#||#||##. || || ##||#||#||||||#||#||#||#||##. || || ##||#||#||||||#||#||#||#||##. || # .#|||||||||#||#|||||||||||#| # # .#|||||||||#||#|||||||||||#| # # .#|||||||||#||#|||||||||||#| # || |#||||||||||||||||||||||#| || || |#||||||||||||||||||||||#| || || |#||||||||||||||||||||||#| || .# |#||||||||||||||||||||#| #. .# |#||||||||||||||||||||#| #. .# |#||||||||||||||||||||#| #. || |#||||||||||||||||||#| || || |#||||||||||||||||||#| || || |#||||||||||||||||||#| || #. .######|#|#########| .# #. .######|#|#########| .# #. .######|#|#########| .# .#. |#####||||#####| .#. .#. |#####||||#####| .#. .#. |#####||||#####| .#. |# ||########|| #. |# ||########|| #. |# ||########|| #. |# ...... #| |# ...... #| |# ...... #| |#. .#| |#. .#| |#. .#| |#. .#. |#. .#. |#. .#. .#| |#. .#| |#. .#| |#. |#| |#| |#| |#| |#| |#| .|#|. .|#|. .|#|. .|#|. .|#|. .|#|. |##||. .||##| |##||. .||##| |##||. .||##| .||########||. .||########||. .||########||. Scale With Search 2026 [scalewithsearch.com](https://scalewithsearch.com) ```