STD001

DCB1605: Accessible Information

0.1

DCB1605: Accessible Information - NHS Digital

Mapped Standard

Draft

STD001-1

Trust Contracts for patient / service user record and administration systems include the requirement for the system MUST adhere to the Accessible Information Standard.

MUST

STD001-2

Suppliers' systems SHOULD enable revision / amendment of records made about individuals’ information and communication support needs and, where possible, include prompts for review at appropriate points.

SHOULD

STD001-3

Where Suppliers' online systems enable patients or service users to access their own records, there SHOULD be evidence that individuals have viewed and / or contributed to their records with regards to information and communication needs

SHOULD

STD001-4

Suppliers' Electronic patient, or service user administration and record systems, SHOULD automatically identify a recorded need for information or correspondence in an alternative format and / or communication support, and flag, prompt or otherwise make this highly visible to staff whenever the record is accessed.

SHOULD

STD001-5

Suppliers' Electronic patient or service user administration and record systems, SHOULD automatically identify relevant recorded needs and either automatically generate correspondence or information in an alternative format or enable staff to manually generate correspondence in an alternative format upon receipt of an alert

SHOULD

STD001-5

Suppliers' systems used for the recording of individuals’ information and communication needs SHOULD be designed and built with consideration for the clinical safety risks identified in the Clinical Safety Case published alongside this Specification

SHOULD

STD001-6

Suppliers' systems MUST enable recording of all of the data items or categories associated with the subsets defined by the Accessible Information Standard, in their specified format. Local systems MAY hold more information than is required by the Accessible Information Standard.

MUST

STD001-7

Suppliers' systems SHOULD alert users – in line with other review reminders – when none of the data items / categories in any one of the subsets associated with the Standard has been selected.

SHOULD

STD001-8

Suppliers' systems SHOULD support edit checking / quality assurance of data recorded about individuals’ information and communication needs. This MAY include generating an alert or preventing users from populating mutually incompatible data fields (in line with best practice).

SHOULD

STD001-9

The Suppliers' systems MUST allow for changes to the data items associated with the Standard over time, including following release of new or amended SNOMED CT, Readv2 or CTV3 codes (where used by relevant systems), and enabling any locally defined additional information to be captured

MUST

STD001-10

The Suppliers' systems MUST include functionality to notify staff involved – or to be involved in the near future – in the administration or care of patients or service users of their communication and information needs (and where appropriate the needs of patients’ or service users’ parents or carers).

MUST

STD001-11

The Supplier's system MUST automatically identify a recorded need for information or correspondence in an alternative format and / or communication support, and flag, prompt or otherwise make this highly visible to staff whenever the record is accessed.

MUST

STD001-12

Where Suppliers' systems automatically generate correspondence, the system MUST automatically identify a recorded need for information or correspondence in an alternative format and in response:

• Automatically generate correspondence or information in an alternative format (preferred); OR

• Enable staff to manually generate correspondence in an alternative format (upon receipt of an alert); AND

• Not produce the standard printed output for sending to the individual

MUST

STD001-13

Where Suppliers' systems automatically generate correspondence, the system SHOULD automatically identify a recorded need for information or correspondence in an alternative format and in response does not produce the standard printed output for sending to the individual, and alerts staff accordingly.

SHOULD

STD001-14

The Supplier's system MUST enable records made about individuals’ information and communication support needs to be revised / amended.

MUST

STD001-15

The Supplier's system SHOULD prompt for a review of data recorded about individuals’ information and communication needs alongside and concurrent with review of data held in other demographic fields.

SHOULD

STD001-16

The Suppliers' systems SHOULD enable recording of all of the data items or categories associated with the subsets defined by the Accessible Information Standard in their specified format.

SHOULD

STD001-17

Suppliers' systems SHOULD alert users – in line with other review reminders – when none of the data items or categories in any one of the subsets associated with the Standard has been selected.

SHOULD

STD001-18

Suppliers' systems SHOULD support edit checking / quality assurance of data recorded about individuals’ information and communication needs

SHOULD

STD001-19

The Suppliers' systems SHOULD generate an alert or prevent or discourage users from populating mutually incompatible data fields when recording individuals’ information and communication needs (in line with best practice).

