EMIS Health website screenshot

EMIS Health

EMIS Health is a United Kingdom health-technology company and one of the two dominant GP clinical-system providers in the NHS (alongside TPP SystmOne), supplying the EMIS Web electronic patient record used across primary care, community pharmacy, and other care settings. EMIS is migrating from EMIS Web to EMIS-X, a cloud-first platform, and exposes third-party integration through the EMIS Partner Developer Portal at docs.partner.emis-x.uk. The gated partner programme documents a RESTful JSON Partner API (PAPI) covering appointments, the clinical/medical record, patient demographics and matching, organisation lookup and clinical searches, plus EMIS-X App Launch and an EMIS-X Analytics data warehouse. Authentication is OAuth2 / OIDC (Microsoft Entra External ID / Azure AD B2C) using authorization-code, PKCE, and client-credentials flows with scoped JWT access tokens; native HL7 FHIR resource support is documented as upcoming rather than yet available.

EMIS Health publishes 1 API on the APIs.io network: EMIS Partner API (PAPI). Tagged areas include Healthcare, United Kingdom, EHR, EMR, and Interoperability.

EMIS Health’s developer surface includes authentication, sandbox, documentation, API reference, getting-started guide, and 15 more developer resources.

37.3/100 thin ▬ flat Agent 50/100 agent ready Full breakdown ↓
scored 2026-07-27 · rubric v0.5
3 APIs
HealthcareUnited KingdomEHREMRInteroperabilityHL7FHIRPrimary CareNHSClinical DataElectronic Patient Record

Kin Score

Kin Score Kin Score How this is scored →
scored 2026-07-27 · rubric v0.5
Composite quality — 37.3/100 · thin
Contract Quality 9.4 / 25
Developer Ergonomics 11.7 / 20
Commercial Clarity 2.1 / 20
Operational Transparency 0.0 / 13
Governance 0.0 / 12
Discoverability 8.8 / 10
Agent readiness — 50/100 · agent ready
Machine-Readable Contract 18 / 18
Agentic Access Contract 15 / 15
MCP Server 0 / 12
Machine-Readable Auth 10 / 10
Idempotency 0 / 9
Stable Error Semantics 0 / 8
Request/Response Examples 0 / 7
Rate-Limit Signaling 0 / 7
Typed Event Surface 0 / 6
Agent Skills 5 / 5
Well-Known Catalog 4 / 4
Consent & Bot Identity 0 / 3
Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. This rating is computed from github.com/api-evangelist/emis-health: open an issue to ask a question, or submit a pull request to add artifacts. Want it done for you? Prioritized profiling — $2,500 →

APIs 3

Individual APIs this provider publishes, each with its own machine-readable definition.

EMIS Partner API (PAPI)

The EMIS Partner API (PAPI) is a RESTful JSON API for EMIS-X / EMIS Web integration, exposing appointments, the clinical/medical record, patient demographics, patient matching, ...

EMIS-X App Launch

EMIS-X App Launch lets partner applications be launched in-context from within the EMIS-X / EMIS Web clinical workflow, passing an authenticated user and patient context to the ...

EMIS-X Analytics

EMIS-X Analytics provides partner access to an EMIS-X data warehouse with modelled datasets across domains including Community Pharmacy, Incremental Primary Care Views (iPCVs), ...

Security Posture 2

Authentication, domain security, vulnerability disclosure, and trust-center signals.

Emis Health Authentication

http/oauth2/openIdConnect · 2 schemes

SECURITY

Emis Health Domain Security

TLSv1.3 · HSTS · DNSSEC · DMARC

SECURITY

Scopes 1

OAuth scopes governing access to this provider's APIs.

Emis Health Scopes

7 scopes · authorizationCode

7 scopes

SCOPES

Agentic Access 1

Recommended x-agentic-access execution contracts for AI agents.

Emis Health Agentic Access

80 operations · 8 acting

80 operations · 8 acting

AGENTIC

Resources

Get Started 4

Portal, sign-up, and the first successful call

Documentation 2

Reference material describing how the API behaves

Agent Surfaces 4

MCP servers, agent skills, and machine-readable catalogs

Design & Contract 3

Pagination, idempotency, versioning, errors, and events

Access & Security 4

Authentication, authorization, and security posture

Commercial 1

Pricing, plans, and the legal terms of use

Company 1

The organization behind the API

Other 1

Properties that don't map to a standard resource type

Source (apis.yml)

apis.yml Raw ↑
aid: emis-health
url: https://raw.githubusercontent.com/api-evangelist/emis-health/refs/heads/main/apis.yml
name: EMIS Health
kind: company
description: EMIS Health is a United Kingdom health-technology company and one of the two dominant GP clinical-system providers
  in the NHS (alongside TPP SystmOne), supplying the EMIS Web electronic patient record used across primary care, community
  pharmacy, and other care settings. EMIS is migrating from EMIS Web to EMIS-X, a cloud-first platform, and exposes third-party
  integration through the EMIS Partner Developer Portal at docs.partner.emis-x.uk. The gated partner programme documents a
  RESTful JSON Partner API (PAPI) covering appointments, the clinical/medical record, patient demographics and matching, organisation
  lookup and clinical searches, plus EMIS-X App Launch and an EMIS-X Analytics data warehouse. Authentication is OAuth2 /
  OIDC (Microsoft Entra External ID / Azure AD B2C) using authorization-code, PKCE, and client-credentials flows with scoped
  JWT access tokens; native HL7 FHIR resource support is documented as upcoming rather than yet available.
