[DRAFT] GP Connect (Patient Facing) Access Record - FHIR API

This guidance is under active development by NHS Digital and content may be added or updated on a regular basis.

Uncategorised data

Uncategorised Data - Data Model

Note - This clinical area differs from others in that whilst other clinical areas represent a standard attribution of data in the GP clinical systems. This area is to represent those other areas where there is inconsistent attribution across clinical concepts such as procedures, family history, measurements and many more. As these boundaries are not consistent, we have decided to represent them in a single clinical area. We understand that this is unlikely to be the manner in which a Consumer wants to represent this data.

It is expected that Consumers will either use this data along with other clinical areas to create aggregated journal type views or use subsets of this data. Or by Identifying categories of coding that meets a specific need for the application, for example representing end of life information.

As a general recommendation, we do not expect this to be useful to the patient / citizen by just presenting this as full clinical area in isolation.

Patient Facing Services incorporates the GP Connect data model, this contains guidelines on how Providers need to populate each of the FHIR resources. It is advised to read the data model first, to understand how this is being populated by GP clinical systems.

The relevant profiles in the data model are as follows:

However, not all clinical information stored on GP systems may be safe to display for the end user (patients / citizens). This guide is intended to help Consumers understand what is clinically safe and useful to display via PFS from the GP Connect data model. Please see the PFS recommendations below.


PFS Recommendation

  • Safe to display to patient / citizen - With a safety rating of 'High', 'Medium' or 'Low'.

  • Useful to display to patient / citizen - With a recommendation of 'Recommended' or 'Not recommended'.

For example, the element 'Id’ has a safety rating of ‘High’, meaning it can be shown via Patient Facing Services (PFS). However, we believe it may not be useful to display 'Not Recommended' for the patient / citizen. It’s worth noting, there are elements that will have no meaning or have any merit in being displayed such as ‘Id’. For example, some elements are just entities that link data together.

For further information on the labelling please visit Data model labels used within this guidance.

Observation - uncategorised data

Element Safe to display to patient / citizen Useful to display to patient / citizen
id
meta.profile
identifier
status
code
subject
context
effectiveDateTime
issued
performer
value[x]
interpretation
comment
exampleelement
referenceRange
related
component

Observation - blood pressure

Element Safe to display to patient / citizen Useful to display to patient / citizen
id
meta.profile
identifier
status
code
subject
context
effectiveDateTime
issued
performer
comment
bodysite
related

Observation - blood pressure (systolic and diastolic)

Element Safe to display to patient / citizen Useful to display to patient / citizen
component.code
component.valueQuantity
component.dataAbsentReason
component.interpretation
component.referenceRange

Further Information

Note - Not every element will have further information. Further information is to simply give additional context and perspective to the element.


Observation - uncategorised data

code

Further information

This element is a CodeableConcept. The element may include more than one code for the medication and/or more one text description. Consumers are strongly advised to use the original term text as the primary text displayed to the end user (patient / citizen). For more information on 'Processing data from a CodeableConcept', specifically section 'Original term text' then please visit -

https://simplifier.net/guide/uk-core-implementation-guide/Home/Guidance/CodeableConcept-Guidance?version=1.0.0-pre-release


context

Further information

Displaying the element alone will have no meaning to the patient. This is not advised and may cause more confusion than benefit to the user. If a clear business case is portrayed, then this can be utilised in conjunction with other information to represent information free from ambiguity or confusion to the patient / citizen.


issued

Use with caution for PFS

Further information

The ‘issued’ element states the date the result was published, not the date when it was taken.


value[x]

Further information

The ‘value[x]’ element has significant information where it is included but it may also be qualified by other elements such as:

  • ‘value[x]’
  • ‘referenceRange’
  • ‘interpretation’
  • ‘comment’

Note - not all of the bullet point elements will have a value. Some may only have a comment / value or a mix of both.


interpretation

Further information

For added value and context for the end user (patient / citizen), the advised order is as follows: - ‘value\[x]’ - ‘referenceRange’ - ‘interpretation’ - ‘comment’

Note - not all of the bullet point elements will have a value. Some may only have a comment / value or a mix of both.


comment

Further information

For added value and context for the end user (patient / citizen), the advised order is as follows: - ‘value\[x]’ - ‘referenceRange’ - ‘interpretation’ - ‘comment’


referenceRange

Further information

It is advised to display the ‘referenceRange’ in a way in which it is immediately clear and obvious that the range value is not the patient's test result but merely the range. There is also a risk that if the ‘referenceRange’ data is separated, the meaning and context may be lost.

For added value and context for the end user (patient / citizen), the advised order is as follows:

  • ‘value[x]’
  • ‘referenceRange’
  • ‘interpretation’
  • ‘comment’


related

Further information

Displaying the element alone will have no meaning to the patient. This is not advised and may cause more confusion than benefit to the user. If a clear business case is portrayed, then this can be utilised in conjunction with other information to represent information free from ambiguity or confusion to the patient / citizen.


component

Further information

This element is useful, however, there are not many use cases that exist other than blood pressure.


Observation - blood pressure

code

Use with caution for PFS

Further information

This element is a CodeableConcept. The element may include more than one code for the medication and/or more one text description. Consumers are strongly advised to use the original term text as the primary text displayed to the end user (patient / citizen). For more information on 'Processing data from a CodeableConcept', specifically section 'Original term text' then please visit -

https://simplifier.net/guide/uk-core-implementation-guide/Home/Guidance/CodeableConcept-Guidance?version=1.0.0-pre-release

Please ensure you are aware of the design for modelling blood pressures in the GP Connect payload.


context

Further information

Displaying the element alone will have no meaning to the patient. This is not advised and may cause more confusion than benefit to the user. If a clear business case is portrayed, then this can be utilised in conjunction with other information to represent information free from ambiguity or confusion to the patient / citizen.


issued

Use with caution for PFS

Further information

The ‘issued’ element states the date the result was published, not the date when it was taken. The 'effectiveDateTime' element is the most clinically relevant date for the patient / citizen for the majority of anticipated use cases. It is advised to display 'issued' as a secondary item to 'effectiveDateTime' and to clearly distinguish this as secondary information.


related

Further information

Displaying the element alone will have no meaning to the patient. This is not advised and may cause more confusion than benefit to the user. If a clear business case is portrayed, then this can be utilised in conjunction with other information to represent information free from ambiguity or confusion to the patient / citizen.

Note - if you wish to represent diastolic and systolic blood pressure pairings together. For example, in cases where they have not been presented as a triple, the ‘related’ element will enable this functionality, please see 'Representing blood pressure readings from GP systems'.


Observation - blood pressure (systolic and diastolic)

component.code

Further information

This element is a CodeableConcept. The element may include more than one code for the medication and/or more one text description. Consumers are strongly advised to use the original term text as the primary text displayed to the end user (patient / citizen). For more information on 'Processing data from a CodeableConcept', specifically section 'Original term text' then please visit -

https://simplifier.net/guide/uk-core-implementation-guide/Home/Guidance/CodeableConcept-Guidance?version=1.0.0-pre-release

Please ensure you are aware of the design for modelling blood pressures in the GP Connect payload.


component.referenceRange

Not advised for PFS

Further information

This element is advised as unsafe for the reason that there isn't a universal reference range that applies to all citizens for all ages. Furthermore, reference range data can occasionally be generated automatically by GP clinical system. Both circumstances are cause for concerns, as incorrect conclusions may be drawn from the reference range.

back to top