Write a compliant physician query letter requesting clarification of an unspecified diagnosis code.

Coder name and credentials: [NAME, CPC/CCS/RHIA]
Attending physician: [DR. NAME, SPECIALTY]
Patient: [MRN or encounter identifier — no PHI in the prompt itself]
Encounter date: [DATE]
Documented diagnosis: [ICD-10 code and description — e.g., J18.9 Pneumonia, unspecified organism]
Why specificity matters: [Clinical and coding reason — e.g., "A specific organism code is required for CC/MCC capture and payer medical necessity determination"]
Clinical data already documented that supports a more specific code: [FINDINGS FROM THE RECORD — e.g., "Sputum culture positive for Streptococcus pneumoniae documented in lab results 04/15/2026"]
Query options to offer: [2-3 non-leading options — e.g., J13 Pneumonia due to Streptococcus pneumoniae / J18.9 Pneumonia, unspecified / Other: _____ / Unable to determine]

AHIMA-compliant format: non-leading, clinical facts only, multiple-choice format. Under 200 words.

Write a physician query requesting documentation of a secondary diagnosis suggested by clinical evidence but not captured in the record.

Coder: [NAME, CREDENTIALS]
Attending: [DR. NAME]
Encounter: [DATE AND TYPE]
Principal diagnosis: [ICD-10 AND DESCRIPTION]
Clinical findings suggesting secondary diagnosis not coded: [SPECIFIC EVIDENCE — e.g., "Blood glucose 312 mg/dL on admission, HbA1c 9.8% in prior workup, no diabetes diagnosis documented in this encounter"]
Potential secondary diagnosis options to offer:
  Option A: [ICD-10 AND DESCRIPTION — e.g., E11.9 Type 2 Diabetes without complications]
  Option B: [ICD-10 AND DESCRIPTION — alternative or more specific code]
  Option C: Unable to determine based on available documentation
  Option D: Other: _______________

Non-leading format. Request physician to select one option and sign. Under 200 words.

Write a physician query requesting procedure documentation that supports a reported CPT code.

Coder: [NAME, CREDENTIALS]
Provider: [DR. NAME, SPECIALTY]
Date of service: [DATE]
CPT code under review: [CODE AND DESCRIPTION]
Documentation deficiency: [SPECIFIC GAP — e.g., "The operative note does not document the size of the lesion excised, which is required to assign the correct CPT code from the 11600–11646 series"]
Supporting documentation needed: [EXACTLY WHAT IS REQUIRED — e.g., "Please document the diameter of the excised lesion in centimeters at the time of the procedure"]

Compliance context: [Note that this query is for documentation completeness only, not retrospective creation of documentation]

Under 150 words. Clinical and factual only.

Write a clinical documentation improvement (CDI) query to capture a complication or comorbidity (CC) or major complication or comorbidity (MCC) supported by the clinical record.

CDI specialist/coder: [NAME, CREDENTIALS]
Attending: [DR. NAME]
Encounter: [DATE, DRG or MS-DRG if known]
Principal diagnosis: [ICD-10 AND DESCRIPTION]
Potential CC/MCC supported by clinical evidence: [DIAGNOSIS AND ICD-10 — e.g., E87.1 Hyponatremia — serum sodium 128 mEq/L on admission, corrected with 3% saline over 48 hours, clinical monitoring documented]
DRG impact: [CURRENT DRG AND WEIGHT vs. DRG AND WEIGHT WITH CC/MCC — e.g., "Current: DRG 194 weight 0.9317 / With MCC: DRG 191 weight 2.0716"]

Non-leading multiple-choice format. Present clinical findings, then offer options. Under 200 words.

Write a physician query requesting Present on Admission (POA) indicator clarification for an outpatient diagnosis.

Coder: [NAME, CREDENTIALS]
Physician: [DR. NAME]
Patient encounter: [DATE, FACILITY]
Diagnosis requiring POA clarification: [ICD-10 AND DESCRIPTION]
Reason POA is unclear: [CLINICAL CONTEXT — e.g., "Patient presents with chest pain; EKG changes noted on arrival; troponin elevated at initial draw. Was the NSTEMI present on admission or did it develop during the ED encounter?"]
POA options:
  Y — Yes, condition was present on admission
  N — No, condition was not present on admission
  U — Unknown
  W — Clinically undetermined

Under 150 words. Factual, non-leading. Reference specific clinical timestamps if available.

