Have we figured out the Medicare Change of Status Notice (MCSN) yet?
By Sara Williams, RN, MSN, ACM
More than a year has passed since hospitals were required to implement the Medicare Change of Status Notice (MCSN), yet the notice remains a source of operational confusion. Some organizations have struggled to reliably identify which beneficiaries qualify for the notice, while others have attempted to incorporate the MCSN into existing Medicare Outpatient Observation Notice (MOON) or Condition Code 44 workflows without fully accounting for the differences among these requirements.
The challenge is understandable. The MCSN does not apply to every patient whose status changes from inpatient to outpatient, nor does it replace the MOON or the requirements associated with Condition Code 44. Instead, it creates additional beneficiary protection for a specific population of Traditional Medicare beneficiaries whose status is changed from inpatient to outpatient receiving observation services.
Consider Mr. Smith, a Traditional Medicare beneficiary with Medicare Parts A and B. He is formally admitted as an inpatient following a ground-level fall and remains hospitalized for several days. During the hospitalization, Utilization Review identifies that inpatient criteria was not supported and refers the case for Condition Code 44. Following review, the hospital reclassifies Mr. Smith from inpatient to outpatient receiving observation services while he is still hospitalized.
Because Mr. Smith has Medicare Part B and his hospital stay lasted at least three days, he now meets the requirements for the expedited status appeal process, via the MCSN. However, his case management team has forgotten about the notice, and instead are working on alternative discharge plans with Mr. Smith as he prolongs his observation stay in the hospital. In this instance, Mr. Smith, had he received the MCSN, may have elected to appeal to the BFCC- QIO with an opportunity for inpatient from time of the initial inpatient order granting his 3 midnights and SNF eligibility.
Why Is the MCSN So Difficult to Operationalize?
Much of the confusion stems from two factors: not every Medicare beneficiary who experiences an inpatient-to-outpatient status change is eligible for the MCSN, and the timing of notice delivery varies based on Medicare Part B coverage. These nuances make MCSN compliance more complex than simply identifying that a patient's status changed from inpatient to outpatient with observation services.
How Did We Get Here?
The MCSN originated from a 2011 class-action lawsuit that challenged Medicare’s failure to provide appeal rights for patients reclassified from inpatient to observation status. These changes created significant financial consequences, especially when beneficiaries later required SNF care but lacked the qualifying inpatient hospital stay needed for Medicare coverage.
The litigation and subsequent CMS actions resulted in an appeal process for certain Traditional Medicare beneficiaries whose status is changed from inpatient to outpatient while receiving observation services. The MCSN is the mechanism used to notify eligible beneficiaries of these appeal rights.
While the concept sounds straightforward, the operational requirements are not.
Who Should Receive the MCSN?
To qualify, the beneficiary must have been formally admitted as an inpatient and subsequently reclassified as an outpatient receiving observation services, remain physically present in the hospital when the reclassification occurs, and meet applicable eligibility and timing requirements.
The timing requirement presents one of the greatest operational challenges because Medicare Part B entitlement affects when the notice must be delivered.
For beneficiaries without Medicare Part B, the MCSN should be delivered as soon as possible following the decision to reclassify the patient. For beneficiaries with Medicare Part B, notice requirements are tied to the applicable three-day hospital stay requirement. Hospitals must therefore track the beneficiary's stay and determine when the patient reaches three days from the original inpatient order.
A hospital cannot simply build an electronic rule stating, "Inpatient changed to observation = MCSN." Instead, the workflow must consider Traditional Medicare versus Medicare Advantage, Part B entitlement, initial inpatient status, subsequent status change, continued physical presence in the hospital, length of stay, and anticipated discharge. Without these elements incorporated into the workflow, hospitals risk both failing to issue required notices and issuing notices to beneficiaries who do not meet the requirements.
MCSN, MOON, and Condition Code 44 Are Not Interchangeable
Another source of confusion is the relationship between the Medicare Change of Status Notice (MCSN), Medicare Outpatient Observation Notice (MOON), and Condition Code 44. Although all three may intersect during a hospitalization, they serve different purposes.
The MCSN advises an eligible Traditional Medicare beneficiary of the right to appeal a qualifying change from inpatient to outpatient status while receiving observation services. The MOON informs Medicare beneficiaries receiving observation services that they are hospital outpatients rather than inpatients and explains the implications of outpatient status. Condition Code 44 relates to the process through which an inpatient admission is changed to outpatient status for Traditional Medicare patients when applicable Medicare requirements are satisfied. Hospitals should not assume that an existing MOON or Condition Code 44 workflow automatically satisfies MCSN requirements.
What Happens if the Patient Appeals?
The MCSN provides eligible beneficiaries access to an expedited determination by the BFCC-QIO. Importantly, the beneficiary is challenging the decision to change the hospitalization from inpatient to outpatient status, not simply appealing discharge or requesting a conversion back to inpatient. UR, Physician Advisors, Case Management, Patient Access, Revenue Cycle, Health Information Management, and other involved departments must understand this distinction and their responsibilities when an appeal occurs.
Hospitals must also establish a process for beneficiaries who remain hospitalized while the QIO reviews the appeal. Because continued services may result in financial liability, organizations need clear procedures for communicating potential financial responsibility and determining when an Advance Beneficiary Notice of Noncoverage (ABN) is appropriate.
Building a Reliable Hospital Workflow
A strong MCSN process begins with automated identification whenever possible. Reliance on staff memory or manual review creates unnecessary compliance risk because eligibility depends on multiple data elements that may reside in different systems.
Ideally, the EHR should identify potential MCSN cases and evaluate Medicare coverage, Part B enrollment, length of stay, continued hospitalization, and timing of the status change. Once eligibility is established, an actionable alert should be generated for the department responsible for notice delivery. Organizations should also clearly define who delivers the notice, how delivery is documented, who manages an appeal, and how communication occurs across clinical and revenue cycle teams.
More Than a Year Later: The Opportunity for Hospitals
More than a year after implementation, hospitals should be asking:
Are we reliably identifying every beneficiary eligible for the MCSN?
Are we avoiding delivery to beneficiaries who do not meet the requirements?
Can we demonstrate that the notice was delivered appropriately?
If a beneficiary appeals tomorrow, does everyone involved know what happens next?
The organizations that manage this requirement most successfully will move away from manual processes and isolated departmental ownership toward a standardized, technology-supported workflow. The goal is simple but critical: identify the right patient, deliver the right notice at the right time, protect the beneficiary's appeal rights, and ensure the hospital is prepared when those rights are exercised.