WARNING
This guidance is under active development by NHS England and content may be added or updated on a regular basis.Scenario - Request Proxy Access
Actors
Name | Type | Description |
---|---|---|
Client Application | System | The application the Proxy uses to create the request. IHE refers to this as the Consent Recorder |
NHS England Proxy Service | System | NHS England National Proxy Service |
National Proxy Registry | System | NHS England National Proxy Data Registry. IHE refers to this as the Consent Registry |
Primary Care | System | General Practice System |
Use Case(s)
Background Standards
Request Proxy Access
The sequence diagram below is a high level view of the actual process which focuses on the interactions exchanged between the actors.
Submit Proxy Access Request
The Client Application creates a FHIR QuestionnaireResponse which matches the FHIR Questionnaire definition Proxy Access Request.
This request is then submitted to the national proxy service via FHIR RESTful API
POST https://proxyservice.example.nhs.uk/FHIR/R4/QuestionnaireReponse
Event Payload Example
Store Proxy Access Request
The proxy access request is stored on the National Proxy Registry. The process followed is HL7 Structured Data Capture Form Data Extraction which takes the FHIR QuestionnaireResponse and creates:
- Consent
- RelatedPerson
on the National Proxy Registry