Electronic copy of PHI

Editorial approval scope: The team checked current source fidelity, scope boundaries, dates, arithmetic, reader usefulness, practical workflow, and general-information limitations.

Electronic maintenance triggers the format rule

45 CFR 164.524 addresses electronic copies when requested PHI is maintained electronically in one or more designated record sets. Ask which systems hold the records, whether the requested format is readily producible, and which readable alternative is available. A scan, data export, PDF, or other file can vary in completeness and usability.

Delivery and recipient are separate decisions

Record whether delivery will use a secure portal, encrypted exchange, mail on portable media, or another agreed route. If the individual directs a copy to another person under the rule, the written and signed request must clearly identify the person and destination. Verify the destination before sending and preserve transmission evidence.

Test the delivered files

Check that every expected file opens, dates and pages are present, text is legible, data fields are interpretable, and assistive technology can use the agreed format when relevant. HHS access guidance covers form, format, timing, and transmission issues. Security controls should protect the copy without making agreed access unusable.

Track usable delivery

A fictional export contains ten expected files. Eight open correctly, one is corrupted, and one record category is missing. Usable delivery is 8 of 10 files. The practice keeps the request open until the corrupted file is replaced and the missing category receives a documented disposition.

Map scope before choosing a format

Search every designated record set maintained by or for the covered entity, including relevant business-associate systems. Build a source list with record family, date range, file type, owner, export method, duplicate rule, and disposition. An EHR portal may expose only part of the designated record set, so “available in the portal” is not proof of complete production.

Ask what the individual wants to do with the copy. A human-readable PDF may serve review and printing, while structured data may support transfer or analysis. Images, audio, video, graphs, signed forms, and message threads can require separate formats. When the requested format is not readily producible, discuss a readable electronic alternative rather than defaulting silently.

Preserve original meaning, dates, authorship, units, legends, attachments, and relationships between records. A spreadsheet export that drops units or a PDF that separates an addendum from its note can be technically open but clinically misleading.

Choose a verified delivery route

Confirm recipient identity, destination, and requested transmission. Use the individual's confidential communication controls and record whether the copy goes to the individual or another clearly identified recipient through the applicable pathway. The HHS guidance contains a court-order notice affecting part of its third-party direction discussion, so verify current scope before relying on that rule.

Offer secure practical options. When an individual requests another electronic route after receiving an appropriate warning about material risk, route the choice through the current rule and policy instead of imposing a portal the person cannot use. Document the discussion, selected route, address, encryption or media controls, and delivery evidence.

Do not place a shared password in the same message as the file. Expire links appropriately, limit downloads when consistent with the request, protect portable media, and verify that vendor retention or tracking does not create an undisclosed copy.

Validate content and accessibility

Create a manifest listing each expected record family, file name, format, page or item count, date range, checksum or integrity control where appropriate, and result. Open every file type in the recipient's likely environment. Check legibility, orientation, OCR quality, metadata needed for interpretation, and whether assistive technology can navigate the agreed format.

Compare sample entries with the source system. Reconcile missing attachments, duplicate pages, corrupted archives, blank exports, truncated fields, broken links, and mismatched patient identity before sending. Scan produced media through approved security controls without changing the clinical content.

If part of the request is denied or unavailable, provide the accessible remainder and a documented disposition for the rest. Keep the request open until each manifest row is delivered, denied through the proper process, redirected to a known holder, or otherwise lawfully resolved.

Use a delivery checklist

• verify requester authority and every designated-record-set source
• confirm requested and readily producible formats
• agree on a readable alternative when needed
• preserve record context, attachments, authorship, and dates
• verify recipient, destination, and confidential delivery controls
• calculate only a permitted access fee
• test files for integrity, readability, and accessibility
• reconcile the delivery manifest to source counts
• record transmission, receipt or failure, and corrective action

Useful measures include sources searched, expected files produced, files that open and reconcile, requested formats satisfied, and failed deliveries corrected by target. Completion means usable access, not merely a successful upload event.