Atomic Unit to capture the consent status for a patient.
Important: This site is under development by NHS Digital and is intended to provide all the technical resources you need to successfully develop the End of Life API.
Warning: This site is information only, intended for those engaged with NHS Digital on the development of the End of Life API. You are advised not to develop against these specifications until a formal announcement.
Consent
When a patient has a record created on the EPaCCS they will discuss whether they consent to electronic record sharing. Some systems do not record refusal to share as such, because if patients refuse to share then there is just no record created.
Other systems may not have a specific consent for sharing the EoL dataset bundle, this may be included in a wider discussion and decision with reference to information sharing.
The following FHIR profiles are used to form the Consent Atomic Unit:
- EOL-Patient-1
- CareConnect-Organization-1
- CareConnect-Practitioner-1 (EOL mandates name.text)
- CareConnect-PractitionerRole-1
- EOL-Consent-1
Consent data item mapping to FHIR profiles
The consent data item are fulfilled by elements within the FHIR resources listed below:
| EOL Data Item | FHIR resource element | Mandatory/Required/Optional | Notes |
|---|---|---|---|
| Consent Status | EOL-Consent-1.status | Mandatory | Active = Consent Given, Inactive = Consent Refused. |
| Consent Decision Details | EOL-Consent-1.consentDecisionDetails (Extension) | Optional | |
| Consent Discussion Details | EOL-Consent-1.consentDiscussionDetails (Extension) | Optional | |
| Date of change in consent status | EOL-Consent-1.dateTime | Mandatory | |
| Professionals recording this consent status | EOL-Consent-1.consentingAuthor (Extension) | Mandatory |
EOL-Consent-1.consentDiscussionDetails (codeableConcept) Guidance
Where the sending system supports a terminology system:
- The codeableConcept.coding element MUST be populated with:
- system: identity of the terminology system (e.g. SNOMED-CT)
- code: symbol in syntax defined by the system
- display: representation defined by the system
- the codeableConcept.text field MUST be populated with the display value from the codeableConcept.coding.display element e.g. ‘Asthma (disorder)’
- the codeableConcept.text field MAY contain free text to capture more detail associated with the codeableConcept.coding.code e.g. ‘Patient uses blue inhaler to relieve symptoms’
Where the sending system does not support a terminology system:
- the codeableConcept.text field MUST be populated with a text description of the concept as a human readable narrative e.g ‘Asthma’.
- the codeableConcept.text field MAY contain free text to capture more detail associated with the concept e.g. ‘Patient uses blue inhaler to relieve symptoms’.