How to follow up when a medical records request goes unanswered

When a medical records request goes unanswered, the next step is not to start over from memory. Follow up with the exact request date, request method, confirmation number, record types, date range, and any partial response you already received.

In this guide, "unanswered" means you do not yet have a clear status or the records you requested. It is a workflow label, not a legal conclusion. A quiet portal thread could mean the request was not received, is still processing, needs verification, reached the wrong department, or has another explanation that only the record holder can confirm.

This article is about practical record-request follow-up. It is not legal advice, medical advice, privacy compliance advice, or a claim that every delay is improper. The goal is to keep the process organized enough that you can ask clear questions, document what happened, and avoid losing track of the record you need.

If you have not sent the request yet, start with the medical record request template for patients and caregivers. If the bigger issue is tracking several missing records at once, use the missing-record log workflow alongside this follow-up.

First, separate the problem

Before you follow up, name what actually happened. Different problems need different messages.

Situation	What you know so far	Follow-up focus
No acknowledgement	You do not know whether the request was received	Confirm receipt and ask if anything is missing
Acknowledged but delayed	The request is in process	Ask for status, expected date, and any written delay notice
Partial records received	Some files arrived, but not everything requested	List what arrived and what is still missing
Wrong records received	The response does not match the request	Restate the record type and date range
Denial or refusal	The organization says it will not provide some or all records	Ask for the written denial basis and next steps
Wrong organization	The office does not maintain the record	Ask where the request should be directed, if they know

That first classification keeps the message specific. "I still need my records" is easy to mishandle. "I received the lab reports, but not the March 2025 cardiology visit note or ECG report requested on June 8" gives the records team something to work with.

Gather the proof before writing

Open your request history before sending another message. You want the follow-up to include enough detail that nobody has to reconstruct the request from scratch.

Collect:

• A copy of the original request or release form
• The date you sent it
• The method you used: portal, web form, fax, mail, email, phone, or in person
• Confirmation number, fax receipt, portal thread, or staff name
• Patient name and date of birth
• Record types requested
• Date range requested
• Preferred delivery method
• Any identity-verification or authorization steps already completed
• Any files already received
• The record pieces still missing

Keep this in a missing-record log. The log is useful even when the records department is helpful because it lets you track the process without relying on memory.

Use a practical follow-up cadence

For an individual's HIPAA access request for protected health information in a designated record set maintained by or for a covered entity, HHS says the covered entity must act no later than 30 calendar days after receiving the request. If it cannot act within that period, it may use one extension of no more than 30 additional calendar days, but it must give the individual a written reason and completion date during the initial period. The 30 days is an outer limit, not a recommended waiting period.

ONC's current patient guide describes the same general timing and notes that some state or other laws may require faster access. Not every organization, record, transfer route, or request falls under the same rule, so use the dates to ask a precise status question rather than to declare a violation.

This does not mean every delay is a violation or that every situation should be escalated immediately. It does mean dates matter.

A practical cadence:

Timing	Action
Same day	Save the request, proof, and expected follow-up date
Day 7 to 14	Check the portal or message thread for acknowledgement or files
Around day 21	Send a light follow-up if there is no acknowledgement or status
Around day 30	Ask whether the request is complete, delayed, denied, incomplete, or needs more information
When anything arrives	Check it against the request and mark partial items separately

The day 7-to-14 and day 21 steps are an editorial follow-up workflow, not legal deadlines. Adjust them to the provider's stated process and your real appointment deadline.

If an appointment or second opinion is time-sensitive, do not wait until day 30 to ask for status. Make the deadline visible in the message, but avoid overstating urgency if the records are not actually needed soon.

Template: no response yet

Use this when you do not know whether the request was received or opened.

Subject: Follow-up on medical record request sent [date]

Hello,

I am following up on a medical record request sent on [date] for [patient full name, date of birth].

Request details:
- Records requested: [record types]
- Date range requested: [date range]
- Request method: [portal/form/fax/mail/email/phone/in person]
- Confirmation number or proof, if any: [number or proof]
- Preferred delivery method: [portal/email/mail/fax/direct send/pickup]

Could you please confirm whether this request was received, whether any identity verification or authorization step is still needed, and when the records are expected to be available?

Thank you,
[Name]
[Date]

If you are helping someone else, add your relationship or role and ask what authorization the organization requires. Do not assume caregiver access works the same way everywhere.

Template: partial records arrived

Partial records are common. Treat them as progress, not completion.

Subject: Follow-up on partial medical records received for request sent [date]

Hello,

I am following up on a medical record request sent on [date] for [patient full name, date of birth].

Received so far:
- [record received, date range]
- [record received, date range]

Still missing from the original request:
- [missing record type and date range]
- [missing record type and date range]

Request details:
- Request method: [portal/form/fax/mail/email/phone/in person]
- Confirmation number or proof, if any: [number or proof]

Could you please let me know whether the missing records are still processing, need clarification, are maintained by another department or organization, or cannot be provided?

Thank you,
[Name]
[Date]

Do not mark the request "received" in your own tracking system until the response matches the request or you decide to close it with a clear note. If only the lab report arrived and the visit note is still missing, keep the visit note open.

Template: wrong record or wrong date range

Use this when the organization sent something, but it does not match what you asked for.