image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/apis-json-logo.jpg
tags:
- Healthcare
- United Kingdom
- EHR
- EMR
- Interoperability
- HL7
- FHIR
- Primary Care
- NHS
- Clinical Data
- Electronic Patient Record
created: '2026-07-24'
modified: '2026-07-24'
specificationVersion: '0.19'
apis:
- aid: emis-health:emis-partner-api
  name: EMIS Partner API (PAPI)
  description: The EMIS Partner API (PAPI) is a RESTful JSON API for EMIS-X / EMIS Web integration, exposing appointments,
    the clinical/medical record, patient demographics, patient matching, organisation lookup, and clinical searches. Documented
    as OpenAPI 3.0.4 (Partner API v1.2) with 40 operations across the appointments, medicalRecord, patient, patientMatching,
    organisation, search, and user domains. Access is OAuth2 authorization-code with scoped bearer (JWT) tokens.
  humanURL: https://docs.partner.emis-x.uk/papi-overview
  baseURL: https://api.platform.emis-x.uk/partner
  tags:
  - Appointments
  - Medical Record
  - Patient
  - Primary Care
  properties:
  - type: OpenAPI
    url: openapi/emis-health-partner-api-openapi.json
  - type: Documentation
    url: https://docs.partner.emis-x.uk/papi-overview
  - type: APIReference
    url: https://docs.partner.emis-x.uk/openapi/papi
  - type: Documentation
    url: https://docs.partner.emis-x.uk/using-the-partner-api
  - type: Authentication
    url: https://docs.partner.emis-x.uk/auth/
  - type: ErrorCatalog
    url: errors/emis-health-problem-types.yml
  - type: DataModel
    url: data-model/emis-health-data-model.yml
  - type: Overlay
    url: overlays/emis-health-partner-api-overlay.yaml
- aid: emis-health:emis-x-app-launch
  name: EMIS-X App Launch
  description: EMIS-X App Launch lets partner applications be launched in-context from within the EMIS-X / EMIS Web clinical
    workflow, passing an authenticated user and patient context to the integrating application via the shared EMIS-X OAuth2
    / OIDC authentication.
  humanURL: https://docs.partner.emis-x.uk/emisx-app-launch/
  tags:
  - App Launch
  - Interoperability
  properties:
  - type: Documentation
    url: https://docs.partner.emis-x.uk/emisx-app-launch/
  - type: Authentication
    url: https://docs.partner.emis-x.uk/auth/
- aid: emis-health:emis-x-analytics
  name: EMIS-X Analytics
  description: EMIS-X Analytics provides partner access to an EMIS-X data warehouse with modelled datasets across domains
    including Community Pharmacy, Incremental Primary Care Views (iPCVs), OpenSAFELY, Recruit, and IM1 Bulk Extract, browsable
    through the developer portal data explorer.
  humanURL: https://docs.partner.emis-x.uk/getting-started/
  tags:
  - Analytics
  - Data Warehouse
  - Community Pharmacy
  properties:
  - type: Documentation
    url: https://docs.partner.emis-x.uk/getting-started/
common:
- type: AgenticAccess
  url: agentic-access/emis-health-agentic-access.yml
- type: DomainSecurity
  url: security/emis-health-domain-security.yml
- type: Authentication
  url: authentication/emis-health-authentication.yml
- type: OAuthScopes
  url: scopes/emis-health-scopes.yml
- type: WellKnown
  url: well-known/emis-health-well-known.yml
- type: Conventions
  url: conventions/emis-health-conventions.yml
- type: Lifecycle
  url: lifecycle/emis-health-lifecycle.yml
- type: Conformance
  url: conformance/emis-health-conformance.yml
- type: Sandbox
  url: sandbox/emis-health-sandbox.yml
- type: AgentSkill
  url: skills/_index.yml
- type: LLMsTxt
  url: llms/emis-health-llms.txt
- type: Website
  url: https://www.emishealth.com/
- type: DeveloperPortal
  url: https://docs.partner.emis-x.uk/
- type: Documentation
  url: https://docs.partner.emis-x.uk/getting-started/
- type: APIReference
  url: https://docs.partner.emis-x.uk/openapi/papi
- type: GettingStarted
  url: https://docs.partner.emis-x.uk/getting-started/
- type: Onboarding
  url: https://docs.partner.emis-x.uk/onboarding-one/
- type: Authentication
  url: https://docs.partner.emis-x.uk/auth/
- type: OpenIDConfiguration
  url: https://identity.stg.emis-x.uk/b205162c-c95a-4639-8076-bb1fcb152d2b/b2c_1a_clientcredentials/.well-known/openid-configuration
- type: PrivacyPolicy
  url: https://www.emishealth.com/privacy-policy
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com