November 20, 2026
The Trump administration has proposed a slew of changes to Medicare Advantage and Part D designed to “revitalize care” in these markets.
This article was originally published on Fierce Healthcare.
The industry's trusted authority on overturning denials and payer audits — equipping providers with the expertise, resources, and community to challenge unfair practices, recover rightful revenue, and drive lasting change in healthcare reimbursement.
AHDAM speaks for the people doing the work — pushing back on payer practices that erode reimbursement, surfacing patterns across hospitals, and partnering with policy bodies to drive change.
122+ tip sheets, templates, policies, and 50 state-by-state legal snippets — searchable by denial type, payer, and clinical scenario. Two decades of practitioner-tested guidance.
Live sessions and on-demand recordings from the appeal professionals who've done it. Clinical validation. DRG downgrades. Prior auth strategy. Ask-the-experts Q&A built in.
AHDAM Appeal Management Certification — the credential that proves you can do this work. Curriculum, exam, continuing education, all in one pathway.
AHDAM is proud to announce a strategic partnership with Hyve Health. Our shared mission is to strengthen the healthcare community's ability to prevent manage, and overturn insurance denials.
HYVE brings advanced analytics and tranparency tools, like the Payer Vitality Scorecard™, empowering providers to track and respond to shifting payer behavior.
Partners →
PayerWatch is on a mission to ensure every hospital in the U.S. is fully capable of defending themselves against egregious payer behavior. That's a mission we at AHDAM can get behind!
Through sophisticated software and world-class appeal solutions PayerWatch is holding payers accountable and protecting provider revenue like no one else in healthcare today.
Partners →AHDAM is the only place I've found where the appeal letters, the legal precedent, and the people who've actually overturned these denials all live in one room.
I've written hospital appeals for 15 years. By far the most practical training I've ever taken — clinically grounded, legally informed, and immediately useful Monday morning.
The Minnesota ACDIS chapter learned an enormous amount. Conversational, candid, and packed with strategy we can deploy that day.
Founded AHDAM to put practitioner intelligence in every appeal professional's hands. Two decades in healthcare denial & appeal management.
Senior Fellow in Hospital Medicine. Leads clinical & physician-advisor programming, peer-to-peer strategy, and the certification curriculum.
AHDAM's board brings together healthcare attorneys, physician advisors, and revenue cycle leaders from health systems nationwide.
Become a member, get certified, or ask the appeal experts — three ways into the AHDAM community.
November 20, 2026
The Trump administration has proposed a slew of changes to Medicare Advantage and Part D designed to “revitalize care” in these markets.
This article was originally published on Fierce Healthcare.
November 19, 2026
Cigna is making $31.5 million in grant funding available over the next three years to nonprofits in 10 states that are aiming to tackle several key community health priorities.
This article was originally published on Fierce Healthcare.
Author: Golam Morshed, MD | November 18, 2026
Providers imagine that somewhere inside an insurer there is a document, a single authoritative list of the rules that decide whether a claim pays.
Having worked for three insurers, I can tell you what is there, and why it explains more about denials than any amount of provider-side training.
There is no document.
There is a claims engine, and a claims engine is not a policy. It is a long accumulation of configuration, built up over years by many people, most of whom have moved on, each addition made to solve a problem at the time. A benefit plan was loaded for a new product. A bundling edit was switched on because a vendor’s update included it.
A modifier requirement was added after an audit. A provider file was mapped to a network tier by someone in a hurry. Each change was reasonable. Nobody has read the whole thing, because the whole thing is not readable; it is thousands of settings across several modules, and the only way to know what it does in a given case is to run a claim through it.
The people closest to it are not the people who write the provider manual. The manual is written by a provider relations or policy team, usually from the contract and the benefit design, and it describes what the plan intends. The engine is maintained by a configuration team, often from a vendor’s rule set, and it describes what the plan does. The two teams meet rarely. When a provider calls to say the manual promises a service that the engine denies, the call goes to a third team, customer service, which can see neither.
The anecdote I use with practices comes from a configuration review I sat in on. A new product had been launched with a benefit design that covered a particular preventive service. The engine denied it. The denial had been going out for the better part of a year. The cause turned out to be that the product had been cloned from an older one whose configuration excluded the service, and the exclusion had been carried across.
Nobody intended it. Nobody noticed it, because the denials went to practices and the practices either appealed and won, or stopped billing the service. The appeals were being paid, one by one, by a different team that had no reason to ask why so many of them involved the same code. The plan had in effect been paying its own staff to overturn its own mistake several hundred times.
That story is not unusual. It is the normal failure mode of a system too large for anyone to hold in their head.
Here is what else I learned on the inside – that I wish every biller knew.
The reason code on a denial is chosen by the engine from a mapping table, not by a person looking at your claim. The mapping is many-to-one. Several distinct internal edits can produce the same external code. When you receive “not a covered benefit,” you may be looking at a configuration error, a bundling rule, a network tier mismatch, or a genuine exclusion, and the plan’s own customer service representative often cannot tell which, without escalating.
Edits are frequently inherited, rather than chosen. Commercial claims engines ship with large libraries of bundling and frequency edits. A plan decides which to switch on, and the default is often to switch on most of them. The plan’s medical policy staff may never have reviewed the individual edits. So, when a provider asks “why does your plan bundle this,” the honest answer, more often than anyone will say aloud, is that the vendor shipped it that way.
Provider files lag. Credentialing approves a clinician on one date, loads the file on another, and the engine sees the change on a third. Claims in between are denied for a provider not recognized. The plan knows this happens and handles it by appeal, which is the most expensive possible process for a problem that a date correction would solve.
Appeals are a separate world. The team that reviews appeals usually works from the policy, the contract, and the clinical record, which is to say from the plan’s intent, rather than from the engine. That is why appeals so often succeed: the appeal reviewer is applying the rules the manual describes, and the engine is applying something else. Nobody feeds the appeal outcomes back into the configuration systematically, so the same edit keeps denying and the same appeals keep resulting in wins.
And the plan does not experience any of this as a problem, because the costs are diffuse. A denied claim that is never appealed is a savings. A denied claim that is appealed and paid is a small administrative expense. A practice that stops billing a covered service is invisible. The only party that sees the whole pattern is the practice, and the practice has no way to tell the plan which of its thousands of settings is wrong.
What would I change, from the inside?
Three things. Publish the engine’s behavior at the code level, so the manual and the machine can be compared. Route appeal outcomes back to configuration, so that an edit overturned 10 times gets reviewed, rather than overturned an 11th. And give the customer service a view of the edit that fired, not just the code it mapped to, so the person a biller reaches on the phone can say what actually happened.
None of that changes a coverage decision. It changes the distance between what the plan means and what the plan does. In my experience, that distance, not any policy, is where most of the friction between payers and small practices lives, and the plan is the only one of the two who can close it.
This article was originally published on RACmonitor.
November 18, 2026
UnitedHealthcare is teaming up with CPSEN for its UHC Pharmacy Care Hub model, a new program that aims to lean on community pharmacists to reach Medicaid patients.
This article was originally published on Fierce Healthcare.
Author: Tiffany Ferguson, LMSW, CMAC, ACM | November 16, 2026
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 as the patient’s experience.
This is particularly important when a hospital determines that a Traditional Medicare beneficiary was admitted as an inpatient, but does not in fact meet the requirements for an inpatient level of care.
Hospitals generally face an important decision in these cases, and it was a recent topic of discussion in the case management community. The conversation centered on advice from a vendor that hospitals do not need to complete Condition Code 44s. Without this code, the hospital utilization review/management committee (UMC) would essentially allow the patient to be discharged as an inpatient. At that point, they would either pursue a self-denial/Part B rebill or leave the account as inpatient if the case hit the short-stay workflow.
For reference, the Condition Code 44 process provides a mechanism for correcting an inpatient admission to outpatient status before discharge when the hospital’s utilization review (UR) process determines that the inpatient admission was not appropriate, the attending concurs, and all is documented.
So, here are some reasons why it is important to ensure status is corrected at the time of review.
If an organization subsequently determines that the inpatient admission was not reasonable and/or necessary, it may pursue the self-denial/Part B rebill process. At that point the hospital essentially has chosen to move work from the front end to the back end. This workflow involves bill holds, utilization management reviews, physician advisor escalations, and outreach to the attending for concurrence.
Depending on the outcome, it also requires recoding and two additional claims going out the door (one no-bill claim and one Part B claim), plus a patient notification by mail (or online portal if self-denied). Instead of sending a clean claim out the door, you would hold up the billing process, put all the work on the back end, and do a rebill.
Yes, Condition Code 44 takes a little more work up front, but the self-denial process takes more time and effort.
Another option is to leave the account as inpatient even if the hospital’s utilization review process indicates that inpatient level of care is not supported. I don’t think I need to elaborate further, as that is Medicare fraud.
Choosing post-discharge Medicare short-stay reviews over Condition Code 44s creates an additional concern. Because the encounter remains inpatient, so do its quality metrics, despite the lack of payment. These encounters will still be reflected as potential index admissions or readmissions, as well as mortalities.
Historically, organizations argued that completing Condition Code 44 was not worthwhile because insufficient observation existed to receive reimbursement. That assumption is untrue when you have upfront UR processes in place. If you catch an inappropriate inpatient case that is more appropriate for observation, it is now easy to do with electronic medical records (EMRs) and quick escalations via secure chat. This allows you to still meet all the required steps and convert the patient to observation with plenty of time to accrue eight units and collect the Comprehensive Ambulatory Payment Classification (C-APC) payment.
There is also an important patient-rights consideration. Medicare beneficiaries who remain hospital inpatients are provided the Important Message from Medicare (IM), which informs them of their hospital discharge appeal rights. By keeping the patient as inpatient, and not doing the Condition Code 44, the patient would retain those rights even during short hospitalizations with no medical necessity.
If an organization determines during the hospitalization that inpatient status is not supported, and the regulatory requirements for Condition Code 44 can be satisfied, there is significant value in correcting the status while the opportunity remains.
The goal of an effective concurrent utilization management program should be to identify issues and create solutions, not watch the problems without action.
This article was originally published on RACmonitor.
Author: Penny Jefferson, MSN, RN, CCDS, CCDS-O, CCS, CDIP, CRC, CHDA, CRCR, CPHQ, ACPA-C | November 16, 2026
Throughout 2026, we discussed how documentation affects medical necessity, payer review, quality measures, and payment. As 2027 approaches, the question is whether those conversations have changed our daily work.
Over the past year, I have written about the information payers receive, the clinical reasoning behind admission decisions, the integrity of hospital benchmarks, and what happens when documentation becomes a legal question. We have also looked at sepsis, surgical episodes, advance care planning, risk adjustment, and outpatient drug billing. These may appear to be separate topics. In practice, they follow the same patient and depend on the same record.
As we prepare for 2027, I would bring those discussions back to one question: can we follow the patient’s clinical story through the decisions, data, and claims it produces – and explain where the information changes?
That is the readiness conversation I want clinical documentation integrity (CDI), coding, utilization review (UR), physician advisors, quality, compliance, revenue integrity, and clinical leaders to have together. An education session is a beginning. We also need evidence that the resulting workflow works.
First, separate what is already in effect, from what begins in January and what requires preparation for a future year. ICD-10 updates for the 2027 fiscal year (FY) began Oct. 1, 2026. January brings calendar-year payment and operational changes. A future payment year may depend on an earlier performance period, so each project needs its own implementation, measurement, submission, and payment dates.
The 2027 outpatient final rule removes 637 services from Medicare’s Inpatient-Only (IPO) List. That creates more outpatient payment options; it does not establish that every patient receiving one of those services belongs in outpatient status. Hospitals should compare the final list with actual surgical volume, update scheduling, and status workflows, and evaluate the financial effects using their own payer mix and contracts.
The leadership question is not “How many procedures can we move to outpatient?” It is “Can we show that each patient’s status was selected for the right clinical reason, documented at the right time, and billed under the applicable rules?” That is where CDI, UR, physician advisors, surgeons, coding, compliance, and revenue integrity must work from the same playbook.
Priority No. 5: Test the documentation and claim together. For selected removed procedures, trace the planned status, admission order, physician rationale, actual course, discharge documentation, coding, modifiers, charges, and final claim. Track short-stay denials, status changes, avoidable write-offs, and unexpected outpatient packaging or payment differences. Use the findings for targeted education, rather than treating every status variance as an error.
Priority No. 4: Payment, coverage, and authorization remain separate checks. Removal from the IPO list does not override an NCD, LCD, Medicare Advantage (MA), or commercial payer coverage rule, medical-necessity requirements, or a payer-specific authorization obligation. Nor does it establish that a service will receive separate Outpatient Prospective Payment System (OPPS) payment in every setting. Revenue integrity and contracting should validate applicable payment rules and the complete encounter, not simply compare inpatient and outpatient rates for a single procedure.
Priority No. 3: Rebuild the surgical workflow before Jan. 1. Compare the final 2027 IPO removals with the organization’s prior-year surgical volume; identify affected specialties and surgeons; and review scheduling, preauthorization, preoperative status planning, orders, patient notices, bed management, case management, and post-procedure escalation. The surgeon, anesthesia team, UR, physician advisor, perioperative leadership, coding, and revenue cycle should agree on how an unexpected complication or change in clinical condition triggers reassessment.
Priority No. 2: Do not confuse the two-midnight benchmark with a review exemption. The Centers for Medicare & Medicaid Services’ (CMS’s) medical-review policies for newly removed procedures and the physician’s obligation to support the admission decision are separate issues. UR and physician advisors should document the expected duration and intensity of care, comorbidities, surgical risk, complications, and the clinical rationale at the time of the admission decision.
Priority No. 1: A removed procedure is not automatically outpatient. Once a service is no longer on the IPO list, Medicare does not require Part A inpatient billing solely because of the procedure code. The patient may still warrant inpatient admission based on the physician’s reasonable expectation of medically necessary hospital care spanning at least two midnights, or a supported case-by-case exception. Conversely, a planned inpatient admission is not justified by historical IPO status alone.
The removal of 637 services from Medicare’s IPO List for 2027 is a payment-policy change, not a blanket determination that the procedures are clinically appropriate for outpatient care. The final list, not the proposed list or a vendor summary, must drive the hospital’s code-level analysis. This is particularly important for procedures that historically have moved through an inpatient surgical pathway. [2]
UR and physician advisors should also distinguish the applicable two-midnight policy from exemptions from certain medical-review activities. An exemption from specified review activity should not become a reason to stop documenting the patient-specific admission decision. Operational priorities for hospitals in 2027 should include the following:
My articles on medical necessity and the payer review process repeatedly returned to the front door. Does the emergency department record, admission order, and history and physical explain why this patient needed this level of care at that time?
Before January, I would review a sample of short stays and surgical admissions with CDI, UR, and physician advisors. Look for the physician’s anticipated course, clinical risk, treatment needs, and explanation when a shorter inpatient stay is appropriate. CMS emphasizes the importance of that individualized rationale for case-by-case exceptions.
Then examine the handoff. Who notices a gap? Who contacts the treating practitioner? Where is the clarification documented? What happens overnight, or on weekends? A strong process needs a clear route from identifying a concern to resolving it.
A procedure’s payment status, its medical necessity, its authorization requirements, and the documentation supporting its diagnosis are different questions. Our readiness work should keep them distinct.
For high-volume and high-risk services, verify the applicable National Coverage Determination (NCD), Local Coverage Determination (LCD), associated billing instructions, and payer requirements for the date of service. National and local policies operate at different levels; local coverage can vary by Medicare contractor jurisdiction. Multistate organizations should not assume that one location’s instructions apply everywhere.
My earlier discussion of prior authorization reductions also raised an operational question worth carrying forward: when a requirement changes, have we updated the correct plan and code combinations? Track the effect through payment, including medical necessity denials and retrospective reviews, rather than measuring only fewer authorization requests.
Under CMS-0057-F, payer application programming interface (API) requirements generally begin in 2027, with exact compliance dates varying by payer type. The rule also introduces an electronic prior authorization measure for eligible hospitals and critical access hospitals (CAHs), beginning with the 2027 electronic health record (EHR) reporting period. These are distinct responsibilities, and organizations should verify their applicable specifications and exclusions.
That makes interoperability a clinical and revenue cycle concern, as well as an IT project. Ask what information the workflow sends, whether it reflects the current encounter, and how incomplete requests, denials, and requests for additional information return to the team responsible for acting on them.
A successful connection does not prove that the clinical content is accurate. I would test representative cases from the source documentation to the information actually transmitted. Old problem-list entries, conflicting diagnoses, and incomplete admission narratives deserve attention before they are reused downstream.
Recent articles on hospital benchmarking, U.S. Department of Health and Human Services (HHS) Office of Inspector General (OIG) audits, and documentation governance asked a difficult question: what happens when correcting the record makes a performance number less favorable?
Our 2027 plan should give equal attention to supported diagnoses that are missing and documented diagnoses that need clarification. Reporting criteria and clinical validation address different issues. Coders should follow official guidance while unresolved clinical concerns move through an established clarification and escalation process.
That includes how we review sepsis, malnutrition, respiratory failure, and disputed wound diagnoses. A desired Diagnosis-Related Group (DRG), risk score, or quality result should not determine the clinical conclusion. Audit automated prompts and artificial intelligence (AI)-assisted recommendations for the evidence presented, the clinician’s response, and the resolution of conflicting information. My recommendation is to measure accuracy and corrective follow-through alongside productivity and financial impact.
Our sepsis discussions highlighted how different methods can identify different patients. Claims, clinical surveillance, and quality specifications do not necessarily produce identical populations. Before comparing results, teams should be able to explain the definition, exclusions, timing, and data source behind each number.
CMS finalized sepsis readmission early-look reports for FY 2028 and FY 2029, with payment-reduction calculations beginning in FY 2030. The FY 2027 rule also adopted modified mortality measures incorporating MA patients beginning with the FY 2028 Inpatient Quality Reporting (IQR) payment determination, with modified measures entering Hospital Value-Based Purchasing (VBP) in FY 2032. These are preparation priorities, not new January 2027 penalties.
For failure to rescue, patient safety indicators, and external rankings, I would ask quality and analytics to demonstrate how the applicable specifications use diagnoses, complications, and present-on-admission (POA) information. Review the record for accuracy, then evaluate its measure effect. Improving a benchmark should never substitute for understanding what happened to the patient.
Advance care planning belongs here, too. CMS finalized its electronic Clinical Quality Measure (eCQM) for the FY 2030 payment determination. Use the preparation period to reconcile patient preferences, surrogate information, orders, narrative notes, and structured fields. The information must remain useful to the next care team, as well as available for measurement.
The Transforming Episode Accountability Model (TEAM) is already operating for selected hospitals and continues through 2030, with episodes extending 30 days after discharge. Participation is not universal. Hospitals included in the model should verify their 2027 track, financial exposure, target-price information, and current specifications.
Comprehensive Care for Joint Replacement Expanded (CJR-X) begins Jan. 1, 2028, with 90-day episodes. Unlike TEAM, CJR-X is mandatory nationwide for most eligible acute-care hospitals, subject to exclusions, including TEAM participants, Maryland hospitals, and hospitals not eligible for both Inpatient Prospective Payment System (IPPS) and OPPS payment. For affected organizations, 2027 is a preparation year.
Both discussions bring outpatient CDI, surgical clinics, case management, rehabilitation, and post-acute partners into the same room. Review how baseline complexity, surgical indications, complications, discharge needs, and follow-up plans travel across settings. A completed inpatient claim does not complete the patient’s episode.
The Ambulatory Specialty Model (ASM) belongs on the immediate readiness list. It applies to selected specialists treating heart failure or lower back pain, with performance beginning Jan. 1, 2027. Selection occurs at the taxpayer identification number and National Provider Identifier (NPI) combination, so hospital leaders should verify whether their employed and affiliated clinicians are selected participants, rather than assuming universal applicability. Payment adjustments follow performance by two calendar years. Outpatient CDI, specialty leadership, coding, quality, and analytics should verify diagnosis accuracy, episode attribution, care coordination, and reporting workflows before the performance year starts.
Other models require an applicability check. ACCESS (Advancing Chronic Care with Effective, Scalable Solutions) is a voluntary model for eligible participants and ties payment to outcomes in technology-supported chronic care. For participating organizations and referring practices, I would review how baseline status, follow-up outcomes, electronic updates, and any billed co-management work are documented.
LEAD (the Long-term Enhanced ACO Design Model) is a voluntary Accountable Care Organization (ACO) model beginning Jan. 1, 2027, following ACO REACH (Accountable Care Organization Realizing Equity, Access, and Community Health). Organizations entering LEAD should confirm participation arrangements, attribution, risk-adjustment data quality, and responsibility for care transitions with their population health and contracting teams. Neither model creates a universal hospital participation requirement.
For readers in participating states or regions, AHEAD (Achieving Healthcare Efficiency through Accountable Design) also warrants leadership review. Its hospital global budgets and total-cost-of-care approach make coordination between finance, quality, clinical leaders, and documentation teams essential. Confirm the applicable state, cohort, participation pathway, and implementation calendar before assigning deadlines.
GLOBE (Global Benchmark for Efficient Drug Pricing Model) connects directly to our outpatient drug billing discussion. The model begins Jan. 1, 2027; reduced coinsurance for selected eligible beneficiaries and drugs begins April 1, 2027. Participation is mandatory for manufacturers of qualifying Part B drugs, not for hospitals as model participants. Hospitals and suppliers serving selected beneficiaries should validate remittance and patient-liability workflows; CMS states that no separate GLOBE billing system or modifier is required.
For every applicable model, the first deliverable should be a named operational owner and a documented assessment of what changes in the clinical record, data submission, or payment workflow. A model announcement becomes actionable when someone can explain which patients and clinicians it affects, and what must work differently.
My outpatient drug billing segment asked who verifies that the claim accurately represents the medication administered. In its October 2026 data brief, HHS OIG identified 160,918 Medicare Part B outpatient drug claim lines, spanning dates of service from April 1, 2024, through March 31, 2025, where billed procedure codes did not match codes associated with the reported drug identifiers in CMS crosswalk files. OIG described potential oversight vulnerabilities, including absent system edits and gaps in provider education. These mismatches warrant investigation; the full set of claim lines should not be described as confirmed improper payments.
Carry that question into 2027 system testing. Follow selected medications from product identification and administration through charge mapping, HCPCS assignment, billing units, and the final claim. Include applicable discarded-drug reporting and modifiers in the review. Pharmacy, revenue integrity, coding, billing, and informatics need a shared way to resolve discrepancies. A documentation query cannot repair an incorrect system conversion.
Use the Program for Evaluating Payment Patterns Electronic Report (PEPPER), audit findings, and denial patterns to select additional areas for review. PEPPER identifies patterns warranting attention, not proof of payment errors. The useful outcome is a tested correction and evidence that the problem stopped recurring.
For California organizations, federal readiness is only part of the conversation. State requirements create an additional governance checkpoint for AI used in patient care and coverage decisions. Three laws should be considered together, but not treated as interchangeable: SB 1120, already effective Jan. 1, 2025, and AB 1979 and SB 503, both taking effect Jan. 1, 2027.
SB 1120 addresses the use of AI, algorithms, and other software in utilization review and utilization management. Its safeguards focus on individualized clinical information, and prohibit an AI tool from replacing a licensed professional’s determination of medical necessity or other clinical decisions within the law’s scope. For UR, physician advisors, and denials teams, the question is not simply whether an automated recommendation was generated, but whether the decision and its rationale meet the applicable requirements.
AB 1979 focuses on preserving licensed clinicians’ independent professional judgment when covered healthcare entities use AI clinical decision-support tools. It also restricts AI from independently undertaking functions that require a professional license. SB 503 separately addresses known or reasonably foreseeable discriminatory impacts of covered clinical decision-support systems, with responsibilities that differ for developers and deployers. These laws are not a blanket prohibition on AI, and their precise application depends on the statutory definitions and the role of the organization.
What should California hospitals do before January? Start with a cross-functional inventory: which tools influence clinical decisions, which support utilization review, which merely assist documentation, and which are subject to each statute? Then identify the licensed decision-makers, review and override pathways, validation, and bias-assessment processes, vendor responsibilities, and the record retained when an AI-generated recommendation is accepted, modified, or rejected. CDI and coding should be part of that review when generated diagnoses, queries, or summaries could influence the clinical record; compliance, informatics, quality, UR, and physician leadership should own the controls appropriate to their workflows.
The practical test is whether the organization can demonstrate who made the clinical decision, what patient-specific information informed it, and how unsupported or biased recommendations are detected and corrected. AI may accelerate the workflow; it should not obscure accountability.
Before the year ends, I would ask each team to bring its highest-priority unresolved issue to a shared readiness meeting. Identify the affected patients and services, the responsible owner, the applicable date, the workflow change, and how completion will be verified. Keep clinical education, EHR testing, policy updates, and audit follow-up connected.
We have spent the year discussing why documentation matters across the organization. Now we need to show what we did with that information. When the first patient arrives in 2027, the test will be whether the people, processes, and systems associated with that patient can produce a clear, accurate, and defensible record.
Companion Planning Guide | Distinguish compliance dates from preparation priorities.
TimingPriorityAccountability and next stepAlready effectiveFY 2027 ICD-10 updates: Oct. 1, 2026.Coding/CDI: confirm code-set implementation, education, and post-update review.Jan. 1, 2027637 services removed from the IPO List.UR, surgeons, PAs, revenue cycle: validate affected volume, status workflows, coverage, and payment modeling.Generally, 2027; payer-specific datesCMS-0057-F API requirements; hospital electronic prior authorization measure begins with CY 2027 reporting.IT, access, UM, and PI reporting lead: confirm applicability, test requests and responses, and review measure exclusions.2027 performance yearTEAM continues; applicable tracks and financial exposure need review.Episode lead, finance, surgery, CDI, and case management: verify current specifications and care-transition processes.Prepare during 2027 for 2028CJR-X begins Jan. 1, 2028; verify participation and exemptions.Executive sponsor and episode team: plan documentation, analytics, post-acute coordination, and 90-day episode oversight.FY 2028–2029 early look; FY 2030 paymentSepsis readmission measure.Quality, CDI, coding, and analytics: reconcile cohorts and plan review of confidential reports.FY 2028 IQR; FY 2032 VBPModified mortality measures include MA patients.Quality/Analytics: distinguish program years and underlying performance periods.FY 2030 payment determinationAdvance Care Planning eCQM.Quality, informatics, clinical teams, and health information management (HIM): verify measurement dates and structured-data capture.Ongoing readiness workClinical validation, query/AI governance, coverage policies, paid-claim testing, and audit follow-through.Assign an owner, evidence of completion, and recheck date for each identified gap.Jan. 1, 2027California AB 1979 and SB 503: clinical AI oversight and biased-impact safeguards.Compliance, clinical leadership, CDI, quality, and informatics: inventory covered tools, confirm independent clinical judgment, assess bias risks, and document oversight.
TEAM, CJR-X, and ASM merit a direct participation check. The remaining models need targeted review based on organizational participation, geography, or affected services.
ModelWho needs to actReadiness focusTEAMSelected hospitals; already active.Verify 2027 track, financial risk, target prices, and 30-day episode coordination.CJR-XApplicable hospitals; starts January 2028.Use 2027 for 90-day episode preparation. Verify exclusions, including TEAM participation.ASMSelected specialists; January 2027 performance start.Check TIN/NPI participation. Validate outpatient documentation, attribution, and quality reporting; payment adjustments lag two years.ACCESSVoluntary participants and referring/co-managing practices.Validate baseline and outcome data, patient updates, and support for any co-management billing.LEADVoluntary ACO participants; starts January 2027.Confirm organizational participation and attribution, risk-adjustment, and care-transition responsibilities.AHEADParticipating states/regions and organizations.Verify cohort-specific timing and hospital/global-budget or other participation pathway with Finance and population health.GLOBEManufacturers participate; affected providers assess billing implications.January 2027 launch; applicable coinsurance changes begin April 2027. Check affected drugs, beneficiaries, and system updates.
“Mandatory” means required only for organizations, clinicians, payers, or manufacturers meeting the stated applicability criteria. “Voluntary” identifies optional model participation; “operational review” is a recommended internal action, not a separate legal mandate. Years distinguish effective dates, model performance periods, and later quality-payment consequences.
TopicImpact yearMandatory vs. voluntary / scopeWho should participateFY 2027 ICD-10-CM/PCS and IPPSOctober 2026 / FY 2027Mandatory coding/payment rules for applicable hospitalsHIM coding, CDI, compliance, finance, IT; physician advisorsCY 2027 OPPS; 637 IPO List removalsJanuary 2027Mandatory payment rules for applicable services; inpatient status remains individualizedUR, physician advisors, surgery, coding, CDI, revenue integrity, financeTwo-Midnight and NCD/LCD coverageOngoing; reassess 2027Mandatory where Medicare coverage/payment rules apply; payer-specific variationUR, physician advisors, compliance, coding, revenue cycle, cliniciansCMS-0057-F payer APIs/ePA reporting2026 operational provisions; 2027 API/measure milestonesMandatory for specified impacted payers and eligible reporting entities; not all providers have identical dutiesIT/EHR, patient access, UR, revenue cycle, compliance, payer relationsClinical validation/AI-assisted CDIOngoing; 2027 readinessMandatory underlying coding, record and privacy duties; AI prompt audits recommendedCDI, coding, medical staff, compliance, quality, IT/AI governanceSepsis HRRP readmissionsFY 2028–29 early look; FY 2030 paymentMandatory HRRP measure for applicable hospitals; review now recommendedQuality, CDI, sepsis leads, analytics, case management, financeMA-inclusive mortality measuresFY 2028 payment determinationMandatory IQR specifications for applicable hospitalsQuality, CDI, coding, analytics, clinical service linesAdvance Care Planning eCQMFY 2030 payment determinationMandatory reporting for applicable IQR hospitals under final-rule scheduleQuality, IT/EHR, nursing, physicians, HIM, complianceTEAM2026–2030Mandatory selected hospitals; limited voluntary opt-in pathwaysFinance, quality, CDI, coding, surgery, case management, post-acuteCJR-XJanuary 2028Mandatory nationwide for most eligible acute-care hospitals; exclusions applyOrthopedics, finance, CDI, coding, quality, UR, post-acuteAmbulatory Specialty Model (ASM)January 2027Mandatory for selected specialists/TIN–NPI combinationsSpecialty clinicians, OP CDI, quality, analytics, finance, ITACCESS2026 onward/model scheduleVoluntary for eligible participantsAmbulatory leadership, digital health, finance, quality, complianceAHEADState-specific implementation yearsVoluntary state participation; obligations for participating entitiesState strategy, C-suite, finance, quality, population health, CDILEADModel-specific future timelineParticipation/applicability check; do not assume mandatory hospital enrollmentACO/population health, finance, quality, analytics, complianceGLOBE Part B drug modelJanuary 2027; coinsurance April 2027Mandatory qualifying manufacturers; provider operational impact where applicablePharmacy, revenue integrity, billing, finance, patient financial servicesOIG outpatient drug coding findings2026 report; remediation in 2027Audit recommendation; underlying claim accuracy requirements mandatoryPharmacy, revenue integrity, chargemaster, coding, complianceCalifornia SB 1120 AI in URJanuary 2025; ongoingMandatory for covered California utilization-review decisionsUR, physician advisors, compliance/legal, payer contracting, AI governanceCalifornia AB 1979 clinical AIJanuary 2027Mandatory for covered entities and covered AI usesCMO, clinicians, compliance/legal, IT, AI governance, CDICalifornia SB 503 AI bias safeguardsJanuary 2027Mandatory for covered developers/deployers as specified by statuteCompliance/Legal, AI governance, IT/vendors, quality, equity leadersPEPPER and denial trend reviewsOngoing; 2027 planningVoluntary analytic improvement activity; not itself a CMS compliance mandateCDI, coding, revenue cycle, denials, compliance, analytics
Primary-source verification updated Nov. 16, 2026. Model participation and applicability must be confirmed for each organization.
1. CMS. ICD-10 files and FY 2027 Official Guidelines.
2. CMS. CY 2027 OPPS/ASC Final Rule fact sheet. November 4, 2026.
3. CMS. Two-Midnight Rule Fact Sheet.
4. CMS. Hospital Patient Status Review Frequently Asked Questions.
5. CMS. Medicare Coverage Determination Process.
6. CMS. Interoperability and Prior Authorization Final Rule CMS-0057-F.
7. ACDIS. Clinical validation and the role of the CDI professional (2021 update).
8. CMS. FY 2027 IPPS/LTCH PPS Final Rule fact sheet. July 31, 2026.
9. CMS. Transforming Episode Accountability Model.
10. CMS. Comprehensive Care for Joint Replacement Expanded Model. https://www.cms.gov/priorities/innovation/innovation-models/cjr-x
11. HHS OIG. Potential Vulnerabilities in CMS’s Oversight of Medicare Providers’ Billing of Selected Outpatient Drugs. OAS-25-09-090, October 2026. https://www.oig.hhs.gov/reports/all/2026/potential-vulnerabilities-in-cmss-oversight-of-medicare-providers-billing-of-selected-outpatient-drugs/
12. PEPPER. Frequently Asked Questions.
13. CMS. Ambulatory Specialty Model: CY 2027 PFS Final Rule Fact Sheet.
14. CMS. Advancing Chronic Care with Effective, Scalable Solutions (ACCESS) Model.
15. CMS. Long-term Enhanced ACO Design (LEAD) Model.
16. CMS. Achieving Healthcare Efficiency through Accountable Design (AHEAD) Model.
17. CMS. Global Benchmark for Efficient Drug Pricing (GLOBE) Model. https://www.cms.gov/priorities/innovation/innovation-models/globe
18. California Assembly Bill 1979 (2026), Chapter 854, Health care services: artificial intelligence. Effective January 1, 2027. https://leginfo.legislature.ca.gov/faces/billNavClient.xhtml?bill_id=202520260AB1979
19. California Senate Bill 503 (2026), Chapter 857, clinical decision-support systems and biased impacts. Effective January 1, 2027. https://leginfo.legislature.ca.gov/faces/billNavClient.xhtml?bill_id=202520260SB503 20. California Senate Bill 1120 (2024), Physicians and surgeons: artificial intelligence, effective January 1, 2025. https://leginfo.legislature.ca.gov/faces/billNavClient.xhtml?bill_id=202320240SB1120
This article was originally published on RACmonitor.
November 16, 2026
OpenAI is expanding computer-use agents for healthcare, enabling AI to navigate electronic health record systems, payer portals and other software to tackle repetitive and manual tasks.
This article was originally published on Fierce Healthcare.
November 13, 2026
CMS is offering states an optional six-month enforcement grace period for new Medicaid work requirements, allowing them to test and improve eligibility systems without denying or terminating otherwise eligible beneficiaries for noncompliance through June 30, 2027.
This article was originally published on Fierce Healthcare.
November 12, 2026
Over the past year, UnitedHealth Group has conducted a series of independent reviews of its practices as part of a broader turnaround effort at the company.
This article was originally published on Fierce Healthcare.
November 12, 2026
CMS and ONC are launching a voluntary industry testing initiative to help healthcare organizations prepare for federal electronic prior authorization requirements taking effect in 2027.
This article was originally published on Fierce Healthcare.