What does MEAT mean?
In risk adjustment and documentation review, MEAT commonly stands for Monitor, Evaluate, Assess/Address, and Treat. It is an industry teaching framework used to help coders and providers recognize documentation showing that a condition was actively considered during an encounter.
MEAT can be especially helpful when reviewing chronic conditions. Instead of asking only, “Is this diagnosis listed somewhere in the chart?” the coder asks, “What did the provider actually do with this condition today?”
Breaking down M-E-A-T
Monitor
Look for evidence that the provider is following the condition over time.
Examples: monitoring symptoms, disease progression or regression, blood pressure readings, blood glucose trends, weight, renal function, or other condition-related findings.
Evaluate
Look for evidence that the provider is reviewing information to judge the status of the condition.
Examples: reviewing lab results, imaging, test findings, medication effectiveness, response to treatment, or whether the condition is stable or worsening.
Assess / Address
Look for the provider's clinical assessment, discussion, or decision-making related to the diagnosis.
Examples: documenting stable versus uncontrolled disease, discussing complications, reviewing specialist findings, counseling the patient, or incorporating the condition into the assessment and plan.
Treat
Look for active treatment or a treatment plan related to the condition.
Examples: prescribing or continuing medication, adjusting a dose, ordering therapy, referring to a specialist, recommending a treatment intervention, or continuing an established plan.
What can MEAT look like in a medical record?
“Type 2 diabetes—A1c improved to 7.2. Continue metformin 500 mg twice daily.”
Possible MEAT: Evaluation of A1c plus treatment with continued medication.
“Blood pressure 148/88 today. Home readings reviewed. Increase lisinopril to 20 mg daily.”
Possible MEAT: Monitoring blood pressure, evaluating home readings, assessing control, and treating with a medication change.
“CKD stage 3b, renal function stable. Creatinine reviewed. Avoid NSAIDs and continue nephrology follow-up.”
Possible MEAT: Evaluation of renal function, assessment of stability, and ongoing treatment/management plan.
“Problem list: CHF” with no discussion, assessment, treatment, monitoring, or other encounter-related documentation.
Key question: Is there enough current documentation under the applicable rules to support reporting the condition for this encounter? The problem-list entry alone should not be treated as an automatic green light.
MEAT is a framework—not a universal pass/fail rule
One of the biggest mistakes in risk adjustment education is turning MEAT into a rigid checklist: “If I find one letter, I can code the condition.” That is too simplistic.
A MEAT element may provide useful evidence that a condition was addressed, but the coder still has to consider the complete medical record, ICD-10-CM guidelines, setting-specific coding rules, provider documentation requirements, payer rules, and the requirements of the applicable risk adjustment program.
Likewise, the absence of an obvious word that fits neatly into M, E, A, or T does not automatically prove that a diagnosis is invalid. Documentation has to be evaluated as a whole.
Why a diagnosis on the problem list is not always enough
A diagnosis may remain on a problem list long after its status changes, or it may appear without any indication that the provider considered it during the current encounter. That is why risk adjustment coders need to read the whole note rather than simply scanning the diagnosis list or limiting review to the assessment and plan.
Relevant documentation may appear in the history, exam, assessment, plan, medication discussion, test review, or another part of the encounter. The key is not where the diagnosis appears, but whether the complete record supports reporting it under the applicable rules.
Ask whether the current documentation shows the condition being evaluated, monitored, assessed, addressed, treated, or otherwise supported according to the rules that apply.
| Documentation | Coder thinking |
|---|---|
| Diagnosis appears only on an old problem list. | Do not assume it is current or reportable. Review the present encounter. |
| Condition is discussed in the assessment and plan with current status. | Evaluate whether documentation and coding rules support reporting it. |
| Medication appears on the med list. | Do not automatically infer the diagnosis. Determine whether the provider documents the condition. |
| Test result is abnormal. | Do not code a diagnosis solely from the result unless coding rules permit it and provider documentation supports the diagnosis. |
Why MEAT matters in risk adjustment compliance
CMS uses the Medicare Advantage Risk Adjustment Data Validation program to verify that diagnoses submitted for risk-adjusted payment are supported in beneficiaries' medical records. Unsupported diagnoses can result in overpayment recovery.
That is why documentation review should never become a hunt for diagnoses that increase RAF. The objective is accurate reporting of conditions that are documented and supported.
MEAT can help coders ask better questions during chart review, but the compliance standard remains broader: Does the record support the diagnosis according to current coding and program requirements?
Read: Supported vs. Unsupported Diagnoses in Risk Adjustment →
Read: What Is RADV? →
How to use MEAT during chart review
A practical workflow is to first identify the diagnosis documented by the provider, then review the entire encounter for evidence showing how that condition was addressed. Documentation supporting a condition is not limited to the assessment and plan; useful information may also appear in the history, exam, medication review, test discussion, or follow-up instructions. Note any monitoring, evaluation, assessment, or treatment, but do not stop there.
Next, verify the ICD-10-CM code using the Alphabetic Index and Tabular List, apply the Official Guidelines and any relevant payer or program rules, and determine whether the condition is reportable for the encounter. For outpatient coding, do not report a resolved condition merely because it appears in the chart, and do not assume an unclear diagnosis.
If documentation is unclear, conflicting, or insufficient to support the code, follow your organization's compliant provider-query or escalation process rather than guessing. A query is meant to clarify the record—not to lead the provider toward a diagnosis that increases risk.
Use our ICD-10-CM Quick Guide for diagnosis-code verification →
How MEAT connects to HCC and CRC coding
MEAT is commonly taught in risk adjustment because the specialty requires close attention to chronic-condition documentation. But it makes the most sense when you understand the larger picture: ICD-10-CM coding first, risk adjustment model logic second, and accurate documentation throughout.
Read: What Is HCC Coding? →
Read: What Is a Certified Risk Adjustment Coder? →
Read: CRC vs CPC →
MEAT FAQ
Does every diagnosis need all four MEAT elements?
No. MEAT is a review framework, not a requirement that every condition contain all four elements.
Is one MEAT element always enough?
No. One element can be helpful evidence, but reportability depends on the full record and applicable coding and risk adjustment rules.
Can I code a diagnosis from a medication alone?
Do not infer a diagnosis solely from a medication list. The diagnosis should be documented by an appropriate provider and meet applicable coding rules.
Can I code a chronic condition just because it was coded last year?
No. Prior-year coding does not automatically support current-year reporting. Evaluate the current documentation and applicable program rules.
Is MEAT the same as HCC coding?
No. MEAT is a documentation-review framework. HCC coding involves accurate ICD-10-CM coding, documentation, risk adjustment models, hierarchy, and compliance.
Practice documentation decisions with MediCode
Our free CRC study resources and risk adjustment training use case-based examples to help you decide whether a diagnosis is supported—not just whether it appears somewhere in the chart.
Free CRC Study SessionsExplore the Self-Paced CRC CourseView CRC Boot CampSource note: CMS requires diagnoses used in Medicare Advantage risk adjustment to be supported by the medical record and validates diagnoses through RADV audits. MEAT is a commonly used educational framework in coding and documentation review; it should not be treated as a replacement for official CMS, ICD-10-CM, payer, or organizational requirements. This guide also reflects the documentation-review approach taught in MediCode Bootcamp's CRC curriculum: review the entire note, code the most accurate supported diagnosis, and query rather than assume when documentation is unclear.