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 9

Context of Issue
Context:	Extension-UKCore-CodingSCTDescDisplay (Extension)
Type:	Implementation Guide
Source:	UK Core Development Team
Scope:	Proposed In Scope

Issue	Proposal
The IG guidance states that if the sct-descId is sent, then the UK Core sctdescDisplay SHALL be used.	Initial Proposal: The requirement should be changed from SHALL to MAY. Click here Main Points Raised in C&TA Calls: Kevin Sprague: There’s a live vendor issue suggesting UK Core diverges from base FHIR behavior; reviewing; may need options (including deprecation). Ann Wrightson: While under review, relaxing to MAY helps implementers and reduces harm. Charlie McCay: This should be solved internationally (HL7 + SNOMED), not by a UK only extension; avoid extending extensions; basic FHIR–SNOMED integration must be straightforward. Ryan May: Context: the need was to send a non preferred term text alongside the conceptId; past misuse included sending descriptionIds as codes.

Issue

Proposal

The IG guidance states that if the sct-descId is sent, then the UK Core sctdescDisplay SHALL be used.

Initial Proposal:

The requirement should be changed from SHALL to MAY.

Click here

Main Points Raised in C&TA Calls:

Kevin Sprague:

There’s a live vendor issue suggesting UK Core diverges from base FHIR behavior; reviewing; may need options (including deprecation).

Ann Wrightson:

Charlie McCay:

This should be solved internationally (HL7 + SNOMED), not by a UK only extension; avoid extending extensions; basic FHIR–SNOMED integration must be straightforward.

Ryan May:

Context: the need was to send a non preferred term text alongside the conceptId; past misuse included sending descriptionIds as codes.