How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

EMIS Health Patient Matching API

The patientMatching API from EMIS Health — 4 operation(s) for patientmatching.

EMIS Health Patient Matching API is one of 12 APIs that EMIS Health publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Patient Matching. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, an API reference, and authentication docs.

This API exposes 4 operations across 4 paths, and defines 31 schemas. It is described by OpenAPI 3.2.0, at version 1.2.

Requests are made against the base URL https://api.platform.emis-x.uk/partner.

4 operations 4 paths 31 schemas 4 GET

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.2
Base URL
https://api.platform.emis-x.uk/partner
Authentication
HTTP Bearer, OAuth 2.0
Resource Areas
1

Authentication & Security 2

EMIS Health Patient Matching API declares 2 security schemes for authenticating requests. It accepts HTTP bearer tokens (JWT) (bearer). It supports OAuth 2.0 (OAuth2CodeEMIS-X-GP-PAPI) using the authorizationCode flow, exposing 7 scopes.

Paths & Operations 4

Across 4 paths, the API surfaces 4 operations — 4 GET. Each is listed below with its method, path, parameters, and response codes.

patientMatching 4
GET
/api/v1/patientMatching/GetChangedPatients
Get changed patients
GetChangedPatients 2 params → 500400401404415200
GET
/api/v1/patientMatching/GetChangedPatientsMR
Get changed patients MR
GetChangedPatientsMR 2 params → 500400401404415200
GET
/api/v1/patientMatching/GetMatchedPatients
Get matched patients
GetMatchedPatients 2 params → 500400401404415200
GET
/api/v1/patientMatching/GetPatientSequence
Get patient sequence
GetPatientSequence 3 params → 500400401404415200

Schemas 31

The contract defines 31 schemas that model the data the API accepts and returns. The most detailed are PartnerApi.EmisOpen.PatientMatches37.PatientMatchesPatient (57 properties), PartnerApi.EmisOpen.PatientMatches37.PersonType (49 properties), PartnerApi.EmisOpen.PatientMatches37.AddressType (11 properties), PartnerApi.EmisOpen.PatientMatches37.PersonCategoryType (9 properties). Each schema is shown below with its type and property counts.

PartnerApi.EmisOpen.PatientMatches37.StringCodeTypeScheme
integer
PartnerApi.EmisOpen.PatientMatches37.PersonCategoryTypePurpose
integer
PartnerApi.EmisOpen.PatientMatches37.PersonTypeScripts
integer
PartnerApi.EmisOpen.PatientMatches37.RoleType
object
8 properties
PartnerApi.EmisOpen.PatientMatches37.PersonTypeRegistrar
integer
PartnerApi.EmisOpen.PatientMatches37.PersonTypeTwentyFourHour
integer
PartnerApi.Service.Model.ErrorResponse
object
4 properties
PartnerApi.Service.Model.Issue
object
4 properties
PartnerApi.EmisOpen.PatientMatches37.PersonTypeDoctor
integer
PartnerApi.Service.Model.SeverityType
integer
PartnerApi.Service.Model.Text
object
2 properties
PartnerApi.EmisOpen.PatientMatches37.PersonTypeConsulter
integer
PartnerApi.EmisOpen.PatientMatches37.IdentType
object
5 properties
PartnerApi.EmisOpen.PatientMatches37.ApplicationType
object
7 properties
PartnerApi.EmisOpen.PatientMatches37.RegistrationTypeDead
integer
PartnerApi.Service.Model.Details
object
2 properties
PartnerApi.EmisOpen.PatientMatches37.PersonTypeLocum
integer
PartnerApi.Service.Model.Coding
object
3 properties
PartnerApi.EmisOpen.PatientMatches37.StatusType
object
8 properties
PartnerApi.EmisOpen.PatientMatches37.PersonCategoryType
object
9 properties
PartnerApi.EmisOpen.PatientMatches37.IntegerCodeType
object
7 properties
PartnerApi.EmisOpen.PatientMatches37.AddressType
object
11 properties
PartnerApi.EmisOpen.PatientMatches37.RegistrationTypeCustomRegistrationEntry
object
2 properties
PartnerApi.EmisOpen.PatientMatches37.PersonTypeContraceptive
integer
PartnerApi.EmisOpen.PatientMatches37.StringCodeType
object
7 properties
PartnerApi.EmisOpen.PatientMatches37.PersonTypeContractualRelationship
integer
PartnerApi.EmisOpen.PatientMatches37.PatientMatches
object
2 properties
PartnerApi.EmisOpen.PatientMatches37.PersonTypeChildSurveillance
integer
PartnerApi.EmisOpen.PatientMatches37.PatientMatchesPatient
object
57 properties
PartnerApi.EmisOpen.PatientMatches37.PersonTypeMinorSurgery
integer
PartnerApi.EmisOpen.PatientMatches37.PersonType
object
49 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

emis-health-patientmatching-api-openapi.yml Raw ↑

Other APIs EMIS Health publishes across the network.

EMIS-X App Launch
EMIS-X Analytics
EMIS Health Appointments API
EMIS Health CORS API
EMIS Health API
EMIS Health Medical Record API
EMIS Health Organisation API
EMIS Health Patient API
EMIS Health Search API
EMIS Health Swagger API
EMIS Health User API
Where this information came from

This is an independent, third-party profile of EMIS Health Patient Matching API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.