Healthcare Administrators
Clinical Documentation Reviewer for Denial Prevention
Review clinical documentation for completeness and payer-readiness before claim submission. This prompt helps healthcare administrators identify documentation gaps that commonly lead to medical necessity and coding denials — enabling proactive correction before claims are submitted.
This prompt helps healthcare administrators perform a pre-submission documentation review by working with service type, CPT and ICD-10 codes, payer type, and a description of documentation completeness — no actual patient records or PHI are input. It produces a structured review covering medical necessity assessment, diagnosis code support, procedure documentation adequacy, specific documentation gaps, querying opportunities for clinical staff, an overall risk level, and a prioritized action list. It is designed for CDI specialists, coding teams, and revenue cycle managers at physician practices and hospital outpatient departments conducting prospective denial prevention reviews.
Testedclaude-sonnet-4-6ValidatedMar 2026ScopeThis does not constitute medical advice. Follow HIPAA guidel…TierAdvanced
Constraints
This does not constitute medical advice. Follow HIPAA guidelines. Recommend consulting qualified healthcare professionals.
Never include actual patient Protected Health Information (PHI) in prompts or outputs.
Documentation reviews must not result in altering clinical documentation to support billing — documentation must reflect actual clinical care provided.
Upcoding (billing for a higher level of service than documented) is healthcare fraud — documentation reviews should identify appropriate coding, not maximize revenue at the expense of accuracy.
Tested Models
claude-sonnet-4-6
Uncertainty
If documentation is described in general terms without clinical specifics, note that the review framework is general guidance and that the actual documentation must be reviewed by a qualified coder or CDI specialist for a specific risk assessment.
Scope
PHI-free admin only — use a BAA-compliant AI (e.g. BastionGPT or Azure OpenAI) for PHI.
Last updated
2026-05-28 — Published
The prompt
You are a senior healthcare administrator with expertise in clinical documentation integrity, medical necessity review, and payer audit preparedness. Review the following clinical documentation for denial prevention: Claim context: - Service type: [SERVICE_TYPE] - CPT code(s): [CPT_CODES] - ICD-10 diagnosis codes: [DIAGNOSIS_CODES] - Payer type: [MEDICARE / MEDICAID / COMMERCIAL] - Setting: [INPATIENT / OUTPATIENT / OFFICE] Documentation available for review (describe without PHI): - Note type(s): [NOTE_TYPES — e.g., H&P, progress note, operative report, discharge summary] - Documentation completeness: [DESCRIBE WHAT IS PRESENT VS. MISSING] - Known payer scrutiny areas for this service: [KNOWN_ISSUES] Perform a documentation review covering: ## Medical Necessity Documentation Assessment Is the documentation sufficient to support medical necessity for the claimed service? What specific elements establish or undermine medical necessity? ## Diagnosis Code Support Are the ICD-10 diagnosis codes documented with sufficient clinical specificity to support the codes billed? Are secondary diagnoses that affect complexity or decision-making documented? ## Procedure/Service Documentation Adequacy Does the documentation support the CPT code(s) billed? For E/M services: medical decision-making or time; for procedures: operative report completeness. ## Documentation Gaps Specific elements that are missing or insufficiently documented that could support a denial if the claim is audited. ## Querying Opportunities Items where a clarification query to the treating provider (through CDI process) could improve documentation without altering clinical facts. ## Risk Assessment Overall risk level for denial or audit if submitted as-is: Low / Moderate / High — with specific risk factors identified. ## Recommended Actions Prioritized action list: what must be corrected, what should be queried, what can proceed as-is.
WAITLIST
Runner beta coming — join the waitlist.
In-product execution isn't live yet. Leave your email and we'll let you know if the Runner beta opens.
How to use this prompt
1
1. Use this review framework for prospective review (before claim submission) on high-risk service types — after-the-fact reviews require more complex remediation.
2
2. Share the review output with the clinical team as educational feedback, not as criticism — documentation improvement is a collaborative process.
3
3. Track documentation deficiency patterns by provider and service type to identify where focused education or CDI staffing is most needed.
Customization tips
Add 'Focus the review on inpatient DRG accuracy — identify documentation that supports or undermines the assigned DRG' for hospital inpatient billing.
For E/M services, add 'Apply the current AMA E/M guidelines for medical decision-making documentation — confirm that the level of MDM is clearly documented.'
Append 'Flag any documentation that uses cloned note text without personalization — this is a significant audit risk for post-payment review.'
Sample output
Clinical Documentation Review — Specificity Improvement Recommendations
Chart Audit: Internal Medicine Outpatient Visit — 12 records reviewed this cycle
DOCUMENTATION DEFICIENCIES IDENTIFIED:
Case 1 — Coding Opportunity: Acute on Chronic Conditions
Current documentation: "Patient with CHF, doing poorly"
Recommended improvement: Specify current acuity (acute exacerbation vs. chronic stable), current ejection fraction classification (HFrEF vs. HFpEF), NYHA functional class, and whether current presentation represents decompensation requiring treatment change. Specificity supports correct severity-of-illness capture.
Case 4 — Comorbidity Not Linked to Encounter
Current documentation: "Type 2 diabetes, controlled — no issues today"
Required addition: Diabetes with or without complications must be documented with current manifestation status when it is managed during the encounter. Even "well-controlled" diabetes may have monitored complications that should be co-coded. Note whether a point-of-care test was reviewed and what clinical decision was made.
Case 7 — Procedure Documentation Incomplete
Current documentation: "Injected right knee"
Required elements: Specific injection site (intra-articular vs. periarticular), substance administered (corticosteroid class — document class only, avoid brand names), volume, patient response to procedure at time of service, and follow-up plan.
Case 9 — Symptom vs. Definitive Diagnosis
Current documentation: "Chest pain, r/o PE"
Required clarification: If PE was ruled out during the encounter, document the confirmed working diagnosis. Coding symptom codes when a definitive diagnosis has been established is inappropriate. If workup is ongoing, document "chest pain, evaluation in progress."
Case 12 — Uncertainty Instruction Not Followed
Current documentation: "Possible viral syndrome"
Per coding guidelines, "possible" conditions may be coded for inpatient settings but require the coder to use symptom codes in outpatient settings. Revise to document presenting symptoms (fever, myalgias, sore throat) as the primary encounter reason.
Recommended Actions: Schedule clinical documentation improvement training for Q2. Provide individualized feedback to providers with 3+ deficiencies. Track query response rates monthly.
Related prompts
Frequently asked questions
CDI is a process by which clinical documentation specialists review records to identify documentation gaps that affect coding accuracy and reimbursement. CDI specialists query physicians to clarify ambiguous documentation — for example, whether a condition is 'acute' or 'chronic,' whether conditions are 'present on admission,' or to clarify the clinical relationship between diagnoses. CDI must only clarify existing clinical facts, never create or alter clinical information to change coding. CDI is appropriate for complex inpatient cases, high-cost procedures, and services at high risk for medical necessity denials.
Focus training on documenting the clinical reality accurately and completely. Physicians should document: why the service was medically necessary (not just what was done), the complexity of medical decision-making, responses to treatment, co-morbidities that affect the patient's course, and the clinical basis for diagnoses. Documentation training should emphasize that complete and accurate documentation protects both the patient (continuity of care) and the practice (reimbursement and audit defense) — not that it is about maximizing revenue.
Professional Disclaimer
This AI-generated content is for informational and educational purposes only. It does not constitute medical or legal advice. Always follow HIPAA guidelines and consult qualified healthcare professionals for specific clinical or regulatory matters.