Guide

The export you should test before you need it

Summary

Run your EHR's export function now, before you need it. The information-blocking rule bars your vendor from unreasonably interfering with your access to the electronic health information you and your patients created, but a right you have never exercised is a right you do not actually know the shape of. Export a real chart, check the format, the completeness, and who can trigger the process — then fix whatever breaks while it costs nothing.

By Gale Editorial · Updated 2026-07-27. Every figure cited to a dated source. How we write.

How do I get my records out of an EHR?

Ask your vendor for an export, and if the answer is delay, a paywall unrelated to actual cost, or a format nobody can open, you may be looking at information blocking. Under the 21st Century Cures Act, an EHR vendor and its healthcare-provider users are both "actors" who may not unreasonably interfere with access to, exchange of, or use of electronic health information, subject to eight defined exceptions 1. Most systems expose some export path — bulk or per-patient, usually rendered as C-CDA, CSV, or PDF.

The gap that catches solo practices is not the legal right; it is never having exercised it. A menu option that has sat untouched for years may not do what the vendor's marketing page says. The only way to know is to run it.

What the information-blocking rule actually covers

The rule reaches practices, not just vendors — a clinician who refuses to share a record for reasons the rule does not recognize can be an actor engaging in information blocking too 1. The eight exceptions are narrow and specific: preventing patient harm, protecting privacy, securing the system, technical infeasibility, reasonable content-and-manner limits, reasonable fees, licensing terms, and a health-IT-performance exception for planned maintenance. "We've always done it this way" is not one of them.

When a vendor cites an exception to slow-walk an export, ask which one and hold them to its actual terms — infeasibility and content-and-manner are the two most often stretched past their real scope.

Run the test now, not during a crisis

Schedule an export test on a fixed cadence — annually is reasonable for most solo practices — rather than waiting for the day you actually need the file. Export one full chart and one bulk sample, then check three things: the record count matches what you expect, the file opens in a viewer you do not depend on your vendor for, and the clinical content is complete rather than a truncated summary.

Write down who in your practice has the administrative right to trigger an export and how. A solo clinician is often the only person who knows this, which means the knowledge dies with a bad week unless it is documented somewhere outside the EHR itself — a password manager entry or a printed instruction sheet in a locked drawer, not a memory only you carry.

Time the test too. A vendor's export tool that quietly times out on a large chart, or that emails a download link which expires before you get to it, is a problem you want to discover on a slow Tuesday, not the week a subpoena arrives.

Formats you'll get: C-CDA, CSV, PDF

Each format solves a different problem, and c-cda, csv, pdf are not interchangeable despite often being offered from the same button. A C-CDA is a structured clinical document meant for exchange with another certified system — useful for a receiving EHR, less useful for a human reading on a screen. A CSV is a flat data dump, good for a spreadsheet audit of what you have but stripped of clinical narrative. A PDF is the most human-readable and the least reusable by another system.

If your export test only produces one of the three, ask whether the others exist. A closure or a malpractice-carrier request may specify a format you have never actually generated.

Your vendor is a business associate — the contract should say export is a live right

An EHR vendor that creates, receives, maintains, or transmits protected health information on your behalf is a business associate, and the agreement governing that relationship has to address the arrangement, not just breach notification 2. Read your business associate agreement for what it says about data portability and export on termination — some vendor contracts are silent, which leaves you negotiating access after the relationship has already soured.

If you are choosing a new system, ask about its participation in national exchange networks before you sign. TEFCA establishes a national floor for network-to-network exchange through Qualified Health Information Networks, and a vendor's posture toward that floor is a reasonable proxy for how seriously it takes getting data out later 3.

A missing export clause is worth raising with a vendor before signing, not after. Ask specifically what happens to your data on termination, whether export triggers a fee, and how long the vendor retains a copy once you leave — three questions a sales call rarely answers unprompted.

The right of access sets a floor independent of your export button

A patient's own right to their records is a separate legal track from your practice-level export, and it can be the one that actually gets tested first. Under the HIPAA right of access, a patient may inspect and obtain a copy of their record within 30 days, with one 30-day extension, in the form and format they request where you can readily produce it, for a reasonable cost-based fee 4. If your EHR's patient-facing export cannot hit that timeline, you are exposed on access grounds even if your practice-level bulk export works fine.