SHOULD

STD001-20

The Suppliers' system SHOULD allow for records made about individuals’ information and communication support needs to be revised or amended.

SHOULD

STD001-21

The Suppliers' system SHOULD prompt for a review of data held about individuals’ information and communication needs alongside and concurrent with review of data held in other demographic fields

SHOULD

STD004

DAPB0108

0.1

https://digital.nhs.uk/data-and-information/information-standards/information-standards-and-data-collections-including-extractions/publications-and-notifications/standards-and-collections/dapb-0108-automatic-identification-and-data-capture-aidc

Data Standard (NHS)

Draft

STD004-1

Compliance to GS1 Standards

To be compliant with DAPB0108, is to be compliant to any relevant GS1 Standards, which means that the AIDC system or product being procured, deployed, and used.

MUST

STD004-2

GS1 Identification keys

Utilise GS1 Identification keys for the required data elements based on the functionality and purpose of the system being considered.

MUST

STD004-3

GS1 Data Carriers

Produce, print, and read GS1 Data Carriers such as barcodes or EPC/RFID tags, in accordance with the specifications provided for the intended application.

MUST

STD004-4

Data Format/Carriers

Whilst system design and business processes around collections and data flow remain out of scope for DAPB0108, health IT systems may need to be modified to ensure the data format and data carrier requirements specified can be complied with. The safety implications of any such modifications must be considered by manufacturers of health IT systems as well as those involved in the deployment and use of health IT systems.

MAY

STD013

DCB1609

0.1

DCB1609 - Child Protection Information Sharing

Data Standard (NHS)

Draft

TBC

STD013-1

NHS Number

The children’s social care system MUST use a validated NHS number as the unique identifier to send CP-IS information.

MUST

STD013-2

NHS Number Validation

The children's social care system SHOULD undertake NHS number check validation, to ensure NHS numbers entered locally are valid NHS numbers. The actual verification of the NHS number (to confirm the NHS number received is the correct child) will be the responsibility of the CP-IS Service, upon receipt of the CP-IS Local Authority Upload message.

SHOULD

STD013-3

NHS Spine

The children's social care system MAY use the NHS Spine PDS service to verify NHS numbers prior to any submission to the CP-IS service.

MAY

STD013-4

Date and Time format

The presentation of any date & times associated with CP-IS information MUST be in a standardised format, e.g. DD/MM/YYYY and HH/MM/SS

MUST

STD013-5

CP-IS Data Set

The children’s social care system MUST be able to send current and up to date CP-IS information as outlined in the CP-IS dataset, using the CP-IS Local Authority Upload message. Sending of CP-IS information will be undertaken; - as an initial upload of all CP-IS information for each child - as subsequent uploads of all CP-IS information for each child - as subsequent updates of all CP-IS information where a child's CP-IS status has changed

MUST

STD013-6

CP-IS Data Set - Update

Any update to a CP-IS data item within a local record MUST automatically (and without manual intervention) trigger the creation of a CP-IS Local Authority Upload message, in order for this to be sent to the CP-IS service within 12hours of the original change being made. It is anticipated that the SFT client provided, will be embedded within the children’s social care application, and upon creation of the CP-IS Local Authority Upload message will automate the transmission of the CP-IS information via the SFT mechanism to the CP-IS service.

MUST

STD013-7

CP-IS Data Set - Upload Tel Number

Where an 'Office Hours' telephone number is available locally, this SHOULD be included in the CP-IS Local Authority Upload message, in addition to the 'Out of Hours/ Emergency' telephone number. This will assist NHS healthcare workers to easily identify where to contact in non-emergency/ office hours circumstances, and will specifically be useful where a child has presented in out of area settings

SHOULD

STD013-8

CP-IS Data Set - Identify Update

Any update to a CP-IS information locally within a local record SHOULD be easily identifiable

SHOULD

STD013-9

CP-IS Data Set - LA Upload message

Where there is any update to a CP-IS dataset item held locally within the children's social care system, this MUST trigger the creation of a new CP-IS Local Authority Upload message (replacing what is held within the CP-IS service). E.g. the addition of an End Date to a CPP. Any update to a local record that is not a CP-IS data item, SHOULD not trigger the creation of a new CP-IS Local Authority Upload message, e.g. updated assessment information, change of address etc.

