What it is
The Patient Data Export and Portability Checklist is a practical guide for getting your data out of an EHR — whether you're switching systems, building an archive, or honoring a patient's right-of-access request. Its premise is blunt: exports are harder than vendors admit. They are often partial, they lock discrete data inside rendered PDFs, and they quietly drop attachments and history. The checklist helps you demand the right formats, validate completeness, handle retention and legal obligations, and avoid being held hostage by your old system at the worst possible moment.
The document is organized around right-of-access and legal obligations, format and structure, the specific data objects to export and validate, completeness validation, and the questions to ask the outgoing vendor. On the legal side it pushes you to confirm your contractual data-export and data-return rights, formats, fees, and timelines before signing or terminating, to honor the HIPAA right of access by delivering records in the form a patient requests when readily producible, and to determine your medical-record retention obligations — which under state law often exceed federal minimums — before deleting anything.
On the technical side it insists you demand structured, discrete data — C-CDA, FHIR, or a database extract — rather than just rendered PDFs, and that you map code systems (ICD-10, CPT, LOINC, RxNorm, SNOMED) so coded data survives the move. It makes you export documents and attachments in usable formats with the metadata that links them to the right patient and encounter, and capture audit trails and version history where legally required. The vendor questions at the end — will you provide a full discrete-data export or only PDFs, are attachments and audit logs included, what are the fees and turnaround at termination, and how far back does the export reach — are designed to surface lock-in before it traps you.
What it's used for
Practices reach for this checklist at the highest-stakes data moments — choosing a vendor (to verify exit rights before entry), terminating one, archiving a legacy system, or fulfilling a patient's right-of-access request. Its job is to make sure the data that leaves is complete, usable, and legally compliant.
- ✓ Confirming contractual data-export and data-return rights, formats, fees, and timelines before signing a new EHR or terminating an old one — so you're never surprised at exit.
- ✓ Demanding structured, discrete data (C-CDA / FHIR / database extract) instead of rendered PDFs, so the exported data stays usable in the next system.
- ✓ Mapping code systems (ICD-10, CPT, LOINC, RxNorm, SNOMED) so coded clinical data survives the export rather than collapsing into text.
- ✓ Honoring the HIPAA right of access for patient requests — delivering records in the requested form and format when readily producible, within the required timeframe.
- ✓ Determining medical-record retention obligations, including stricter rules for minors and special-category data like behavioral health and substance use, before deleting anything.
- ✓ Validating completeness — confirming attachments, scanned documents, imaging, and audit logs are included and that the export reaches as far back as the record requires.
- ✓ Interrogating the outgoing vendor with pointed questions to expose partial exports, hidden fees, and history limits before they become a crisis.
Who uses it
Data export sits at the crossroads of health information management, IT, compliance, and the practice's leadership, and the checklist is built to coordinate all of them around a complete, lawful export.
Context & good to know
Data portability is where EHR lock-in becomes concrete. A vendor that makes it easy to enter and painful to leave can extract significant leverage at renewal or termination, and the most common form of that leverage is a degraded export — one that delivers PDFs instead of discrete data, omits attachments and audit logs, charges steep fees, or only reaches back a limited number of years. The checklist's emphasis on confirming export rights before signing is the single most effective defense, because the time to negotiate a clean exit is before you're committed, not when you're already trying to leave.
The legal layer is as important as the technical one. The HIPAA right of access obligates covered entities to provide patients their records in the form and format they request when readily producible, within required timeframes, which means the EHR's export capabilities directly affect your ability to comply. Retention obligations cut the other way — state laws often require keeping records for years beyond federal minimums, and minors' records and special-category data such as behavioral health and substance use carry stricter rules — so the checklist insists you determine these obligations before deleting anything from a system you're leaving.
Technically, the difference between a usable export and a useless one is whether discrete data survives. Demanding C-CDA, FHIR, or a database extract preserves the coded values — diagnoses in ICD-10, procedures in CPT, labs in LOINC, medications in RxNorm, problems in SNOMED — that the next system can act on, while a PDF-only export strips that structure and turns your medical record into a stack of images. This is the same discrete-vs-document problem that breaks migrations, viewed from the export side, which is why the checklist pairs format demands with completeness validation: confirming that attachments, imaging, audit trails, and the full historical reach all come across intact whether you're exporting from Epic, eClinicalWorks, Kareo, or any other system.