How to document partial medical records when only some files arrive

In this guide, "partial medical records" means that files arrived but the response does not cover every item in your request. That is different from ONC's use of "partial record" for a deliberately scoped request for only certain information. Maybe the portal delivered the lab report but not the visit note. Maybe the imaging report arrived but not the image files. Maybe the hospital sent the discharge summary but not the procedure report, medication list, or related labs.

The mistake is marking the request "done" just because something arrived. A better workflow is to document what you received, compare it against what you requested, name exactly what is still missing, and keep proof of the follow-up.

This is record-organization guidance, not legal advice, medical advice, privacy compliance advice, or a claim that every partial response is improper. The goal is to make the next request precise enough that you, a caregiver, a records department, or a clinician can see the remaining gap quickly.

If you are still trying to get the first request out, start with the medical record request template for patients and caregivers. If the request has gone quiet, use how to follow up when a medical records request goes unanswered. This article focuses on the narrower moment when some records arrived and you need to document what is missing.

Start with the original request

Open the exact request before judging whether the response is complete.

You need:

• Request date
• Request method: portal, form, fax, mail, phone, email, or in person
• Confirmation number, fax receipt, portal thread, or staff name
• Source organization
• Provider, department, or location, if known
• Record types requested
• Date range requested
• Preferred format and delivery path
• Any authorization or identity-verification steps completed

ONC's current Get It guide says health records can be hundreds of pages long and uses "partial record" for an intentionally selected subset, such as allergies, medications, immunizations, one visit note, test results, or X-rays. In this workflow, the original request is the comparison baseline: it shows whether the response matches the subset or full record you actually requested.

Use a received-vs-missing table

Use one row per requested item, not one row per organization. If one hospital sent three files and missed two, make that visible.

Requested item	Date range	Source organization	Received?	File name or proof	Still missing	Next action
Cardiology visit note	2025-03-12	Northside Cardiology	No	Request confirmation 88391	Visit note	Follow up with HIM
ECG report	2025-03-12	Northside Cardiology	Yes	2025-03-12_northside_ecg-report.pdf	Nothing	Add to timeline
Lab report	2025-03-01 to 2025-03-31	Northside Cardiology	Partial	2025-03-12_labcorp_lipid-panel.pdf	CBC and CMP	Ask if outside lab has rest
MRI report	2024-11-09	Valley Imaging	Yes	2024-11-09_valley_lumbar-mri-report.pdf	Image files	Ask imaging desk

Keep the statuses simple:

• Requested
• Acknowledged
• Partial received
• Received
• Wrong record received
• Duplicate only
• Needs clarification
• Redirected
• Denied
• Closed with note

"Closed with note" is useful when you decide not to keep chasing a record, but you still want future-you to know why.

A missing item is not automatically a legal denial. It may still be processing, sit with another department, fall outside the requested date range, or not be maintained by that organization. If a covered entity denies access to part of an individual's HIPAA access request, HHS says the denial must be in writing and, to the extent possible, the entity must provide access to the other requested protected health information after excluding the denied portion. Record the office's actual response instead of relabeling every partial delivery as "denied."

Separate received files from missing items

Do not hide missing items inside a general note. Split them out.

Instead of:

• "Records came, maybe incomplete."

Write:

• "Received: lab report dated May 4, 2026 from Labcorp."
• "Still missing: primary care visit note dated May 4, 2026 and medication list reviewed at that visit."
• "Next action: follow up with primary care records department; original request sent June 10, confirmation #1293."

This makes the next message straightforward. It also keeps partial progress from disappearing into a folder full of PDFs.

Check whether the date range matches

Partial responses often look complete until you check the date range.

Compare:

• Date range requested
• Dates on every received file
• Dates mentioned inside the file
• Collection date for labs
• Service date for visits, procedures, imaging, hospital stays, or billing
• Report date when it differs from service date

Example:

What you asked for	What arrived	Gap
All primary care notes from Jan 2024 through Jun 2026	Notes from Jan 2025 through Jun 2026	2024 notes missing
MRI report and image files from Mar 12, 2024	Written MRI report only	Image files missing
Hospital stay beginning Apr 9, 2025	Discharge summary only	ED note, medication list, labs, and imaging reports may still be missing
Ferritin, CBC, and iron studies from 2022 through 2026	Ferritin only	CBC and iron studies missing

When the date range is unclear, write "date range unclear" instead of guessing. If you only know the month, say that. Do not invent exact dates to make the log look cleaner.

Record the source organization

The source organization is the place that likely created or maintains the record. It may not be the same as the portal where you found a summary.

Examples:

• Hospital that created a discharge summary
• Imaging center that performed a scan
• Radiology group that wrote the report
• Lab that processed the test
• Specialist office that wrote the consult note
• Primary care office that imported an outside record
• Pharmacy that administered a vaccine

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 staff member will know the answer immediately, but it is a practical reason to ask, "Do you maintain this record, and if not, where should I direct the request?"

