Skip to main content
Operations

The Operations team is responsible for the ongoing maintenance and support of operational services.

We ensure the health and social care products under NHS Digital’s remit are delivered from a programme environment into an operational environment, where they can be managed on a day to day basis in line with agreed product roadmaps and strategies.

At the appropriate point in a programme's delivery the run and maintain elements of a service are transitioned into operations. 

IT Operations aims to bring efficiencies and economies of scale by taking products into a maintenance and improvement environment, right through to product retirement.  It aims to standardise the management of products which the NHS and NHS IT suppliers interface in a controlled and secure manner.

What we do

As IT Operations, we support the ‘maintain’ aspects of live service management. We work with three main parties: 

  • NHS Digital, (this includes programmes, projects, subject matter experts and directorates)
  • our technology partners, such as third-party system developers and suppliers and NHS Digital development teams
  • health and social care organisations 

Our two core roles are transition and BAU operations. 

The primary role of the operations function is to provide a permanent home for products and services after they have been developed by programmes, projects or development teams and are ready to be made available to our external customers. Moving home involves a process called transition (to ops).  

Our second role is to put products, services and applications in the hands of health and care professionals, “to transform the NHS and social care”. There are various ‘BAU operations’ processes to achieve this, depending on the type of data or service and the external organisations involved. These include the following processes.

Onboarding

This process involves a technology partner requesting access to an NHS Digital dataset or service so that they can integrate it with their health and social care application or system. The onboarding process has a risk management and assurance focus to ensure that we, our partners and health and social care organisations take appropriate responsibility for using data safely to provide health and social care services.

Monitoring

Once an NHS Digital product, service or application is being used by an health and social care organisation, IT Operations continues to monitor partners and the organisations using their products, for compliance with core requirements, standards and specifications (these vary with the data, product or service and cover technical/functional, clinical safety, Information Governance and Security). As with the onboarding process, the emphasis is upon self-assurance by our partners and deploying organisations, but IT Operations provides an oversight and governance role.

Product management

As the demand on NHS Digital’s services changes, our products, services and applications need to evolve to meet those changing demands. Our product management role is to assess changes and developments and implement them based on impact and urgency. These changes may be mandated, imposed due to statutory changes or needed to improve functionality.


Onboarding

Onboarding is NHS Digital’s process for allowing connecting Systems to integrate with national services. Connecting systems are developed by technology partners to provide healthcare organisations and individuals with access to national services, in support of the provision of direct care.

There are three main approaches to Onboarding and NHS Digital is working towards standardising these. GPIT, IM1 and full integration approaches are separate to the following 'self-declared compliance' approach, which uses a Supplier Conformance Assessment List (SCAL) and Connection Agreement (CA).

The NHS Digital services and APIs that currently follow this onboarding approach include:

  • Spine Mini Service Provider for Personal Demographics Service (SMSP-PDS)
  • PDS FHIR APIs
  • Electronic Referrals Service APIs (e-RS)
  • Electronic Prescription Service (EPS) Prescription Tracker API
  • Electronic Prescription Service (EPS) HL7 and FHIR APIs
  • GP Connect capabilities e.g. HTML and Appointments
  • NHS login
  • NHS App
  • Summary Care Record 1-click (SCR 1-click)
  • Care Identity Service 2 (CIS) - formerly NHS Identity
  • National Event Management Services (NEMS) 
  • NEMS with Digital Child Health (NEMS-DCH)
  • National Record Locator (NRL)
  • Urgent & Emergency Care (UEC) Appointment Booking
  • Ambulance Analytics API

The onboarding process is risk-based and:

  • assesses the technical conformance of the connecting system with the integration standards and requirements of the service
  • requires self-declared compliance with specified standards for data protection, clinical safety, information governance and security

The aim of the onboarding process is for all parties to work together to ensure the safe and secure transmission and/or sharing of data for healthcare purposes.

The parties involved in onboarding are:

  • NHS Digital the owner of the National Service
  • the connecting party an individual or organisation that develops, owns, and maintains the connecting system that connects to one or more national service or services - this is sometimes called a partner or supplier
  • the end user organisation, the recipient or commissioning body wishing to use or commission a connecting system to access a national service or services - the end user organisation often represents individual end users for example  healthcare professionals or patients

Each party is responsible for their own information governance, data protection, information security, clinical risk management and incident management. The connection agreement explains the  the responsibilities, obligations and terms of use and is signed by the connecting party. The end user acceptable use policy explains the responsibilities, obligations, and terms of use for every end user organisation. 

Each national service also has a web page or portal, that contains the technical, functional, and non-functional standards and requirements that a connecting system must meet in order to integrate to the national service.

Finally, there is a Supplier Conformance Assessment List (SCAL), currently presented as a workbook. This is completed by the connecting party to create a record of the technical conformance of its connecting system with the technical requirements of the national service being integrated. It also contains declarations of organisational compliance with standards, regulations, and policies.


Reference documentation

Core documents

When you begin the onboarding process for a national service, you will be guided how to complete the correct versions of these documents. These downloadable files are examples only. 

Last edited: 7 October 2021 11:53 am