Responsible Local Authority from Address
The challenge facing NHS Trusts that need to make referrals to Social Care include:
- NHS Trusts deal with multiple Local Authorities
- Health system / end user does not know which Local Authority is responsible for providing Social Care for a patient
- Manual checking of responsible Local Authority is time consuming
- System / user may not know the appropriate format and/or current address to send a referral to, once the LA has been determined.
- Existing tools work on Postcode, however many Postcodes span Local Authority boundaries (see below)
The Healthcare Service Locator API is service that NHS Trusts can use to identify which Local Authority is responsible for a patient (i.e. based on their home/main address), the service will also return the preferred Endpoint(s) for the required Healthcare Service. It operates at the property/building level, so will still provide the correct result where postcodes straddle Local Authority boundaries
The diagram below show the system interactions:
HTTPS Request
Method:
GET
Host Environments:
Environment | Host |
---|---|
Test | fhir-test.nottinghamshire.gov.uk |
Live | fhir.nottinghamshire.gov.uk |
Base URL:
/LocatorService/v2/HealthcareService
Query Parameters:
Name | Card. | Type | Note |
---|---|---|---|
_query | 1..1 | Fixed: "responsibleLAfromAddress" | Additional query types could be supported in future versions, e.g. Responsible LA from GPS Co-ordinates |
address | 1..1 | string | The address should be comma separated, however, because the comma has special meaning in FHIR, each comma in the parameter value should be escaped with a preceding '\'. The address parameter is case insensitive. The value SHALL be URL Encoded |
postcode | 1..1 | string | The postcode parameter is case insensitive & can be supplied with or without a space. The value SHALL be URL Encoded |
type | 1..1 | coding | Coding for the type of Social Care Sevice required.Binding: LocatorService-HealthcareServiceTypeNote: Currently only http://snomed.info/sct|715591000000108 is suppported. Additional HealthcareService types could be supported in future versions, e.g. "GP Referral to Social Care". The value SHALL be URL Encoded. |
The HTTP GET will consist of 'https
See examples for an illustration of a search query and respective URL encoding
Response
The API Resposne will be a single Bundle Resource with Zero or One HealthcareService entries:
Profiles
StructureDefinition | Version |
---|---|
CareConnect-LocatorService-HealthcareService-1 | 0.0.1 |
CareConnect-LocatorService-Organization-1 | 0.0.1 |
CareConnect-LocatorService-Location-1 | 0.0.1 |
LocatorService-Endpoint | 0.0.1 |
Extensions | Version |
---|---|
tbc | tbc |
ValueSets | Version |
---|---|
LocatorService HealthcareServiceType | 0.0.1 |
LocatorService OrganizationType | 0.0.1 |
CodeSystems | Version |
---|---|
ODS API Organization Role | 1.12.0 |
Further details of the StructureDefinitions, including tree and table structures, are available here
Examples
Search Query
Unencoded query string
https
URL Encoded version
https
Responses
Example 1 - Response for Local Authority in a two tier structure that supports FHIR and Email Referrals
The resposne below is for the same Address **except** that the building number is '15' instead of '23'. Although on the same street with an identical Postcode, the Responsible Local Authority is different. Example 2 - Response for Local Authority in a Unitary structure that supports only Email Referrals