Write a Level 1 claim denial appeal letter for a medical necessity denial.

Facility/Group: [NAME AND NPI]
Provider: [ATTENDING NAME AND NPI]
Payer: [INSURANCE COMPANY AND PLAN NAME]
Date of denial: [DATE]
Denied service: [CPT CODE AND DESCRIPTION]
Denial reason (exact language from EOB or denial letter): [PASTE THE DENIAL REASON VERBATIM]
Clinical summary of the encounter: [3-5 sentences — patient presentation, clinical findings, treatment provided, outcome]
Evidence of medical necessity: [SPECIFIC CLINICAL DATA — vital signs, lab values, imaging results, documented clinical decision-making]
Applicable clinical guidelines supporting medical necessity: [GUIDELINE NAME AND ORGANIZATION — e.g., "AHA/ACC 2023 Chest Pain Guidelines recommend cardiac biomarker testing (CPT 82228) for all patients presenting with acute chest pain"]
Specific request: Overturn the denial and process the claim for payment.

Under 400 words. Professional tone. Direct rebuttal of the stated denial reason.

Write a timely filing denial appeal with documentation of the original submission date.

Biller/Coder: [NAME]
Facility: [NAME AND NPI]
Payer: [NAME AND PLAN]
Claim number: [NUMBER]
Date of service: [DATE]
Denial reason: Timely filing — claim not received within [X] days of date of service
Evidence of timely original submission: [SELECT ALL THAT APPLY AND FILL IN DETAILS:
  - Electronic clearinghouse acknowledgment receipt: [DATE AND CONFIRMATION NUMBER]
  - EDI 997 or 999 acknowledgment: [DATE]
  - Payer portal submission log: [DATE AND REFERENCE]
  - Certified mail confirmation: [DATE AND TRACKING NUMBER]
  - Previous EOB showing receipt: [DATE AND STATUS]]
State/contract timely filing limit applicable: [X days per contract/regulation]

Request: Reopen and process the claim based on documented timely original submission. Under 300 words.

Write an appeal for a duplicate claim denial where the claims are for distinct services.

Biller: [NAME]
Payer: [NAME]
Denied claim date of service: [DATE]
Denied CPT code: [CODE AND DESCRIPTION]
Original claim that triggered "duplicate" flag: [DATE OF SERVICE AND CPT CODE]
Why these are NOT duplicate services: [SPECIFIC CLINICAL REASON — e.g., "The 04/15 claim (CPT 99214) was for an office visit for hypertension management. The 04/22 claim (CPT 99214) is for a separate acute care visit for UTI — distinct chief complaint, different assessment and plan, documented as a new encounter in the medical record"]
Supporting documentation attached: [LIST — e.g., Progress note 04/15, Progress note 04/22, appointment schedule showing two separate encounters]

Request: Process the 04/22 claim as a separate billable service. Under 250 words.

Write an appeal for a prior authorization required denial where authorization was obtained or was not required.

Facility: [NAME AND NPI]
Provider: [NAME AND NPI]
Payer: [NAME AND PLAN]
Denied service: [CPT CODE]
Denial reason: Prior authorization required — not obtained
[SELECT ONE AND FILL IN:
  OPTION A — Authorization was obtained:
    Authorization number: [NUMBER]
    Authorization obtained on: [DATE]
    Authorized by: [PAYER REPRESENTATIVE NAME IF KNOWN]
    Service authorized: [EXACT SERVICE DESCRIPTION AS ON AUTH]
    Explain discrepancy if any: [WHY THE CLAIM WAS STILL DENIED]
  OPTION B — Service did not require authorization per contract:
    Contract year: [YEAR]
    Specific contract provision or payer policy excluding this service from auth requirements: [REFERENCE]
  OPTION C — Emergency/urgent service where prior authorization was not possible:
    Emergency circumstances: [CLINICAL DESCRIPTION]
    Notification provided: [WHEN AND HOW — e.g., "ER notification call made to payer on [DATE] at [TIME]"]]

Under 300 words. Attach all supporting documentation.

Write an appeal for a claim denied for unbundling where the services were separately reportable.

