Requirement Specification

This is for collaboration and discussion purposes and is subject to change.

This is not an Implementation Guide

Radiology (Sandbox) - Local Development build (v0.0.1-current) built by the FHIR (HL7® FHIR® Standard) Build Tools. See the Directory of published versions

Home

Official URL: https://fhir.nhs.uk/England/RAD/ImplementationGuide/nhs.england.rad				Version: 0.0.1-current
Draft as of 2024-10-24				Computable Name: NIR_England_National_Imaging_Registry

This is an elaboration of an approach. It is not an official guide

Introduction

TODO.

Assumptions

Identifiers

It is assumed entity identifiers specified in the NHS Data Dictionary will be used (TODO ISN?) and the following principles will be followed:

• It is the responsibility of the sender or provider to ensure these identifiers are correct, not the recipient.
• Only verified/traced NHS Numbers should be be used, untraced NHS Numbers can be used when verifying or tracing them via PDS, DBS, etc.
• Other identifiers may be used but NHS England identifiers should take precedence.

If details of these entities such as Patient, Practitioner or Organisation are required, then the following services can be used:

• Personal Demographics Service (PDS)
• Organisation Data Service (ODS)
• Healthcare Worker API (in development)```

Alternatively, these services can be created locally. IHE recommendations for these interfaces are shown on the diagram below.

NHS Number - misidentification. This is when a patient or person has been incorrectly linked to a NHS Number, normally by mistaken identity. This may require the use of a Patient Master Identity Registry (PMIR) but this topic is not covered here.

Suggested Terminology and Directory Services

Terminology

Where possible/practical UK SNOMED CT will be used (TODO ISN). The following principles will be followed:

• It is the responsibility of the sender or provider of information to perform any code conversions, not the recipient.

To aid with the use of UK SNOMED CT and other terminology, the Terminology Server is recommended

Alternatively, these services can be created locally. IHE recommendations for these interfaces are shown on the diagram above.

Dependencies

Package hl7.fhir.uv.extensions.r4#5.1.0 This IG defines the global extensions - the ones defined for everyone. These extensions are always in scope wherever FHIR is being used (built Sat, Apr 27, 2024 18:39+1000+10:00)

Package fhir.r4.ukcore.stu2#2.1.0 UK Core FHIR profiles and Assets

Package hl7.fhir.uv.extensions.r4#1.0.0 This IG defines the global extensions - the ones defined for everyone. These extensions are always in scope wherever FHIR is being used (built Sun, Mar 26, 2023 08:46+1100+11:00)

Package ihe.iti.mhd#4.2.1 ImplementationGuide for IHE IT Infrastructure Technical Framework Supplement Mobile access to Health Documents (MHD) (built Wed, Aug 2, 2023 10:57-0500-05:00)

Package ihe.rad.imr#1.1.0 Support encoding and presentation of an interactive multimedia report (built Thu, Jun 20, 2024 08:48-0500-05:00)