Record retrieval sits in most budgets as paperwork, somewhere near postage and copy fees. In practice? The story's a bit different. In reality, it works more like a supply line, and everything downstream waits on it. A quality score, a risk adjustment submission, an audit response, a legal review, a care decision at the receiving end: none of them happen until the chart arrives.
Most teams learn this in the middle of a season, when the charts stop showing up and there's no time left to fix the reason. The people chasing them are rarely the people who set the budget. What separates a retrieval vendor from a retrieval partner is what happens between requests. A vendor works the list you hand over. A partner keeps the access, the records, and the provider relationships alive, so your next request starts further ahead than the last one did.
This article covers four things: why retrieval got harder, where retrieval programs break down, how the work changes depending on who is asking, and what to ask before you choose help. We draw on HHS guidance on the HIPAA right of access, federal information blocking rules, CAQH research on administrative paperwork, and Bureau of Labor Statistics data on health information staffing as our guidance.
Retrieval holds up everything else. Quality reporting, risk adjustment, audit response, and legal review all wait on the same charts, so spending less on retrieval doesn't remove the cost. It moves it somewhere less visible.
Access gets arranged long before you need it. EHR credentials, security approvals, and named contacts at each practice take weeks to set up, and then they hold for years.
A chart you already pulled should count toward the next request. Ask any partner what happens to a record after delivery. If it disappears, you'll pay to pull the same chart again next season.
The process changes depending on who is requesting the records. Health plans, provider organizations, and outside requesters like law firms work under different rules, timelines, and scope. A single process built to cover all three usually ends up serving none of them well.
Know where every chart came from. When an auditor asks where a document originated and who handled it, you need a straight answer with a date on it.
Three things changed at once. Federal information blocking rules raised the stakes on a slow release or a refused one. The HIPAA right of access puts a clock on responses and limits what you charge, and there's real enforcement history behind it. And the number of requests aimed at any single practice went up sharply, because quality programs, risk adjustment reviews, audits, and outside requesters all scaled up at the same time.
Staffing didn't keep pace. The Bureau of Labor Statistics profile of medical records specialists shows steady growth spread unevenly, with the smallest practices holding the thinnest coverage. One release coordinator at a small practice carries the same legal obligations as a whole department at a health system. When your request sits in that person's queue for three weeks, the problem is rarely indifference. They're outnumbered.
Every practice releases records its own way. Examples include remote access to their EHR, a portal upload, secure email, onsite scanning, or plain fax. Each route often needs its own approval, and approvals move at the speed of legal and security review rather than the speed of your deadline. If you start the access work when the requests start, you may have already already lost the weeks the approvals take.
A chart shows up without the operative note, the outside lab, or the scanned intake form. It counts as retrieved in your tracker, and for every practical purpose downstream, nothing arrived.
You find out later, at coding or abstraction, when going back is a harder conversation than the first ask was. The office on the other end already did the work once, and the second request lands as your mistake rather than theirs. Check the chart against a defined list of what you asked for before you close the request, not after.
Average turnaround makes a program look better than it is, so watch the stragglers instead. How many requests are still open past the deadline, and why?
Those stragglers come from a small number of hard sites, and the same sites show up season after season. Usually someone there is short-staffed rather than stonewalling you, which matters, because the two problems have different fixes. Naming the sites gets you working on the real one, while averaging them into the total produces a number nobody acts on.
Most records still arrive by fax. National exchange networks like TEFCA are growing, and they matter, but fax still carries the majority of the volume in day-to-day retrieval work.
Either way, the same questions come up later. Auditors, coders, and attorneys all ask where a document came from, who opened it, and whether anything is missing. If nobody wrote it down at the time, nobody's reconstructing it a year later.
Sherpas runs retrieval for health plans, provider organizations, and outside requesters. The access work continues between seasons, so your next request starts from a warm relationship instead of a cold one.
Plans pull charts in volume against fixed calendars, for quality reporting, risk adjustment, and audit response. Their real limit usually isn't capacity, it's provider goodwill. Practices get asked too many times by too many people, and a plan running three separate programs often shows up as three separate askers. From the front desk, all three look like the same health plan asking three times.
Completion rates for chart retrieval follow the quality of the relationship more closely than the volume of the outreach, and HEDIS season gets decided by work done months before it starts.
Providers sit on the receiving end and carry the legal obligation. Their job is confirming the requester has the right to ask, sending only what the request covers, meeting the response clock, and not over-sharing. The cost of running release of information in-house often lands on staff already handling coding, chart corrections, and patient requests. Or sometimes it lands on staff whose primary role is patient care. Release work does not always get its own headcount. It gets added to somebody's day.
Law firms, disability reviewers, and life insurance underwriters ask for records under a signed authorization rather than a treatment or payment relationship. These third-party requesters need the complete file on one matter, fast, and they don't need coverage across a whole population.
Providers releasing to this group face the tightest documentation standard, because the right of access and authorization rules decide what leaves the building and what it costs. Retrieval partners serving requesters win on turnaround and on getting the scope right the first time.
No partner scores perfectly on all four, and the point isn't to find one who does. What you're listening for is a straight answer. A partner who tells you where their coverage is thin is worth more than one who claims none of it is.
A high monthly record count tells you little about whether the specific practices holding your charts are reachable today, so ask about the sites you actually need. Coverage where you need it is worth more than scale everywhere else.
If a partner keeps records in one place across audit types, the chart you pulled in March covers a request in September. If records get deleted at delivery, you pay to pull the same chart twice.
Requests reach a practice one of two ways: through a single coordinator, or separately from every program. CAQH research puts a real cost on each manual exchange, and the practice absorbs the duplicated ones. Sending the same office three uncoordinated requests is the fastest way to burn a provider relationship nobody rebuilds quickly.
Ask what a partner produces when an auditor asks where a document came from. Certifications establish important baseline standards, but they’re only part of the picture. What matters day to day is whether every completed release carries a date, a time, a destination, and a status you pull up later without asking anyone to reconstruct it.
Judge your retrieval program between seasons, not during one. Mid-season there's no room to fix anything, and the people who know what's broken are the ones with the least time to tell you.
If you do one thing this month, make a list of the sites that ran late last season and write down why each one did. Most teams find the same handful of names, year after year. The list can be short, and it's where nearly all the pain lives.
Then look at what carried forward: access agreements still valid, contacts still accurate, records still on hand without a new ask. Programs holding those things run a season. Programs starting from zero rebuild every year, and the rebuild eats the time the season needed.
For most operations leaders the question isn't whether to add capacity. It's where the capacity should sit. Internal teams handle steady volume well and strain against seasonal peaks. No two programs are shaped the same way, so the honest answer depends on which peaks hurt and how often they come. A partner working across payer, provider, and requester needs absorbs the peak, holds the access map, and keeps the records on hand - no matter what comes next.
Sherpas takes the retrieval work off your team's plate. Charts already pulled are documented, thus helping reduce the likelihood of a duplicate for the same request again for the next project, and every completed release keeps its date, time, and delivery destination on file. Your people get back to the decisions the records support.
Finding who holds the record, setting up a way to receive it, sending a compliant request, following up until it arrives, checking the file against what you asked for, and delivering it with a note on where it came from. Services stopping at "request sent" leave the hardest part with you, and the follow-up and the missing-pages work is where most of the effort lives.
Days, if there's remote access or an established portal in place. Weeks if there isn't, because the access approval has to happen before the retrieval starts. The number worth watching is how many requests are still open past the deadline, not the average across all of them.
Yes, under a business associate agreement with defined scope and safeguards. The questions worth asking a partner are more specific. How do they confirm the requester has the right to ask? How do they keep from sending more than the request covers? And what do they keep on file showing who handled each document?
Four things, in order of how often they show up. No established way into the site. An out-of-date provider roster. Requests arriving separately from several programs, so the practice pushes them down the pile. And incomplete first pulls forcing a second ask. More phone calls fix none of the four, and they wear down a relationship you'll need next season.
Inside your organization, splitting them is normal. It's rarely ideal, and it happens anyway. The bigger problem starts when those separate payer teams generate overlapping or duplicate chart requests. When one health plan sends three requests through three separate teams, the office sees three uncoordinated askers, and the next request from any of them moves down the pile.
What happens between requests. A vendor works a list on demand. A partner keeps the access map current, holds on to the records, maintains the provider relationships, and shows up to the next request with some of the work already done.
Have more questions?
Software, full-service, or both. Sherpas handles the hard work so your team can focus on what matters.
