Versions Compared

Version Old Version 6 New Version Current
Changes made by

Martin Eland

Michael France

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Updated term "Framework(s)" to "Contracting Vehicle(s)"
Page Properties

ID

S38

Version

1.0.0

Type

Interoperability

Standard

Status

Effective

Effective Date

Insert excerpt
GPITF:Day One Effective Date
GPITF:Day One Effective Date
nopaneltrue

Framework

Contracting Vehicle(s)

  • DPL
    • Excerpt
    hiddentrue

    Ensures that email services within Solutions are securely configured.

    toc

    Table of Contents
    minLevel1
    maxLevel3
    outlinefalse
    styledisc
    typelist
    printabletrue

    Introduction

    Health and care systems that send and receive

    email

    emails need to ensure their email service meets the secure email

    standard

    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

    Standard, covering secure email configuration.

    Further guidance on the secure email

    standard

    Standard is available via

    the NHS Digital

    The Authority's website.

    Status

    NHSmail and Office 365

    colourRed
    titleMUST

    E02

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

    There is then the organisation section of the accreditation requirements to meet.

    • NHSmail have on behalf of organisations that use the service completed the organisation requirements

    of the standard. For those that use Office365 each organisation will need to complete those parts themselves as it relies on NHS policy.

    • of the Standard

    Status
    colourRed
    titleMUST

    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

    Status
    colourRed
    titleMUST

    The Implementation and Business Change function within

    NHS Digital

    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

    Excerpt

    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

    Page Properties Report
    firstcolumnRoadmap Item
    headingsStandards and Capabilities, Status, Effective Date, Description, Change Type, Change Route
    pageSize300
    sortByEffective Date
    cqllabel = "S38" and space in ( currentSpace ( ) , "DCSDR" , "DCSDCS" )