Connect

hello@6bdigital.com
0113 350 1290
Contact us

Planning for the Transition: Migrating EMIS Integration Capabilities from EMIS Web to EMIS-X

EMIS is in the process of transitioning from its EMIS Web platform to the next-generation EMIS-X.

For digital health innovators, particularly those already integrated with EMIS Web via the EMIS Partner Program, IM1, or GP Connect, this shift presents both opportunities and challenges. EMIS-X integration capabilities are set for release in early 2025, and EMIS Web integration capabilities will continue to be maintained, however organisations should begin planning their migration strategies now to ensure a seamless transition.

EMIS Web is the most commonly used clinical application in GP Practices, with around 3755 GP Practices in England using EMIS Web every day (compared to approx 2554 practices using SystmOne). This article outlines key considerations for navigating migrating EMIS Web integrations to EMIS-X and highlights steps digital health innovators can take today to prepare for tomorrow.

Understanding EMIS’ Rationale for Migrating EMIS Web to EMIS-X

The migration from EMIS Web to EMIS-X is driven by the need to align with modern technology standards and address limitations in the current platform and integration capabilities. EMIS Web relies heavily on desktop-based integration, which constrains scalability and cloud compatibility. In contrast, EMIS-X will embrace a cloud-first architecture, leveraging modern JSON APIs for enhanced interoperability, real-time data access, and streamlined workflows. These advancements promise to improve patient care delivery while offering innovators more efficient and flexible integration options.

For EMIS this transformation is necessary, but for innovators integrating with EMIS it represents a significant departure from the existing integration paradigms. For innovators, the shift will require a reevaluation of current solutions, potentially a redesign of integration approaches, and potentially a revalidation of compliance and assurance processes.

Mapping the EMIS Web to EMIS-X Migration Timeline

The phased rollout of EMIS-X allows for deliberate planning and gradual adoption, here are the migration dates as we understand them currently:

  • 2024: EMIS Web continues alongside EMIS-X
  • 2025: Initial EMIS-X integration capabilities are released, and migrations begin
  • 2026-2027: EMIS-X becomes the primary platform, with EMIS Web entering its sunset phase

For innovators, this timeline prompts the urgency of proactive planning. Waiting until EMIS-X capabilities are live may leave organisations scrambling to adapt, risking disruptions to services and user experiences.

Opportunities in the EMIS-X Integration Ecosystem

While integration migration may seem daunting, it also presents opportunities for innovation and differentiation. EMIS-X’s modern capabilities enable digital health innovators to:

  • Leverage near real-time APIs to provide clinicians with up-to-date patient data, enhancing decision-making.
  • Build scalable, cloud-native solutions that integrate seamlessly across different healthcare settings and geographies.
  • Use context management features to create intuitive, synchronised workflows for users navigating between systems.

Additionally, the forthcoming EMIS-X Developer Portal will offer self-service tools and documentation, empowering developers to build and test integrations with more autonomy.

Key Considerations for EMIS Web to EMIS-X Migration Planning

Evaluate Existing Integrations – Begin by conducting a comprehensive audit of your current EMIS WEB integration capabilities. Identify which of your systems rely on IM1, GP Connect, or other EMIS Partner APIs. Understanding the depth and scope of your integration dependencies will provide a foundation for mapping transition requirements.

Understand EMIS-X Principles – EMIS-X introduces several core principles that differ significantly from EMIS Web. It is important to familiarise yourself with these principles to align your future development efforts with EMIS-X’s design ethos:

  • Cloud-Native Integration: APIs will be internet-facing, removing the need (and capabilities) for desktop-based solutions.
  • Real-Time Capabilities: Near real-time data synchronisation will replace the need for local data caching.
  • Generic, Reusable Capabilities: EMIS-X prioritises standardised, scalable solutions, rather than bespoke integrations.

Anticipate Changes in Assurance Processes – Although EMIS-X aims to streamline technical integration through self-service tools like the upcoming EMIS Developer Portal, assurance and validation will remain mandatory and EMIS Partner integrations will need to demonstrate compliance with EMIS-X guidelines before deployment.

Assess Cloud Readiness – EMIS-X is built for cloud-first integration, meaning organisations must ensure their solutions are compatible with cloud architectures. Evaluate whether your existing infrastructure supports cloud-hosted APIs and scalable data exchanges. For desktop-based applications, consider strategies to replatform or rebuild for web compatibility.