Build the habit of testing both paths — the one you use for yourself and the one a patient triggers — because they sometimes run through different parts of the same system.

When you'll actually need this: migration, closure, a departure, a dispute

The moments this matters rarely come with much notice. The ehr migration to a new system is the obvious one — you cannot evaluate a replacement's import tooling until you know what your export actually looks like. Leaving employment at a group practice raises a parallel question about who controls the record and how it travels with you. Chart ownership disputes, a request tied to when a patient dies, and a payer or malpractice-carrier audit can all land on your desk with a short deadline attached.

Each of those situations goes faster when the export has already been tested once, calmly, with nothing riding on the outcome. Retention obligations under §164.316 and your state's schedule keep running underneath all of this regardless of which system holds the file 5.

Common questions

Not without fitting one of eight narrow exceptions in the information-blocking rule — patient harm, privacy, security, infeasibility, content-and-manner limits, fees, licensing, or health-IT performance. A vendor citing generic business reasons, or simply not building a working export tool, does not meet that bar. Ask which specific exception applies and hold the answer to its actual, defined scope rather than accepting a vague refusal.

Test all the formats your system offers rather than assuming one covers every use. C-CDA suits exchange with another certified system, CSV suits a data audit, and PDF suits human reading and printing. A closure, an audit, or a new vendor's import tool may specify a format you have never actually generated, so knowing what each one produces before you need it saves time under pressure.

Annually is a reasonable cadence for most solo practices, treated the same way you would treat a backup restore test. Export a full chart and a bulk sample, confirm the record count and clinical content are complete, and confirm the file opens outside your vendor's own viewer. Document who has the administrative access to trigger it, since that knowledge often sits with one person.

Both. Clinicians are actors under the rule alongside health IT developers, so a practice that refuses to share electronic health information for a reason outside the eight recognized exceptions can itself be engaging in information blocking. The rule was written to reach the whole chain that can obstruct access, exchange, or use of the record, not just the software company.

No — they are separate tracks that can behave differently inside the same system. Your practice-level bulk export is an operational tool; a patient's right-of-access request carries its own 30-day timeline, format duty, and cost-based fee rule. Test both, because a system that exports cleanly for you may not hit the access-right timeline for a patient request routed through a different feature.

Run your practice on Gale

The software is free. Gale earns one flat 3.5% all-in per paid transaction — only on transactions that actually pay. No subscription, no setup fee, no network cut.

Start or manage a practice →

References

  1. 1.Office of the National Coordinator / ASTP (2026). Information Blocking. HealthIT.gov. linkThat the 21st Century Cures Act prohibits practices interfering with access, exchange, or use of electronic health information, subject to eight defined exceptions, and that clinicians are actors under the rule.
  2. 2.HHS Office for Civil Rights (2026). Business Associates. U.S. Department of Health and Human Services. linkThat an EHR vendor creating, receiving, maintaining, or transmitting PHI on a practice's behalf is a business associate requiring a BAA covering the relationship.
  3. 3.Office of the National Coordinator / ASTP (2026). TEFCA — Office of the National Coordinator for Health Information Technology. HealthIT.gov. linkThat TEFCA establishes the national floor for network-to-network health information exchange via QHINs, relevant to evaluating a vendor's exchange posture.
  4. 4.HHS Office for Civil Rights (2026). Individuals' Right under HIPAA to Access their Health Information. U.S. Department of Health and Human Services. linkThat patients have a right to inspect and obtain copies of their records within 30 days (one 30-day extension), in the form and format requested where producible, for a reasonable cost-based fee.
  5. 5.Office of the Federal Register (2026). 45 CFR Part 164 — Security and Privacy. eCFR. linkThe §164.316 documentation-retention rule that continues to apply regardless of which system currently holds the exported file.

https://www.gale.care/for-providers/rr-ehr-export-portability · 5 sources. Competitor details are cited to dated public sources and maintained as they change; figures are estimates, not commitments. Synthetic demonstration.

Findability, by specialty

How practices like yours get found in local search and AI answers — the honest playbook, per specialty.

SEO for private practices · SEO for AI search / answer engines (all verticals)