SPECIAL BULLETIN: Mandatory Malnutrition Reporting Brings the Resource Question into Focus

SPECIAL BULLETIN: Mandatory Malnutrition Reporting Brings the Resource Question into Focus

After reviewing a new regulation, the conversation usually turns to implementation. Someone identifies the affected departments, assigns an owner, and begins developing a plan. The resource discussion may come later, sometimes after the expectation has already been established that existing teams will handle the work.

That is the part worth examining as hospitals prepare for changes under the Medicare fiscal year (FY) 2027 Inpatient Prospective Payment System (IPPS) final rule. Understanding a requirement does not tell us whether the organization has the people, technical support, or time to carry it out.

Mandatory malnutrition reporting provides a useful example. The question is not whether hospitals should support accurate reporting and appropriate nutrition care. The question is whether the implementation plan accounts for the work required, including work that falls between departments.

What Is Changing?

The Centers for Medicare & Medicaid Services (CMS) finalized mandatory reporting of the Malnutrition Care Score electronic clinical quality measure beginning with the FY 2030 payment determination under the Hospital Inpatient Quality Reporting (IQR) Program. An electronic clinical quality measure, or eCQM, uses electronic health record data to calculate results according to defined specifications. [1]

The payment determination year is not the date to begin preparation. It identifies the payment year associated with meeting program requirements. Hospitals need to understand the applicable reporting period and have the necessary processes functioning before the payment consequence occurs.

IQR is a pay-for-reporting program. Hospitals that do not meet its requirements are subject to a reduction of one-fourth of their annual IPPS payment update. That does not mean a 25 percent reduction in total Medicare reimbursement. It means a reduction in the annual payment update. The consequence relates to meeting reporting requirements, not a direct payment penalty based on the hospital’s malnutrition score. [1]

That distinction matters, but it does not make preparation a submission task alone. Before approving a plan, leadership should know whether the organization can produce, validate, and explain the information it will report.

Start With Work Already Being Done

Consider a hypothetical hospital where nursing screens patients, dietitians complete nutrition assessments, providers document diagnoses, and CDI and coding review the record within their respective responsibilities. Quality oversees reporting, while informatics supports the electronic health record.

Leadership assigns preparation for mandatory reporting to quality. No additional resources are approved because the hospital already has a malnutrition process.

That may be a reasonable decision. It is not yet a complete assessment.

The proposed review should establish whether the existing process supports the applicable measure specifications. Information may be available in the record, but the team still needs to determine whether it is captured in the form required for calculation. Someone must investigate missing information, test unexpected results, and determine whether a problem involves documentation, workflow, data mapping, or measure logic.

These are recommended readiness activities, not additional federal staffing requirements. The point is to identify what needs attention before deciding that current resources are sufficient.

The review should also keep clinical care, diagnosis documentation, code assignment, and electronic reporting distinct. They are related, but an improvement in one area should not be assumed to resolve a problem in another. A plan centered only on diagnosis capture would leave important reporting questions unanswered.

The Digital Transition Belongs in the Discussion

The associated implementation-guide version is labeled draft, and the official measure page lists reporting options as “Not yet available.” Those sources do not establish a mandatory implementation date. Its availability should not be presented as a requirement to use it by the mandatory eCQM reporting deadline. [2,4]

For planning purposes, hospitals should separate current obligations from future technical considerations. A technology proposal can address how a solution might accommodate evolving standards without treating a draft specification as a finalized requirement.

Existing Resources Need an Actual Plan

Once the work is defined, the resource discussion becomes more useful. Some hospitals may need temporary analytical support. Others may need changes to an existing report or workflow.

Implementation work should also be separated from ongoing operations. Reviewing specifications, validating data, developing education, and resolving initial problems are different assignments from maintaining a stable process. A temporary implementation need should not automatically become a permanent staffing request. Conversely, recurring responsibilities should not disappear from the plan once the initial project closes.

If existing staff will perform the work, the plan should explain how it fits with their current assignments. That may require postponing another project, reducing a lower-priority activity, or changing how work is distributed. These are legitimate choices. Leaving the tradeoff unstated makes it harder to determine whether the approved expectations are realistic.

Technology Is Part of the Answer, Not the Entire Answer

The business case should account for the work remaining after implementation. Reviewing output, resolving exceptions, validating changes, and maintaining the process all belong in the discussion. If projected savings depend on reducing manual effort, the proposal should explain which tasks will change and how the organization will confirm the benefit.

The same scrutiny applies to tools the hospital already owns. An existing platform may avoid another software purchase, but the staff effort needed to build and maintain a solution still needs to be considered.

Readiness Requires a Decision

Mandatory malnutrition reporting gives hospitals a concrete reason to examine how implementation is supported. It does not automatically justify another position, another product, or another committee. It does justify defining the work before assigning it.

If resources are limited, the plan should say what can be accomplished, what must change, and what will wait. If the full scope is expected, the resource decision should reflect that expectation.

