Stream: uk
Topic: UK Core 0.3.0 Pre-release Review
Ben McAlister (Jan 28 2022 at 16:19):
Message from the UK FHIR Delivery Senior Leadership Team
The version of UK Core (0.3.0 Pre-Release) that has been updated following Sprint 4 of Clinical and Technical Assurance is now available as a pre-release for review.
This Implementation Guide is available here and the changes which have been applied to this version(0.3.0) are documented here.
The issues that were highlighted in the UK Core and proposed changes are detailed here.
There is now an opportunity for anyone who wishes to review and raise issues during a two week review period. The review runs from 27th January 2022 until 10th February 20022 . Issues can be raised here (requires Simplifier.net account registration).
Important Note: The raising of issues should only be related to the changes done for the Sprint 4 and this is not intended to be a full review of the implementation guide. This version (0.3.0 Pre-Release) will be updated following any necessary rework and become 0.4.0 forming the base for Implementation Guide 0.5.0 which is the version to be used for the Sprint 5 of Clinical and Technical Assurance.
Also Note: that this is distinct from the current HL7 UK Ballot on UK Core 0.1.0. Feedback from that formal process will be integrated into newer versions at a later date.
For more information on the HL7 UK Ballot progress see the HL7 UK Website
Cooper Thompson (Jan 28 2022 at 17:31):
One of the really interesting things we noticed in UK Core (which we did comment on in the ballot) is the approach of including workflow requirements embedded in the interop spec. For example, The UK Core AllergyIntolerance Guidance has a blurb about the consuming system MUST prevent prescribing while degraded drug allergies are present in the patient record. Ballot comments aside, I'm curious what folks think about this sort of approach in FHIR specs.
F Leen (Feb 07 2022 at 11:33):
Hi. May I ask a question, apologies in advance if answered elsewhere. Why are countries defining their own fhir standards rather than using R4 to begin and extending for the few exceptions ?
Kevin Mayfield (Feb 07 2022 at 11:41):
UK Core does use the core FHIR standard. What is does do is add some UK rules and guidances on top. E.g. for Patient we say (English/Welsh) NHS Number is represented as
{
"system": "https://fhir.nhs.uk/Id/nhs-number",
"value": "9000000009"
}
Kevin Mayfield (Feb 07 2022 at 11:43):
In the UK, the NHS uses the UK edition of SNOMED. So we have some rules around that. (Not so much rules but hints)
F Leen (Feb 07 2022 at 11:58):
Thank you for the quick answer Kevin! I found this explanation from google useful too: For instance, recording a patient's ethnicity is not allowed in certain regions, but required in others. Using profiles, the FHIR base specification can define and require an "ethnicity" extension in accordance with the regional policies. Therefore, profiles help countries, regions, districts, and organizations customize data in accordance with their healthcare data regulations and needs.
Last updated: Apr 12 2022 at 19:14 UTC
