Can your care records leave the system without losing their meaning?

An export is not the same as an exchange

A downloaded archive, a structured migration file and a working shared-care-record connection serve different purposes. Define the use case before asking whether a product is interoperable. A manager seeking a readable historic account needs a different test from a receiving system importing coded fields. A hospital handover has its own information and access requirements. One successful demonstration does not establish all three capabilities.

Care Circle recommends writing a short scenario for each required use. Identify the authorised receiving person or system, information needed, reason for sharing and acceptable delay. Use these scenarios to compare supplier answers. Keep technical terminology attached to an actual care task so that colleagues can challenge whether the proposed connection will help them, rather than assuming that an integration label guarantees usefulness.

Preserve the person and the chronology

The PRSB Core Information Standard defines common information for sharing; local implementation and access remain important. Its page identifies version 2.01 and management by NHS England from January 2026. This gives the provider a standards reference, not proof that its own system or every local partner has implemented a functioning connection.

In a safe test record, include a preference, a later correction, a dated change to support and a clearly labelled historical entry. Examine whether those distinctions remain visible after export and, where applicable, import. A receiving team should not mistake an old statement for the current plan. Explain any transformation or lost context. Test data should be realistic enough to expose a weakness without copying confidential live records unnecessarily.

Check what the receiving team can actually use

PRSB’s standards resources set out common information for recording and sharing and provide models and release information. Providers should ask which version the supplier implements and how changes are managed. A claim of standards alignment should be accompanied by an explanation of the relevant function. Do not substitute a general standards label for evidence about the destination system and the specific exchange.

Care Circle proposes involving a representative receiving user in an agreed demonstration. Can they find the current support information, distinguish attachments from structured fields and identify the author and date? Can they interpret abbreviations consistently? A technically successful transfer can still create additional work. Capture the difficulties and ask who resolves them before agreeing that the transition or connection is ready for normal operation.

Budget the transition as a care project

A change of supplier can require staff training, data mapping, reconciliation and a period when old and new records are available under controlled arrangements. Estimate the time and cost using the provider’s own scale, then record the assumptions. This is an illustrative planning exercise, not an industry benchmark. Agree who checks completeness and who authorises the final move to the new workflow.

Ask for contractual clarity about export formats, assistance, charges, retention, access after termination and secure deletion when appropriate. The responsible data lead should check applicable legal and retention requirements before authorising disposal. Deleting the old system too early can remove necessary evidence; retaining uncontrolled copies indefinitely creates its own risk. The decision must reflect the actual records and obligations, not a generic product promise.

Rehearse the exit while the relationship is healthy

An exit test is easier when there is time to resolve a discrepancy. Ask for a controlled sample export before renewal or expansion, with agreed security arrangements and appropriate authorisation. Count the expected and received records, inspect a sample for meaning, record missing elements and confirm how the supplier will address them. Avoid moving real personal information into an informal spreadsheet or unsecured trial account.

Care Circle’s suggested outcome is a documented portability decision: usable for the stated purpose, usable with agreed remediation, or not yet demonstrated. This does not predict a future migration or imply that one test covers every record. Repeat relevant checks after material product changes. The provider gains negotiating clarity and a better understanding of its information, even if it decides to stay with the current supplier.

Document who will retain the final decision record, including the limitations of any sample test. A later procurement team should be able to distinguish an agreed contractual right to export from a migration that has actually been demonstrated. Those are different pieces of evidence.