EHR / EMR Systems
EMIS Integration
EMIS (EMIS Web, evolving to the EMIS-X platform) is, alongside SystmOne, one of the two dominant clinical systems in NHS primary care. Integrating with EMIS is critical for products serving GP practices, primary care networks, and community services. As with SystmOne, EMIS integration runs through NHS-governed frameworks and partner APIs, under UK GDPR and the NHS Data Security and Protection Toolkit. This guide covers how it works and what it takes to go live.
Written and reviewed by the Speed AI Labs engineering team — healthcare AI & EHR integration specialists
Last reviewed July 2026
How EMIS integration works
EMIS provides partner APIs and supports the NHS IM1 interface mechanism for third-party access to GP records. The EMIS-X platform direction emphasises modern, API-led and increasingly FHIR-aligned integration. Apps obtain controlled read and/or write access to clinical data under partner agreements. National NHS APIs and shared record standards complement vendor-specific access for certain data flows. The route to production is governed by NHS approvals rather than a purely commercial sign-up.
Partner programme and NHS approvals
Integrating with EMIS involves becoming an approved partner and securing the appropriate IM1 agreement, alongside completing the NHS Data Security and Protection Toolkit and meeting clinical safety standards (DCB0129/DCB0160). Information governance and a clear lawful basis underpin everything. These assurance steps run in parallel with engineering and are usually the critical path to a live NHS deployment.
Compliance and clinical safety
EMIS integrations process patient data under UK GDPR and the DPA 2018, with the NHS DSP Toolkit and DCB clinical safety standards as the governing frameworks. Expect to evidence encryption, access control, audit logging, and documented clinical risk management. This maturity is the precondition for an NHS organisation connecting your product to real patient records.
How to integrate with EMIS
- 1
Scope data flows and governance
Define the read/write data you need and establish the lawful basis and information-governance approach.
- 2
Join the EMIS partner programme
Engage EMIS to become an approved partner and obtain access to partner APIs and documentation.
- 3
Secure IM1 access
Obtain the appropriate IM1 pairing agreement for EMIS clinical system access.
- 4
Complete DSP Toolkit and clinical safety
Achieve a satisfactory NHS DSP Toolkit status and produce DCB0129/DCB0160 clinical safety documentation.
- 5
Validate and deploy with the organisation
Test in a controlled environment and coordinate go-live and configuration with the NHS body.
Common use cases
- Patient access apps for appointments, prescriptions, and messaging
- Risk stratification and population health across primary care networks
- Automation of recalls, referrals, and administrative workflows
- AI summarisation of the GP record under appropriate governance
Workflow example
Medication review prioritisation
- App reads relevant medication and condition data from EMIS via partner/IM1 APIs.
- A model flags patients due for structured medication reviews and ranks by risk.
- The prioritised list surfaces in the practice's workflow for clinician action.
- Outcomes and any writes are recorded and logged for audit.
Frequently asked questions
What is EMIS-X?
EMIS-X is EMIS's next-generation, cloud and API-led platform direction, intended to modernise integration and interoperability compared with the established EMIS Web system. It emphasises API-led, increasingly FHIR-aligned access.
Is EMIS integration similar to SystmOne?
Yes — both are NHS GP systems reached through the IM1 framework and partner programmes, under the same UK GDPR, NHS DSP Toolkit, and clinical safety requirements. The vendor-specific APIs and onboarding differ, so each needs its own implementation.
How long does NHS integration take?
It varies, but the assurance steps — partner approval, IM1 agreement, DSP Toolkit, and clinical safety — typically dominate the timeline over the engineering itself. Planning for them early is essential.
What is IM1 and why does it govern EMIS integration?
IM1 (Interface Mechanism 1) is the NHS Digital framework under which principal GP system suppliers such as EMIS must expose interfaces to approved third parties. It is the contractual route to EMIS patient data, not merely a technical one: you need an IM1 pairing agreement covering the specific data flows your product uses, and each GP practice must consent to the connection. Budget for the agreement and per-practice enablement as first-class delivery work.
Integrating with EMIS for the NHS? We handle partner APIs, IM1, DSP Toolkit, and clinical safety. Book a discovery call to scope your build.