Subject: Correction request for records received on [date]

Hello,

Thank you for sending records on [date]. I received [what arrived], but the response does not appear to match the request sent on [original request date].

Original request:
- Records requested: [record types]
- Date range requested: [date range]
- Provider, department, or location: [if known]
- Confirmation number or proof, if any: [number or proof]

What I still need:
- [specific missing record]
- [specific missing record]

Could you please confirm whether these records are available from your organization, whether the request should be redirected, or whether you need a corrected form?

Thank you,
[Name]
[Date]

This is especially useful for imaging. A specialist may need both the written imaging report and the image files, not just a portal summary. For that workflow, use how to export medical records for a specialist.

Ask whether the request is in the right place

Sometimes the delay is not a refusal. The request may be sitting with the wrong clinic, wrong department, wrong portal support queue, or wrong health system.

Ask directly:

• "Does your organization maintain this record?"
• "Is this request handled by medical records, health information management, imaging, the lab, or another department?"
• "If this office does not maintain the record, do you know where I should direct the request?"
• "Is there a separate form for imaging files, pathology slides, billing records, or outside records?"
• "Is authorization or identity verification still incomplete?"

HHS access guidance says that if a covered entity does not maintain the requested protected health information but knows where it is maintained, the covered entity must tell the individual where to direct the access request. That does not mean every front-desk employee will know the answer, that the next organization must have the record, or that every request falls under HIPAA. It is a practical reason to ask for the correct destination instead of sending the same request repeatedly.

When to ask for written status

If the request has reached the 30-day point, ask for a written status rather than only a verbal update.

Useful wording:

Could you please provide the current written status of this request?

If the request is delayed, please let me know the reason for the delay and the expected completion date.

If any part of the request is denied, please provide the written denial and the process for asking questions or submitting a complaint.

If records are maintained elsewhere, please let me know where the request should be directed, if known.

HHS explains that when a covered entity denies all or part of an individual's HIPAA access request on a permitted ground, the denial must be in writing. It must include the basis for denial, review rights when applicable, and how to submit a complaint to the covered entity or HHS Office for Civil Rights. A quiet portal is not itself a written denial, so ask the record holder to identify the actual status before labeling it.

Escalation paths to keep in the log

Escalation should be factual and documented. The point is to find the right owner for the request, not to make broad accusations.

Common escalation paths:

• Medical records or health information management department
• Provider office manager or clinic administrator
• Imaging center or radiology records desk
• Lab customer service or records process
• Portal support for technical delivery issues
• Privacy officer or privacy contact for access-rights questions
• HHS Office for Civil Rights complaint process if you believe HIPAA rights were violated
• ONC information-blocking claim process when the facts concern electronic health information and an organization covered by those rules

HHS's current complaint instructions explain how to submit a written complaint about possible noncompliance and say OCR can investigate only entities and allegations within its authority. ONC accepts claims of possible information blocking online, but ONC also says that failing to meet an information-blocking exception does not automatically prove information blocking; the practice is evaluated case by case.

These are not first-step troubleshooting tools for every delayed request. Read the current filing requirements, use the process that matches the facts, and preserve what actually happened rather than turning a delay into a legal conclusion.

Turn follow-up into a reusable record

For every follow-up, capture:

• Date sent
• Person, department, or system contacted
• Message or script used
• Response received
• New confirmation number
• New expected date
• Remaining missing items
• Whether the next step is follow-up, clarification, redirect, or escalation

Then attach or link the actual proof: portal message, PDF, fax receipt, email, phone note, or mailed copy. If you later need to explain the situation to a caregiver, clinician, records department, or advocate, the story is already in order.

This is also where Libby can help. Libby gives you one place to keep the original request, follow-up notes, received files, missing pieces, and timeline context. It does not automatically retrieve every record, guarantee provider timelines, give legal advice, or decide what a record means medically. It helps you keep the process visible so the next step is easier to see.

If the first setup is the hard part, white-glove setup gives you hands-on help turning scattered records, requests, and follow-ups into a usable personal health record. You can also watch the Libby demo to see how the product fits into the workflow.

The short version

When a medical records request goes unanswered:

1. Find the original request and proof.
2. Classify the issue: no response, delayed, partial, wrong record, denial, or wrong organization.
3. Follow up with dates, confirmation numbers, record types, and date ranges.
4. Ask what is missing, who owns the request, and when the next update should happen.
5. Keep every response in a missing-record log.
6. Escalate only with facts, documentation, and conservative language.

You are not trying to win an argument. You are trying to get the right record, keep the timeline straight, and give your next clinician or advocate enough context to help.

Safety boundaries

• This is not legal advice, medical advice, privacy compliance advice, or a substitute for a qualified professional.
• Do not delay urgent care while waiting for records.
• Do not post private health information, confirmation numbers, IDs, or portal screenshots in public forums or public AI chats.
• Do not assume a missing portal item means the record never existed.
• Do not assume Libby can retrieve every record automatically or replace the provider's required process.
• Verify important details against the original record before using them in a medical conversation.

References

• ONC: How to Get It
• HHS: Individuals' Right under HIPAA to Access their Health Information
• HHS: How to File a Health Information Privacy or Security Complaint
• ONC: Information Blocking