References

  1. Centers for Medicare & Medicaid Services. FY 2027 Hospital Inpatient Prospective Payment System and Long-Term Care Hospital Prospective Payment System Final Rule (CMS-1849-F). July 31, 2026. See “Hospital Inpatient Quality Reporting Program.” CMS final rule fact sheet.
  2. CMS eCQI Resource Center. Malnutrition Care ScoreFHIR—CMS986FHIR. See “Guidance” and “Reporting Options.” Official measure information.
  3. CMS eCQI Resource Center. About Digital Quality Measures. See “Transitioning to Digital Quality Measures.” CMS dQM overview.
  4. Draft dQM CMS Content Implementation Guide: Malnutrition Care ScoreFHIR. Draft based on version 1.0.000; continuous-build content is subject to change. Draft technical specifications.
Facebook
Twitter
LinkedIn

Penny Jefferson, MSN, RN, CCDS, CCDS-O, CCS, CDIP, CRC, CHDA, CRCR, CPHQ, ACPA-C

With more than 33 years in healthcare, Penny began her career as a U.S. Army medic and has held roles spanning CNA through MSN. She brings 14 years of critical care nursing experience and 14 years in Clinical Documentation Integrity. She joined Mayo Clinic in 2019 as a concurrent CDI reviewer and advanced to Supervisor of CDI in Rochester, Minnesota. In December 2022, she transitioned to the University of California Davis Medical Center, where she serves as the Director of CDI. She is a published author, national thought leader, and currently leads the ACPA CommUnity Denials & Appeals Interest Group, fostering collaboration on denial prevention, appeals strategy, and payer engagement. She is also the newly appointed co-host of Talk Ten Tuesday.

Related Stories

Condition Code 44 Versus Self-Denial Workflow

Condition Code 44 Versus Self-Denial Workflow

Patient status decisions are rarely isolated utilization management decisions. They affect reimbursement and compliance. They also shape quality reporting and revenue cycle operations, as well

Read More

Leave a Reply

Please log in to your account to comment on this article.

Featured Webcasts

Inpatient Ulcers and Gangrene: Avoid FY 2027 ICD-10-CM Coding, Sequencing, and Documentation Errors

Avoid costly inpatient coding errors involving ulcers and gangrene. This practical FY 2027 ICD-10-CM webcast clarifies pressure injury staging, non-pressure ulcer severity, diagnosis sequencing, documentation requirements, and POA reporting. Through real-world cases, gain the confidence to make defensible coding decisions, reduce denials, strengthen compliance, and support accurate reimbursement.

November 4, 2026

One Chart, Five Truths: How CDI Prevents the Same Diagnosis from Becoming Five Different Outcomes

What happens when everyone reviews the same chart, but reaches a different conclusion? In this case-based clinical documentation integrity (CDI) webcast, Penny Jefferson examines how documentation involving clinical support, timing, causation, linkage, and terminology can produce very different outcomes for ICD-10 coding, reimbursement, quality, risk adjustment, medical necessity, denials, and compliance. Using cases involving postoperative respiratory failure, severe malnutrition, and encephalopathy, you’ll learn the practical CLEAR framework to help attendees learn to evaluate whether a diagnosis is codeable, consistent, specific, reportable, and ultimately defensible across the different teams and systems that rely on the medical record.

September 30, 2026

Mastering Spinal Fusion Coding for Inpatient Facilities: ICD-10-PCS Precision, Documentation, and MS-DRG Impact

Spinal fusion cases are among the most complex inpatient procedures to code, where even minor ICD-10-PCS errors can affect MS-DRG assignment, reimbursement, compliance, and audit outcomes. This practical webcast provides a step-by-step framework for interpreting operative reports, assigning accurate ICD-10-PCS codes, recognizing documentation gaps, and confidently coding complex fusion procedures. You’ll leave with practical tools that improve coding accuracy, reduce denials and audit risk, and strengthen documentation-driven reimbursement decisions.

July 29, 2026

Trending News

Featured Webcasts

Radiation Oncology Fundamentals: Coding, Billing & Compliance for Hospital Outpatient & Professional Services

Now Available On Demand

Join Michael Calahan, PA, MBA for this radiation oncology coding and compliance webcast as he explains the fundamentals of coding, billing, reporting, and documentation for hospital outpatient and professional services. Learn how the 2026 radiation therapy coding changes affect current practices, how to distinguish technical and professional services, and how to address bundling, units, frequency, modifiers, and documentation requirements. Michael will also help you identify radiation oncology coding and billing vulnerabilities that could lead to denials, overpayments, repayment demands, or federal audit exposure.

October 20, 2026

Trending News

Prepare for the 2025 CMS IPPS Final Rule with ICD10monitor’s IPPSPalooza! Click HERE to learn more

Get 15% OFF on all educational webcasts at ICD10monitor with code JULYFOURTH24 until July 4, 2024—start learning today!

This Memorial Day, we honor those who gave all for our freedom. Take 20% off sitewide through May 29 with code MEMORIAL26 at checkout

CYBER WEEK IS HERE! Don’t miss your chance to get 20% off now until Dec. 1 with code CYBER25

CYBER WEEK IS HERE! Don’t miss your chance to get 20% off now until Dec. 2 with code CYBER24