Why medical records are still scattered when portals exist

Medical records are still scattered because a patient portal is an access surface for a particular organization's systems, not a universal personal health record. Exchange rules and networks can make information available or movable without producing one verified, deduplicated timeline for you.

The useful mental model has four layers:

1. Source organization: who maintains the record
2. Access surface: which portal or app shows some of it
3. Exchange path: how some information may move
4. Personal record: what you index, including its preservation and provenance-check status

Confusing those layers creates the false feeling that one login should equal one complete chart.

Current-state note: This guide was verified on July 10, 2026. Portal features, access rules, information-blocking regulations, TEFCA services, and organization workflows can change. Check current instructions at each source.

The short answer

Use portals, but do not use the number of portal logins as your record inventory. Build a source map instead.

For every organization that may maintain part of your history, record:

• What record groups and date ranges you expect
• Which portal, app, or request route provides access
• What is visible now
• Which provided file or faithful scan you preserved
• What you verified against the source
• What remains missing or uncertain
• What your next action is

Download the medical-record source map CSV. The work is bounded when every known source has a status and every unresolved gap has either a next action or an explicit decision to leave it open. It is not bounded by reaching a certain page count or assuming a large export is complete.

The fragmentation is measurable

The problem is not merely that some people forgot a password. In its July 2025 analysis of 2024 survey data, ASTP/ONC reported that 59% of individuals nationally had multiple online medical records or patient portals. Only 7% reported using a portal-organizing app to combine information from different portals or online records in one place.

Those two percentages are not complements. They describe different survey measures. Together, they show why digital access can grow while the burden of assembling a cross-organization history remains.

The same data brief describes online records or portals associated with primary-care offices, other health care providers, insurers, clinical laboratories, pharmacies, and hospitals. Each relationship can be useful. None of them, by itself, establishes that the others' records are present.

Layer 1: the source organization maintains the record

Start with organizations, not apps.

A primary-care practice, specialist group, hospital, independent imaging center, clinical laboratory, pharmacy, health plan, or prior health system may maintain different information. One organization can also have multiple departments, archives, or systems that do not appear identically in its patient portal.

For each source, ask three concrete questions:

1. What could this source reasonably hold? Name the record group and date range rather than writing "everything."
2. What can I see or download now? Record the portal or app and the date you checked it.
3. What requires another path? Identify the current records-office, access-request, or support route.

Keep original exports and reports with the source organization, document type, and date attached. A copied value, screenshot, or personal summary can be useful, but it should not silently replace the source file.

Layer 2: a portal or app exposes a view

A portal can make appointments, messages, notes, results, bills, medicines, and downloads easier to reach. Its contents still depend on the organization, system configuration, date range, record type, and available patient-facing functions.

ONC's current patient-access guide recommends checking the provider portal first and says some health information may be available there. It also gives other routes when the needed information is not visible, including the provider website, phone, administrative staff, or a record-request process.

That creates a practical rule:

Access visible is a status, not a completeness judgment.

Record what you can actually see. Do not convert "not visible here" into "does not exist," and do not convert "visible here" into "preserved in my record." Download important source files in the form the organization provides when you can, then log the download date and location.

Layer 3: exchange paths move some information

Provider-to-provider exchange, health information networks, APIs, direct transmission, and patient-directed access can reduce manual work. They do not all perform the same job.

Exchange has its own states:

• A request was made
• A source was found
• A response was returned
• A destination received something
• A person or system matched it to the right patient
• Particular documents or data elements were included
• The receiving system displayed or imported them
• A clinician reviewed them

Do not collapse those states into "the records transferred." A successful exchange can still return a scoped result, preserve duplicate entries, omit an unavailable source, or leave clinical review unknown.

For a patient-facing explanation of one nationwide exchange path, use TEFCA and medical-record access in plain English. That guide owns identity proofing, participating services, requests, responses, and stopping rules.

Layer 4: a personal record organizes what you obtained

A patient-controlled longitudinal record is the organization layer, whether information came through a portal, exchange, paper record, or another route and whether or not a copy has been preserved. It keeps source files when available, extracted facts, summaries, timelines, preservation status, provenance-check status, and gaps connected without pretending they are interchangeable.

The useful output is not one giant merged PDF. It is a record that can answer:

• Where did this item come from?
• What date or date range does it cover?
• Is this the original source file, a personal extraction, or a summary?
• When was a copy preserved or the source last checked?
• Is it verified against the source?
• What conflicts or gaps remain visible?
• Which smaller packet is appropriate for the next task?

