Get proxy role
Overview
Use this endpoint to get the details of a proxy role, including current status, based on a provided id.
You can (optionally) include the _include=Consent:performer request parameter to include the proxy's details in the response.
You can (optionally) include the _include=Consent:patient request parameter to include the patient's details in the response.
Access modes
This endpoint supports the following access modes:
- Healthcare worker access
- Application-restricted access
Sandbox test scenarios
You can test the following scenarios in our sandbox environment:
| Scenario | Request | Response |
|---|---|---|
| Retrieve single consenting adult relationship | Valid request with ID 74eed847-ca25-4e76-8cf2-f2c2d7842a7a | HTTP Status 200 Bundle containing a single active proxy relationship |
| Retrieve single consenting adult relationship with patient details | Valid request with ID 74eed847-ca25-4e76-8cf2-f2c2d7842a7a?_include=Consent:patient | HTTP Status 200 Bundle containing a single active proxy relationship with patient details |
| Retrieve single consenting adult relationship with performer details | Valid request with ID 74eed847-ca25-4e76-8cf2-f2c2d7842a7a?_include=Consent:performer | HTTP Status 200 Bundle containing a single active proxy relationship with performer details |
| Retrieve single consenting adult relationship with performer and patient details | Valid request with ID 74eed847-ca25-4e76-8cf2-f2c2d7842a7a?_include=Consent:performer&_include=Consent:patient | HTTP Status 200 Bundle containing a single active proxy relationship with performer and patient details |
| Retrieve single mother-child relationship | Valid request with ID 39df03a2-1b14-4d19-b1dc-d5d8cbf96948 | HTTP Status 200 Bundle containing a single active proxy relationship |
| Retrieve single mother-child relationship with patient details | Valid request with ID 39df03a2-1b14-4d19-b1dc-d5d8cbf96948?_include=Consent:patient | HTTP Status 200 Bundle containing a single active proxy relationship with patient details |
| Retrieve single mother-child relationship with performer details | Valid request with ID 39df03a2-1b14-4d19-b1dc-d5d8cbf96948?_include=Consent:performer | HTTP Status 200 Bundle containing a single active proxy relationship with performer details |
| Retrieve single mother-child relationship with performer and patient details | Valid request with ID 39df03a2-1b14-4d19-b1dc-d5d8cbf96948?_include=Consent:performer&_include=Consent:patient | HTTP Status 200 Bundle containing a single active proxy relationship with performer and patient details |
Sandbox constraints
The sandbox environment has the following constraints for this endpoint:
- Request headers are not tested. X-Request-ID and X-Correlation-ID are disregarded.
Request
- Base URLhttps://sandbox.api.service.nhs.uk/validated-relationships/FHIR/R4
- URLhttps://sandbox.api.service.nhs.uk/validated-relationships/FHIR/R4/Consent/{id}
- Authnone declared. Required headers: Authorization, X-Request-ID
Path parameters
The logical id of the Consent resource
Query parameters
Include referenced resources in the bundle response by specifying one or more _include parameters. Further info here.
Headers
A globally unique identifier (GUID) for the request, which we use to correlate logs through different components. Must be a universally unique identifier (UUID) (ideally version 4). Mirrored back in a response header.
An optional ID which you can use to track transactions across multiple systems. Must be a universally unique identifier (UUID) (ideally version 4). Mirrored back in a response header.
Response
Information successfully returned.
Example response
{
"entry": [
{
"search": {
"mode": "match"
}
}
]
}Changes
No recorded changes to this operation across all 1 revision of this API.