Email

Email

ID

S38

Version

1.0.2

Type

Standard

Status

Effective

Effective Date

Jan 19, 2026

Contracting Vehicle(s)

 

Introduction

Health and care systems that send and receive emails need to ensure their email service meets the secure email Standard as detailed below in the requirements section. Example secure email services are:

  • NHS.net Connect (formerly NHSmail) - On Premise Exchange

  • Locally operated Solutions based variously on Microsoft Office 365 or Exchange

Where a system needs to systematically send a large volume of emails then application accounts are available via NHS.net Connect (formerly NHSmail).

Requirements

ID

Requirement

Level

E01

If an organisation uses or provides an email capability within a health and care system, the email part of the selected system must comply with the DCB 1596 Standard, covering secure email configuration.

Further guidance on the secure email Standard is available here

MUST

E02

  • Organisations using NHS.net Connect (formerly NHSmail) have met/meet the email system section of the accreditation requirements.

  • NHS.net Connect (formerly NHSmail) have on behalf of organisations that use the service completed the organisation requirements of the Standard

MUST

E03

  • Organisations using Office 365 have met/meet the email system section of the accreditation requirements.

  • Organisations using Office 365 need to complete the organisation section of the accreditation requirements

MUST

Compliance, Assurance & Testing

See the Email section on Onboarding Overview of the Digital Care Services Interoperability Standards and Requirements.

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