MUST

STD013-10

CP-IS Data Set - Messenger Identity

Any update to a CP-IS data item within a local record SHOULD easily identify locally who updated the CP-IS information.

SHOULD

STD013-11

CP-IS Data Set - Schema Validation

The children's social care system SHOULD ensure that prior to any sending of CP-IS information to the CP-IS service, the schema is validated to ensure the message is appropriately formed, and all appropriate fields have been populated appropriately. This will include: - NHS number; Source Organisation Name (Local Authority Name); - Source Organisation Code (ODS Code); - Source Organisation Telephone (Emergency Duty Team/ Out of Hours); - At least one Start Date included for 1 of the 3 CP-IS status types (CPP, Unborn CPP or LAC); - Delete Date (which will be the expected Due Date) where CPP for an Unborn Baby details have been provided.

SHOULD

STD013-12

CP-IS Data Set - Mothers details

The children's social care system MUST ensure that when details of an Unborn CPP are sent, the following demographic information is used to populate the CP-IS Local Authority Upload message: - the Mother's NHS Number; - the Mother's Given Name; - the Mother's Family Name; - the Mother's Date of Birth

MUST

STD013-13

CP-IS Data Set - Birth details

The children's social care system MUST ensure that when details of an Unborn CPP is sent, the expected Due Date for the baby (held locally) is used to populate the Unborn CPP End Date. The End Date (expected due date of the baby) provided will be used to trigger the deletion of the information from the mother’s NHS record at End Date+28days. As part of the wider process, the new-born baby's NHS number will be manually provided to the children's social care team. This will need to be used to resubmit any CP-IS information using the new-born baby’s NHS number, instead of the mother's NHS number.

MUST

STD013-14

CP-IS Data Set - Stop Sending

The children’s social care system MUST allow the sending of CP-IS information, to be switched on and off, at the discretion of the Children’s Social Care Team. This will be managed by end point enabling/ disabling. Where this occurs, the CP-IS Owner (NHS Digital), MUST be informed by the Local Authority management team, that the functional capability to send CP-IS information has been switched off

MUST

STD013-15

CP-IS Data Set - Identify Child Record

It MUST be possible to identify within the children's social care system, the appropriate child record that will have their CP-IS information sent to the CPIS service. E.g. by having an active CP-IS status associated to the local record within the children's social care system

MUST

STD013-16

CP-IS Data Set - Unique File Identifier

The children's social care system MUST ensure that any files sent are sequential and are uniquely identifiable

MUST

STD013-17

CP-IS Data Set - Message Resubmission

The children's social care system SHOULD resubmit a CP-IS Local Authority Upload file if no CP-IS Acknowledgement Response has been received for a CP-IS Local Authority Upload message. This SHOULD be sent if no CP-IS Acknowledgement Response message is received within15hrs of the initial CP-IS Local Authority Upload message being submitted to the CP-IS SFT client

SHOULD

STD013-18

CP-IS Data Set - End Date

Where a child’s case (or child record) is closed locally by the social care team, (and where an End Date for the CP-IS information has not been uploaded to the CP-IS service), then the children's social care system MUST apply End Dates for each of the relevant CPP/UCPP/LAC items within that child’s case (or child record). The End Date will be the date that a child’s case (or child record) is closed. The application of the End Date to the record, will trigger the submission of a CP-IS Local Authority Upload message outlining all associated End Dates for that record. In the case of the initial bulk upload of records to the CP-IS Service, a child record MUST not be included in the upload message when it is closed or when the CPP or LAC record has an End Date that is in the past at the point of data extraction / submission to CP-IS. Where there are multiple CPP and/or LAC records for one child and if one or more CPP, UCPP or LAC record has an End DCB1609 Child Protection Information Sharing 31/05/2019 Final v2.0 Copyright © 2019 Health and Social Care Information Centre. Page 18 of 35 Date in the past, only those records without an End Date in the past are to be sent to the CP-IS Service. For example in the case of a child that has a LAC record with an End Date of 6 weeks ago and a CPP record that has a Start Date of 5 weeks ago and no End Date, only the CPP record would be sent to the CP-IS Service. Following the bulk upload, for reconciliation purposes, a report MUST be made available to the end user which will list the CPP, UCPP and LAC records that were not successfully uploaded to the CP-IS Service due to the End Date being in the past

