Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 9 Next »

ID

S54

Version

2.0.0

Type

Standard

Status

Effective

Effective Date

 

Framework(s)

Introduction

Identity and Access Management (IAM) provides a trusted digital identity service for Health and Care Professionals to authenticate their identity when accessing national clinical information systems. This authentication allows the Health and Care Professional to log on and access those systems securely through a range of access options.

The NHS Care Identity Service makes use of current technologies and Smartcards to allow Health and Care Professionals in England to authenticate their identity when accessing national clinical information systems. This was previously implemented using CIS (Care Identity Service), but this is now replaced by NHS Care Identity Service 2 (CIS2).

NHS CIS2 has a number of main aims:

  1. Allow the use of new authentication methods to support user’s workstyles

  2. Simplify the effort needed to integrate an application with the authentication service

  3. Remove the need for outdated technology like IE11 or Java applets

  4. Allow the use of the latest operating systems and browsers

To enable these aims, the CIS2 authentication service (CIA) is providing an OpenID Connect (OIDC) Solution. OIDC is an Internet Engineering Task Force (IETF) standard that defines a protocol for applications to request a user authentication from an Identity Provider (IdP) such as NHS CIS2.

Requirements 

ID

Requirement

Level

AA01

Implement and maintain the latest specification version of NHS Care Identity Service 2 (NHS CIS2) for the authentication of Health or Care Professionals accessing NHS systems and national services

MUST

Compliance, Assurance and Testing

See the Care Identity Service (CIS2) section on Onboarding Overview of the Digital Care Services Interoperability Standards and Requirements.

Documentation

Dependencies

There may be dependencies for implementing this Standard, however, there are no Interoperability Standards within the Capabilities and Standards model that are dependents.

Roadmap

Items on the Roadmap which impact or relate to this Standard

  • No labels