Coder: [NAME, CREDENTIALS]
Provider: [NAME AND NPI]
Payer: [NAME]
Denied CPT codes: [LIST ALL DENIED CODES WITH DESCRIPTIONS]
Denial reason: Unbundling — services are component parts of [BUNDLING CODE]
Clinical reason the services were separately reportable: [SPECIFIC TECHNICAL ARGUMENT — e.g., "CPT 11042 and CPT 11045 were performed on two anatomically distinct wounds: a 4cm wound on the right heel and a 7cm wound on the left lower leg. These are separate procedures on separate anatomic sites, not a single wound debridement"]
CCI (Correct Coding Initiative) modifier applicable: [MODIFIER 59, XS, XU, XE, or XP — and reason]
Supporting coding guideline: [AMA CPT guidelines, CCI policy, LCD/NCD if applicable]

Request: Reprocess the claim with the modifier recognized and pay the correctly unbundled services. Under 300 words.

Write a weekly denial trend summary memo for the revenue cycle manager.

Reporting period: [DATE RANGE]
Total claims submitted: [NUMBER]
Total claims denied: [NUMBER] ([X]% denial rate)
Denial breakdown by reason code:
  CO-4 (service not covered): [NUMBER] — [$ AMOUNT]
  CO-16 (claim lacks info): [NUMBER] — [$ AMOUNT]
  CO-22 (prior auth required): [NUMBER] — [$ AMOUNT]
  CO-50 (not medically necessary): [NUMBER] — [$ AMOUNT]
  PR-1/PR-2 (patient deductible/coinsurance): [NUMBER] — [$ AMOUNT]
  Other: [DESCRIBE AND AMOUNT]
Top 3 denial clusters to address: [SPECIFIC ROOT CAUSES IDENTIFIED — e.g., "CO-22 spikes for cardiology — payer added auth requirement for CPT 93306 effective 04/01 without adequate notice"]
Recommended actions: [3 SPECIFIC ITEMS — who needs to act, what needs to change, deadline]

Executive memo format. Under 400 words. Include a clear "owner/action/deadline" table.

Write a denial pattern analysis report for a specific payer.

Payer: [INSURANCE COMPANY AND PLAN NAME]
Analysis period: [DATE RANGE]
Denial rate for this payer: [X]% (company average: [Y]%)
Top denial reasons for this payer:
  1. [REASON CODE AND DESCRIPTION] — [NUMBER OF DENIALS] — [$ AT RISK]
  2. [REASON CODE AND DESCRIPTION] — [NUMBER OF DENIALS] — [$ AT RISK]
  3. [REASON CODE AND DESCRIPTION] — [NUMBER OF DENIALS] — [$ AT RISK]
Patterns identified: [SPECIFIC OBSERVATIONS — e.g., "All CO-16 denials from this payer in the last 30 days involve missing NPI in box 33a — front desk process gap identified"]
Appeal win rate for this payer: [X]% (past 90 days)
Recommended next steps: [SPECIFIC ACTIONS — CDI education, front desk retraining, contract review request, escalation to payer rep]

Analytical memo format. Under 350 words. Focus on actionable root causes, not just data.

Write a zero-pay remittance advice review summary for internal tracking.

Date of remittance: [DATE]
Payer: [NAME]
Total claims on this remittance: [NUMBER]
Total $0 paid claims: [NUMBER] — [$ TOTAL AT RISK]
Zero-pay breakdown:
  Patient responsibility — deductible met: [NUMBER] — [$ AMOUNT]
  Patient responsibility — plan not yet met deductible: [NUMBER] — [$ AMOUNT]
  Denied — medical necessity: [NUMBER] — [$ AMOUNT]
  Denied — timely filing: [NUMBER] — [$ AMOUNT]
  Denied — auth required: [NUMBER] — [$ AMOUNT]
  Contractual write-off: [NUMBER] — [$ AMOUNT]
Priority follow-up items: [TOP 3 — specific claims or groups worth appealing or working]
Escalation flag: [ANY UNUSUAL PATTERNS — large denials, systematic errors, payer-side processing errors]

Under 300 words. Summary format suitable for pasting into the AR log.

Write a narrative summary of the current appeals aging report for a leadership update.

Report date: [DATE]
Total open appeals: [NUMBER] — [$ TOTAL]
Aging breakdown:
  0–30 days: [NUMBER] — [$ AMOUNT]
  31–60 days: [NUMBER] — [$ AMOUNT]
  61–90 days: [NUMBER] — [$ AMOUNT]
  91+ days: [NUMBER] — [$ AMOUNT] (risk of exceeding appeal deadline)
