Medical Coding M.E.A.T.

MEAT in Medical Coding: Why It Matters

In the world of medical coding and risk adjustment, one acronym stands out as the gold standard for validating diagnoses: MEAT. This simple tool helps coders ensure that each diagnosis is accurate, complete, and supported by provider documentation. Without medical coding MEAT, diagnoses may be questioned, denied, or removed during audits, leading to compliance risks and loss of reimbursement.

What Does MEAT Stand For?

MEAT is an acronym for the four key elements that demonstrate a provider has evaluated and managed a condition during a patient encounter:

• M – Monitor
  Evidence that the provider is keeping track of the condition.
  Example: “Check blood pressure daily,” “Lab results reviewed,” “Monitor A1C.”

• E – Evaluate
  Notes showing assessment of the condition.
  Example: “Blood pressure stable,” “Improved since last visit,” “Worsening neuropathy.”

• A – Assess/Address
  Provider actions taken for the condition.
  Example: “Increase insulin dosage,” “Referral to cardiology,” “Lifestyle counseling.”

• T – Treat
  Active treatment provided or prescribed.
  Example: “Prescribed metformin,” “Started physical therapy,” “Provided inhaler.”

Why MEAT Is Important in Coding

1. Validation of Diagnoses
   Coders must only code conditions that are supported in the medical record. MEAT provides the necessary proof.

2. Risk Adjustment Accuracy
   For HCC (Hierarchical Condition Category) coding, diagnoses must meet MEAT criteria to count toward risk scores.

3. Audit Readiness
   Payers and CMS require documentation to show that diagnoses are being managed. MEAT ensures compliance.

4. Quality of Patient Care
   Clear documentation benefits not only coders but also the entire healthcare team by improving continuity of care.

Examples of MEAT in Action

• Hypertension (I10):
  Provider note: “Blood pressure 148/92. Continue lisinopril 10mg daily. Will monitor and recheck in 3 months.”

  • Monitor: Recheck in 3 months

  • Evaluate: Blood pressure recorded

  • Assess/Address: Continue medication

  • Treat: Lisinopril prescribed

• Diabetes Mellitus Type 2 (E11.9):
  Provider note: “Patient’s A1C is 8.2. Increased metformin dosage to 1000mg BID. Ordered repeat labs in 3 months.”

  • Monitor: Ordered labs

  • Evaluate: A1C reviewed

  • Assess/Address: Medication adjusted

  • Treat: Prescribed higher metformin dose

Key Takeaways

• Every diagnosis must be backed by MEAT.

• Coders should look for one or more MEAT elements to validate a diagnosis.

• If documentation doesn’t meet MEAT, the diagnosis cannot be coded.

• MEAT is especially critical in HCC risk adjustment coding.

HCC Chronic Conditions and M.E.A.T. Criteria 

Coding Clarified Blog 

MEAT vs TAMPER: Two Ways to Check Support

Some organizations use TAMPER instead of, or alongside, MEAT. TAMPER stands for Treatment, Assessment, Monitor or Medicate, Plan, Evaluate and Referral. Both acronyms ask the same question: did the provider actively address this condition at this encounter? Use whichever framework your organization’s coding policy adopts, and apply it consistently.

MEAT in 2026 Risk Adjustment (CMS-HCC V28)

Medicare Advantage risk adjustment now runs fully on the CMS-HCC V28 model. Under V28, some diagnoses no longer map to a payment HCC, but MEAT still matters for every condition you report, because coding rules require the condition to be documented and addressed, and Risk Adjustment Data Validation (RADV) audits review whether the record supports each submitted HCC. A diagnosis with no evidence of monitoring, evaluation, assessment or treatment is a common RADV finding. Learn more in our HCC coding in 2026 guide.

Common MEAT Documentation Gaps

• Problem list only: a condition listed in the problem list or past medical history with nothing in the assessment and plan.
• Medication list only: a drug appears in the medication list but the provider never ties it to the condition.
• Copied forward notes: identical text carried from visit to visit without evidence the condition was reviewed that day.
• Unsigned or non-acceptable sources: diagnoses taken from documents that are not valid for risk adjustment, such as unsigned notes or diagnostic reports without provider interpretation.
• Vague status words: terms like “history of” for a condition that is still active, or “stable” with no supporting detail.

When a condition appears to be managed but the note does not say so clearly, send a compliant query. See our guide on how to query a provider.

Frequently Asked Questions About MEAT

What does MEAT stand for in medical coding?

MEAT stands for Monitor, Evaluate, Assess or Address, and Treat. It is used to confirm that a diagnosis was actively managed at the encounter.

How many MEAT elements are needed to code a diagnosis?

At least one element is generally needed to show the condition was addressed, but stronger documentation includes several. Follow your organization’s policy.

Is MEAT an official CMS rule?

MEAT is an industry best practice, not a term written in the ICD-10-CM guidelines. It is widely used because it lines up with the guideline requirement to code conditions that affect patient care, treatment or management, and with what RADV auditors look for.

Does MEAT apply outside risk adjustment?

Yes. MEAT is most associated with HCC coding, but the same logic helps support secondary diagnoses in any setting.

Ready to become a certified medical coder? Our online CPC certification training prepares you for the AAPC CPC exam with a credentialed instructor. Many students train at little or no cost through medical coding scholarships and WIOA grants available in 30+ states.