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
- 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.
- CMS eCQI Resource Center. Malnutrition Care ScoreFHIR—CMS986FHIR. See “Guidance” and “Reporting Options.” Official measure information.
- CMS eCQI Resource Center. About Digital Quality Measures. See “Transitioning to Digital Quality Measures.” CMS dQM overview.
- 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.

















