Readily producible format

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

Assess the actual source systems

45 CFR 164.524 connects the format duty to how the requested PHI is maintained. Inventory the designated record sets, native exports, PDF and data options, accessibility, encryption, media, and delivery constraints. A vendor preference is evidence about capability, not the legal conclusion by itself.

Build the assessment at the source level. A practice may maintain clinical notes in one platform, billing records in another, signed forms as images, and older files in an archive. A format can be readily producible for one source and unavailable for another. Record the native form, supported export options, whether a conversion is routine, and whether the resulting file preserves content, chronology, labels, and attachments.

Capability changes over time. An export that failed before a platform upgrade may work today, while an old workflow may break after migration. Keep screenshots, vendor documentation, test exports, or other evidence behind the capability matrix. Staff preference, a portal's default button, or the fact that a format takes several steps does not by itself settle whether it is readily producible.

Agreement follows an unavailable format

HHS access guidance explains requested and agreed form and format. Document the requested option, capability test, reason it is unavailable, alternatives offered, individual's choice, readability test, and any fee effect. Avoid substituting paper when a readable electronic alternative is available and agreed.

The conversation should be specific enough for an informed choice. Explain which part of the request cannot be produced as asked, identify feasible alternatives, describe how each will be delivered, and note any accessibility or software requirements. Capture the person's affirmative selection. If the request combines multiple sources, the agreement may use different formats for different record groups.

When the individual and entity cannot agree on an electronic format, the rule's fallback depends on how the PHI is maintained. Privacy or legal review should resolve unusual cases rather than allowing an open format discussion to consume the response deadline. Keep fulfillment work for agreed portions moving while the remaining choice is clarified.

Test usability at the destination

Readability is an outcome, not a file extension. Open a sample from the actual export path, verify page and attachment counts, search or navigate the file where applicable, and check for truncated text or blank images. Encrypted files need a separate, usable credential path. Large exports may require multiple archives with a manifest so the individual can confirm completeness.

Accessibility belongs in the intake conversation. Ask about a requested accessible format or assistive technology, route accommodation questions appropriately, and test the selected output. A scanned image-only PDF may technically open yet remain unusable for someone relying on text extraction. Preserve what was requested, what the system could produce, and what the individual accepted.

Example across file formats

Seven requests specify electronic formats. Five are produced as requested, one uses an agreed readable alternative, and one receives an unreadable image export. Usable format completion is 6 of 7 requests. The failed export requires replacement.

In a mixed-source request, suppose the person asks for searchable PDF. Clinical and billing platforms export 94 records as searchable PDFs, but an archive exports six legacy scans. The practice explains the limitation, offers the six scans as image PDFs with a separate index, and records the person's agreement. Format completion is 100 of 100 records only after both sets open, the index matches the files, and the delivery includes the promised alternative.

Format-decision checklist

• Record the requested form, format, delivery method, and accessibility needs.
• Map each requested category to its source system and native maintenance form.
• Test available exports and retain evidence for unsupported conversions.
• Offer clear readable alternatives for formats that are unavailable.
• Capture the individual's affirmative agreement to each alternative.
• Reconcile files and attachments to the request before delivery.
• Test opening, readability, searchability where promised, and credential delivery.
• Reassess the capability matrix after migrations, upgrades, or vendor changes.

Owner controls

Keep a current system capability matrix and retest it after migrations or vendor changes. Sample delivered files, record assistive-technology issues, train request staff to negotiate format, and avoid promises unsupported by the actual export path.

Measure requests fulfilled as asked, requests using an agreed alternative, unreadable deliveries, format-related delay, and rework. Investigate recurring substitutions that favor paper or a single portal option despite other established capabilities. A defensible program can reproduce both its capability conclusion and the person's final choice.