That last question matters. A personal archive, a new-doctor summary, a specialist packet, and an AI context packet are different artifacts. Build each from source-linked items, preserve source files when available, and keep preservation and provenance-check status explicit rather than treating one homemade document as the complete chart.

Five status flags that should never become one checkmark

Track these five flags separately for every important record group. They are not one completion ladder: access visibility, copy preservation, and organization do not depend on every earlier flag. There is one logical validation rule: provenance checked can be yes only when source identified is yes, because checking provenance includes matching the record to a known organization.

1. Source identified: a named organization is confirmed as the source for the record group; keep candidates unknown or no and explain the uncertainty.
2. Access visible: you can currently view it through a portal, app, paper record, or another source surface.
3. Copy preserved: you saved the provided file or a faithful scan and recorded when.
4. Provenance checked: after identifying the source, you checked patient, organization, dates, document type, and obvious file gaps against it.
5. Organized: the item is indexed in your longitudinal record with its provenance-check status and gaps still visible.

A mailed paper report that is still in hand has access visible marked yes. After a faithful scan, copy preserved can also be yes; neither flag depends on the other. If the paper is later lost and no current source surface exposes it, access visible becomes no even though the preserved scan remains. An exchanged result can be visible in a second portal while copy preserved remains no. A spreadsheet row can be organized while provenance checked remains no, as long as that uncertainty is not hidden. If the source organization is still unknown, provenance checked must remain no.

Keep the flags explicit. That makes uncertainty actionable instead of invisible.

Why access rights do not automatically produce one chart

Three often-confused mechanisms address different problems.

HIPAA defines a scoped access right

HHS explains that HIPAA-covered entities generally must provide individuals, upon request and with limited exceptions, access to protected health information in designated record sets maintained by or for them. HHS says those sets can include medical and billing records, health-plan record systems, and other records used to make decisions about individuals.

That right is broader than a portal screen. HHS says it can apply whether the information is in paper or electronic systems, onsite, remote, or archived.

It is still scoped. Not every organization is a HIPAA-covered entity, not every held file is necessarily in a designated record set, and limited grounds for denial exist. The article is not legal advice.

HHS and ONC also distinguish patient access from treatment exchange. ONC says the HIPAA Privacy Rule permits health care providers to share information for treatment without requiring the patient to submit an individual access request. That permission does not guarantee that every provider will automatically locate, send, match, import, or review every source record.

When you need records that are not visible, use the medical-record request template for patients and caregivers for a source-specific request rather than assuming another portal search will surface them.

Information blocking addresses conduct

ONC describes information blocking as a practice likely to interfere with, prevent, or materially discourage access, exchange, or use of electronic health information, except as required by law or when an applicable exception is met. ONC identifies privacy and security among the exception categories.

That is not a rule that every absent item, portal limitation, delay, mismatch, or partial response is information blocking. Actor status, facts, knowledge, law, and exceptions matter. Keep a factual log before drawing a conclusion about why a record is missing.

TEFCA provides exchange infrastructure

ONC describes TEFCA as a nationwide framework and network-of-networks for health information sharing. That belongs in the exchange layer. It does not turn every source into one patient-facing screen or prove that a particular response is complete, matched correctly, normalized, or clinically reconciled.

Access rights, conduct rules, and exchange infrastructure can all improve availability. The organization layer still has to preserve provenance, expose gaps, and shape information for a specific use.

Build your source map in one pass

Open the CSV and create one row per source organization and record group. Do not create one row per portal login; one portal can expose several record groups, and one organization can require more than one access route.

Step 1: list known sources

Start with places that created, received, or maintained information during the period you care about. Use statements, referral paperwork, old appointment notices, and existing reports to discover source names, but verify the current organization and request route before sending private information.

Step 2: define expected scope

Write a record group and date range:

• Visit notes, January 2023 through December 2024
• Laboratory reports, 2025
• Imaging reports from one episode
• Hospital discharge documents from one encounter

These are scope examples, not a universal clinical checklist. Use the receiving clinician's or office's instructions when preparing a care handoff.

Step 3: check the access surface

Record the portal or app, last check date, visible date range, and export format. If only a summary is visible, say so. If a document opens but you have not saved the provided file or a faithful scan, keep copy preserved false.

Step 4: preserve and verify

Keep the original file. Check the patient, source organization, dates, document type, page count when available, and obvious truncation or duplication. Mark provenance checked yes only when source identified is yes and those checks are complete. Verification here means checking provenance and file integrity, not deciding that the clinical content is correct.

Step 5: log the gap and next action

If something expected is absent, describe the gap without guessing the cause. Then choose a next action: use the current request process, confirm the source, ask the receiving office what it already has, or leave the gap open with a reason.

