Showing posts with label persivia. Show all posts
Showing posts with label persivia. Show all posts

Wednesday, April 29, 2026

Traditional MIPS vs. MIPS Value Pathways: All You Need To Know

 MIPS reporting has changed considerably in recent years. The Merit-based Incentive Payment System has always required clinicians to report across quality, cost, improvement activities, and promoting interoperability. The problem with the traditional structure was that it pulled from a broad measure library, and providers often ended up reporting on things that had little connection to their actual clinical work. MIPS Value Pathways were designed to address that. CMS introduced MVPs as a voluntary option starting with the 2023 performance year, and the broader intent is straightforward: traditional MIPS will eventually be replaced.

MIPS Value Pathways

What Is Traditional MIPS

Traditional MIPS covers four performance categories:

  • Quality
  • Cost
  • Improvement Activities
  • Promoting Interoperability

Under traditional MIPS reporting, clinicians select from a large pool of measures across these categories. There is no requirement that the chosen measures connect to a specific specialty or condition. A cardiologist and a general practitioner could end up reporting on the same measures, even if those measures reflect very different clinical realities. That disconnect is what made the data less useful for both CMS and the clinicians themselves.

What Are MIPS Value Pathways

MIPS Value Pathways are a defined subset of measures and activities grouped around specific specialties, clinical conditions, or episodes of care. Rather than selecting from the full MIPS measure library, clinicians reporting through an MVP work within a pathway that reflects what they actually treat.

The MVP framework also incorporates a foundational layer that includes Promoting Interoperability measures and administrative claims-based quality measures focused on population health, which helps reduce overall reporting burden. 

There are currently 16 available MVP options covering a range of specialties and conditions, from rheumatology to anesthesia to chronic disease management.

Traditional MIPS vs. MVPs: Key Differences

Features

Traditional MIPS

MIPS Value Pathways

Measure selection

Broad, clinician's choice

Specialty or condition-specific

Reporting burden

Higher

Reduced

Subgroup reporting

Not available

Available

Population health layer

Not required

Built in

Future status

Being phased out

Becoming mandatory

The whole point of MVP reporting is to start measuring the performance of specialists within a practice who have, under traditional MIPS, been reporting on practice-wide measures largely irrelevant to their scope of work. 

Who Can Report MVPs

MVPs can be reported by individual MIPS eligible clinicians, single specialty groups, multispecialty groups, or APM Entities. MVPs can also be reported at the subgroup level, which is not an option under traditional MIPS. 

Registration is required. Clinicians must register with CMS as MVP participants within the designated window during the performance year. Choosing an MVP also means committing to the measures within that pathway for the full performance year.

What Scoring Looks Like Under MVPs

Scoring under MIPS Value Pathways largely mirrors traditional MIPS. Performance category weights remain consistent with traditional MIPS, and reweighting policies also align, with one exception: CMS will not reweight the Quality category if a score cannot be calculated because there is no applicable quality measure for the clinician. 

For the 2026 performance year, clinicians reporting an MVP will need to report four quality measures, one improvement activity, and promote interoperability measures, with CMS calculating the Medicare Spending Per Beneficiary measure for the Cost category. 

Where MIPS Reporting Is Headed

CMS has been clear about the direction. Traditional MIPS reporting is being phased out, with MVPs set to become the standard path forward unless clinicians are reporting through the APM Performance Pathway. The 2027 performance year has been referenced as the point after which traditional MIPS would no longer be an option. Practices that have not yet looked into MVPs will need to get familiar with the available pathways and what registration involves before that window closes.

Conclusion

The move from traditional MIPS to MIPS Value Pathways changes how performance gets measured, not just how it gets reported. Specialty-aligned measures give CMS more relevant data and give clinicians a clearer picture of how their work is being assessed. The transition is gradual for now, but the timeline is moving. Organizations that start understanding MVP requirements early will have more room to plan, rather than adjusting under pressure when reporting becomes mandatory.

Persivia offers various health management platforms that help healthcare organizations stay on top of quality program requirements, track performance across measures, and manage reporting without the manual work that typically slows teams down.

Traditional MIPS vs. MIPS Value Pathways: All You Need To Know

