As states transition from traditional fee-for-service to Value-Based Payments (VBP), DSRIP has been a critical bridge. But for many organizations, the very mechanism designed to reward innovation is now drowning in redundant metrics, legacy reporting, and “just in case” data collection.
But recently, a new term has crept into the lexicon of Medicaid transformation: bloat dsrip
The “Bloat” in DSRIP: When Value-Based Care Metrics Get Too Heavy to Lift Share your worst "report crash" story in the comments below
Have you experienced DSRIP data bloat in your organization? Share your worst "report crash" story in the comments below. Your interface engines are processing millions of duplicate
To satisfy DSRIP, you need to pull claims data, EHR data, and social determinant (SDOH) data. The bloat happens in the middleware . Your interface engines are processing millions of duplicate ADT messages just to confirm a patient is still "attributed" to your PCP. This bloat slows down real-time dashboards to a crawl, making your November report look like it was written in July.
Here is how bloat manifests in DSRIP, why it destroys your ROI, and how to lean out your reporting. 1. Metric Creep (The "Nice to Know" Syndrome) DSRIP originally focused on high-impact areas: avoidable ER visits, cardiovascular health, and perinatal care. But over three years, someone always asks, "Can we just add one more measure?" Suddenly, you are tracking 120 discrete data points for a single patient cohort. When every metric is a priority, none are. The bloat comes from measuring things that are easy to track (data availability) rather than things that change outcomes (clinical relevance).