Plan for Resource Allocation – Migrating to EMIS-X will require dedicated resources, including technical teams for redevelopment, compliance specialists for assurance, and project managers for migration coordination. Budgeting for these resources now will prevent bottlenecks when the migration process begins.

EMIS-X Integration Pre-Migration Steps to Take Now

While direct migration efforts cannot commence until EMIS-X capabilities are available (expected in early 2025), several preparatory steps can be taken to streamline the transition:

Engage with EMIS – Stay connected with EMIS communications to receive updates on the Developer Portal, technical specifications, and support resources. Attend EMIS partner forums and developer events to build a deeper understanding of the migration roadmap.

Redesign for Scalability and Modularity – Begin refactoring existing integrations to adopt modular, scalable designs. This will simplify adaptation to EMIS-X’s generic, reusable capabilities. Focus on decoupling tightly integrated components and replacing hardcoded dependencies with flexible interfaces.

Enhance Security and Authentication – EMIS-X will align with modern authentication standards, likely requiring secure, token-based access mechanisms. Start implementing OAuth 2.0 or similar protocols in your solutions to ensure compatibility with future EMIS-X APIs.

Develop a Data Strategy – Transitioning to real-time APIs requires a rethinking of data management. Evaluate how your solutions handle data storage, caching, and synchronisation. Prepare to migrate from local storage models to cloud-based, real-time interactions.

Foster Cross-Functional Collaboration – Migration is not just a technical challenge; it impacts business operations, user workflows, and compliance. Establish cross-functional teams to align technical, operational, and regulatory perspectives early in the planning process.

Frequently Asked Questions

When will EMIS-X Partner integration capabilities be available?
The first API capabilities are expected in Q1 2025, with rollout starting in Q2 2025. Enhanced features will continue to be delivered throughout 2025 and 2026.

Will existing EMIS Web integrations continue to work (eg IM1 and GP Connect)?
Yes, existing integrations via IM1 and GP Connect with EMIS Web will remain operational until full functional parity is achieved in EMIS-X, (EMIS are anticipating this will be around 2026-2027).

Will existing desktop application integrations be supported in EMIS-X?
No, EMIS-X will not natively support launching or integrating with desktop applications. Instead, it will focus on cloud-hosted, internet-facing APIs.

Will EMIS Web Portal SDK integrations work with EMIS-X?
No, Portal SDK integrations will need to be reconfigured to work with EMIS-X. Portal SDK integrations with EMIS Web will continue to be supported by EMIS until full functional parity is achieved in EMIS-X, (EMIS are anticipating this will be around 2026-2027).

Will solutions built against EMIS-X require assurance?
Yes, all integrations with EMIS-X will need to be validated for compliance with EMIS-X guidelines in a similar way to EMIS Web integrations.

Can I migrate my existing integration solution to EMIS-X?
Yes, but migration will involve reconfiguring solutions to align with EMIS-X’s modern cloud-based architecture.

Will EMIS-X replace all EMIS products?
Not in the immediate future, EMIS-X is solely focused on replacing EMIS Web. Integration for other EMIS products (e.g., Community, Pharmacy, Symphony) may come later, likely post-2025.

What tools will be available for integration with EMIS-X?
For EMIS Partners, a Developer Portal will be released in early 2025 to guide and support developers through integration processes. It will eventually become a self-service platform for testing and building against EMIS-X APIs.

Will EMIS enable bespoke integration capabilities with EMIS-X?
No, bespoke integrations will not be directly supported, but the platform’s flexibility should cover most requirements.

Will EMIS-X adopt any open data standards, like HL7 FHIR or openEHR?
This is not clear, however we think it is unlikely because nothing has been communicated on this so far.

Looking Ahead: Preparing for 2025 and Beyond

As EMIS-X’s integration capabilities become available in early 2025, organisations must be ready to act. If you are an EMIS Partner, prioritise early access to the Developer Portal to familiarise your teams with new APIs and integration workflows and plan pilot projects to test EMIS-X integration in controlled environments before scaling to full production. If you are not an EMIS Partner, stay informed on the upcoming changes to EMIS through subscribing to EMIS newsletters (https://www.emishealth.com/news-insights/newsletters), and start today with planning your long-term migration from EMIS Web to EMIS-X.

By adopting a proactive and strategic approach, digital health innovators can not only navigate the migration successfully but also position themselves strategically in the upcoming EMIS-X ecosystem. The time to prepare is now.

Ready to accelerate your technology project?

Chat to our team of experts and let's see how we can help you.