Nobody calls to confirm anymore:  What the first year on a connected record actually changes

SUMMARY: 

 The first year on a connected operations record is not marked by anything dramatic. It is marked by the disappearance of small verification habits that teams had stopped noticing they had. The recruiter calling the site manager to check whether the schedule is still correct. The printed schedule on the wall that everyone worked from. The second look in another system before deploying someone. Those habits are the clearest measure of whether a record is trusted, and watching them fade is the most reliable signal I have that something actually changed. 

The first year is measured in what stops happening.

I wrote earlier this year about the gap between credentialing and scheduling, and about how a clinician can be fully approved while the people making coverage decisions are still working from an incomplete picture. That piece was about the friction. This one is about what happens on the other side of it.

I have a slightly unusual vantage on this. I was the first person to use Kimedics, back when I was in operations rather than customer success, which means I have watched the same handful of workflows evolve for years and across a lot of different organizations. What I did not expect, early on, was how quiet the change would be when it came. Nobody announces that their operation got more connected. There is no moment. What there is instead is a set of behaviors that stop, usually without anyone deciding to stop them.

This past summer, I was on a routine check-in call with the operations director at one of the groups I work with. What they wanted to talk about was the schedule. It was current. It was live. Before they moved to Kimedics, the printed schedule on the wall was what everyone worked from. It was not the source of truth anymore. When they shared a schedule through a Kimedics link, they trusted that the link was live.

What stayed with me was that they described it as something that had stopped being necessary. It made me think of a call I have watched happen at organization after organization: a recruiter phoning a site manager to check whether the schedule is still correct. The printout and the call exist for the same reason. Nobody can be sure the schedule in front of them is still right. Once a shared link is more reliable than the paper, neither one has much work left to do.

The calls go first.

The confirmation call is the first habit to go, and it goes earlier than most teams expect. Sometimes it is a recruiter calling a site manager to check whether the schedule is still what it says it is. Sometimes it is a recruiter calling credentialing to confirm a status already marked approved. Both calls stop for the same reason: what the recruiter is looking at is the same thing everyone else is looking at, updated at the same moment. That sounds like a small thing. In practice it is the most visible change in the first quarter, because those calls were never really about information. They were about confidence.

What I have noticed is that people rarely connect the change to the system. They tend to describe it as the credentialing team getting faster, or as things generally running better lately. The credentialing team was already fast. What changed is that their work became visible to the people downstream of it at the moment it was finished rather than at the moment someone thought to ask.

Then the double checking goes, and that one takes longer.

Cross-system verification is a harder habit to break, and I think that is because it was built over a longer period and for better reasons. A scheduler who has been burned once by deploying a clinician whose privileging had not actually cleared will keep checking for a while, regardless of what the screen says. That is a reasonable response to having been given bad information before, and it would be a mistake to call it stubbornness.

So the second and third quarters tend to look like a slow calibration. People check, find the record was right, check again a little less carefully, find it was right again. Somewhere in there the checking stops being a step in the process and becomes something they do when a situation feels genuinely unusual, which is what verification is supposed to be. I have come to think of this phase as the record earning its standing, and I do not think it can be shortened much. Trust in an operational record is built the same way trust in a colleague is built: slowly, and through repetition.

The last thing to change is what people are willing to plan.

This is the part I find most interesting, and it is the part that takes closest to a full year.

When a team cannot be confident about the current state of their coverage, their planning horizon quietly contracts. They plan the next two weeks well, because two weeks is as far as they can see with any confidence, and anything past that gets handled when it arrives. Nobody describes it this way. It is not a stated policy. But you can see it in what questions get asked in operating reviews, and in how far out the schedule is actually built rather than sketched.

When the record becomes reliable, that horizon starts extending, and the questions change shape along with it. Early in a first year, the questions I hear are about the present: who is cleared right now, what is open next week. Later in that year, the questions move forward: what the coverage pattern at a given site has looked like across two quarters, whether a recurring gap is seasonal or structural, what a staffing decision made in October will cost by February. Those are better questions, and they are only available to someone who trusts what they are looking at.