MIPS reporting has changed considerably in recent years. The Merit-based Incentive Payment System has always required clinicians to report across quality, cost, improvement activities, and promoting interoperability. The problem with the traditional structure was that it pulled from a broad measure library, and providers often ended up reporting on things that had little connection to their actual clinical work. MIPS Value Pathways were designed to address that. CMS introduced MVPs as a voluntary option starting with the 2023 performance year, and the broader intent is straightforward: traditional MIPS will eventually be replaced.

MIPS Value Pathways

What Is Traditional MIPS

Traditional MIPS covers four performance categories:

  • Quality
  • Cost
  • Improvement Activities
  • Promoting Interoperability

Under traditional MIPS reporting, clinicians select from a large pool of measures across these categories. There is no requirement that the chosen measures connect to a specific specialty or condition. A cardiologist and a general practitioner could end up reporting on the same measures, even if those measures reflect very different clinical realities. That disconnect is what made the data less useful for both CMS and the clinicians themselves.

What Are MIPS Value Pathways

MIPS Value Pathways are a defined subset of measures and activities grouped around specific specialties, clinical conditions, or episodes of care. Rather than selecting from the full MIPS measure library, clinicians reporting through an MVP work within a pathway that reflects what they actually treat.

The MVP framework also incorporates a foundational layer that includes Promoting Interoperability measures and administrative claims-based quality measures focused on population health, which helps reduce overall reporting burden. 

There are currently 16 available MVP options covering a range of specialties and conditions, from rheumatology to anesthesia to chronic disease management.

Traditional MIPS vs. MVPs: Key Differences

Features

Traditional MIPS

MIPS Value Pathways

Measure selection

Broad, clinician's choice

Specialty or condition-specific

Reporting burden

Higher

Reduced

Subgroup reporting

Not available

Available

Population health layer

Not required

Built in

Future status

Being phased out

Becoming mandatory

The whole point of MVP reporting is to start measuring the performance of specialists within a practice who have, under traditional MIPS, been reporting on practice-wide measures largely irrelevant to their scope of work. 

Who Can Report MVPs

MVPs can be reported by individual MIPS eligible clinicians, single specialty groups, multispecialty groups, or APM Entities. MVPs can also be reported at the subgroup level, which is not an option under traditional MIPS. 

Registration is required. Clinicians must register with CMS as MVP participants within the designated window during the performance year. Choosing an MVP also means committing to the measures within that pathway for the full performance year.

What Scoring Looks Like Under MVPs

Scoring under MIPS Value Pathways largely mirrors traditional MIPS. Performance category weights remain consistent with traditional MIPS, and reweighting policies also align, with one exception: CMS will not reweight the Quality category if a score cannot be calculated because there is no applicable quality measure for the clinician. 

For the 2026 performance year, clinicians reporting an MVP will need to report four quality measures, one improvement activity, and promote interoperability measures, with CMS calculating the Medicare Spending Per Beneficiary measure for the Cost category. 

Where MIPS Reporting Is Headed

CMS has been clear about the direction. Traditional MIPS reporting is being phased out, with MVPs set to become the standard path forward unless clinicians are reporting through the APM Performance Pathway. The 2027 performance year has been referenced as the point after which traditional MIPS would no longer be an option. Practices that have not yet looked into MVPs will need to get familiar with the available pathways and what registration involves before that window closes.

Conclusion

The move from traditional MIPS to MIPS Value Pathways changes how performance gets measured, not just how it gets reported. Specialty-aligned measures give CMS more relevant data and give clinicians a clearer picture of how their work is being assessed. The transition is gradual for now, but the timeline is moving. Organizations that start understanding MVP requirements early will have more room to plan, rather than adjusting under pressure when reporting becomes mandatory.

Persivia offers various health management platforms that help healthcare organizations stay on top of quality program requirements, track performance across measures, and manage reporting without the manual work that typically slows teams down.

Monday, April 20, 2026

Digital Health Platforms: Past Challenges and What Comes Next

Healthcare has spent decades buying technology that promised more than it delivered. Systems went in, costs went up, and care teams ended up managing the tools instead of the patients. A Digital Health Platform in 2026 looks nothing like what got sold under that name ten years ago. The difference is worth understanding, both for what went wrong before and for what is actually working now.

