Changes to Data Migration Standard

ID

RM233

Version

1.0.1

Type

Roadmap Item

Contracting Vehicle(s)

Title

Changes to Data Migration Standard

Description

Clarifications to Data Migration Standard requirements DMI02, DMI03 and DMI07

Date Added

Apr 25, 2024

Standards and Capabilities

Data Migration

Change Route

Managed Capacity - Minor/Patch uplifts

Change Type

Uplift

Status

Draft

Publication Date

May 9, 2024

Effective Date

May 23, 2024

Incentives / Funding

No

Incentive / Funding Dates

N/A

Background

NHSE has engaged with all Suppliers over the course of the past few months to discuss clarifications to be made to the Data Migration Standard. Following the engagement this Roadmap Item will update DMI02, DMI03 and DMI07 in the Data Migration Standard to provide clarification of the requirements. This Roadmap Item includes the changes in RM180 and will therefore supersede it.

Outline Plan

N/A

Summary of Change

Data Migration: Requirements updated

Applicable Contracting Vehicle(s)

Requirement ID

Requirement Text

Applies to

Level

Applicable Contracting Vehicle(s)

Requirement ID

Requirement Text

Applies to

Level

Target and SourceĀ SolutionĀ Suppliers

All

DMI02

Provide aĀ DocumentedĀ Data Extract (DDE) that allows a Target SolutionĀ Supplier to understand and interpret theĀ form and structureĀ of the extracted data. This will include, but is not limited to:

  1. A description of the physical data included in the extract of all of the data stored in the Patient Record and all other data included in the data extract

  2. A logical model explaining the relationships between the data in the extract, and any physical primary/compound/foreign key information required to be able to understand and process the extract

  3. A mapping between the physical and logical models

  4. Details of units of measure for numeric fields where these are not clearly identified in the extract itself

  5. FullĀ descriptions of the meaning of any coded valuesĀ included in the extract

  6. Details of any business rules/logic that the Target SolutionĀ Supplier would have to understand to successfully import the extract

  7. Details of any exceptional or specific handling required for the Target SolutionĀ Supplier to successfully import the extract, e.g. where handling of certain data has to be treated differently if it was created between certain dates

  8. Rules for any data which the Source Solution derives from the extracted data but which is not included

  9. Any excluded data

  10. Any checks or validations (e.g. integrity checks) which the Target Solution Supplier needs to undertake to ensure the accuracy of the imported data

  11. Any documentation which would be required to support Solution reconstitution

  12. The format of the data extract to be provided Any additional information reasonably required by the Target Solution Supplier to facilitate a clinically safe migration

Note: This is an overarching DDE to be provided to the Authority as part of Standards Compliance and then tailored according to the specifics of each Data Migration undertaken.

Target and Source

MUST

All

DMI03

Provide the Documented Data Extract (DDE) to the Authority for Standards Compliance.

  • at the request of the Authority (e.g. for Standards Compliance)Ā or in the case of significant changes to the DDE

Within 10 Working Days of a written request by the Authority, the Supplier shall provide to the Authority an Uplifted DDE.Ā 

In the event a Supplierā€™s DDE changes materially it shall provide the Authority with an updated DDE as soon as reasonably practicable.

Target and Source

MUST

Source Solution Suppliers only

All

DMI07

All data extracts will:

  • be in an encrypted electronic format

  • be in conformance with the DDE provided

  • be provided to the Target Solution Supplier and/or the Service Recipient as instructed by the Service Recipient (as Data Controller)

  • employ cryptographic techniques which conformĀ to NIST Cryptogrophy Standards

  • contain theĀ full set of Patient Records, including documents and attached images as well as other clinical and administrative information such as tasks and appointments where applicable to the individual migration event Ā·Ā Ā Ā Ā Ā Ā 

    • all documents and attached images

    • historic and future appointments

    • Patient registration details, related contacts

    • IG flags including.

      • consent to SMS

      • consent to Summary Care Records (SCR)

      • flags on care record elements

      • Patient Facing Services (PFS) availability

      • privacy settings applied to Consultations

      • any consent statuses recorded against any SNOMED code

    • tasks including all incomplete & historic tasks including comments

    • test results

    • to the extent relevant a full set of audit trails and audit log of all changes made to Patient Record, all accesses to Patient Record and all NHS API requests associated with the Patient, date time stamps, staff attribution and data provenance

    • miscellaneous data requested by the Authority (acting reasonably) for example Electronic Prescription Service (EPS) prescription order IDs, e-RS referral Unique Booking Reference Numbers (UBRN), laboratory order numbers from test requests

  • beĀ in a human readable format without any undue degradation (i.e. flattening from structured data to plain text) or the need for access to the legacy Solution to be available, for example, any fields separate in the Source Solution should be kept as separate machine readable fields in any Data Extract.

Source

MUST

Full Specification

The updated Data Migration Standard will be added at a later date. Proposed changes can be viewed in the Summary of Change above.

Assurance Approach

N/A