The industry already proved this at a larger scale.

Earlier this year CAQH published its 2025 Index, which found that U.S. healthcare avoided an estimated $258 billion in administrative costs in 2024 through electronic transactions and improved data exchange, with roughly $21 billion in savings still available if the transactions that remain manual or partly manual were fully automated.

I want to be careful about what that measures. The CAQH Index looks at the traffic between health plans and the organizations that bill them: claims, eligibility inquiries, prior authorization. It says nothing about scheduling or credentialing inside a medical group, and I would not stretch it to claim otherwise. I raise it because the shape of the finding is familiar. The savings came from transactions that used to require a person to carry information between two systems no longer requiring that. The remaining opportunity sits in the transactions where a person is still doing the carrying.

Inside a workforce operation, that person is the recruiter making the confirmation call, the scheduler checking the second system, and whoever keeps the printout on the wall current. The scale is smaller and nobody is measuring it nationally. The mechanism is the same.

None of this is about anyone working harder.

I said this in the last piece and I will say it again, because it gets misread constantly. The teams I work with are not inefficient. The confirmation call is a rational response to a schedule that has been wrong before. The printout on the wall is what people rely on when they do not have a live schedule they can open themselves. The second look is good judgment applied to partial information. When those habits disappear, it is because the information in front of people stopped being partial, and the habits were no longer doing any work.

What that means practically is that the first year asks less of change management than people tend to brace for. The behaviors do not need to be trained out. They fall away on their own once they stop earning their keep, and the main thing an operations leader can do is give them time to.

Why we built Kimedics the way we did

Kimedics is the clinician workforce operations platform built by healthcare operators. Scheduling, credentialing, time, and pay run on one connected operational record, so a status that is approved in credentialing is the same status the scheduler is looking at, and a schedule shared as a link is the live schedule, not a copy of it. That design came from people who had spent years making those confirmation calls themselves.

The organizations I have watched get the most out of a first year did not approach it as a replacement project. They connected what they already had and then let the verification habits fall away at their own pace. A year on, the clearest evidence that it worked is in the calls nobody is making, and the printout nobody walks over to check.

Q&A

Q:  What actually changes in the first year on a connected operations record? 

Mostly, things stop. Follow-up calls to confirm already-approved statuses go first, usually within a quarter. Cross-system double-checking fades more slowly, over two or three quarters, as the record proves itself. The last shift, closer to a full year, is in planning horizon: teams start asking questions about coverage patterns across quarters rather than only about the current week.

Q: Why do teams keep confirming statuses that are already approved? 

Because confirmation is about confidence, not information. When credentialing, privileging, and scheduling live in separate systems updated on separate timelines, a status on screen may be accurate or may be a few hours stale, and the person making the coverage decision usually cannot tell which. Calling to confirm is the rational response. It stops when the record stops being ambiguous.

Q: Does this require replacing our credentialing or scheduling systems? 

Usually not. Most of the organizations I work with have capable systems already. What they lack is a shared operational record those systems write to and read from, so that a change in one is immediately true in the others. The question worth asking is architectural, about which functions run on a connected record, rather than about which product to buy next.

Q: How long before a team should expect to see the difference? 

The first changes show up inside a quarter and the planning shift takes closer to a year. I would be skeptical of anyone promising faster, because the slow part is not implementation. It is the record accumulating a track record, and that takes as long as it takes.

Q: How does Kimedics help?

Kimedics is the clinician workforce operations platform built by healthcare operators. Scheduling, credentialing, time, and pay share one live operational record, so eligibility and cost are visible at the moment a coverage decision is made rather than confirmed afterward by phone. Health systems and staffing organizations run on the same record, which is what removes the verification step between them.