Referrals
Referrals - Data Model
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:
- ReferralRequest - CareConnect-GPC-ReferralRequest-1
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.
| Element | Safe to display to patient / citizen | Useful to display to patient / citizen |
|---|---|---|
| id | ||
| meta.profile | ||
| identifier | ||
| basedOn | ||
| status | ||
| intent | ||
| priority | ||
| serviceRequested | ||
| subject | ||
| context | ||
| authoredOn | ||
| requester | ||
| requester.agent | ||
| requester.onBehalfOf | ||
| specialty | ||
| recipient | ||
| reasonCode | ||
| description | ||
| supportingInfo | ||
| note |
Further Information
Note - Not every element will have further information. Further information is to simply give additional context and perspective to the element.
basedOn
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.
We do not currently expect this element to be present. Consumers should check the availability of this information if they have a use case to present it.
status
Use with caution for PFS
Further information
This element is fixed to ‘unknown’ (only unknown is used).
There is potential for the language 'unknown' to be misunderstood by patients or citizens. This may cause them to take an inappropriate action as a consequence.
intent
Use with caution for PFS
Further information
There is potential for the language 'order' to be misunderstood by patients or citizens. This may cause them to take an inappropriate action as a consequence.
priority
Further information
This is the priority assigned to the referral by the practice making the referral. It does not represent the priority being given to the referral by the recipient.
serviceRequested
Further information
We do not currently expect this element to be present. Consumers should check the availability of this information if they have a use case to present it.
The main coded representation for the referral can be found in ‘reasonCode’. This may be populated if they are supplementary information.
This element is a CodeableConcept, it is advised to use the original term text as your primary clinical term. For more information on 'Processing data from a CodeableConcept', specifically section 'Original term text' then please visit -
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.
authoredOn
Further information
This element is the preferred date for Referrals.
specialty
Further information
We do not currently expect this element to be present. Consumers should check the availability of this information if they have a use case to present it.
The main coded representation for the referral can be found in ‘reasonCode’. This may be populated if they are supplementary information.
reasonCode
Further information
This will carry the main clinical code used for a referral (to identify the type of referral being made). It is not strictly a reason and will often be a SNOMED referral code.
This element is also a CodeableConcept, it is advised to use the original term text as your primary clinical term. For more information on 'Processing data from a CodeableConcept', specifically section 'Original term text' then please visit -
supportingInfo
Further information
This element may reference a referral letter (or other referral related documentation). Much of the detail of a referral is in the referral letter and not in the referral meta data which this carries. However, this won’t always be linked up.
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.