GP Connect - Update Record (ITK3)

Part of the GP Connect product family
A newer version of this specification is available (v1.1.1-public-beta).
An issue was identified with the FHIR package supplied with this version of the specification, which has been rectified.
Please click here to view the patched v1.1.1-public-beta specification with the updated FHIR package.

Patient-facing services and disclosure of information

Parts of the GP record may be visible to a patient within patient-facing services such as the NHS App.

The NHS App enables a parent, family member or carer to provide access services using linked profiles (also referred to as 'proxy access').

It is possible for a patient to request to a healthcare professional (such as a pharmacist) that they do not want individuals with proxy to be able to access some/all of their information about the care they have received - for example, if discussing a sensitive issue.

The meta.security element within any profile can be used to pass this information across with a simple code NOPAT which will inform the GP that the information received should not be disclosed to anyone else without the provider or patient authorisation.

Using meta.security

The meta.security element within the CareConnect-GPC-Encounter-1 FHIR profile can be used to pass this information across with a simple code NOPAT which will inform the GP that the information received SHOULD NOT be disclosed anyone else without the provider or patient authorisation.

Note: This specification requests that the non-disclosure code be used where relevant for the entire Encounter (and all information contained) rather than individual FHIR profiles to avoid complexity. 
<Encounter xmlns="http://hl7.org/fhir">
    <meta>
        <security>
            <system value="http://terminology.hl7.org/CodeSystem/v3-ActCode" />
            <code value="NOPAT" />
            <display value="no disclosure to patient, family or caregivers without attending provider's authorization" />
        </security>
    </meta>
    ...
</Encounter>
back to top