Appendix 1: Impact assessment

Spine and Spine connected systems

Care ID, Care Identity Service and access control.

System suppliers, for example, Cerner.

e-RS.

Secondary Uses Service (SUS) and CDS.

Spine is fed by the ODS system in real-time. Functionality within Spine fed systems, linked to an ODS code which is operationally closed, will be removed instantaneously.

Non-Spine connected systems

NHS.uk.

NHS.net Connect.

System suppliers, for example, TPP.

Cancer waiting times.

DSPT.

Non-Spine connected systems that use ODS data will consume the data via differing ODS publication mechanisms – Data Search and Export (DSE) Predefined Reports, an XML file or an API.

If the system consumes ODS data via the DSE predefined reports, there will be no impact. Operational dates are not published in the predefined reports.

If the system consumes ODS data via the XML file or API and validates against operational dates, there will be impact.

Functionality within these types of systems, that’s linked to an ODS code which is operationally closed, will be removed upon the particular system taking a refresh of ODS data.

The frequency at which systems take a refresh of ODS data differs dependent upon what publication mechanism they use and their own system requirements. This could be on a daily, weekly, monthly, quarterly or ad hoc basis.

Local bespoke systems

For example, internally built HR system or internally built finance system. These types of systems may not use ODS data. If they do, where do they consume ODS data from, how often and do they use operational dates?

System suppliers consume ODS data from different sources based on their requirements, for example, from Spine (P1) or from the ODS XML file/API (P2).