SystmOne vs EMIS: A Practical Analytics Comparison for ICBs and PCNs

SystmOne (TPP) and EMIS (EMIS Health) together cover the vast majority of UK general practice. ICBs and PCNs that span both face a practical analytics question: how do you unify reporting across two EHRs that look superficially similar but model data differently? The honest answer involves both technical and operational work.

Where the two are similar

• Both use SNOMED CT as the primary clinical coding system (since Read codes were retired).
• Both expose population reporting tools — SystmOne's reports module and EMIS's Population Reporting / EMIS Search and Reports.
• Both feed national systems (QOF achievement, GP Connect, NHS Spine).
• Both support QOF and IIF measure calculation natively, with the same indicator set.

Where they diverge

1. Data model details. SystmOne's data model centers on the “event” — every clinical action is an event with metadata. EMIS organizes around the “consultation” with sub-records. Same conceptual data, different access patterns.
2. Search syntax. SystmOne's Reports module and EMIS's Population Reporting use different search-builder syntaxes. A QOF query built in one cannot be copy-pasted to the other.
3. Data export. SystmOne SLAM access is controlled by TPP at the ICB level. EMIS's data export controls are managed differently. Cross-EHR ICB-level reporting requires coordination of access pathways.
4. Performance characteristics. The same indicator query on the same patient cohort can take quite different times to run on the two platforms depending on indexing.

The ICB / PCN analytics challenge

For a PCN with a mix of SystmOne and EMIS practices, four operational realities apply:

• QOF achievement at the PCN level requires harmonizing rates across EHRs. The SNOMED codes are the same, but the export schemas aren't.
• IIF measure rollups have the same issue at the PCN level.
• Patient-level lists for outreach must be deduplicated if patients move between practices.
• ICB-wide views need both EHRs in the same analytics layer.

The pragmatic approach

Several patterns work:

1. Direct connector to both. Vizier's SystmOne and EMIS connectors pull data from each via the same analytics layer. SNOMED mapping is normalized centrally.
2. Scheduled CSV export to a shared analytics warehouse. Workable if your ICB has BI capacity to maintain the warehouse.
3. EHR-by-EHR reporting with manual aggregation. The default many PCNs end up with. Functional but slow.

What 2026 ICB / PCN leadership should ask

• Can we see QOF and IIF achievement at PCN level, today, without waiting for end-of-month?
• Can we cross-reference patient cohorts across SystmOne and EMIS practices in our PCN?
• Does our analytics layer support both EHRs natively, or just one?

See the NHS QOF/IIF 2026 picture for the broader context.