Skip to main content

Clinical system migration guide

This guide aims to help practices, GP IT delivery partners (such as Commissioning Support Units (CSUs)) and Commissioning Clinical Groups (CCG) plan and prepare their migration from one foundation clinical system to another.

Whilst approaches to migration may differ by region, this guide contains a collection of common phases and strategies aimed at reducing the impact and burden for the practice.

This is a generic guide and may not cover everything that happens in your migration, but it does aim to cover the key activities and make suggestions on how to act on them. This guide can be used in conjunction with any deployment schedules and guidance issued by your new supplier.

Current Chapter

Clinical system migration guide


Summary

This guide aims to help practices, GP IT delivery partners (such as Commissioning Support Units (CSUs)) and Commissioning Clinical Groups (CCG) plan and prepare their migration from one foundation clinical system to another.

Whilst approaches to migration may differ by region, this guide contains a collection of common phases and strategies aimed at reducing the impact and burden for the practice.

This is a generic guide and may not cover everything that happens in your migration, but it does aim to cover the key activities and make suggestions on how to act on them. This guide can be used in conjunction with any deployment schedules and guidance issued by your new supplier.


Please note

This is a beta version 1.5 of the guide and will continue to be updated as the GP IT Futures framework develops and matures.


Information Governance

Performing a migration inevitably involves access to, and processing of, significant amounts of personal patient data. It’s crucial, therefore, that all parties involved adhere to the laws, policies, standards and guidelines in respect to Information Governance, including:


How long does a migration take?

Migrations on average take between 12-16 weeks.  This is from the point of placing the order for the new system to go-live.  Some migration related activities will continue after go-live.  


Overview of migration steps

Migrations require a lot of planning and effort from practice staff, breaking this activity into smaller incremental steps will help ease the pressure and make the migration effort more sustainable.

 

The decision to migrate and funding

The practice completes a business case providing reasons to justify the migration and detailing the preferred clinical system (otherwise known as a solution). This is assessed by the CCG and if approved, they will authorise the funding to support the migration.

More information.

Ordering a new system

Estimated timeline: 1 to 2 weeks

The order is placed with the new supplier.

Please note

The process for ordering a new system under GP IT Futures is currently being finalised. As soon as the new process is ready, we will let you know.

Kick-off meeting

Estimated timeline: 1 day

Involving discussions with all the key people who will take part in the end-to-end process of migrating your system.

Find out more about kick-off.

Technical survey

Estimated timeline: 1 day

Checking the current hardware and software at the practice for compatibility. The timing of the technical survey can vary across areas, but likely to happen shortly after the Kick-off meeting. Some delivery partners conduct Technical Surveys remotely and do not necessarily need to be on site.

Find out more about the technical survey.

Pre-migration tasks

Estimated timeline: 1 to 2 weeks

Critical activities practices can start doing to get ahead and prepare for the later stages such as tidying up current data and notifying third party services and patients.

Find out more about pre-migration tasks.

Initial data production

Estimated timeline: 1 day

Initial Data Production (IDP) is the point at which the current system (solution) supplier carries out a data extraction, which contains all data on the system. This is passed to the new supplier, who uploads the data into a test or ‘dummy’ version of the system.

Find out more about IDP.

Data checking

Estimated timeline: 3 days to 3 weeks

Supported by the new supplier, the practice performs a series of data checking processes to validate the data in the test ‘dummy’ system against the current one.

Find out more about data checking.

Data recheck and sign-off

Estimated timeline: 1 to 5 days

Rechecking the data after the new supplier has fixed any issues found in the previous data checking phase. If satisfied with the quality of the data, the practice will sign it off at this point. This signifies approval to proceed to final data collection and go-Live.

Find out more about the data recheck and sign-off.

Cutover planning and preparation

Preparation and activities to reduce the impact of the cutover period and data re-entry.  A meeting should be held at least four weeks before the start of the cutover period to plan activities and processes so that data for re-entry can be identified and captured.

Find out more about cutover planning and preparation.

Training

Training can happen throughout the end to end migration process. Generally this will take place over a period of 2-3 weeks immediately prior to go-Live.

Find out more about training.

Final data production

Estimated timeline: 1 day

The final data extract is provided to the new supplier by the current supplier. The data is then imported into the live version of the new system. From this point in time, any changes in the current system will not be automatically migrated and will require manual entry into the new system.

Find out more about the final data production.

Cutover period

Estimated timeline: 2 to 3 weeks

The period of time between the final data production and the go-Live. The practice should put in place the manual processes agreed at the cutover planning stage. During the cutover, the practice may continue to use the current clinical system, knowing that the data entered will not be migrated. 

Find out more about the cutover period.

Go-live

Estimated timeline: 1 day

The point at which the practice has approved and signed off that the data is accurate, and gains access to the new system. From go-live onwards, the new system becomes the primary operational tool and the practice should stop entering data into the old one.

Find out more about go-live.

Post go-live

Estimated timeline: This will vary depending on size of practice and volume of data.

Practice staff re-enter data for all activities that took place in the previous system during the cutover period (such as appointments, prescriptions and consultations).

Find out more about post go-live.

Help us improve this guide

Your feedback about this guide would be greatly appreciated.

You can also send feedback to nhsdigitalpracticemigrationteam@nhs.net with a subject title of Feedback: clinical system migration guide.

Last edited: 9 April 2021 10:52 am