All insights
The Insight Gap

Every plan runs on a care gap list. Almost none of them fully trust it.

The list a care team works on Monday describes members as they were weeks ago. The gaps that already closed crowd out the ones that are still open.

7 min readPayors · ACOs

Every Medicare Advantage plan runs on a care gap list. Almost none of them fully trust it.

The list a care team works on Monday was built from a data extract that closed a few weeks earlier. In that time, members got the mammogram at a retail clinic, filled the statin the plan still thinks they aren't taking, and completed the eye exam at an optometrist who hasn't filed the claim yet. The list says open. Reality says closed.

Care gap list accuracy rarely comes up in a planning meeting. It rarely has a line in the budget or a row on a report. But it decides whether a care team's week goes to members who need something, or to members who already did it.

Why does a care gap list go stale?

It isn't that the plan lacks the data. The supplemental feed, the lab result, and the pharmacy fill all exist somewhere. The trouble is that none of them reach the gap list until the next extract cycle, and by then the team is a step behind the member.

Most gap lists are built in batches. Data lands in different places on different schedules. Claims often arrive weeks after the visit. A screening done outside the network may show up only in a lab result or a supplemental file. Then, on a set cycle, someone pulls it all together, runs it against the measures, and publishes a list. Whatever happened after the cut-off waits for the next one.

So the list is never wrong by much on any one row. It is a little behind on a great many rows, all at once, and each row looks equally certain. Nothing tells the care manager which open gaps closed last week and which have been open since January.

This is the Insight Gap at the level of a single quality measure: the time between when the data exists and when someone can act on it.

What does a stale gap list cost?

Picture Maria, a care manager at a health plan (a composite, not a real person). Her Monday list has a member flagged for an overdue eye exam. She calls. The member is polite but puzzled: they had the exam weeks ago, and the doctor said everything looked fine. Maria apologizes, marks the call, and moves to the next row. A similar thing happens a little later with a mammogram reminder.

Neither call was a disaster. Together, they show what a stale list really costs.

  • The member's time and goodwill. Someone who did what their doctor asked gets a reminder to do it again. Do that often enough and the plan's calls start to sound like noise, including the ones that matter.
  • The care team's capacity. Every call spent on a gap that already closed is a call not spent on one that is still open. The week is finite, and the list quietly spends part of it.
  • The open gaps that matter. The members who still need a screening sit on the same list as the ones who don't, and nothing on the screen tells them apart. The real work hides behind the noise.
  • Trust in the list itself. Each wasted call lowers trust a little more. Care managers start checking the medical record before every call, or keeping their own side notes, or skipping rows they suspect are already done. The list stops being the plan and becomes a suggestion.

The list says open. Reality says closed. And the gaps that are truly open sit behind the noise.

That last cost lasts longest. Once a team has learned not to trust the list, a more accurate list doesn't fix it overnight. People keep their workarounds until the list has earned their trust back.

Why doesn't a faster extract solve it?

The instinct is to run the extract more often. That helps a little, but it keeps the same shape. A list rebuilt more often from batched data is still a snapshot, and it is out of date the moment it is published. The result that arrived an hour after the cut-off still waits.

Adding people doesn't solve it either. Asking analysts to check each row by hand before outreach just moves the reconciliation from the data to the care team's desk. It also tends to make the team work the easiest gaps first rather than the most important ones, because checking takes time and the easy rows feel safer.

The real question is when the list learns that a gap closed. Is it the day the result is received, or the week the next extract runs?

What does care gap list accuracy look like in practice?

A gap list that updates the day a result is received changes what the call is for. Instead of re-arguing gaps that already closed, the call confirms the few that are truly open.

It comes down to a few things:

  • Evidence counts when it arrives. A screening done outside the network or recorded only in a lab result closes the gap as soon as it lands, not after the next batch.
  • Open means open. When a row says a member still needs something, the care manager can believe it without opening the chart first.
  • Closed gaps leave the list. Members who already did the thing stop getting reminders about it.
  • The remaining list is short enough to be honest. With the noise gone, the team can see which open gaps carry the most weight and start there.

What changes in a care team's week?

Go back to Maria. With a list that keeps up, her Monday starts with fewer rows, and each one is real. The member who had the eye exam is no longer on it. She calls the members who still need care, and the conversations are about scheduling, not explaining.

Over a year, that adds up. Outreach can start early and run steadily, rather than piling up in the fall, when the time left to close a gap is already short. Members hear from the plan when there's something to do. And the care team can stop double-checking and get back to the work it was hired for.

So it's worth asking: how current is the gap list your team will work tomorrow?

ElevateCare 360 was built around that question. ElevateCare 360's Quality Module checks claims, the medical record, and lab results against each quality measure continuously, and matches completed screenings and results back to the measure automatically. See how it works on the care gap closure page.

Frequently asked questions

Why does our care gap list show gaps that members have already closed?
Most lists are rebuilt from data extracts on a set cycle. Anything that happens after the cut-off, like a screening at a retail clinic, a lab result, or a claim that hasn't been filed yet, doesn't appear until the next cycle. So the list shows members as they were a few weeks ago.
Does running the extract more often solve the problem?
Only partly. A list rebuilt more often from batched data is still a snapshot, and it starts aging the moment it is published. What matters is whether the list updates when a result is received, rather than when the next batch runs.
Can screenings done outside our network close a care gap?
They can, if the evidence reaches the list. ElevateCare 360 combines claims, the medical record, lab results, and payor quality files, so a screening done outside your network, or recorded only in a lab result, still counts toward closing the gap.
How does a stale gap list affect care teams?
It spends their week on calls that didn't need to happen, frustrates members who already did what was asked, and buries the gaps that are truly open. Over time, staff stop trusting the list and build their own workarounds, which slows everything down. More on how teams triage in our piece on identical-looking gaps.

See what this looks like on your population.

A 30-minute walkthrough of ElevateCare 360 and ElevateIQ, mapped to your organization, your data, and the window you are actually working inside.