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:
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 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 via The Authority's website. | MUST |
E02 |
| MUST |
E03 |
| MUST |
The Implementation and Business Change function within The Authority’s run engagement sessions covering the secure email requirements via regular online WebEx sessions. To learn more please email feedback@nhs.net
Compliance, Assurance & Testing
NHSmail publishes out standard Microsoft Exchange and Skype for Business APIs. Development against these APIs should follow the guidance contained on the Developer Network and adhere to the ‘Acceptable use’ policy. There is no formal compliance process for NHSmail API development other than that described within the Developer Network guidance and caveats. It should be noted that no test environment is provisioned for external developers wishing to use the published NHSmail APIs.
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 |
|---|