Highest-value single appeal: [$ AMOUNT — claim description]
Appeals at risk of missed deadline: [NUMBER] — [LIST TOP 3 BY DOLLAR AMOUNT WITH DEADLINE DATE]
Appeal win rate (past 90 days): [X]% — [TRENDING UP/DOWN VS. PRIOR QUARTER]
Recommended actions: [SPECIFIC — which appeals need immediate action, who should review, outsource threshold?]

Leadership update narrative format. Under 350 words. Clear owner/timeline on every action item.

Write a payer policy change alert memo to distribute to coding and clinical staff.

Payer: [NAME AND PLAN]
Effective date of policy change: [DATE]
Policy change description: [WHAT IS CHANGING — e.g., "Effective June 1, 2026, [Payer] requires prior authorization for all outpatient sleep studies (CPT 95810, 95811) on Medicare Advantage plans"]
Procedures or codes affected: [LIST CPT/HCPCS CODES]
What this means for our workflow: [SPECIFIC PRACTICE CHANGE — e.g., "PA requests must be submitted at least 5 business days before the procedure; current ordering workflow sends to scheduling first — process must be updated to route to auth team before scheduling"]
Who needs to know: [SPECIFIC DEPARTMENTS OR ROLES — e.g., "Sleep lab scheduler, ordering physician offices, prior auth team"]
Action by: [DATE AND RESPONSIBLE PARTY]

Alert memo format. Under 300 words. Clear, direct, actionable.

Write a response to an internal coding audit finding.

Coder/coding manager: [NAME AND CREDENTIALS]
Audit conducted by: [INTERNAL COMPLIANCE TEAM / EXTERNAL AUDITOR]
Audit date: [DATE]
Finding: [SPECIFIC AUDIT FINDING — e.g., "CPT 99215 was coded for 8 of 10 encounters reviewed; documentation supports 99214 in 6 of those encounters — overcoding pattern identified"]
Coder's response to the finding:
  Acknowledgment: [AGREE/PARTIALLY AGREE/DISAGREE — AND WHY]
  Root cause analysis: [WHAT CAUSED THE PATTERN — training gap, documentation ambiguity, guideline interpretation difference]
  Corrective action plan: [SPECIFIC STEPS — e.g., "Will complete AAPC's E&M coding refresher module, request clarification from CDI team on documentation specificity requirements, and perform self-audit of next 30 encounters with peer review"]
  Timeline for correction: [SPECIFIC DATES]

Professional response format. Factual, non-defensive. Under 350 words.

Write a corrective action plan (CAP) in response to a payer audit demand letter.

Facility: [NAME AND NPI]
Payer: [NAME AND PLAN]
Audit reference number: [NUMBER]
Audit finding summary: [WHAT THE PAYER FOUND — e.g., "Overpayment claim of $47,200 for 23 E&M visits coded at 99215 reviewed and determined to support 99213 or 99214 only"]
Disputed/undisputed amount: [$ DISPUTED / $ UNDISPUTED]
Corrective actions:
  1. Process improvement: [SPECIFIC CHANGE — e.g., "Implement secondary E&M level review for all level-5 office visit codes before claim submission"]
  2. Education: [TRAINING BEING IMPLEMENTED — who, what, by when]
  3. Monitoring: [ONGOING AUDIT SCHEDULE — e.g., "Monthly 10% random sample audit of E&M coding for the next 6 months"]
Overpayment resolution: [DISPUTE PROCESS INITIATED / REFUND OF $X ATTACHED / PAYMENT PLAN REQUESTED]
Contact for questions: [COMPLIANCE OFFICER NAME AND CONTACT INFO]

Under 400 words. Professional, cooperative tone. CAP must be specific and time-bound.

Write a HIPAA minimum necessary justification memo for a coding team's record access requirements.

Compliance officer or coding manager: [NAME]
Purpose: Documentation of minimum necessary access for coding department under HIPAA 45 CFR §164.514(d)
Coding role: [TITLE — e.g., Inpatient Coder, Outpatient Coder, CDI Specialist]
Access required: [SYSTEMS AND RECORD TYPES — e.g., "Epic EHR — full encounter documentation including clinical notes, lab results, radiology reports, operative reports, and discharge summaries for all encounters being coded"]
Why full clinical documentation access is necessary: [SPECIFIC CODING REASON — e.g., "ICD-10-PCS procedure codes require documentation of the specific approach, device, and qualifier — access to operative reports, anesthesia records, and pathology reports is required to code to the highest specificity. Limiting access to a subset of documentation would result in coding errors and compliance violations"]
Access controls in place: [AUDIT TRAILS, ROLE-BASED ACCESS, ANNUAL REVIEW — describe]

