Abeyance and Dispersal GPs

Open data API in a single place

Provided by NHS Digital

Get early access to Abeyance and Dispersal GPs API!

Let us know and we will figure it out for you.

Dataset information

Country of origin
Updated
Created
Available languages
English
Keywords
Quality scoring

Dataset description

Abeyance and Dispersal GP Codes Contains: Usually, when a GP retires or leaves a practice, a successor is appointed prior to the departure of the outgoing GP. In such cases, if the GP in question holds their own 'list' of patients on the Practice and NHAIS systems, these are transferred to the new GP (referred to as the successor) using bulk transfer processes. There are, however, two circumstances where this is not possible: Where a successor has yet to be appointed, the NHAIS system currently offers the facility to set the individual GP list to 'abeyance'. This leaves the patients technically registered with the departing GP until a successor can be obtained. In practice, the patients are usually still treated by the remaining partners in the practice, or sometimes a locum is employed temporarily by the practice. This process ensures the practice list is still calculated appropriately for payment. When a successor is not actively being sought, the NHAIS dispersal function is used; patients registered with the GP are written to advising them to register with a new GP. In order to ensure that NSTS and PDS are correct, it is necessary to set up Abeyance/Dispersal codes; these take the form of GP Practitioner format codes which relate to a practice rather than an individual GP, and ODS has responsibility for this.
European data infrastructure with broad catalog discovery, free evaluation access and production-grade API options.
190K+
indexed dataset pages
32
countries and EU institutions
2019
API-first since
Free API quota
for evaluation and prototypes
SLA
history and push on production APIs
FAQ

Questions before production use

Practical answers on evaluation, licensing, freshness, versioning and support.

api.store is built and operated by Apitalks s.r.o. Company details and a direct contact path are linked in the footer for vendor checks and procurement review.
Yes. Selected APIs include a free API quota, so your team can validate coverage, freshness, response shape and workflow fit before asking for a production plan.
Often yes, but usage rights depend on the source license and dataset. We surface source, license and update metadata where available, and can help review terms before a production integration.
Maintained APIs include update metadata where available. For production integrations, we can add history, monitoring and push updates so changes are easier to detect and act on.
Production APIs can add SLA, stable identifiers, versioning support, history, push updates and direct support around the data your product or AI workflow depends on.

Didn't find the API you need?

Let us know and we will figure it out for you.

European data discovery with free evaluation access and production-grade API options.

Copyright © 2026. Made by Apitalks