You can leave a healthcare AI supplier safely only if the organisation can recover the information it needs, continue essential work and manage the transition in practice. A cancellation clause alone does not establish that ability. The exit plan should address records, pending actions, configurations, access and staff competence before the service becomes difficult to replace.
Lock-in is not always a mistake
A tightly integrated product may reduce implementation effort and provide valuable functionality. Avoiding every supplier-specific feature can create its own complexity and cost. The question is whether the dependence is understood and proportionate to the benefit.
The government's cloud lock-in guidance, checked on 10 October 2026, recognises trade-offs between useful managed services and the difficulty of switching. It recommends understanding and monitoring dependence rather than treating all lock-in as automatically unacceptable.
For healthcare, the additional concern is continuity. A commercial or technical transition may affect information and unfinished work that still matter to patients. The exit plan therefore needs clinical ownership as well as procurement and engineering input.
List what would be lost if access ended
Start with the information and functions the service actually depends on. This may include approved records, drafts, task queues, source references, audit information, local templates, routing rules and user permissions. Some material may already reside in another approved system; some may exist only within the supplier's product.
Do not assume that the visible record is the whole dependency. A team may also rely on saved configurations, exception-handling routines or staff knowledge of how to recover a failed action. Those are harder to see in a data-export demonstration.
A proposed inventory should identify which items are essential for continuing care, which support investigation and which can reasonably be recreated. That distinction helps prioritise an exit rather than demanding indiscriminate copies of everything.
Exporting a file is not the same as restoring a workflow
A readable document can preserve useful information while losing structured fields, relationships or status. An export may show that a referral was drafted without showing whether it was sent or accepted. A collection of notes may not preserve the links needed to identify which action belongs to which episode.
A proposed portability test should therefore inspect meaning, not only file availability. Can the receiving team identify the patient, source, date, approval status and unresolved work? Can it distinguish a suggestion from an authorised decision and a completed action from an attempted one?
No universal export format solves every task. The appropriate format depends on what must be preserved and how the receiving service will use it. The contract and technical specification should reflect that purpose.
A fictional supplier withdrawal
Imagine a fictional clinic whose AI workflow prepares correspondence and tracks responses. The supplier announces that the service will end. The clinic can export completed documents, but the status of unanswered requests is available only in a proprietary dashboard.
The immediate priority is not to reproduce every feature. It is to identify unresolved work, assign responsibility and establish an approved route for continuing it. The migration team needs to distinguish requests completed elsewhere from those that still require action, or it may create duplicates while trying to prevent omissions.
This scenario is constructed, not a claim that a named supplier is insolvent or planning to withdraw. It shows why exit preparation should be tested while the service is functioning and support remains available.
Contract for assistance, then test what it means
A proposed contract review should cover export availability, formats, notice, transition support, costs, access during migration and the handling of retained information. Ask which commitments survive ordinary termination and what happens if the supplier cannot provide normal support.
Specific legal rights and insolvency arrangements require appropriate advice. Do not assume that ownership language, a portability promise or a standard clause guarantees access to every configuration, proprietary component or model. Nor should an organisation assume that a contractual right can be exercised instantly without technical work.
The practical test is whether the information can be obtained, understood and used within the continuity plan. A successful sample export is more informative than reassurance that export is theoretically possible.
Plan for both orderly and abrupt exit
An orderly migration allows time for validation, staff training and parallel checks. A sudden loss of access may require a narrower emergency workflow using information already held in approved systems.
The SAFER Guides, checked on 10 October 2026, include contingency planning for electronic record unavailability. They provide a useful resilience reference, although they are US guidance and not a complete UK AI-supplier exit standard.
For the local service, identify what can continue without the tool, what needs manual coordination and what must be deferred. The plan should name responsible people and the sources they will use. It should not depend on staff finding an unapproved replacement during the outage.
Preserve capability as well as data
A technically complete export may be of limited use if nobody knows how to run the alternative workflow. Staff should understand how to identify outstanding work, verify its status and continue without reproducing actions already completed.
A proportionate drill can use fictional cases to test that capability. Introduce a mixture of approved documents, unfinished drafts and uncertain external confirmations, then ask the team to explain what happens next. The exercise should reveal gaps in ownership and information before real care depends on the process.
The objective is not to maintain every old manual process indefinitely. It is to preserve enough understanding and operational capacity to recover when the chosen supplier is unavailable.
Learning records need their own exit question
A professional learning platform creates a different dependence from an action-taking clinical system. The user may need continued access to completed evidence even after deciding not to renew, while new tutoring or practice functions can reasonably remain subscription services.
As checked on 10 October 2026, iatroX's CPD page states that completed evidence remains available to view and export after a subscription ends. It also describes PDF export and direct export to linked FourteenFish accounts. Those are published product commitments, not a guarantee that any online service would remain available through every possible business failure.
A learner should retain appropriate copies of important completed evidence and check that the export represents what they actually did. A professional learning record is not automatically formally accredited CME, and moving the file does not change that status.
Make renewal an opportunity to retest dependence
Before renewal, revisit the functions now used, the information held and the cost of switching. A service may have expanded beyond the original procurement assumptions, making the old exit plan incomplete.
Ask whether a recent export still works, whether pending actions can be reconciled and whether the named staff still know the fallback. Then decide whether the benefits justify the remaining dependence.
The strongest position is not to avoid commitment to useful software. It is to ensure that the organisation remains able to question, correct, stop and, when necessary, leave the system without abandoning the people whose care or learning depends on it.
Frequently asked questions
Does a cancellation clause prove that a healthcare AI service is easy to leave?
No. Safe exit also depends on usable information, transition support, unresolved-work reconciliation and the ability to continue the workflow.
Is a PDF export enough for every clinical migration?
Not necessarily. It may preserve readable content while losing structured information, relationships or action status needed by the receiving service.
What does iatroX say happens to completed CPD evidence after cancellation?
Its CPD page, checked on 10 October 2026, states that completed evidence remains accessible for viewing and export after the subscription ends. That should be distinguished from access to new paid learning functions and from any guarantee of indefinite service availability.
Review and export your completed professional learning evidence →