Practice Operations
Medical Records Requests and Non-Patient Callers
Attorneys, pharmacies, other offices and insurers call about records every day. How to route medical records requests so nothing sits for months unanswered.
Most medical records requests are not hard. They are just unowned. An attorney’s office calls, a pharmacy calls, another practice calls, and the front desk writes a note that goes into a pile nobody is measured on. One practice described attorney offices calling to follow up on records requests they never got back, some of them sitting for six months.
That is a routing problem before it is a records problem, and it is one of the cheapest front-office gaps to close.
The callers nobody designed the phone tree for
Phone systems are built around patients. Press 1 to schedule, press 2 for a refill. But a meaningful share of inbound calls come from people who are not patients at all:
- Attorneys and records services asking for copies, or asking where a request they sent weeks ago stands.
- Other practices asking for prior records before a new-patient visit, or returning a request you sent them.
- Pharmacies calling about a prescription, a refill authorization or a prior authorization the plan bounced back.
- Insurers and third-party administrators asking for documentation to support a claim or a disability file.
- Family members and caregivers calling on a patient’s behalf.
None of these callers fit the patient menu, so they land wherever the call lands. The front desk is already busy. In a March 2026 MGMA Stat poll of 294 practice leaders, 45% named eligibility and prior authorization as their staff’s most time-consuming phone task and 31% named scheduling (MGMA). Records follow-ups compete with all of that and lose, because they have no queue of their own.
Why “we’ll call you back” turns into six months
A records request has three moving parts: the request itself, the paperwork that makes the release legal, and the delivery. Each one can stall without anyone noticing.
The clock is real. Under HIPAA a practice generally has 30 days to act on a patient’s own request for access to their records, with one extension of up to 30 more days if the patient gets a written explanation and a new date (45 CFR 164.524). A third party asking for records usually needs the patient’s signed authorization, and that authorization has required elements (45 CFR 164.508). When a request arrives with an incomplete form, it waits. When nobody tells the requester the form is incomplete, it waits indefinitely.
That is where most of the follow-up calls come from. The attorney on the line usually has no idea the form came back incomplete, because nobody told them.
What to automate, and what stays with records staff
The work around a records request is logistics, and logistics is what an AI agent working inside athenaOne handles well. Pretty Good AI runs administrative front-office work across 820+ athenaOne APIs, which matters here because the agent can do the work behind the call, not just take a message.
On the inbound call, the agent:
- Asks the first question every records call needs: is this the patient, or someone calling about a patient? A shared family phone number is one of the most common ways a request ends up in the wrong chart.
- Captures who is calling, the organization, a callback number and what they are asking for, and writes it into athenaOne as a patient case document so it lands in a work queue instead of on a sticky note.
- Answers the status question for an existing request (“received, waiting on a signed authorization” or “sent by fax on this date”) without pulling a person off the desk.
- Tells a requester exactly what is missing, so an incomplete authorization gets fixed in days rather than discovered in months.
On the outbound side, the same agent chases what your practice is waiting on. A specialist practice asked whether the system could notice missing labs or imaging on an inbound referral and call the referring office to request them. That is a records chase, and it is the kind of call nobody on staff has time to make twice. For a pain practice, sending records out turned out to be a document job with a fax at the end, because the receiving offices still want faxes.
What stays with people. The agent does not decide whether an authorization is valid, whether a subpoena is enough, or which parts of a chart get released. It does not read or summarize clinical content to answer a caller’s question. Those calls belong to your records staff, your release-of-information vendor or your compliance lead. The agent’s job is to make sure every request reaches them complete, logged and with the requester already told what happens next.
A worked complication: the caller who is not who the chart expects
Third-party callers are an exception to identity verification, and the exception has to be written down. One OB/GYN practice asked for authorized third parties to be allowed to book on a patient’s behalf. A primary care practice wanted name and company captured for service companies calling for patients. A records line needs the same kind of rule.
In practice that looks like this. A caller says they are from a law office and asks whether records were sent. The agent does not confirm anything about the patient. It records the caller’s name, firm, callback number and request reference, checks the open request in athenaOne, and tells the caller only what your practice has approved for a non-patient: that the request is logged and who will follow up. Anything beyond that goes to the records queue with the context attached. The handoff is the point where a person applies judgment. Done well, it replaces a callback with a queue item someone can act on immediately.
Questions to ask before you change anything
- Do records calls have their own route, or do they land in the general queue?
- Can the person answering see the status of an existing request without leaving athenaOne?
- When a request arrives incomplete, who tells the requester, and how fast?
- Who owns the 30-day clock, and is it tracked anywhere a manager can see?
- Do outbound records chases happen on a schedule, or only when someone remembers?
For a closer look at the paperwork side, see how family practices clear records requests and release forms and how a surgery center chases inbound charts before the procedure.
Key Takeaways
- Non-patient callers (attorneys, other practices, pharmacies, insurers, family members) do not fit a patient phone menu, so their requests land in an unowned pile.
- HIPAA generally gives a practice 30 days to act on a patient’s access request, with one 30-day extension in writing, so an untracked request is a compliance exposure as well as a service problem.
- Most follow-up calls come from requesters who were never told their authorization was incomplete; telling them on the first call removes the follow-up.
- An AI agent inside athenaOne can capture the request, log it as a patient case document, answer status questions and run the outbound chase.
- Release decisions, authorization validity and anything involving clinical content stay with records staff and your compliance lead.
Give records requests an owner and a queue of their own, and make the first call end with the requester knowing what happens next. Most of the follow-up calls stop there.
Sources
Ready to See It in Action?
See how Pretty Good AI logs and tracks medical records requests inside athenaOne
Schedule a Demo →Written by Kevin Henrikson