EHR Systems
SystmOne vs EMIS
SystmOne (by TPP) and EMIS are the two dominant clinical systems in NHS primary care. For any product targeting GP practices, primary care networks, or community services, these are the systems you must integrate with — and the path runs through NHS frameworks rather than a simple commercial sign-up. This comparison looks at SystmOne vs EMIS through an integrator's lens: the IM1 mechanism, APIs, market presence, onboarding, and the NHS governance that surrounds both.
Overview of each system
SystmOne, developed by TPP, is widely used across GP practices, community, and other care settings, and is known for a shared, centralised model of the patient record across organisations using it. EMIS (EMIS Web, moving toward the cloud-based EMIS-X platform) is the other primary-care heavyweight, with a large GP install base. Both are deeply embedded in NHS primary care, and both are reached through NHS-approved integration routes rather than open public APIs.
Integration: IM1 and APIs
Integration with both runs primarily through the NHS IM1 (Interface Mechanism) pairing framework, which grants controlled read and/or write access under partner agreements and information governance. EMIS-X emphasises a more modern, API-led and increasingly FHIR-aligned direction, while national NHS APIs and shared-record standards complement both. The headline point for builders: the technical access is gated by NHS approvals, partner programmes, and assurance — these, not the code, usually set the timeline.
Onboarding, compliance, and clinical safety
Both require the same NHS assurance: an appropriate IM1 agreement, a satisfactory NHS Data Security and Protection Toolkit status, and DCB0129/DCB0160 clinical safety documentation, all underpinned by a clear lawful basis and information governance. The vendor-specific partner processes differ between TPP and EMIS, but the overall shape — approvals, governance, and clinical safety alongside the engineering — is common to both. Plan for these from day one of an NHS-facing product.
Feature comparison
| Feature | SystmOne (TPP) | EMIS |
|---|---|---|
| Vendor | TPP | EMIS Health |
| Primary integration route | NHS IM1 framework | NHS IM1 + EMIS partner APIs |
| Modern platform direction | SystmOne (centralised record model) | EMIS-X (cloud, API-led) |
| Market | GP, community, wider care settings | Large GP install base |
| FHIR alignment | Via NHS APIs / standards | Increasing with EMIS-X |
| Governance required | DSP Toolkit + DCB safety | DSP Toolkit + DCB safety |
| Onboarding | TPP partner + IM1 | EMIS partner + IM1 |
Which should you choose?
National primary-care coverage
Integrate with both — together they cover most NHS GP practices.
Community and multi-setting care
SystmOne's broader care-setting footprint is an advantage.
Modern API-led integration
EMIS-X's direction may suit cloud-native, FHIR-aligned builds.
Fastest route to a pilot
Start with whichever system your initial practice partners run.
Verdict
For NHS primary care you usually can't pick just one — SystmOne and EMIS together cover the vast majority of GP practices, so national products integrate with both. SystmOne brings a broad, multi-setting footprint and centralised record model; EMIS brings a large GP base and a cloud, API-led direction via EMIS-X. The integration route (IM1), governance (DSP Toolkit), and clinical safety (DCB) are common to both — and they, not the code, are the critical path.
Frequently asked questions
Do I need to integrate with both SystmOne and EMIS?
For broad NHS primary-care coverage, usually yes — they are the two dominant GP systems, so national products typically support both. For a pilot, you can start with whichever system your first practice partners use.
Is integration the same for both?
The route is similar — both use the NHS IM1 framework with partner agreements, DSP Toolkit, and DCB clinical safety. The vendor-specific partner processes and APIs differ, so each still needs its own implementation and approvals.
What is EMIS-X?
EMIS-X is EMIS's next-generation, cloud and API-led platform direction, intended to modernise integration compared with EMIS Web, with increasing FHIR alignment.
Building for NHS primary care? We handle SystmOne and EMIS integration — IM1, DSP Toolkit, and clinical safety end to end. Book a discovery call.