Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Content of Epics updated to provide clarification

...

MUST Epics - Describes the minimum functionality required to deliver a Capability. Catalogue Solutions MUST be successfully evaluated against each Epic and Acceptance Criteria via Capability Assessment in order to be associated with this Capability

E00163 - manage Patient Registrations

As a Health or Care Professional

I want to manage Patients Registrations

So that I can manage which Patients are currently registered with my Healthcare Organisation

Acceptance criterion 1: create a Patient Registration

Given the Health or Care Professional is permitted to create Patient Registrations

When the Health or Care Professional selects to create a Patient Registration

Then the Registration Type is recorded

And the date the Patient Registration started is recorded

And the Named Accountable GP for the Patient is recorded

And the Patient Registration is created

Acceptance criterion 2: amend a Patient Registration

Given the Health or Care Professional is permitted to amend Patient Registrations

When the Health or Care Professional selects to amend a Patient Registration

And the Patient Registration is amended

Acceptance criterion 3: end a Patient Registration

Given the Health or Care Professional is permitted to end Patient Registrations

When the Health or Care Professional selects to end a Patient Registration

Then the date the Patient Registration ended is recorded

And the Patient Registration is ended

Acceptance criterion 4: view Patient Registration information

Given the Health or Care Professional is permitted to view Patient Registration information

When the Health or Care Professional selects to view a Patient’s Registration information

Then the Patient’s Registration information is displayed

E00163 - Additional Implementation Details

Solutions MUST comply with the following when implementing this Epic:

  • Patient Registration Types will be in line with legislative registration statuses as defined in the GP Contract

Info

E00163 - Supporting Information

  • Registration Types MAY include, but are not limited to:

    • Fully Registered

    • Temporary Resident

    • Immediately necessary treatment


E00164 - manage Patient Demographic Information 

As a Health or Care Professional

I want to manage Patient Demographic Information

So that Patient Demographic Information is managed

Acceptance criterion 1: create Patient Demographic Information

Given the Health or Care Professional is permitted to create Patient Demographic Information

When the Health or Care Professional selects to create Demographic Information for a Patient

Then the Patient’s NHS Number is recorded

And the Patient’s name is recorded

And the Patient’s date of birth is recorded

And the Patient’s address is recorded

And the Patient’s telephone number can be recorded

And other contact details for the Patient can be recorded

And the Patient’s ethnicity can be recorded

And the Patient Demographic Information is created

Acceptance criterion 2: amend Patient Demographic Information

Given the Health or Care Professional is permitted to amend Patient Demographic Information

When the Health or Care Professional selects to amend Patient Demographic Information

Then the Patient Demographic Information is amended

Acceptance criterion 3: view Patient Demographic Information

Given the Health or Care Professional is permitted to view Patient Demographic Information

When the Health or Care Professional selects to view a Patient’s Demographic Information

Then the Patient's Demographic Information is displayed

Info

E00164 - Supporting Information

  • Examples of other contact details for a Patient MAY include, but are not limited to:

    • Email address

    • Alternative telephone numbers (e.g. work)

  • Other examples of Demographic Information MAY include, but are not limited to:

    • Preferred Name

    • Former Family Name

    • Preferred written language

    • Preferred spoken language

    • Gender identity

    • Sex


E00442 - manage Detained Estate registration information

As a Health or Care Professional

I want to manage Detained Estate registration information for a Patient

 So that I can manage which Patients are currently registered with the Detained Estate

Acceptance criterion 1: create Detained Estate registration information

Giventhe Health or Care Professional is permitted to manage Detained Estate registration information

When the Health or Care Professional selects to create Detained Estate registration information for a Patient

Then the Patient’s Resident Status is recorded

And the Patient’s location in the Place of Detention is recorded

And the Patient’s admission date is recorded

And any the release date for the Patient can be recorded

And the Patient’s Local Record Value is recorded

Acceptance criterion 2: view Detained Estate registration information

Giventhe Health or Care Professional is permitted to manage Detained Estate registration information

When the Health or Care Professional selects to view Detained Estate registration information for a Patient

Then the Detained Estate registration information is displayed

Acceptance criterion 3: amend Detained Estate registration information

Giventhe Health or Care Professional is permitted to manage Detained Estate registration information

When the Health or Care Professional selects to amend Detained Estate registration information for a Patient

Then the Detained Estate registration information is amended

E00442 - Additional Implementation Details

