CMS’s Malnutrition Mandate Raises Coding Audit Stakes

Hospitals are about to face a coding contradiction that has been building for more than a decade. Starting with payment year 2028, CMS will require hospitals to report a new quality measure — the Malnutrition Care Score — as part of the FY2027 Inpatient Prospective Payment System (IPPS) rule. It is the first nutrition-focused electronic clinical quality measure CMS has ever mandated. At the same time, CMS’s own auditors have spent more than ten years rejecting malnutrition diagnosis codes as unsupported, as detailed in an August 11, 2026 analysis by CDI specialist Cheryl Ericson published on ICD10monitor. Coders and CDI teams are now caught between a reporting mandate that rewards finding malnutrition and an audit program that routinely denies it.

How the Malnutrition Care Score Mandate Reached This Point

The Malnutrition Care Score did not appear overnight. It originated in 2013 as the Global Malnutrition Composite Score, developed by the Academy of Nutrition and Dietetics in partnership with Avalere Health. CMS adopted it as a voluntary measure for CY2024 reporting, giving hospitals a runway before finalizing it as a mandatory measure in the FY2027 IPPS rule. That mandate takes effect for payment year 2028, which means the data hospitals report starting soon will directly shape how their malnutrition identification and treatment programs are scored.

A Measure Built to Reward Documentation, Not Just Coding

The score is not just about whether a malnutrition code appears on a claim. It evaluates whether a hospital’s screening, diagnosis, and treatment workflow is complete and consistent — which puts new weight on exactly the kind of documentation gaps that have triggered OIG denials for years.

A Decade of OIG Findings Point the Other Way

While CMS builds a reporting structure that assumes malnutrition is under-identified, its Office of Inspector General has spent years arguing the opposite: that hospitals are over-coding it. Two audits illustrate the pattern. An OIG review of kwashiorkor claims from 2006 through 2015 examined 2,145 claims across 25 hospitals and found a 99 percent error rate, tied to roughly $102 million in improper Medicare payments. A follow-up review of severe malnutrition claims from 2016 through 2017 found errors in 164 of 200 sampled claims, extrapolated to more than $1 billion in overpayments across the audited population. Severe malnutrition has since become a standing PEPPER outlier target, meaning individual hospitals can be flagged automatically when their coding rates diverge from peers.

Why Malnutrition Codes Keep Failing Audits

The recurring failure pattern in OIG’s findings is narrow and well documented, which is part of why it keeps repeating. A malnutrition diagnosis cannot be coded from a dietitian’s note alone — a treating provider has to independently document the diagnosis in their own note. Auditors then check whether the documented severity lines up with the actual treatment: minimal dietitian involvement, no escalation of nutritional support, and no electrolyte monitoring on a chart coded as severe malnutrition is, in Ericson’s words, “the fact pattern that has decided nearly every malnutrition audit CMS has ever won.”

What Coders and CDI Teams Should Do Before 2028

Ericson’s core warning is that CDI leaders should not wait until the payment year 2028 deadline to act, since the documentation habits that determine audit outcomes take longer than a single reporting cycle to fix. A few steps carry the most weight right now:

• Standardize on one validated screening and diagnostic framework — either ASPEN or GLIM criteria — rather than mixing tools like MST, MUST, MNA-SF, or NRS-2002 across units.
• Confirm that every malnutrition diagnosis has independent provider documentation, not just a dietitian assessment, before the code is finalized.
• Audit internally for the treatment-severity mismatch pattern OIG has flagged repeatedly: severe malnutrition codes with no corresponding escalation in nutritional care.
• Track PEPPER outlier data on malnutrition coding rates the same way compliance teams already track other outlier categories.
• Build the Malnutrition Care Score’s documentation requirements into concurrent CDI review now, rather than treating it as a claims-side coding fix later.

Where Automated Coding Platforms Can Close the Gap

The core problem CMS has created is a documentation consistency problem, not a coding knowledge problem — coders already know malnutrition codes exist and know roughly when they apply. What has repeatedly failed audits is the gap between what a dietitian charts, what a provider independently documents, and what the treatment record actually shows. That is the kind of cross-document consistency check that is difficult to enforce manually at scale across every inpatient chart, but well suited to agentic AI systems that can flag a malnutrition code the moment provider documentation is missing or treatment intensity doesn’t match the coded severity, before the claim ever goes out the door.

Coding teams that want that kind of consistency check built into their workflow, rather than discovered during an audit, should take a look at Medikode’s automated medical coding platform.