For repeated follow-up states and an evidence log, use how to keep a missing-record log when portals are incomplete.

Step 6: organize for the next job

Index items by source, date, and type. Keep copy preserved and provenance checked as separate flags: an item can be organized while either flag is no only if those statuses and the item's gaps remain visible. Then create a smaller artifact for the immediate task. For example, repeated lab results need units, reference ranges, methods, and source context preserved; use how to organize years of blood-test results rather than copying values into an unlabeled chart.

A worked source-map example

Suppose one person has a primary-care portal, a specialist portal, an independent laboratory portal, and a hospital account.

Their source map might show:

• Primary-care notes: visible for 2024-2026, copy preserved, provenance checked, organized
• Older primary-care notes: not visible, request route confirmed, request not yet sent
• Specialist reports: visible, copy preserved, provenance checked, not yet organized
• Laboratory reports: visible as results, original PDF availability unknown, next action recorded
• Hospital discharge documents: copy preserved, page sequence checked, organized
• Diagnostic images: expected from a separate imaging source, source not yet confirmed

The map does not say the record is complete. It says exactly what is known, what is preserved, and what happens next. That is more useful than four successful logins and a folder named "medical stuff."

The stopping rule

Stop the first pass when:

• Every known source and important record group has a row
• Access-visible and copy-preserved are separate fields
• Preserved files have source, date, and document type
• Important files have a source-verification status
• Every known gap has a next action or an explicit decision to leave it open
• The next task has a focused artifact built from those sources

Restart the map when a new organization, record group, date range, conflicting item, or use case appears. Do not wait for a mythical state in which every system agrees that your lifetime chart is complete.

Where Libby fits

Libby belongs in the organization layer. It can help keep files you obtain, source context, timelines, summaries, and unresolved gaps together so the next conversation starts with better evidence.

This page does not claim that Libby:

• Connects to every portal or EHR
• Requests, retrieves, or transfers every record automatically
• Operates a health information exchange
• Verifies clinical accuracy or reconciles conflicting records
• Proves a record set is complete
• Coordinates care or replaces a clinician

If building the first organized record is the hard part, white-glove setup provides hands-on help with files you bring and the product workflow. It is record organization and product guidance, not medical, legal, privacy, security, or clinical advice.

Questions people ask about scattered medical records

Why does one health system have more than one portal?

An organization can use different systems, acquired practices, departments, archives, laboratories, or patient-facing products. Ask the organization which current surface and records process covers the date range and record type you need.

Does a portal contain my complete medical record?

Do not assume it does. ONC describes the portal as a useful first place to check and gives other request routes when needed information is not available there. HHS describes a broader, scoped access right for PHI in designated record sets maintained by or for covered entities.

If my doctors exchange records, do I still need my own copy?

Provider exchange can reduce work, but you may not know which sources, dates, documents, or data elements moved or whether they were reviewed. A source map and preserved original files give you a traceable personal layer without replacing provider systems.

Is every missing portal item information blocking?

No. Information blocking is a specific regulatory concept with defined actors, facts, knowledge standards, applicable law, and exceptions. Record the facts and use current official guidance before making a legal or regulatory conclusion.

Will TEFCA create one national patient portal?

ONC describes TEFCA as a nationwide exchange framework and network-of-networks, not as one universal patient portal. Available patient-access services and results depend on current participants, identity proofing, matching, source availability, supported data, and response content.

What is the first thing I should do?

List source organizations and record groups. Then mark what is visible, preserved, provenance checked, organized, and missing. That source map turns a vague feeling of fragmentation into bounded work.

Safety boundaries

This guide is about record organization and access preparation. It is not medical, legal, privacy, security, insurance, or interoperability advice.

• Do not delay urgent care while waiting for records.
• Do not assume a portal, export, exchange response, or personal archive is complete or current.
• Do not guess why an item is absent or label a situation unlawful without qualified review.
• Do not send identity documents or health information through an unconfirmed destination.
• Do not merge conflicting dates, results, medicines, allergies, or diagnoses without preserving each source.
• Do not change medicines, supplements, testing, or treatment based on an app, portal, personal record, or AI answer.
• Discuss medical decisions and important record discrepancies with qualified professionals.

If symptoms may be urgent, contact a clinician, urgent care, emergency services, or your local emergency number instead of waiting to finish the record.

References

• ASTP/ONC: Individuals' Access and Use of Patient Portals and Smartphone Health Apps, 2024
• ONC: How to Get It
• HHS: Individuals' Right under HIPAA to Access their Health Information
• ONC: Information Blocking Enforcement Alert
• ONC: Advancing Nationwide Interoperability with TEFCA