Migration
Changing clinical systems is one of the most significant operational changes a GP practice will undertake. Our experienced implementation team will guide your practice through every stage of the process, ensuring your patient data is transferred safely, accurately and with minimal disruption to care.
Talk to Us →
Every migration we deliver is built around five core principles, regardless of which system you are migrating from.
Maintaining continuity of care and protecting patient safety is our highest priority. Every stage of the migration has been designed to ensure clinicians continue to have access to the information they need throughout the transition.
Patient records are carefully mapped and transferred into the appropriate locations within Medicus. For SystmOne and EMIS Web migrations, this mapping is independently assured against NHS England's Data Migration Overarching Standard.
Your practice plays an important role in validating the migrated data before go-live. The people who know your patients best should have the opportunity to review the migrated records.
Every migration is individually planned and managed. Detailed implementation planning, readiness reviews and coordinated cutover activities help ensure a smooth transition.
Every migration is reviewed following go-live. Lessons learned are incorporated into future migrations to continually improve our processes.
SystmOne
Our implementation and data migration methodology has been developed specifically to support GP practices transitioning to Medicus from SystmOne. Every migration follows a carefully managed process that has been independently assured against NHS England's Data Migration Overarching Standard, ensuring patient records are transferred safely and consistently into Medicus.
Assurance
Medicus is assured against NHS England's Data Migration Overarching Standard. Our data migration methodology has been independently reviewed to confirm that information held within SystmOne is correctly mapped into Medicus, including clinical information, coded data, patient demographics, documents and all other relevant clinical and administrative information required to safely recreate the patient record.
Our migration process is supported by comprehensive Clinical Safety documentation, including Clinical Safety Case Reports, Hazard Logs and structured risk management procedures.
Every migration follows a structured implementation programme consisting of six key stages.
Following signature of your Call-Off Agreement, your dedicated Implementation Lead will begin planning your migration.
Medicus requests an initial data extract from SystmOne, a point-in-time extract of your full patient records, well in advance of go-live. This allows your practice to review the migrated data early and become familiar with Medicus before the final migration takes place.
Your nominated Clinical Safety Officer or Clinical Lead undertakes a structured validation exercise. This typically includes reviewing:
As your go-live date approaches, we complete a final readiness review confirming that staff training, user accounts, practice configuration, national integrations and all implementation activities are complete. A formal Go / No-Go decision is made before commencing the migration.
Note: Due to SystmOne's underlying architecture, the source system supplier requires up to three working days to generate the final migration dataset. Cutover normally begins on a Thursday evening following the close of practice.
During the cutover period, SystmOne remains available in read-only mode for viewing historical patient information while Medicus becomes your new system of record. Once the final data extract is received, Medicus immediately begins the production migration including data transformation, loading and comprehensive quality assurance.
Our implementation team remains available throughout the cutover period to provide guidance and support.
Once all validation and readiness activities are complete, Medicus becomes your primary clinical system. Our implementation specialists remain closely engaged throughout go-live, providing rapid support and guidance to practice staff.
Following migration your practice enters a structured Hypercare period with regular check-ins, rapid response to queries, additional user guidance and continued clinical and operational support, until your practice is confident using Medicus.
EMIS Web
Our implementation and data migration methodology has been designed to ensure that your transition from EMIS Web to Medicus is safe, well planned and carefully managed. Every migration follows an NHS England assured migration methodology and is supported by an experienced implementation team who will guide your practice through every stage of the project.
Assurance
Medicus is assured against NHS England's Data Migration Overarching Standard. This independent assurance confirms that patient records are migrated using approved mapping methodologies that safely transfer information from EMIS Web into Medicus, including clinical records, coded information, medications, allergies, documents, correspondence and other clinical and administrative information required to recreate the patient record.
The migration process is supported by comprehensive Clinical Safety documentation, including Clinical Safety Case Reports, Hazard Logs and formal risk management procedures.
Every implementation follows a structured programme consisting of six key stages.
Following signature of your Call-Off Agreement, your dedicated Implementation Lead will begin planning your migration.
Medicus requests an initial data extract from EMIS Web early in the project. This provides an early opportunity to load your patient records into your Medicus environment well before the live migration, allowing your practice to begin familiarising itself with Medicus and for any questions to be identified and resolved well in advance of migration weekend.
Your nominated Clinical Lead or Clinical Safety Officer reviews a representative sample of patient records using validation guidance provided by Medicus. Typical areas reviewed include:
As your planned migration date approaches, Medicus and your practice complete a comprehensive readiness review, confirming that training, configuration, national services and user accounts are all complete. A formal Go / No-Go meeting is held before migration weekend begins.
Before cutover, your practice should ensure all clinical consultations are completed, outstanding workflow is processed, investigation results reviewed and correspondence filed. Where Docman is used alongside EMIS Web, all outstanding documents should also be processed before migration begins.
Migration begins following the close of practice on Friday. The final data extract is prepared from EMIS Web overnight on Friday, and on Saturday Medicus securely imports your production data into your live Medicus environment using the same NHS England assured migration methodology used during validation.
Once production migration is complete, your nominated Clinical Lead completes a final validation exercise to confirm the live environment accurately reflects patient records held in EMIS Web immediately before cutover. Medicus also completes a comprehensive series of operational smoke tests before go-live.
On Monday morning, Medicus becomes your live clinical system. Your implementation team will be available throughout go-live to support practice staff and answer questions from the first day.
Following go-live your practice enters a structured Hypercare period with regular check-ins, responsive support, additional guidance and monitoring of key services, until your practice is fully established on Medicus.
Semble
Migrating from Semble to Medicus is fully supported. We have a complete data migration routine for Semble practices, and your implementation team will manage the entire process from initial planning through to go-live.
A dry run migration is performed a few weeks before your go-live date. This loads a copy of your patient records into your Medicus environment early, giving your practice the opportunity to review and validate the migrated data and become familiar with Medicus before you go live.
When you are ready to go live, Medicus takes a final extract from Semble and loads it into your live Medicus environment. Your dedicated implementation team will be with you throughout go-live and into Hypercare to ensure a smooth transition.
Talk to us about migrating from Semble →