UK Core Clinical and Technical Assurance Sprint 8 Documentation Pack

Please note:

This is a 'technical sprint'. The scope of this sprint only includes improvements and fixes. New FHIR assets are out of scope for this sprint.
The menu links for 'Use Cases', 'FHIR Assets' and 'Version Comparison' have been removed in this Documentation Pack.

Issue 6

Context of Issue
Context:	UKCore-Observation-AverageBloodPressure (Profile), UKCore-BloodPressure-Average (ValueSet)
Type:	Profile, ValueSet
Source:	UK Core User Community
Scope:	Proposed In Scope

Issue	Proposal
Require clarification of the word 'average' to mitigate clinical risk. The existence of the profile UKCore-Observation-AverageBloodPressure with its wording mentioning 'average' in unclear and creates a potential clinical risk. There is also a lack of 'parameters'.	Need to understand a need for this profile as average has a variation of meaning e.g. 24 hours, 72 hours, 30 days readings etc. Due to the uncertain meaning of average, it is felt clinically to be unsafe to keep this resource. If a resource is required, then keep generic Blood Pressure and then add parameters e.g.: invasive blood pressure, laterality, position etc: By doing this, the ValueSet is more constrained as the VS as-is is too large. Until there is a use case and a requirement, this resource is too risky to pursue as is.

Issue

Proposal

Require clarification of the word 'average' to mitigate clinical risk. The existence of the profile UKCore-Observation-AverageBloodPressure with its wording mentioning 'average' in unclear and creates a potential clinical risk. There is also a lack of 'parameters'.

Need to understand a need for this profile as average has a variation of meaning e.g. 24 hours, 72 hours, 30 days readings etc. Due to the uncertain meaning of average, it is felt clinically to be unsafe to keep this resource. If a resource is required, then keep generic Blood Pressure and then add parameters e.g.: invasive blood pressure, laterality, position etc: By doing this, the ValueSet is more constrained as the VS as-is is too large. Until there is a use case and a requirement, this resource is too risky to pursue as is.