TPP (SystmOne)
TPP (The Phoenix Partnership) is a UK healthcare software company founded in 1997 and headquartered in Leeds, England. Its flagship clinical system, SystmOne, is one of the two dominant GP electronic health record platforms in England (alongside EMIS Web) and holds more than 61 million patient records shared across the NHS, serving over 300,000 users and 7,800+ organisations spanning general practice, hospitals, urgent care, mental health, community, and social care. TPP does not operate a public self-serve developer portal; integration is a gated, partner-conformance process. Third parties integrate with SystmOne through NHS England's Interface Mechanism 1 (IM1 Transaction, Bulk, and Patient Facing Services APIs) and the national GP Connect FHIR programme, both governed by the Digital Care Services (DCS) framework and a Supplier Conformance Assessment List (SCAL) approved by NHS England. TPP additionally publishes its own downloadable interface specifications - the SystmOne Client Integration API (XML over a TCP socket), a Patient Facing Services (PFS) API, a Generic HTML API, and a Telephony API - and a formal Integration Request process. Home market is the United Kingdom, exclusively within the NHS.
More than an index entry, but the surface is still mostly links rather than artifacts — the cohort most likely to move a full band from modest, well-targeted work.
API Evangelist profiles TPP (SystmOne) the way a machine reads it — 8 machine-readable artifacts across 6 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — TPP (SystmOne) scores 28.0/100 (emerging), with a separate agent-readiness read of 14/100 (human only). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile TPP (SystmOne)
Each block below is one kind of artifact we hold for TPP (SystmOne). For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 6
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
SystmOne Client Integration API
TPP's local client-integration interface allowing an approved third-party application to interact with a running SystmOne client. Communication is performed with XML documents (...
SystmOne Patient Facing Services (PFS) API
TPP's Patient Facing Services API, enabling patient-facing applications to interact with SystmOne for services such as appointment booking, prescription requests, and record acc...
SystmOne Generic HTML API
TPP's Generic HTML API for embedding and launching third-party web content in context within the SystmOne client. Distributed as a downloadable specification package. Access req...
SystmOne Telephony API
TPP's Telephony API for integrating telephony systems with SystmOne, supporting computer-telephony workflows such as inbound-call patient matching. Distributed as a downloadable...
Interface Mechanism 1 (IM1)
The NHS England national integration route by which approved third-party applications connect directly to GP clinical systems including TPP SystmOne. IM1 comprises the Transacti...
GP Connect (FHIR)
GP Connect is NHS England's national FHIR-based interoperability programme. TPP SystmOne clinical records are exposed through GP Connect's FHIR API for authorised record viewing...
Security Posture 2
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Resources
Every other property we hold for TPP (SystmOne) — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Get Started 2
Portal, sign-up, and the first successful call
Documentation 1
Reference material describing how the API behaves
Agent Surfaces 2
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 2
Pagination, idempotency, versioning, errors, and events
Access & Security 4
Authentication, authorization, and security posture
Operate 1
Status, limits, changes, and where to get help
Commercial 1
Pricing, plans, and the legal terms of use
Company 2
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/tpp-systmone · machine-readable index on apis.io