A person who is directly or indirectly involved in the provisioning of healthcare.

0. References

1. Read

Return a single Practitioner for the specified id.

All requests MUST contain a valid ‘Authorization’ header and SHOULD contain an ‘Accept’ header. The `Accept` header indicates the format of the response the client is able to understand, this will be one of the following application/fhir+json or application/fhir+xml.

1.1. Response

A full set of response codes can be found here API Response Codes. FHIR Servers MUST support the following response codes:

200 successful operation
400 invalid parameter
401/4xx unauthorized request
403 insufficient scope
404 resource not found
410 resource deleted

Fetches a bundle of all Practitioner resources for the specified search criteria.

All requests MUST contain a valid ‘Authorization’ header and SHOULD contain an ‘Accept’ header. The `Accept` header indicates the format of the response the client is able to understand, this will be one of the following application/fhir+xml or application/fhir+json.

2.1. Search Parameters

The search parameters that are mandated as a minimum in the API for the Practitioner resource are detailed below.

Query parameters conformance will be categorised as:

MUST - these search parameters MUST be implemented for the specified resource type.

SHOULD - these search parameters are expected to be implemented, if the data to support the query is present in the host system.

Additional search parameters MAY be added to reflect local requirements.

To be conformant, provider systems are required to implement all of the MUST parameters.

The parameters can be used independently to help refine the search results returned.

Name Type Description Conformance Path
identifier token Any identifier for the practitioner (e.g. GMP/GMC code) MUST Practitioner.identifier
name string A server defined search that may match any of the string fields in the HumanName, including family, give, prefix, suffix, suffix, and/or text MUST Practitioner.name

2.1.1. identifier (SDS Id or ODS Code)

See token for details on this parameter.

GET [baseUrl]/Practitioner?identifier=https://fhir.nhs.uk/Id/sds-user-id|123456

Return all Practitioner resources with SDS User ID of 123456.
GET [baseUrl]/Practitioner?identifier=https://fhir.nhs.uk/Id/sds-role-profile-id|G8133438

Return all Practitioner resources that have a ODS Practitioner/Consultant of G8133438

2.1.2. name

See string for details on this parameter.

GET [baseUrl]/Practitioner?name=bernie%20kanfeld

Return all Practitioner resources with name of Bernie Kanfeld.

2.2. Search Response

If the search fails (cannot be executed, not that there is no matches), the return value is a status code 4xx or 5xx with an OperationOutcome.

If the search succeeds, the return content is a Bundle with type = searchset containing the results of the search as a list of resources in a defined order. The result list can be long, so servers MAY use paging. If they do, they MUST use this Paging method for breaking the list into pages if appropriate. The server MAY also return an OperationOutcome resource with additional information about the search.

A full set of response codes can be found here API Response Codes. FHIR Servers MUST support the following response codes:

200 successful operation
400 invalid parameter
401/4xx unauthorized request
403 insufficient scope
404 resource not found
410 resource deleted
## 3. Example ##

3.1 cURL

Return all Practitioner resources for GP Code of G8133438, the format of the response body will be xml. Replace 'baseUrl' with the actual base Url of the FHIR Server. 
curl -X GET -H 'Accept: application/fhir+xml' -H 'Authorisation: BEARER [token]' -v 'https://data.developer.nhs.uk/ccri-fhir/STU3/Practitioner?identifier=G8133438'

3.2 Explore the Response

Explore the response in XML & JSON on the Reference Implementation below 
Reference Implementation

XML GP Code search RI viewer
JSON GP Code search RI viewer

Tags: fhir