MUST

STD013-19

CP-IS Data Set - Local Configuration

The children's social care system MUST be able to manage the receipt of the following CP-IS messages and display the content of these messages to the end user. How the display of this information will be provided, will need to be locally defined and configured to the children's social care team’s requirements. The CP-IS messages to the children's social care system will include: - CP-IS Local Authority Acknowledgment Response (which includes file and record validation responses); - CP-IS Access to Service Notification (which includes who, when, where the CP-IS service was queried); - CP-IS Inactive NHS Number Notification (where available the new NHS Number will be provided).

MUST

STD013-20

CP-IS Data Set - Acknowledgment Response

On receipt of a CP-IS Local Authority Acknowledgement Response message, the children's social care system MUST determine the file and record validation responses of the CP-IS Local Authority Upload message. Where all records are successfully uploaded, consideration SHOULD be given to how the successful uploads are replayed to the end user, if this is required. Where records within the Upload message are not successfully uploaded, consideration SHOULD be given to how the unsuccessful uploads will be handled by the children's social care system and/ or end user. E.g. unverified NHS numbers and the associated reasons for that number not being uploaded to the CP-IS service, being displayed to the end user.

MUST

STD013-21

CP-IS Data Set - Display of Information

On receipt of a CP-IS Access to Service Notification message, the children's social care system SHOULD be locally configured to determine how this information will be displayed to the end user. This will include the following information: - the name of the NHS healthcare worker (in a readable format) who accessed the CP-IS service; - the name of the NHS organisation (in a readable format) where the access to the CP-IS service took place; - the date and time of when the CP-IS service was accessed. Access to Service Notification messages will be provided daily to the children's social care system, including all access event history for all the associated children to that Local Authority, specifically including where there has been no access to the CP-IS service for that day. On receipt of a CP-IS Access to Service Notification message, consideration SHOULD be given to how this information will be displayed to the end user, including any alerting functionality. Further to this, consideration SHOULD also be given to how the receipt of the access history will be managed in the following scenarios; 1. Where ‘no access’ event history is received, and whether this daily information SHOULD be displayed to the end user; 2. When an End Date is; - received as part of a typical Start/ End Dating of CP-IS information automatically created by the CP-IS service on the child's 18th birthday - automatically provided by the children’s social care system, upon closure of a case/ record locally. Following the capture of an End Date for a CP-IS information item (however this is done), the CP-IS item will still be retrievable by the NHS healthcare worker up to the End Date +365 days. Any access to CP-IS service during this 365 day period, will result in the creation of a CP-IS Access to Service Notification message back to the children's social care team.

SHOULD

STD013-22

CP-IS Data Set - Inactive NHS Number

On receipt of a CP-IS Inactive NHS Number message, the children's social care system MUST be able to inform the end user that the NHS number previously used to submit CP-IS information to the CP-IS service is no longer a valid NHS number. The children’s social care system MUST also inform the end user of the new NHS number, where this has been included within the Inactive NHS number message. Where Inactive NHS number information is received, consideration SHOULD be given to how this information is displayed to the end user

MUST

STD013-23

CP-IS Data Set - Update NHS Number

On receipt of a CP-IS Inactive NHS Number message that includes details of the new NHS number, the children's social care system MAY want to automatically update the NHS number within the local system.

MAY

STD013-24

CP-IS Data Set - Update Message

On receipt of a CP-IS Inactive NHS Number message that includes details of the new NHS number, the children's social care system MAY want to automatically create and resubmit a new CP-IS Local Authority Upload message using the new NHS number

MAY

STD013-25

CP-IS Data Set - Local Authority Connection

Only authorised Local Authority end-points MUST be permitted to connect to the CP-IS service. The mechanism for doing so may vary between systems that consume webservices to those that submit Local Authority data

MUST

STD030

ISB 1556

0.1

ISB 1556 Guidance

Guidance

Draft

STD030-1

DICOM Networking Conformance Requirements

IT system suppliers implementations claiming DICOM network conformance shall:

• conform to the minimum conformance requirements defined in this section;

• provide with the implementation a Conformance Statement structured according to the rules and policies in this Part including Annex A;

• conform to at least one Standard or Standard Extended SOP class as defined in PS3.4; Note Conformance to a Standard or Standard Extended SOP class implies conformance to the related IOD outlined in PS3.3, the Data Elements defined in PS3.6, and the operations and notifications defined in PS3.7.

• comply with the rules governing SOP Class types outlined in Section 7.3;

• accept a Presentation Context for the Verification SOP Class as an SCP if the implementation accepts any DICOM association requests;

• produce and/or process Data Sets as defined in PS3.5; Note Conformance to PS3.5 also implies conformance to PS3.6.

• obtain legitimate right to a registered for creating UIDs (see PS3.5) if an implementation utilizes Privately Defined UIDs (i.e., UIDs not defined in the DICOM Standard);

• support the following communication mode: • TCP/IP (See PS3.8).

MUST

STD030-2

DICOM Media Interchange Conformance Requirements

IT system suppliers implementations claiming DICOM Media Interchange conformance shall:

• provide with the implementation a Conformance Statement structured according to the rules and policies in this Part including Annex A;

• conform to at least one Standard Application Profile as defined in PS3.11;

• support one of the Physical Media and associated Media Format, as specified by PS3.12; • comply with the rules governing SOP Class types outlined in Section 7.3;

• comply with the specific rules governing media storage Application Profile according to their types as specified in Section 7.4. No other types of Application Profiles may be used; - Standard - DICOM PS3.2 2022c - Conformance Page 49

• read as an FSR or FSU all SOP Classes defined as mandatory by each of the supported Application Profiles encoded in any of the mandatory Transfer Syntaxes. • write as an FSC or FSU all SOP Classes defined as mandatory by each of the supported Application Profiles in one of the mandatory Transfer Syntaxes;

• be able to gracefully ignore any Standard, Standard Extended, Specialized or Private SOP Classes that may be present on the Storage Medium but are not defined in any of the Application Profiles to which conformance is claimed. Note There may be more than one Application Profile used to create or read a File-set on a single physical medium (e.g., a medium may have a File-set created with Standard and Augmented Application Profiles).

• be able to gracefully ignore Directory Records in the DICOMDIR file that do not correspond to Directory Records defined in any of the Application Profiles to which conformance is claimed.

• access the File-set(s) on media using the standard roles defined in PS3.10; • produce and/or process Data Sets as defined in PS3.5 encapsulated in DICOM Files; Note Conformance to PS3.5 also implies conformance to PS3.6

• obtain legitimate right to a registered for creating UIDs (see PS3.5) if an implementation utilizes Privately Defined UIDs (i.e., UIDs not defined in the DICOM Standard). An implementation that does not meet all the above requirements shall not claim conformance to DICOM for Media Storage Interchange.

MUST

STD039

DAPB0090

0.1

DAPB0090 - Health and Social Care Organisation Reference Data

Data Standard (NHS)

Draft

STD0039-1

Data Composition

This standard describes and governs reference data about the Organisations that comprise health and social care services, and the Sites they provide services from. This reference data is comprised of a number of core components, listed below:

Dates, Name,. Identifier, Geographic Location, Contacts, Roles, Relationship(s), Succession and Additional Attributes.

Full details of the data and structures is included here Health and Social Care Organisation Reference Data (SCCI0090): Requirements Specification

MUST

STD043

DCB3051

0.1

DCB3051

Data Standard (NHS)

Draft

STD0043-1

See full details in the Specification and Implementation Guidance at https://digital.nhs.uk/data-and-information/information-standards/information-standards-and-data-collections-including-extractions/publications-and-notifications/standards-and-collections/dcb3051-identity-verification-and-authentication-standard-for-digital-health-and-care-services

MUST

STD045

DAPB0086

0.1

DAPB0086: Data Security and Protection Toolkit

Data Standard (NHS)

Draft

STD0045-1

See full details in the Requirements Specification https://digital.nhs.uk/data-and-information/information-standards/information-standards-and-data-collections-including-extractions/publications-and-notifications/standards-and-collections/dapb0086-data-security-and-protection-toolkit

MUST