With limited exceptions, the access right applies to existing protected health information in designated record sets maintained by or for a covered entity. HHS also says the entity is not required to create new explanatory material or analysis that does not already exist. If the requested summary was never created, log that response separately from "record exists but was not delivered," and confirm the status with the record holder.

Name files so the gap stays visible

File names should preserve the basics: date, source, record type, and status when needed.

Use:

YYYY-MM-DD_source_record-type.pdf

Examples:

2026-05-04_labcorp_lipid-panel.pdf
2026-05-04_primary-care_visit-note-missing.txt
2024-11-09_valley-imaging_lumbar-mri-report.pdf
2024-11-09_valley-imaging_lumbar-mri-images-requested.txt
2025-04-09_general-hospital_discharge-summary.pdf
2025-04-09_general-hospital_hospital-labs-missing.txt

For missing items, a small note file can be useful. It does not replace the actual record. It tells you what you are still waiting for, when you requested it, and what proof you have.

If the missing item is a lab trend, keep units and reference ranges attached to the original report. For lab-heavy records, use how to organize years of blood test results.

Save follow-up proof next to the record

Partial-record follow-up is much easier when the proof lives near the file.

Save:

• Original request text
• Release form or access request form
• Confirmation number
• Portal message thread
• Fax confirmation
• Email receipt
• Mailed copy or tracking number
• Phone note with date, time, department, and staff name if provided
• Written response explaining a delay, denial, redirect, or clarification request

This is not about building a legal case by default. It is about avoiding the common loop where every follow-up starts from scratch.

Follow-up template for partial records

Use this when some files arrived but the response does not match the original request.

Subject: Follow-up on partial 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].

Original request:
- Source organization: [organization]
- Records requested: [record types]
- Date range requested: [date range]
- Request method: [portal/form/fax/mail/email/phone/in person]
- Confirmation number or proof: [number or proof]

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

Still missing:
- [missing record type and date range]
- [missing record type and date range]

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

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

Thank you,
[Name]
[Date]

Keep the message factual. "Here is what arrived; here is what is still missing" usually works better than a broad complaint.

Do not overinterpret partial records

Partial records can be misleading because they show only part of the story.

Be careful with:

• A lab result without the visit note explaining why it was ordered
• An imaging report without the prior comparison study
• A discharge summary without medication reconciliation
• A specialist assessment without the referral question
• A portal problem list without the source note
• Duplicate reports that make it look like there are more records than actually arrived

ONC's Check It guide tells people to review whether a health record is complete, correct, and up to date. In this workflow, keep two questions separate: whether the delivered file set matches the request, and whether information inside a delivered record is correct. A missing file belongs in the request log; a suspected error inside a record belongs in the provider's correction process.

Do not change medication, treatment, urgency, or care plans based only on a partial file set, checklist, or AI answer. Use the partial record to ask better questions and to request the missing context.

What to do when the partial response is enough

Sometimes a partial response is enough for the immediate job.

Examples:

• The specialist only asked for the written imaging report, not image files.
• The new primary care doctor only needs the last annual visit and medication list for intake.
• You needed one lab report for a timeline and it arrived.
• You found the discharge summary and no longer need every hospital lab for the current visit.

If you stop chasing the missing pieces, document that decision:

Closed with note: Received the written MRI report needed for the July 2026 specialist visit. Image files not requested further because the specialist office said the written report is enough for this appointment.

That way, a future specialist packet or second opinion can reopen the missing item intentionally instead of relying on memory.

What Libby helps with

Libby helps with the organization layer around partial records. You can keep the original request, received files, missing items, source organization, date range, follow-up proof, and next action in one place.

That can mean:

• A received-vs-missing table for each request
• Source-aware file organization
• A missing-record log that distinguishes partial from complete
• A timeline that shows where each file fits
• A specialist or new-doctor packet that does not hide missing context
• Better AI context, with human and clinician review still required

Libby does not automatically retrieve every record, guarantee provider timelines, give legal advice, decide what a record means medically, or replace a records department's required process.

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

Safety boundaries

• This is not legal advice, medical advice, privacy compliance advice, or insurance advice.
• Do not delay urgent care while waiting for missing records.
• HHS notes that HIPAA generally does not protect information voluntarily shared online or health data stored in personal apps unless the app is provided by a covered entity or its business associate. Do not put private health information, confirmation numbers, IDs, or portal screenshots into public forums or public AI chats.
• Do not assume a partial response proves that the missing record does not exist.
• Do not assume Libby can retrieve records automatically or bypass a provider's required process.
• Verify important details against the original source record before relying on them.

References

• ONC: How to Get It
• ONC: How to Check It
• HHS: Individuals' Right under HIPAA to Access their Health Information
• HHS: Protecting Health Information on a Personal Cell Phone or Tablet