You are invited to review the Clinical and Technical Assurance Sprint 2 Documentation Pack. The purpose of this documentation pack is to provide a Subject Matter Experts (SMEs) review pack for the Allergy Intolerance profile for the purpose of Clinical and Technical Assurance(C&TA).
- The review period of the review pack is 3 weeks from 8th March - 26th March.
- A consolidated feedback review and disposition call will be held on 9th April 9:30-11:30 to discuss your feedback.
This pack contains the guidance and reference material required to participate in the Sprint 2 of Clinical and Technical Assurance. The content of the UK Core to be reviewed is contained in the UK Core Snapshot.
The Sprint 2 of the clinical and technical assurance process is building on the work done in the Sprint 1 and assuring the first clinical profile for inclusion in the candidate ‘HL7 FHIR UK Core Implementation Guide R4’ in development.
The ‘HL7 FHIR UK Core Implementation Guide R4’ is proposed to form a foundation for derivative FHIR Implementation Guides in development in a UK context and is based on the international standard that is common in other countries such as Canada, the US and Australia.
The scope for Sprint 2 is Allergy Intolerance profile along with associated FHIR conformance assets such as Extension, CodeSystems, ValueSets and ConceptMaps
The purpose of the Sprint 2 is to iteratively build a Minimum Viable Product candidate release of a candidate ‘HL7 FHIR UK Core Implementation Guide R4’ which is planned would go through an HL7 UK ballot process. Based on the feedback the scope of further sprints will be developed working with the community and will be used to improve the process. Future Clinical and technical assurance will target prioritised use cases from the service, vendors, and NHS arm’s length bodies.
The key value add of the process is the multi-disciplinary collaboration in an agile team and ability to improve quality of the product. It helps stakeholders, including vendors, to understand the rationale and details behind the design based on use cases. The vendors can raise implementation issues and resolve these issues before the specifications are published. The process promotes consistency in FHIR assets across different programmes and use cases to support interoperability.
The guidance on how to leave feedback is available here.
If you have any other questions, please email us at NHS Digital