Your coders understand MEAT criteria. Monitor, Evaluate, Assess, Treat. They’ve been trained extensively. They can explain what each letter means. They pass certification exams testing MEAT knowledge.
Then a RADV audit reveals your organization has a 17% overturn rate on diagnoses your coders believed had adequate MEAT criteria. The codes that seemed bulletproof during internal QA are failing external audit.
The problem isn’t that your coders don’t understand MEAT criteria conceptually. The problem is they’re making a fundamental assumption about how MEAT criteria works that doesn’t match how CMS auditors apply it.
The Single Element Sufficiency Assumption
Your coders were trained that MEAT criteria requires documentation of at least one of the four elements: Monitor OR Evaluate OR Assess OR Treat. The “OR” is critical. One element should be sufficient.
Your coder reviews a note documenting: “Patient continues metformin 1000mg twice daily for diabetes management.” The coder identifies this as “Treat” (medication management). One MEAT element is present. The coder codes diabetes.
CMS auditor rejects it. Their rationale: While treatment is mentioned, there’s no evidence the provider actually evaluated the patient’s diabetes status during this encounter. The medication continuation might be automatic refill, not active clinical management.
The assumption gap: Your coders think any single MEAT element is adequate. CMS auditors increasingly expect multiple MEAT elements for chronic conditions, or at minimum, evidence that the single MEAT element represents active clinical engagement rather than administrative documentation.
For chronic conditions like diabetes, CHF, or COPD, documentation showing only treatment without any monitoring, evaluation, or assessment creates audit risk. CMS wants to see evidence the provider actually managed the condition during the encounter, not just perpetuated existing treatment.
The fix requires adjusting coder expectations. While technically one MEAT element may be sufficient, conditions with only a single MEAT element (especially only Treatment without any Monitoring, Evaluation, or Assessment) should trigger provider queries for additional detail.
The Problem List Equals Assessment Mistake
Your coders were trained that “Assess” means the provider identified the condition during the encounter. If a condition appears in the assessment section of the note, the “Assess” element of MEAT is satisfied.
Your coder reviews a note where “Type 2 Diabetes” appears in the assessment/problem list section. The coder considers this adequate Assessment. The coder codes diabetes.
CMS auditor rejects it. Their rationale: The condition appearing in a problem list doesn’t demonstrate the provider assessed the patient’s current status. Problem lists often contain historical conditions copied forward without active evaluation.
The assumption gap: Your coders think problem list presence equals Assessment. CMS auditors want evidence the provider actually evaluated the condition’s current impact on the patient during this specific encounter.
“Assessment” in MEAT criteria doesn’t mean “the provider listed it in the assessment section.” It means “the provider assessed the patient’s current clinical status regarding this condition.” Those are different things.
The fix requires training coders to distinguish between documentation showing a condition exists versus documentation showing the provider evaluated the condition’s current status. “Patient has diabetes” (problem list mention) is not the same as “Patient’s diabetes is well-controlled on current regimen with A1C 6.8” (actual assessment).
The Historical Documentation Continuity Confusion
Your coders were trained that chronic conditions need to be documented at least once annually. If a chronic condition was documented with full MEAT criteria in January, and the patient has multiple encounters throughout the year, the January documentation validates coding the condition all year.
Your coder reviews a June encounter mentioning “diabetes” in the problem list but no diabetes-specific evaluation or management. The coder codes diabetes based on the comprehensive January documentation that had full MEAT criteria.
CMS auditor rejects the June coding. Their rationale: Each encounter’s coding must be supported by that encounter’s documentation. The January encounter can be coded based on January’s MEAT criteria. The June encounter needs its own MEAT criteria documentation.
The assumption gap: Your coders think adequate MEAT documentation in one encounter validates coding in subsequent encounters. CMS auditors evaluate each encounter independently.
This creates particular problems in organizations with high encounter frequency. A patient with diabetes might have eight encounters annually. If only the annual wellness visit documents comprehensive diabetes management and the other seven encounters just list “diabetes” in the problem list, CMS’s position is that you can code diabetes once (at the wellness visit) not eight times.
The fix requires either: (1) ensuring chronic conditions have MEAT criteria documentation at each encounter where they’re coded, or (2) coding chronic conditions only at encounters with adequate MEAT documentation and not coding them at other encounters.
The Implied Clinical Judgment Problem
Your coders were trained to use clinical judgment. If a provider documents clinical information that implies evaluation of a condition, coders can infer MEAT criteria is present.
Your coder reviews: “Patient’s CHF medications include Lasix 40mg daily and carvedilol 12.5mg twice daily. Patient reports improved breathing and less leg swelling.” The coder infers the provider evaluated CHF status (implied by medication review and symptom inquiry). The coder codes CHF.
CMS auditor rejects it. Their rationale: The provider never explicitly stated they evaluated CHF. The auditor won’t infer evaluation from symptom documentation that could be incidental conversation rather than structured assessment.
The assumption gap: Your coders think clinical context allows reasonable inference of MEAT criteria. CMS auditors want explicit documentation without requiring inference.
When clinical evaluation is implied but not stated, audit risk increases. “Patient reports improved breathing” could mean the provider systematically evaluated CHF status, or it could mean the patient volunteered information the provider passively noted.
The fix requires training providers to explicitly document evaluation. Instead of documenting symptoms that imply evaluation occurred, document the evaluation: “Evaluated patient’s CHF status. Patient reports decreased dyspnea and orthopnea. Lower extremity edema improved from +2 to trace. Continue current CHF regimen.”
The Specialist Documentation Reliance
Your coders were trained that documentation from any qualified provider can support coding. If a specialist documents comprehensive evaluation of a condition, that documentation can validate coding at other encounters.
Your coder reviews a primary care visit documenting “diabetes” in the problem list. The patient saw endocrinology last month with comprehensive diabetes evaluation including A1C, medication adjustments, and complication screening. The coder codes diabetes at the primary care visit based on the specialist’s documentation.
CMS auditor rejects it. Their rationale: The primary care encounter being coded doesn’t contain MEAT criteria for diabetes. The specialist’s documentation supports coding at the specialist encounter, not at unrelated encounters.
The assumption gap: Your coders think specialist documentation validates coding across all encounters. CMS auditors require each encounter to have its own supporting documentation.
This becomes particularly problematic when patients see multiple specialists. The cardiologist documents comprehensive CHF management. The nephrologist documents comprehensive CKD management. The endocrinologist documents comprehensive diabetes management. The primary care provider lists all three conditions in the problem list without specific evaluation. Your coders code all three at the primary care visit. CMS audits reject all three because the primary care documentation doesn’t support them.
What Actually Works for MEAT Criteria Coding
Preventing MEAT criteria audit failures requires aligning coder expectations with CMS auditor interpretation.
Train coders that single MEAT element documentation (especially Treatment alone) creates audit risk for chronic conditions. Teach coders that problem list presence isn’t adequate Assessment – actual evaluation of current status is required. Ensure coders understand each encounter needs independent MEAT criteria documentation, not reliance on prior encounters. Eliminate inference-based coding – require explicit documentation of evaluation and management. Code based only on the specific encounter’s documentation, not specialist documentation from other encounters.
Organizations with high MEAT criteria coding validation rates aren’t the ones with the most liberal interpretation of MEAT requirements. They’re the ones with the most conservative interpretation that matches CMS auditor expectations. If your internal QA accepts MEAT criteria documentation that external auditors reject, you’ve got an interpretation alignment problem. Close the gap before RADV audits expose it.
