Most organizations in value-based care run separate programs side by side. One keeps the roster accurate. One closes care gaps. One documents how sick members really are. Each has its own team, its own reports, its own meetings, and often its own list of who the members are.
On an org chart, that looks tidy. In practice, it is a value-based care operating model built around a division that the work itself doesn't respect. Look at what each program depends on, and the lines start to blur almost immediately.
Why do roster, quality, and risk work depend on each other?
You can't close a care gap for a member who isn't on the right doctor's list. The outreach goes to a practice that no longer sees her, or to no practice at all, and the gap stays open while everyone involved does their job.
You can't document a patient's conditions accurately if she hasn't been seen this year. Chronic conditions have to be addressed again each year to count, and that happens in a visit. If the member never makes it to the exam room, the record describes a healthier person than the one who needs care.
And you can't decide whose gaps matter most without knowing who is sickest. A long list of open screenings, sorted by how easy each one is to close, will put the members with the most at stake near the bottom.
Every one of those questions starts with the same facts: who is this member, who is caring for them, and what do we know about their health right now. The programs are not separate problems that happen to share some data. They are one problem, viewed from different desks.
Every one of those questions starts with the same facts: who is this member, who is caring for them, and what do we know about their health right now.
What does running them separately cost a care team's week?
Take a composite example. Dana leads network operations at an accountable care organization. Her team spends much of the month matching payor files to work out which patients belong to which practice. When they finish, the quality team is already working from a gap list built on an earlier version of the roster. The risk team has its own list of members due for a visit, drawn from a different extract again.
Marcus, a quality coordinator, calls a practice about a member with an open screening. The office tells him the member transferred to another doctor in the spring. He updates his own list. The risk team's list still has the member at the old practice. Nobody tells them, because nobody's job is to tell them.
Meanwhile the practice gets a quality list from one team and a risk list from another, often for the same patients, with different names spelled different ways and different doctors attached. The office manager prints both, sets them side by side, and works out by hand which patients appear on each. We've walked through that scene in the year-end lists that land on one practice.
None of this shows up as a line item. It shows up as part of every team's week spent reconciling with the others: a meeting to agree on the member count, an email chain about which doctor a patient belongs to, an analyst's afternoon matching one report to another. Each team experiences it as its own local annoyance. Added together, it is real capacity spent on agreeing what is true rather than acting on it.
The cost lands on patients, too. When the roster lags, every workflow built on top of it quietly works on a population that no longer exists. Members who left months ago drag down the gap list. New members wait for their first contact. The visit that could have done several things at once does only one.
What changes when the facts live in one place?
The clearest way to see it is through a single visit. When the facts live in one place, the same visit that closes a gap also confirms the member's conditions and confirms the member belongs to that practice.
- Before the visitThe practice gets one view of the patient: the open gaps, the conditions due to be addressed this year, and confirmation that this patient is theirs. Not separate lists from separate teams.
- In the roomThe clinician addresses what is open while the patient is there. The screening gets ordered. The chronic conditions get evaluated and documented if the clinical evidence supports them.
- After the visitThe visit itself is a fact about who is caring for this member. When it lands in one place, it updates the roster, the gap list, and the risk picture together, rather than travelling separately into each.
- The next weekEvery team starts from the same current list. Nobody spends Monday finding out what another team learned on Friday.
That changes what each team's week looks like. Network operations stops being the department that hands a file to everyone else and starts being the reason everyone else's list is right. The quality team prioritizes by need because it can see who is sickest. The risk team plans visits around members it knows are attributed and reachable.
Is a value-based care operating model just a technology question?
No. It is an operating one. Plenty of organizations have pulled their data into one warehouse and still run separate programs with separate targets, separate lists, and separate rhythms. Unified data does not help much if each team still starts its month by pulling its own extract and building its own list.
The operating question is simpler and harder: who owns the basic facts every program depends on, and does every team work from that same version of them? When the answer is "each team keeps its own," the reconciliation is built into the structure, no matter how good the tools are.
Getting there usually means a few changes in how the work is organized, not just where the data sits:
- One shared definition of who the members are, kept current, that every program uses rather than rebuilds.
- Goals set across programs, so a visit that closes a gap and confirms a member's conditions counts as one success, not several unrelated ones.
- One combined view of each patient going to each practice, instead of separate requests from separate teams.
- Regular reviews where roster, quality, and risk leaders look at the same population together, rather than reporting upward in parallel.
Why does this matter heading into next year?
Every January, members arrive at new plans and new doctors, the gap lists reset, and chronic conditions have to be addressed again. The organizations that handle the new year best will be the ones that stop treating these as separate projects with separate starting lines. They will begin the year with one picture of who their members are and let every program work from it.
That is the idea behind ElevateCare 360: every module reads from the same unified roster, claims, and clinical record, so action in one place updates the whole picture. It is the platform the work moves to, so the shared facts are not something each team has to rebuild. If you're running these as separate programs today, contact the Elevate team to see how ElevateCare 360 can help.
Frequently asked questions
- What is a value-based care operating model?
- It is how an organization structures the work behind its value-based contracts: who keeps the roster current, who closes care gaps, who makes sure conditions are documented, and how those teams share information. The key question is whether they work from one shared picture of each member or each keep their own.
- Why do our roster, quality, and risk teams keep reconciling with each other?
- Usually because each team builds its own list of members from its own source on its own schedule. Members change doctors and plans during the year, and those changes reach each team at different times. The lists drift apart even when everyone is doing their job well.
- Should we merge our roster, quality, and risk teams?
- Not necessarily. The specialized skills still matter. What changes is that the teams share the same facts about who each member is, who is caring for them, and what is known about their health, and set goals that recognize when one visit serves several programs at once.
- Where should an organization start?
- With the roster. Every other program assumes it knows who the members are and which doctor is responsible for them. A current, shared roster is the foundation the rest builds on. See how roster management keeps that list current for every team.