Digital Health Platform

What Early Digital Health Got Wrong

Early digital health tools were built to solve one problem at a time. A hospital would have one system for documentation, another for billing, another for outreach, and another for quality reporting. None of them shared data cleanly. Care teams spent as much time moving information between systems as they did using it.

The tools were not necessarily bad. The problem was that they were never designed to work together. Each solved its own problem and stopped there, leaving organizations with a collection of systems and no coherent way to operate across them.

The Data Problem That Kept Coming Back

Social determinants barely made it into the picture. Care managers pulled together whatever they could find from whichever system they had access to that day and made decisions from there. By the time the right information reached the right person, the window to act had often already closed. Connecting all of that data turned out to be a much harder problem than it looked.

Every organization accumulates patient data. Very little of it was usable in real time. Records sat in systems that could not talk to each other. Claims lived separately from clinical data. Digital health platforms were supposed to fix this. Early versions tried. But the integration work proved harder than product roadmaps suggested.

What Changed and Why It Matters Now

Interoperability Moved From Optional to Required

For years, data sharing between systems depended on custom integrations built case by case. That changed when FHIR-based standards moved into enforcement. Interoperability standards, including FHIR R4/R5, USCDI+, and TEFCA, have moved from encouragement to enforcement, accelerating modernization across care settings. 

When data can actually move between systems reliably, a Digital Health Platform can do what it was always supposed to: give care teams a complete, current view of a patient regardless of where care was received.

The Shift From Point Solutions to Unified Platforms

Organizations stopped looking for the best tool for each task and started looking for one environment that handled all of them. The shift happened because the cost of managing multiple disconnected vendors, each with its own data format and integration requirements, became too high.

That shift matters because the problems healthcare organizations face are not isolated. Risk stratification connects to care management. Care management connects to quality reporting. Quality reporting connects to reimbursement. A platform that handles one piece well but requires manual work to connect the others does not solve the underlying problem.

What a Modern Digital Health Platform Actually Does

A modern Digital Health Platform is not a dashboard. It is an operating environment for care delivery.

A current patient record built from EHRs, claims, labs, and social data. Risk scores that update as new information comes in. Care gaps that surface where clinicians are already working, not in a separate tab. Quality measure performance is tracked throughout the year, not just at submission time.

The ones that actually work were built to connect from day one. They did not start as a single-use tool and expand outward. They started with the assumption that data comes from everywhere and needs to end up in one place.

Where Digital Health Platforms Are Heading

AI That Does More Than Flag

AI in early digital health platforms mostly flagged things: a potential risk, a possible gap. The next step is not just identifying a problem. It is doing something about it automatically. Routing outreach, updating care plans, and filling documentation gaps: these used to require a person to connect the dots. Platforms handling this directly are where the real-time savings show up for care teams.

Modular Architecture That Adapts

A large health system and a small ACO do not need the same setup. Platforms that can be configured to fit how an organization actually works, without a full rebuild every time something changes, hold up better as contracts and regulations shift. That flexibility is what separates a platform organization from one that they eventually replace.

Conclusion

Digital health has a long history of tools that worked in demos and fell short in practice. The gap between a promising product and something a care team actually uses every day has always been the hard part. What is different now is that the infrastructure, data standards, integration capabilities, and clinical workflow design have caught up enough that the gap is finally closable for organizations willing to make the right platform choice.

The CareSpace® Digital Health Platform from Persivia has been doing exactly this work for nearly two decades, across more than 200 hospitals and 20 million patients. It connects clinical and claims data, continuously runs risk stratification, surfaces care gaps at the point ofcare, and tracks quality and financial performance in one place. Fororganizations looking at where digital health platforms actually deliver on their promise, see what CareSpace® covers.

Thursday, April 16, 2026

Population Healthcare Analytics for ACOs: The Metrics That Actually Move Outcomes

