Patient Record Exports: A Clinic Portability Checklist

The right time to inspect a record export is while the software still works and the supplier relationship is comfortable. A downloaded archive can look reassuring while omitting the note text, separating attachments from patients or requiring a licence you will no longer have. Treat export readiness as a routine clinic check: know what you can obtain, who can obtain it and whether someone can understand it outside the original application.

Define the job the export needs to do

Start by naming the purpose. A patient may need a readable copy of a particular episode of care. The clinic may want a periodic extract for continuity planning. A future software change may require structured information that another application can import. Each purpose calls for different contents, permissions and checks. An attractive visit summary may answer one request well while leaving important material out of a broader clinic export.

Keep patient rights requests within the applicable law and your established release process. For US HIPAA covered entities, HHS electronic-copy guidance discusses providing information in a requested electronic format when readily producible, with alternatives where appropriate. It does not mean every vendor offers an identical export. Establish scope and recipient authority before selecting or sending records, and check current requirements in your jurisdiction.

The word portability can also have a specific legal meaning. The ICO explains the UK GDPR right to data portability as conditional, including requirements about the processing basis and automated processing. Do not assume it guarantees a complete clinical database transfer in every situation. For procurement, agree the clinic's export and exit requirements explicitly; for an individual request, assess the applicable rights and obligations.

Create a manifest of what the clinic holds

A manifest is a plain list of the information you expect to find. Write it before pressing export, using your actual workflow. Include patient details, appointments, notes and invoices where you hold them. Add attachments, referral correspondence, consent records and other materials relevant to your practice. Some information may live in a separate service or file store. Put its location beside the item so it does not disappear from the check.

• Patient identity: the stable record identifier, name and other relevant demographic fields. Confirm which identifier connects the other exported files.
• Clinical content: visit dates, note text, authors and relevant status or amendment information. Ask which historical versions are included and which are excluded.
• Supporting documents: the actual attachment files, their descriptions and a clear association with the patient or visit.
• Operational records: appointments, invoice details and payments where these are part of the agreed export scope.
• Interpretation: file formats, field definitions, date and time conventions, codes, units and known exclusions.

Ask the supplier to answer against that list. A useful answer says notes are in one file, attachments are in another folder and payment history requires a separate export. An answer that says all data can be exported leaves too much unresolved. Record whether each item is available directly, needs supplier assistance or is unsupported. Keep the written answer and the tested result together, including the product version or plan.

Inspect content and relationships, not just file size

Begin with a fictional test patient whose contents you know. Create two visits, a sample note, a harmless attachment and a sample invoice, using only functions available in the system. Then export and compare against the case sheet. Follow the identifier through each file. If you can read two notes but cannot determine which visit each belongs to, you have found an interpretation problem even though no text is missing.

Open the export with an appropriate independent reader on a clinic-controlled device. Avoid uploading it to a public conversion tool. Examine long text, line breaks, accented names and dates that could be interpreted differently across regions. Where codes or numeric values appear, look for definitions and units. A blank cell can mean missing, not applicable or withheld; ask which meaning applies instead of choosing one that makes the totals look tidy.

For relevant US certified health IT, the ONC EHI export criterion addresses computable exports and export-format documentation. Its scope is that certification criterion; it is not a promise about every clinic product worldwide. The useful buyer question is whether the actual files and documentation let a recipient interpret the contents. A familiar extension alone does not establish that capability.

Once the test works, an authorised person can review an appropriately selected sample of actual records under the clinic's privacy process. Choose different record shapes rather than the easiest recent visit: a long history, an amended note and a patient with multiple attachments, if you hold these. Keep a discrepancy list with the expected item, observed result and explanation. Never turn missing material into an undocumented assumption.

Check the boundary of the export

Record the date, time, filters and scope of every production export. Is it one patient, a date range, active records or the entire available population? Does an appointment-date filter also exclude older notes? What happens to archived patients? If the job takes time, ask whether its contents represent one consistent point in time or information collected while users continued editing. The answer affects how you interpret the result.

Compare available counts carefully. In a hypothetical exercise, the clinic expects three appointments and two notes for one fictional patient. An export with three appointments and one note needs investigation. It may reflect an export limit, a draft-status exclusion or a missing save. Matching counts are useful evidence, but they do not prove that the correct patients, authors or note contents are present. Inspect meaning as well as quantity.

Do not edit the only exported copy to make it easier to read. Preserve the original archive and create a working copy for review, with controlled access. Keep any transformations and explanations alongside it. If a supplier regenerates an incomplete export, label the replacement distinctly and retain the discrepancy record. Staff should be able to identify which export was checked and why it was accepted.

Make export access survive staff and contract changes

Choose a responsible owner and a backup owner. Both should know the supported procedure and have appropriately authorised access. Test the process using the level of permission the clinic will actually maintain. An export that only works through a former administrator's account is an operational dependency to fix. Our patient data security checklist helps organise the access and device questions around that task.

• Ask whether exports are self-service and whether large jobs need a support ticket, identity verification or a different plan.
• Obtain written details of charges, format documentation and any technical limits. Clarify which parts need separate requests.
• Ask what access remains during cancellation, what contractual window applies and how records can be returned before service ends.
• Confirm who can authorise a full export and how the clinic records that authorisation. Keep downloads restricted to the intended purpose.
• Ask how a changed export format will be communicated, so an old successful test does not become your only evidence.

Protect the copy throughout its useful life

A full export concentrates sensitive information in a portable package. Choose a clinic-approved storage and transfer method, restrict access and record where the copies are held. Include the device download folder and any temporary extraction folder in the handling plan. If a recipient needs the files, confirm identity and authority through your normal process. A typo in an address should not be the only barrier between an export and the wrong person.

Set retention and disposal rules according to the purpose, applicable obligations and clinic policy. A temporary review copy may have a different lifecycle from a retained record archive. Explain that distinction to the person performing the export. Also keep recovery planning separate: a readable export may not contain the configuration and relationships needed to restore the original application. Test whichever recovery process you intend to rely on.

Keep a short readiness record

Finish with one page containing the export owner, procedure, scope, checked sample, findings and next review trigger. Repeat the check when the product, format, contract or clinic workflow changes materially. Our guide to choosing clinic software can help turn unresolved findings into supplier questions. An export check is useful even when you have no immediate intention of changing software.

Apply the same manifest when evaluating MedRecPlus. Test the export options that are actually available for the records, appointments, notes and invoices you use, and obtain an explanation for anything additional your practice holds. This checklist makes no promise about universal import compatibility or legal compliance. The practical goal is modest and important: the clinic knows what it can obtain and has evidence that the obtained information is understandable.