Under 300 words. Regulatory compliance tone. Reference specific HIPAA provision.

Write an internal documentation note for a coding discrepancy identified after claim submission.

Coder: [NAME AND CREDENTIALS]
Date discrepancy identified: [DATE]
Original code submitted: [ICD-10/CPT CODE AND DESCRIPTION]
Corrected code: [CORRECT CODE AND DESCRIPTION]
Reason for discrepancy: [SPECIFIC CAUSE — e.g., "Documentation reviewed during appeal preparation revealed a lab result not previously available at time of coding that supports a more specific diagnosis code"]
Action taken: [CORRECTED CLAIM SUBMITTED / CREDIT BALANCE NOTED / REFUND INITIATED / APPEAL WITHDRAWN]
Date corrected claim submitted: [DATE]
Disclosure required: [YES — proactive disclosure protocol initiated / NO — internal correction only per [POLICY NAME]]

This is an internal documentation note for the compliance file. Under 200 words. Factual and specific.

Write an internal coding guideline interpretation memo for a specific coding scenario.

Author: [CODER OR CODING MANAGER NAME AND CREDENTIALS]
Issue date: [DATE]
Topic: [CODING QUESTION — e.g., "Reporting of modifier 25 with evaluation and management services on the same date as a procedure"]
Relevant CPT/ICD-10 guideline: [SPECIFIC GUIDELINE TEXT OR REFERENCE]
Payer-specific policy (if different from standard): [PAYER NAME AND POLICY VARIATION]
Our interpretation: [SPECIFIC CONCLUSION AND RATIONALE — e.g., "Modifier 25 is appropriate when the E&M service is for a separately identifiable significant condition from the procedure performed. Documentation must support two distinct clinical decision-making pathways in the same note. We will append modifier 25 only when the attending's note explicitly documents the separate presenting problem and clinical assessment"]
Effective for encounters beginning: [DATE]
Coding guidance owner: [NAME AND ROLE]

Internal memo format. Cite sources. Under 300 words.

Write a medical necessity narrative for a prior authorization request for a high-cost procedure.

Ordering provider: [NAME, SPECIALTY, NPI]
Requested procedure: [CPT CODE AND DESCRIPTION]
Payer: [NAME AND PLAN]
Patient: [AGE, SEX — NO PHI IN PROMPT]
Diagnosis: [ICD-10 CODE AND DESCRIPTION]
Clinical indication: [SPECIFIC FINDINGS — symptoms, severity, duration, functional impact, objective data]
Conservative treatments already attempted and failed: [LIST — treatment, dose or duration, outcome, date discontinued]
Why this specific procedure is medically necessary: [CLINICAL RATIONALE — connect the failed treatments and clinical findings to the specific procedure being requested]
Supporting evidence: [CLINICAL GUIDELINE, SOCIETY RECOMMENDATION, OR PEER-REVIEWED EVIDENCE — specific reference]
Expected clinical outcome: [WHAT IMPROVEMENT IS EXPECTED AND HOW IT WILL BE MEASURED]

Medical necessity narrative for prior auth form. Under 350 words. Clinical language, specific data.

Write a prior authorization request narrative for durable medical equipment.

Ordering provider: [NAME, NPI]
Equipment requested: [SPECIFIC ITEM AND HCPCS CODE]
Patient: [AGE, SEX]
Diagnosis: [ICD-10 CODE AND DESCRIPTION]
Clinical need: [SPECIFIC FINDINGS — what the patient cannot do without this equipment, objective measurements, clinical documentation supporting the need]
Face-to-face encounter: [DATE — required for many DME categories]
Duration of medical necessity: [LIFETIME / X MONTHS — clinical basis for duration]
Equipment being replaced (if applicable): [PRIOR EQUIPMENT, REASON FOR REPLACEMENT]

DME prior auths are approved with objective, functional, and diagnosis-specific language. "Patient needs X for quality of life" is rejected. Under 250 words.

Write a specialty medication prior authorization appeal narrative following a denial.