Solutions MUST comply with the following when implementing this Epic:

  • The Local Record Value will support the Prison Management System number

  • The Resident Status categories will be the same as the categories used by the Prison Management System

  • The Solution will make Resident Status categories available for use based on the Place of Detention residential detention site (e.g. prison, secure children's homeChildren and Young Persons Secure Estate, Immigration Removal Centre)

Info

E00442 - Supporting Information

  • Other information may be recorded as part of the Detained Estate registration information

  • An example of other information recorded in the Detained Estate registration information MAY include, but is not limited to:

    • The Patient’s requested name, i.e. the name by which the Patient wishes to be known whilst in the Place of Detention

  • Patient location information can vary depending on the Place of Detention. Examples of Patient location information MAY include, but are not limited to:

    • Wing

    • House block

    • Floor/Level

    • Landing

    • Cell

    • Room number


E00165 - manage Electronic Patient Records (EPRs)

As a Health or Care Professional

I want to manage Electronic Patient Records (EPRs)

So that clinical and administrative information relating to a Patient is stored in a single Electronic Patient Record (EPR)

Acceptance criterion 1: view an Electronic Patient Record (EPR) 

Given the Health or Care Professional is permitted to view Electronic Patient Records (EPRs)

When the Health or Care Professional selects to view an Electronic Patient Record (EPR)

Then the Electronic Patient Record (EPR) is displayed

Acceptance criterion 2: update an Electronic Patient Record (EPR) 

Given the Health or Care Professional is permitted to update Electronic Patient Records (EPRs)

When the Health or Care Professional selects to update an Electronic Patient Record (EPR)

Then the Electronic Patient Record (EPR) is updated

Acceptance criterion 3: view of all historical information relating to a Patient’s care

Given the Health or Care Professional is permitted to view Electronic Patient Records (EPRs)

When they select to view all historical information relating to a Patient’s care

Then a view of all historical information relating to a Patient’s care is displayed


E00443 - manage Patient images

As a Health or Care Professional

I want to manage Patient images

So that Patients can be visually identified

Acceptance criterion 1: add Patient image to the Patient’s Electronic Patient Record (EPR)

Given the Health or Care Professional is permitted to manage Patient images

When the Health or Care Professional selects to add a Patient image to the Patient’s Electronic Patient Record (EPR)

Then the Patient image is added to the Patient’s Electronic Patient Record (EPR)

Acceptance criterion 2: view Patient image in the Patient’s Electronic Patient Record (EPR)

Given the Health or Care Professional is permitted to manage Patient images

When the Health or Care Professional selects to view a Patient image in the Patient’s Electronic Patient Record (EPR)

Then the Patient image is displayed

Acceptance criterion 3: update Patient image in the Patient’s Electronic Patient Record (EPR)

Given the Health or Care Professional is permitted to manage Patient images

When the Health or Care Professional selects to update a Patient image in the Patient’s Electronic Patient Record (EPR)

Then the Patient image is updated

Acceptance criterion 4: delete Patient image in the Patient’s Electronic Patient Record (EPR)

Given the Health or Care Professional is permitted to manage Patient images

When the Health or Care Professional selects to delete a Patient image from the Patient’s Electronic Patient Record (EPR)

Then the Patient image is deleted


E00444 - restrict visibility of elements in a Patient’s Electronic Patient Record (EPR)

As a Health or Care Professional

I want to restrict the visibility of elements in a Patient’s Electronic Patient Record (EPR)

So that these elements are only visible to authorised Health or Care Professionals

Acceptance criterion 1: record elements of a Patient’s Electronic Patient Record (EPR) as restricted visibility

Given the Health or Care Professional is permitted to manage a Patient’s Electronic Patient Record (EPR)

When the Health or Care Professional selects to record an element of a Patient’s Electronic Patient Record (EPR) as restricted visibility

Then the element is recorded as restricted visibility

Acceptance criterion 2: view elements of a Patient’s Electronic Patient Record (EPR) recorded as restricted visibility

Given the Health or Care Professional is permitted to view elements of a Patient’s Electronic Patient Record (EPR) recorded as restricted visibility

When the Health or Care Professional selects to view a Patient’s Electronic Patient Record (EPR)

Then the element recorded as restricted visibility is displayed

Acceptance criterion 3: unable to view elements of a Patient’s Electronic Patient Record (EPR) recorded as restricted visibility

Given the Health or Care Professional is not permitted to view elements of a Patient’s Electronic Patient Record (EPR) recorded as restricted visibility

When the Health or Care Professional selects to view a Patient’s Electronic Patient Record (EPR)

Then the element recorded as restricted visibility is not displayed

And an indication that an element has been recorded as restricted visibility is displayed

E00444 - Additional Implementation Details

Solutions MUST comply with the following when implementing this Epic:

  • Visibility restrictions to be based on Role Base Access Controls (See Role-based Access Control requirements in the Information Governance Standard)

  • Restricted visibility elements are not to be included in report results that contain Patient Identifiable Information Data (PID)

  • Restricted visibility elements will be included in Electronic Patient Record (EPR) transfers (e.g. GP2GP and transfers between detained estate organisations)

Info

E00444 - Supporting Information

  • Types of data to be restricted MAY include, but are not limited to:

    • Safeguarding information for the Patient

    • Substance misuse details

    • Notes by Mental Health Clinicians that do not need to form part of the Electronic Patient Record (EPR)


E00255 - display Patient Alerts for Electronic Patient Records (EPRs)

As a Health or Care Professional

I want Patient Alerts to be displayed for Electronic Patient Records (EPRs)

So key characteristics relating to the Patient are indicated to Health or Care Professionals

Acceptance criterion 1: display Patient Alert in Electronic Patient Records (EPRs)

Given the Health or Care Professional is permitted to view Electronic Patient Records (EPRs)

When the Health or Care Professional selects to view a Patient’s Electronic Patient Record (EPR)

And a Patient Alert is recorded for that Patient's Electronic Patient Record (EPR)

Then the Patient Alert is displayed

Info

E00255 - Supporting Information


As a Health or Care Professional

I want to maintain Patient Registration information via NHAIS HA/GP Links

So that Patient Registration information is up to date

Acceptance criterion 1: send Patient Registration Information

Given a Health or Care Professional is permitted to manage Patient Registrations

When the Health or Care Professional creates a Registration for a Patient

Then a NHAIS HA/GP Links registration message is created

Acceptance criterion 2: receive Patient Registration Information

Given a NHAIS HA/GP Links message has been sent to the GP Practice

When the Health or Care Professional selects to view the received NHAIS HA/GP Links messages

Then the NHAIS HA/GP Links messages are displayed

E00175 - Additional Implementation Details

Solutions MUST comply with the following when implementing this Epic:


E00176 - Personal Demographics Service (PDS)

As a Health or Care Professional

I want the Solution to be integrated with Personal Demographics Service (PDS)

So that Personal Demographics information for Patients is up to date

Acceptance criterion 1: update PDS data based on Solution data

Given the local Electronic Patient Record (EPR) in the Solution is matched to a PDS record

And there are differences between the information held in the Solution for the Patient and the PDS record

When the Health or Care Professional selects to update the PDS record information based on the local Electronic Patient Record (EPR) information

Then the data held in the PDS record for that Patient is updated to match the local Electronic Patient Record (EPR)

Acceptance criterion 2: update Solution data based on PDS data

Given the local Electronic Patient Record (EPR) in the Solution is linked to a PDS record

And there are differences between the information held in the Solution for the Patient and the PDS record

When the Health or Care Professional selects to update the local Electronic Patient Record (EPR) based on PDS record information

Then the data held in the Patient’s local Electronic Patient Record (EPR) is updated to match the PDS record

Acceptance criterion 3: verify Patients using PDS during the Registration process

Given the Health or Care Professional is creating a Patient Registration

When the Health or Care Professional enters the Patient’s information

Then an Advanced Trace on PDS data is triggered

And the results are displayed

E00176 - Additional Implementation Details

Solutions MUST comply with the following when implementing this Epic:


E00177 - transfer Electronic Patient Records (EPRs) between GP Practices

As a Health or Care Professional

I want to electronically transfer Electronic Patient Records (EPRs) between GP Practices

So that Electronic Patient Records (EPRS) are transferred directly and securely when they move from one GP Practice to another

Acceptance criterion 1: automatically transfer and integrate an Electronic Patient Record (EPR)

Given the Health or Care Professional is permitted to create Patient Registrations

When the Health or Care Professional selects to complete the Patient Registration

Then the Patient’s Electronic Patient Record (EPR) is electronically transferred to the GP Practice

And the Electronic Patient Record (EPR) is automatically integrated

Acceptance criterion 2: view a Patient’s transferred and integrated Electronic Patient Record (EPR)

Given a Patient's Electronic Patient Record (EPR) has been transferred and integrated to a new GP Practice

When the Health or Care Professional selects to view the Patient’s integrated Electronic Patient Record (EPR)

Then the Patient’s Electronic Patient Record (EPR) is displayed

E00177 - Additional Implementation Details

Solutions MUST comply with the following when implementing this Epic:


E00445 - transfer a Patient’s Electronic Patient Record (EPR) between residential detention sites

As a Health or Care Professional

I want to electronically transfer a Patient’s Electronic Patient Record (EPR) between residential detention sites

So that the Patient’s Electronic Patient Record (EPR) is transferred when the Patient moves from one residential detention site to another

Acceptance criterion 1: transfer a Patient’s Electronic Patient Record (EPR) between residential detention sites

Given the Health or Care Professional is permitted to transfer a Patient’s Electronic Patient Record (EPR)

When the Health or Care Professional selects to transfer a Patient’s Electronic Patient Record (EPR) from one residential detention site to another

Then the Patient’s Electronic Patient Record (EPR) is electronically transferred to the new residential detention site

E00445 - Additional Implementation Details

Solutions MUST comply with the following when implementing this Epic:

  • Transfer the Patient’s Electronic Patient Record (EPR) structured coded information and unstructured documents

  • Inter-detention transfer of the Patient’s Electronic Patient Record (EPR) will not use the NHS national message transport (e.g. GP2GP)


E00178 - Summary Care Record (SCR)

As a Health or Care Professional

I want to manage Summary Care Records for Patients

So that up to date Summary Care Records are available to be viewed

Acceptance criterion 1: create Summary Care Record

Given the Health or Care Professional is permitted to create Summary Care Records

When the Health or Care Professional selects to create a Summary Care Record for a Patient

Then the Summary Care Record is created

Acceptance criterion 2: update Summary Care Record

Given the Health or Care Professional is permitted to update Summary Care Records

When the Health or Care Professional selects to update the Summary Care Record for a Patient

Then the Summary Care Record is updated

Acceptance criterion 3: view Summary Care Record

Given the Health or Care Professional is permitted to view Summary Care Records

When the Health or Care Professional selects to view the Summary Care Record for a Patient

Then the Summary Care Record is displayed

Acceptance criterion 4: withdraw Summary Care Record

Given there is a Summary Care Record for a Patient

And the Health or Care Professional is permitted to withdraw Summary Care Records

When the Health or Care Professional selects to withdraw the Summary Care Record for a Patient

Then the Summary Care Record is withdrawn

E00178 - Additional Implementation Details

Solutions MUST comply with the following when implementing this Epic:


E00182 - General Practice Extraction Service (GPES)

As a Health or Care Professional

I want to submit data extracts to NHS Digital the Authority using the GPES Data Extraction Service

So that data relating to my GP Practice can be submitted to NHS Digital the Authority

Acceptance criterion 1: create GPES data extracts

Given there is GPES data to be submitted for the GP Practice

When the creation of the GPES data extract file is triggered

Then the GPES data extract file is created

E00182 - Additional Implementation Details

Solutions MUST comply with the following when implementing this Epic:


E00303 - extract vaccination data for Patients

As a Health or Care Professional

I want vaccination data recorded for Patients to be sent to NHS Digital the Authority on behalf of my Healthcare Organisation

So that vaccination data relating to recorded at my Healthcare Organisation for Patients can be submitted to NHS Digitalthe Authority

Acceptance criterion 1: create the vaccination data

extracts

extract file

Given there is vaccination data for Patients to be submitted for the Healthcare Organisation

When the creation of the vaccination data extract file is triggered

Then the vaccination data extract file is created

E00303 - Additional Implementation Details

Solutions MUST comply with the following when implementing this Epic:


E00446 - extract COVID-19 vaccination data recorded for Patients

As a Health or Care Professional

I want COVID-19 vaccination data recorded for Patients to be sent to the Authority on behalf of my Healthcare Organisation

So that vaccination data recorded at my Healthcare Organisation for Patients can be submitted to the Authority

Acceptance criterion 1: create the COVID-19 vaccination data extract file

Given there is COVID-19 vaccination data for Patients to be submitted for the Healthcare Organisation

When the creation of the COVID-19 vaccination data extract file is triggered

Then the COVID-19 vaccination data extract file is created

E00446 - Additional Implementation Details

Solutions MUST comply with the following when implementing this Epic:


E00285 - National Data Opt-Out

As a Health or Care Professional 

I want the Solution to retrieve and uphold each Patient’s National Data Opt-Out preference for data dissemination

So that only appropriate Patient data is included when sharing confidential Patient information for purposes beyond individual care in line with national policy

Acceptance criterion 1: uphold National Data Opt-Out preferences

Given a Patient data extract has been triggered

When a Patient has a National Data Opt-Out recorded

Then they are excluded from the Patient data extract

E00285 - Additional Implementation Details

Solutions MUST comply with the following when implementing this Epic:


E00680 - automatically update Patient details for received PDS Record Change notifications

As a Health or Care Professional

I want to receive notifications when PDS information for a Patient is updated by the Patient

So that the information held for Patients by my Healthcare Organisation can be automatically updated

Acceptance Criterion 1: automatically update mobile phone number for Patients

Given a PDS Record Change notification has been received for a Patient

And the source of the change is specified as the Patient in the PDS Record Change notification

When the PDS Record Change notification includes a mobile phone number change for the Patient

Then the Patient’s mobile phone number is automatically updated

Acceptance Criterion 2: automatically update email address for Patients

Given a PDS Record Change notification has been received for a Patient

And the source of the change is specified as the Patient in the PDS Record Change notification

When the PDS Record Change notification includes an email address change for the Patient

Then the Patient’s email address is automatically updated

E00680 - Additional Implementation Details

Solutions MUST comply with the following when implementing this Epic:

...