MEAT Documentation Review: Uses, Limits, and Chart Examples

MEAT, Monitor, Evaluate, Assess or Address, and Treat, is an industry documentation-review mnemonic. It is not an ICD-10-CM coding rule, a CMS regulation, a required phrase, or a universal RADV pass/fail test. CMS RADV verifies whether submitted diagnoses are supported by medical records, while the classification and Official Guidelines govern code assignment. Apply the encounter, provider, data-period, program, and payer requirements for the case.

This is the HCC Buddy worked-example guide. The short source-boundary reference stays on MEAT documentation review. The examples below show where coders may look; they do not determine reportability by themselves.

This guide walks through common chart language and edge cases. Always return to the full record and applicable official requirements before assigning a code.

Where MEAT Came From and Why It Exists

MEAT is a coding-industry training aid. Organizations define and apply it differently. The AAPC MEAT article is an industry reference, not CMS authority. Do not turn its four labels into an automatic code-assignment rule.

The current CMS RADV program page says CMS checks whether diagnoses submitted for risk adjustment are supported in enrollee medical records. It does not instruct reviewers to count MEAT elements. Use the payment-year-specific RADV methods and instructions for an audit.

The Four Elements

M, Monitor

Monitoring means the provider is watching the condition over time. The clearest evidence of monitoring is an order or a result tied to that condition: a hemoglobin A1c for diabetes, a serum creatinine and eGFR for chronic kidney disease, a blood pressure reading for hypertension, an ECG for atrial fibrillation, an INR for warfarin therapy, a TSH for hypothyroidism.

A provider note that says "Diabetes, A1c 7.4 today, will recheck in 3 months" is monitoring. A note that just lists "diabetes" with no labs, no vitals, no orders, no plan to recheck is not.

Examples that may be relevant in context:

Examples that are not enough by themselves:

E, Evaluate

Evaluating means the provider is forming a clinical judgment about the condition: severity, control, response to therapy, complications. Evaluation language is the most common MEAT element in well-documented charts because it requires the provider to actually think and write about the condition.

Examples that may be relevant in context:

Examples that are not enough by themselves:

A, Assess

Assessing means the provider has made an active diagnosis statement at this encounter. The cleanest evidence of assessment is the diagnosis appearing in the assessment / plan section of the note, not just in the problem list or past medical history. Coders should look for the condition to be named in the body of the assessment, not buried in a free-text history field.

Examples that may be relevant in context:

Examples that are not enough by themselves:

T, Treat

Treating means the provider is doing something about the condition: a medication, a procedure, a referral, a lifestyle intervention, a continuation of an existing therapy. Treatment is the most concrete MEAT element and is the easiest for coders to find.

Examples that may be relevant in context:

Examples that are not enough by themselves:

Why Element Counts Do Not Decide the Code

There is no universal one-element or two-element threshold. A single phrase can be irrelevant or contradicted elsewhere, while a complete record may support a diagnosis without fitting the mnemonic neatly. Read the provider's diagnostic statement, the whole record, and the applicable official rules.

When documentation is ambiguous or contradictory, follow a compliant query process if clarification is allowed and needed. Do not query merely to add a MEAT element or reach a different HCC.

Real Chart Examples

Example 1, Detailed current documentation for diabetes with CKD

> Assessment / Plan:

>

> 1. Type 2 diabetes mellitus with diabetic chronic kidney disease, stage 3a, A1c 7.8 today, eGFR 48, urine albumin/creatinine 320. Continue metformin 1000 mg BID and empagliflozin 10 mg daily. Recheck A1c and BMP in 3 months. ACEi already on board for proteinuria.

This example contains language that fits all four mnemonic labels. The provider also states diabetes with diabetic CKD and stage 3a. Code assignment still requires the full record, official classification, and applicable encounter and program rules; the element count itself does not approve E11.22 or N18.31.

Example 2, Problem-list entries without current discussion

> History: Patient is here for a routine follow-up. Doing well overall.

>

> Past Medical History (problem list): Type 2 diabetes mellitus, chronic kidney disease, hypertension, hyperlipidemia, depression

>

> Assessment / Plan:

>

> 1. Hypertension, BP 132/78, continue lisinopril

> 2. Hyperlipidemia, continue atorvastatin

The problem list points to diabetes, CKD, and depression, while the visible assessment addresses hypertension and hyperlipidemia. Do not treat the list as automatic support or automatic failure. Review the complete eligible record and the applicable rules before deciding whether any additional diagnosis is reportable.

If the record needs clarification, use an approved, non-leading query process. Do not add a sentence solely to satisfy a mnemonic or retain a payment HCC.

Example 3, Edge case (medication only, no mention)

> Assessment / Plan:

>

> 1. Annual physical, patient feels well

>

> Medications: lisinopril 20 mg daily, metformin 1000 mg BID, atorvastatin 40 mg daily, sertraline 50 mg daily

The patient is clearly being treated for hypertension, diabetes, hyperlipidemia, and depression based on the medication list. Is that enough to support reporting all four diagnoses?

A medication list can point to several possible indications and does not establish a diagnosis by itself. Do not infer hypertension, diabetes, hyperlipidemia, or depression from the drugs alone. Review the provider documentation and, if clarification is genuinely required, follow the organization's compliant query policy.

Example 4, Edge case (status condition that does not require active management)

> Assessment / Plan:

>

> 1. History of cerebrovascular accident with right hemiparesis, gait stable, continues to use cane, PT discharged 6 months ago

The I69 family has condition-specific coding rules, and selected residual-deficit codes map to V28 HCC 253. Verify the exact current code and mapping on the CMS 2026 model software page. Treatment is not the only possible chart context, but the mnemonic does not decide the code; use the provider's current diagnosis and official instructions.

The same logic applies to certain ostomies, amputations, and transplant statuses. These are genuine status conditions where the existence of the condition is the documentation, not the active management.

When to Query Instead of Coding

MEAT is not a general code-or-query rule. Assign only the diagnosis and specificity supported by the full record and official ICD-10-CM code set. Query only when clarification is needed under the applicable coding rules and your organization's compliant process.

The most common query patterns:

Why MEAT Matters Beyond Coding

MEAT can help a reviewer organize where to look, but it does not determine RAF capture, code assignment, or audit outcome. Keep the mnemonic subordinate to the medical record, official classification, CMS instructions, payer policy, and coder judgment.