Provider: [NAME, NPI, SPECIALTY]
Medication denied: [DRUG NAME AND NDC CODE]
Diagnosis: [ICD-10 AND DESCRIPTION]
Payer denial reason: [EXACT LANGUAGE]
Step therapy documentation: [MEDICATIONS REQUIRED BY PAYER — list each with dose, duration, documented reason for failure or contraindication]
Why step therapy failed or is contraindicated: [SPECIFIC CLINICAL DATA — adverse reaction documentation, failed trial evidence, contraindication with current conditions or medications]
Clinical urgency: [IF TIME-SENSITIVE — specific clinical risk of delayed treatment]
Supporting literature: [CITE SPECIFIC GUIDELINE OR TRIAL — e.g., "Per ACR 2024 guidelines, biologic therapy is indicated for moderate-to-severe RA patients who have failed 2 conventional DMARDs"]

Under 350 words. Direct rebuttal of step therapy requirement with specific evidence.

Write a formal inquiry letter to a payer's provider relations team regarding a contract issue.

Facility: [NAME AND NPI]
Provider relations contact: [NAME IF KNOWN]
Payer: [INSURANCE COMPANY]
Subject: [SPECIFIC ISSUE — e.g., "Reimbursement Rate Discrepancy for CPT 93306 — Effective Date of Fee Schedule Update"]
Description of issue: [SPECIFIC PROBLEM — e.g., "Our February 2026 remittances for CPT 93306 reflect the 2024 fee schedule rate of $412.17 rather than the 2026 contracted rate of $447.83, effective January 1, 2026 per the contract amendment signed October 2025"]
$ amount of discrepancy identified: [TOTAL AMOUNT UNDERPAID]
Date range affected: [DATE RANGE]
Documentation attached: [LIST — executed contract amendment, sample EOBs, claim list]
Requested action: [SPECIFIC — e.g., "Reprocess all claims from January 1 through current date at the 2026 contracted rate and issue corrected EOBs within 30 days"]
Response requested by: [DATE]

Professional business letter format. Under 300 words.

Write a financial counseling script for coding or billing staff to use when explaining a denial to a patient.

Staff role: [CODER / BILLING SPECIALIST / PATIENT FINANCIAL ADVOCATE]
Situation: [TYPE OF CALL — e.g., "Patient received an unexpected bill after insurance denied the claim"]
Denial type: [SPECIFIC — e.g., "Service not covered under patient's plan / Deductible not met / Prior authorization not obtained"]
Patient concern: [WHAT THE PATIENT IS LIKELY TO SAY — e.g., "My doctor said this was covered" or "I didn't know I had to get approval"]
What happened (plain language): [CLINICAL AND BILLING EXPLANATION IN PLAIN LANGUAGE — no jargon]
What the patient's options are: [SPECIFIC OPTIONS — e.g., "1. Appeal through your insurance (we can help), 2. Apply for our financial assistance program, 3. Set up a payment plan, 4. Request peer-to-peer review if medically necessary"]
What we're doing on our end: [SPECIFIC NEXT STEPS — coder or billing team action]

Empathetic but factual tone. Under 300 words. Patient-appropriate language — no coding jargon.

Write a demand letter to a payer that has failed to process a claim or appeal within the required timeframe.

Facility: [NAME AND NPI]
Payer: [INSURANCE COMPANY AND PLAN]
Claim number(s): [LIST]
Date(s) of service: [DATES]
Date(s) claim/appeal submitted: [DATES]
State prompt pay law / federal regulation applicable: [SPECIFIC LAW — e.g., "California Health & Safety Code Section 1371.35 requires payment or denial within 30 days of clean claim receipt"]
Current status (days outstanding): [NUMBER OF DAYS — and why it violates prompt pay requirements]
Amount at issue: [$ TOTAL]
Previous contact attempts: [DATE AND PERSON CONTACTED IF APPLICABLE]
Demand: [PAY THE CLAIM WITHIN X DAYS OR PROVIDE WRITTEN DENIAL WITH SPECIFIC REASON BY DATE]
State insurance commissioner contact if escalation is needed: [CONTACT INFO]

Formal demand letter format. Under 300 words. Cite specific statute.

Write a continuing education reflection for AAPC or AHIMA CEU documentation.

CE activity completed: [WEBINAR / MODULE / CONFERENCE SESSION — title and provider]
Date completed: [DATE]
CEU hours: [NUMBER] — [CATEGORY — e.g., Medical Coding, CDI, Compliance, Ethics]
Key takeaways applicable to daily coding work: [3-5 SPECIFIC INSIGHTS — not summaries, actionable findings]
How this changes or reinforces my current coding practice: [SPECIFIC APPLICATION TO ACTUAL CODING WORKFLOW]
Cases or code scenarios where I will apply this learning: [EXAMPLE — e.g., "Will apply updated CC/MCC guidance from the session to my CDI query process for cardiac encounters"]