ACOs sit on more data than they know what to do with. The challenge has never been collecting it. It is figuring out which numbers actually connect to patient outcomes and financial performance, and getting those numbers to the right people while there is still time to act. Population Healthcare Analytics is how high-performing ACOs close that gap. For organizations running MSSP, ACO REACH, or other risk contracts, the difference between hitting and missing a shared savings target often comes down to which metrics the care team is tracking and how quickly they can respond.

What Population Healthcare Analytics Actually Means for ACOs

Population Healthcare Analytics turns clinical and claims data into patterns a care team can do something with: which patients are headed toward hospitalization, which providers have high ED utilization, and where costs are running above benchmark three months into the performance year.

Most ACOs are not short on reports. They are short on reports that reach the right person soon enough to change what happens next.

The Metrics That Show Up in High-Performing ACOs

Some metrics look useful, but never connect to a decision. Others sit behind the financial and quality performance of every ACO that consistently hits its targets. Here is what that second group actually tracks.

Risk Stratification Scores

Risk stratification identifies which patients are heading toward high-cost events before those events happen. It works by pulling together clinical history, recent claims, lab results, and social factors into a score that updates as conditions change. A patient managing three chronic conditions who missed two recent follow-ups looks different from one whose care is on track, and the score should reflect that difference in real time, not at the next reporting cycle.

ED Utilization and Avoidable Admissions

Emergency visits and inpatient stays account for a significant share of ACO costs. Tracking these by patient, provider, and care site shows where utilization is concentrated. When one provider's panel drives a disproportionate share of ED visits, that is a specific target. General awareness that utilization is high does not lead to action. Knowing where and why does.

Care Gap Closure Rates

A care gap left open is two problems at once: a patient whose condition is not being monitored and a quality measure that will not close. Tracking how many gaps get closed, by which care managers, across which programs, shows where the outreach process is holding up and where patients are consistently not getting reached. That distinction matters because the fix is different in each case.

Cost and Utilization Patterns

Cost/utilization analytics connects spending to specific care patterns. Which patient groups are running costs above contract benchmarks? Where is post-acute spending higher than expected? Are referrals leaving the network when in-network options exist? A population healthcare analytics solution tracking this through the performance year lets leadership adjust before the year closes, not after.

Readmission Rates

When a patient returns within 30 days of discharge, something in the transition process did not work. Tracking readmissions by diagnosis, discharge destination, and whether a follow-up visit happened shows where the breakdown occurred. That is a different and more useful picture than a single readmission rate at year-end.

Why Most Analytics Fall Short

The gap between analytics that generate reports and analytics that change outcomes usually comes down to timing and workflow. Numbers reviewed once a month show what happened. A population healthcare analytics solution that updates as new data comes in shows what is happening now, when something can still be done about it.

The second issue is where the data lives. Analytics in a separate system from care management requires someone to manually connect the two. By the time a flag reaches a care coordinator, the opportunity may already be gone. When analytics feed directly into care management workflows, the data becomes action without an extra step.

What Strong Analytics Infrastructure Covers

For ACOs, a cost/utilization analytics setup worth running includes:

  • Risk scores that refresh as new clinical and claims data arrive
  • ED and admission tracking at the patient and provider level
  • Care gap performance by measure, site, and contract
  • Cost and utilization benchmarks compared against contract targets throughout the year
  • Readmission monitoring with post-discharge follow-up built in

Each of these ties directly to the financial and quality metrics an ACO is accountable for. Tracking them in one connected place, updated regularly, is what makes population healthcare analytics operationally useful rather than just informational.

Conclusion

ACOs consistently hitting their performance targets are not working from better instincts. They have a clearer, more current picture of their population, and that picture reaches the people responsible for acting on it before the window closes. Analytics sitting in quarterly reports do not drive outcomes. Analytics connected to daily care workflows do.

That connection between data and action is what a well-built population healthcare analytics solution makes possible. Persivia's CareSpace® covers risk stratification, cost and utilization tracking, care gap performance, and quality measure reporting in one place, with analytics flowing directly into care management workflows. For ACOs looking to close the gap between the data they have and the outcomes they are accountable for, see what CareSpace® covers.

Featured post

Traditional MIPS vs. MIPS Value Pathways: All You Need To Know

  MIPS reporting has changed considerably in recent years. The Merit-based Incentive Payment System has always required clinicians to report...