Secondary Care Domain Overview
You are viewing an older version of the secondary care EPR requirements. The current version, which supersedes this version, can be found here
Requirements release | 2.0 |
|---|---|
Publication date | 16/08/2022 |
Status | Retired |
What is the purpose of the catalogue?
The catalogue sets out the minimum digital foundation (MDF) for electronic patient records (EPR). These foundation capabilities are capabilities that form the minimum, base or foundation set of functional capabilities required to support the day-to-day operation of the organisation. A set of clinical and business capabilities is necessary to meet the minimum clinical and administrative system requirements to carry out the provider functions.
As the MDF is defined as the minimum functionality throughout the catalogue there are transformation and innovative capabilities. Transformative capabilities are needed to improve business capabilities, and meet the ever-changing patient need. Innovative capabilities are intended to transform the patient experience.
Role of the Purchaser
The purchaser must ensure that they meet at least the MDF core capabilities. It is understood that some trusts may have an existing digital infrastructure and that it may not be required to purchase an entire system, interoperability between the existing and proposed new systems should be considered.
It is understood that trusts may have specific and individual requirements over and above what is listed here. Existing procurement procedures can be used and this catalogue is intended as guidance and a checklist to ensure compliance. Acceptance criteria, scoring and weighting can be used at the trust’s discretion.
Role of the Supplier
Suppliers must ensure that their product(s) fulfil at least the MDF core capabilities, compliance with all the acceptance criteria as set out in the catalogue is required and suppliers must be able to provide proof of compliance. Partial or future compliance is not acceptable.
Definition of Terms
EPR - Electronic Patient Record.
MDF - Minimum Digital Foundation, this is the minimum functionality required for an EPR defined by NHS frontline digitisation programme. This covers the digital technology to allow the eight core digital capabilities.
Core Requirements Map - A map of the core requirements, level 0 and 1 core requirements and user stories.
MDF Capability - these are the eight, core digital capabilities; records management, transfer of care, diagnostics, management, medicines management, decisions support, remote and assistive care, asset and resource management and business and clinical intelligence.
Core Requirement - These core requirements describe a specific scenario that the business service requires to operate effectively. Each core requirement relates back to a capability. Each one of these has one or many user stories underneath.
User Story - This is a story written from the user’s perspective, it states the functionality required and not the method of delivery, The format is, As a, I want, So that.
Acceptance Criteria - Each User Story has either one or more acceptance criteria. These are written in the format, Given, When, Then. These criteria are binary, comply or not comply.
User Persona - a detailed description and a profile of a typical user that is likely to interact with the product.
Application Function - is a desired piece of functionality or action that is required from the software.
Contents
The Core Requirements Map is the map of the Core Requirements and their trace back to the EPR MDF. Rows coloured green show EPR MDF Core level requirements, rows coloured yellow are EPR MDF Transformation and Innovation level requirements.
User persona details the persona that will use and interact with the system, this is not an exclusive list rather details of the expected main users.
This is a list of applicable standards that are included, this includes DCB, ISB & SCC guidance and some generic guidance. EPR suppliers must demonstrate compliance with relevant standards.
Non-functional requirements define the system attributes and qualities. They ensure the usability and effectiveness of the entire system.
The Application Functions describe the abilities of the software functions in an EPR application by Capability. The Application Functions Catalogue extends links to the User Stories and Core Requirements.