CEU log entries are more useful when they document practice application. Under 250 words.

Write a professional feedback note for a coding peer review session.

Reviewer: [NAME AND CREDENTIALS]
Coder reviewed: [NAME AND CREDENTIALS]
Review date: [DATE]
Sample reviewed: [NUMBER OF ENCOUNTERS AND TYPE — e.g., "15 inpatient surgical encounters, Q1 2026"]
Accuracy rate: [X]%
Findings:
  Correct codes/no change: [NUMBER]
  Coding errors — significant (affecting DRG or RVU): [NUMBER] — [BRIEF DESCRIPTION OF ERROR TYPE]
  Coding errors — minor (specificity/sequencing): [NUMBER] — [BRIEF DESCRIPTION]
  Documentation deficiencies recommended for query: [NUMBER]
Strengths observed: [SPECIFIC POSITIVE OBSERVATIONS]
Areas for improvement: [SPECIFIC, CONSTRUCTIVE — e.g., "ICD-10-PCS root operation selection for complex spine procedures — recommend review of operative report documentation guidelines for the fusion root operation vs. repair"]
Recommended follow-up: [TRAINING, SELF-AUDIT, FOLLOW-UP REVIEW DATE]

Professional tone. Specific, evidence-based feedback. Under 300 words.

Write an annual CPC or CCS certification maintenance plan.

Coder: [NAME AND CURRENT CREDENTIALS]
Certification body: [AAPC / AHIMA]
Renewal date: [DATE]
Required CEUs for this cycle: [NUMBER — typically 36 for CPC, 20 for CCS]
CEUs completed to date: [NUMBER]
Remaining CEUs needed: [NUMBER]
Planned CEU sources:
  [SOURCE 1]: [TOPIC, CEU HOURS, PLANNED DATE]
  [SOURCE 2]: [TOPIC, CEU HOURS, PLANNED DATE]
  [SOURCE 3]: [TOPIC, CEU HOURS, PLANNED DATE]
Ethics requirement status: [COMPLETED / PLANNED DATE]
Annual dues status: [PAID / DUE BY DATE]
Additional credentials being pursued: [CRC, COC, CPCO, CDIP, etc. — or "none this cycle"]

Maintenance plan format. Under 250 words. Specific dates and sources.

Write a cover letter for a medical coding job application.

Applicant: [NAME, CREDENTIALS — e.g., CPC, CPC-H, CCS]
Years of experience: [NUMBER]
Primary coding specialty: [INPATIENT/OUTPATIENT/SPECIALTY — e.g., "Outpatient multi-specialty coding with 4 years cardiology and orthopedics focus"]
Target position: [JOB TITLE AND EMPLOYER NAME]
Specific qualification highlights:
  1. [MEASURABLE ACHIEVEMENT — e.g., "Maintained 98.7% coding accuracy rate over 24 months of monthly audits at [employer]"]
  2. [RELEVANT SKILL — e.g., "Proficient in Epic, 3M 360 Encompass, and Optum360 encoder"]
  3. [SPECIFIC EXPERTISE — e.g., "Experienced with CDI query process for MS-DRG optimization in Level 1 trauma center setting"]
Why this position: [SPECIFIC REASON — what the employer offers that the applicant values]

Professional cover letter format. Under 350 words. Lead with the most impressive credential.

Write an annual performance self-evaluation for a medical coder.

Coder: [NAME AND CREDENTIALS]
Review period: [DATE RANGE]
Coding accuracy rate: [X]% (target: [Y]%)
Productivity: [AVERAGE CPT/ICD-10 CODES PER DAY OR CHARTS PER DAY] vs. target
Denial rate improvement: [IF APPLICABLE — before/after comparison]
Continuing education completed: [CEU HOURS AND SPECIFIC COURSES]
Special projects or contributions: [CDI INITIATIVE, PROCESS IMPROVEMENT, AUDIT SUPPORT, ONBOARDING HELP, ETC.]
Areas of growth: [HONEST SELF-ASSESSMENT — specific coding scenario you strengthened]
Goals for next review period: [3 SPECIFIC, MEASURABLE GOALS WITH TIMELINES — e.g., "Achieve CRC credential by Q3, reduce E&M coding query rate from 8% to 5% through documentation education, complete inpatient coder certification module by December"]

