Search loading...

API Hub

Explore and Make use of Nationally Defined Messaging APIs

 

Authentication and Authorisation

Authentication and Authorisation

Introduction

The NRL and SSP NHS Digital Spine services are subject to various access restrictions. The security section outlines the need for any client to be able to take part in a mutual authentication session at the transport layer. This will protect traffic flowing between client and server and, to some extent, gives the NHS Digital SPINE services confidence in the identity of the client system. However, this transport-layer security does not address authorisation. Additionally, the level of granularity in terms of establishing identity stops at the system level.

Consumers and Providers are required to ensure the correct level of authentication and authorisation is applied to their systems and user access when interacting with NHS Digital SPINE services.

Authentication

Clients are required to authenticate and authorise users, using a mechanism that conforms to the level-3 authentication and RBAC control requirements.

Clients are required to apply appropriate RBAC control to manage access to different types of Pointers and their referenced records.

This level of control can be achieved and verified through integration with the Care Identity Service (CIS), which will become NHS Identity. As well as providing support for existing smartcard-based mechanisms, NHS Identity will provide an array of other authentication types. Consumers will need to integrate with CIS or NHS Identity to access the NRL and the SSP.

Please see the NRL RBAC mapping table for details on the mappings between RBAC codes and Pointer types.

Authorisation

The NRL and SSP use the well-established ASID + interactionId approach to control access to these services. Each RESTful endpoint is associated with a unique interactionId. Each system accredited by NHS Digital as a Consumer or Provider will be issued with an ASID and assigned a set of interactions that it has been authorised to perform. These interactions are mapped to interactionIds. Each ASID is associated with a set of interactionIds. It is this combination of interactionIds that govern which RESTful endpoints a particular system can interact with.


All content is available under the Open Government Licence v3.0, except where otherwise stated