Self-evaluation format. Under 400 words. Lead with measurable outcomes.

Write a quick reference guide explaining a specific ICD-10-CM or ICD-10-PCS coding principle for new coders.

Topic: [SPECIFIC PRINCIPLE — e.g., "When to Code Signs and Symptoms vs. Definitive Diagnosis in Outpatient Settings" or "ICD-10-PCS Root Operation Selection: Excision vs. Resection"]
Official guideline reference: [CITE ICD-10-CM OFFICIAL CODING GUIDELINES SECTION — e.g., "Section I.C.1.a — Coding confirmed vs. uncertain diagnoses in inpatient settings"]
Plain-language explanation: [WHAT THE GUIDELINE MEANS IN PRACTICE]
Three concrete examples:
  Example 1 (correct application): [SCENARIO AND CODE ASSIGNMENT — why this is correct]
  Example 2 (common mistake): [SCENARIO AND INCORRECT CODE — why this is wrong and what the correct code is]
  Example 3 (edge case): [SCENARIO AND CODING DECISION WITH RATIONALE]
Memory aid: [ONE-LINE RULE THAT HELPS A CODER REMEMBER THE PRINCIPLE]

Under 400 words. Educational tone. Reference the official guideline section.

Write a narrative onboarding checklist for a new medical coder joining the department.

Department: [NAME AND SPECIALTY — e.g., "Outpatient Multi-Specialty Coding"]
New coder name: [NAME AND CREDENTIALS]
Start date: [DATE]
30-day milestones:
  Week 1: [SPECIFIC TRAINING ITEMS — system access, shadow sessions, guideline review]
  Week 2: [SPECIFIC CODING TASKS — start with [VOLUME] charts per day, [SPECIALTY] encounters]
  Week 3-4: [PRODUCTIVITY RAMP — target [X] charts/day, first accuracy audit]
60-day milestone: [SPECIFIC — e.g., "Full productivity achieved for outpatient E&M coding; inpatient surgical coding training begun"]
90-day milestone: [SPECIFIC — e.g., "Full productivity across all assigned specialties; first formal peer review conducted"]
Systems to learn: [LIST — EHR, encoder, billing platform, EDITS software]
Mentor assigned: [NAME AND ROLE]

Onboarding checklist narrative format. Under 400 words. Specific, sequential, measurable.

Write a coding team meeting agenda for a monthly quality review.

Meeting date and time: [DATE AND TIME]
Facilitator: [CODING MANAGER OR SUPERVISOR NAME]
Attendees: [TEAM COMPOSITION — e.g., "8 outpatient coders, 2 CDI specialists, billing manager"]
Agenda items:
  1. Accuracy report review: [THIS MONTH'S TEAM ACCURACY RATE AND TOP ERROR TYPES]
  2. Denial trend update: [TOP 3 DENIAL REASONS THIS MONTH AND APPEAL WIN RATE]
  3. Payer policy changes effective this month: [LIST ANY NEW REQUIREMENTS]
  4. Coding question/gray area of the month: [SPECIFIC CODING SCENARIO — open discussion]
  5. Continuing education announcement: [UPCOMING WEBINARS, AAPC/AHIMA EVENTS]
  6. Q&A and open floor: [10 MINUTES]
Prework required: [WHAT ATTENDEES SHOULD REVIEW BEFORE THE MEETING]
Action items from last meeting: [STATUS UPDATE ON PRIOR ACTION ITEMS]

Meeting agenda format. Under 300 words. Time estimates for each item welcome.

Write a Coder of the Month recognition note to share with the department.

Recognized coder: [NAME AND CREDENTIALS]
Recognition period: [MONTH AND YEAR]
Key achievements:
  1. [SPECIFIC MEASURABLE ACHIEVEMENT — e.g., "Achieved 99.2% coding accuracy in April across 1,247 coded encounters — highest rate on the team"]
  2. [SPECIFIC CONTRIBUTION — e.g., "Identified a systematic front-end error in the prior auth workflow for cardiology that was causing 18% of all cardiology PA denials — escalated to the PA team and the fix reduced cardiology denials by 40% in the following month"]
  3. [OPTIONAL THIRD ACHIEVEMENT]
Why this recognition matters: [BRIEF NOTE ON HOW THIS WORK BENEFITED THE TEAM, PATIENTS, OR ORGANIZATION]

Professional recognition note. Under 200 words. Specific and data-driven — generic praise means nothing.