Background
A Supplementary Care Standard is being introduced to describe the Community Pharmacy Clinical Services service, including the associated features and operating capabilities.
Introduction to Supplementary Care Standards
A new class of Standard is being introduced into the Digital Services for Integrated Care (DSIC) environment; the Supplementary Care Standard.
What is a Supplementary Care Standard?
A Supplementary Care Standard describes the DSIC representation of the functional, technical and/or operating conditions required to deliver a specific service within a health and care setting, that can:
Map to services that might be directly commissioned from providers (such as the Community Pharmacy Clinical Services which are part of the Community Pharmacy Commissioning Framework)
Be discretely identified within a commissioning contract, such as Enhanced Access, Anticipatory Care, Enhanced Health in Care Homes etc., which are all newly specified services within the NHS England Network Contract DES - the Primary Care Network (PCN) contract for GPs
Be a new controlled service operating within a domain (such as Community Services Electronic Prescription Service (EPS) Prescribing) which the Authority is seeking to roll out and make available to users
A Supplementary Care Standard operates within DSIC in the same manner that any other Standard operates under the Agreement in relation to Change Management, the Roadmap, Assurance etc.
Examples:
Community Pharmacy Consultations Supplementary Care Standard
DES Enhanced Access Supplementary Care Standard
DES BI Tools Supplementary Care Standard
What is a Supplementary Care Standard used for?
The purpose of a Supplementary Care Standard is to describe a domain specific service, feature or operating capability to a customer, which they can use to confirm the existence of the service feature or operating capability and its valid operation within a given application.
It allows us to group requirements that cover multiple Capabilities when there isn’t a Procurement Product
It’s used to define requirements for a specific service rather than just a Capability or whole Solution, meaning we can focus more on mandatory requirements and assurance ask is potentially smaller
The Supplementary Care Standard is also used for identifying and managing change within the whole service as it can be amended via the Roadmap as services are updated. The Roadmap can also be used to incentivise delivery of the Standard or changes to the Standard via a Roadmap Award.
Supplementary Care Standard Structure
A Supplementary Care Standard follows similar principles to Capabilities and Standards and consists of:
Epic level User Stories (either directly or through the inclusion of one or more Capabilities)
Additional Implementation Details associated with some Epics which mandate related:
Interoperability Standards
Data Standards
Non-Functionals specific to the implementation of the Epic
Secondary Artefacts (these are Non-Functionals derived from the DSIC Overarching Standards, which are overarching for the Supplementary Care Standard and are necessary for the safe and effective operation of the service as a whole)
Outline Plan
The Supplementary Care Standard; including all Capabilities, Epics, Interoperability Standards and Secondary Artefacts, will be developed further as requirements are finalised.
The following Epics have associated dates attached by which Suppliers must be compliant:
CPC015 - manage Community Pharmacy Consultation Information for Patients
12/01/2024
CPC010 - launch Patient Group Directions (PGDs) for Community Pharmacy Consultations
31/01/2024
CPC017 - submit record of Patients Urgent Medicine Supply Service Consultation to registered GP Practice for Community Pharmacy Consultations
31/01/2024
Summary of Change
Consultation Management - Community Pharmacy: Capability added |
Epic and Acceptance Criterion Titles |
CPC011 - record Patients Consent for Community Pharmacy ConsultationsAcceptance criterion 1: record Patients Consent for Community Pharmacy ConsultationsCPC011 - Additional Implementation DetailsSolutions MUST comply with the following when implementing this Epic:
CPC015 - manage Community Pharmacy Consultation Information for PatientsAcceptance criterion 1: record Consultation Information for PatientsAcceptance criterion 2: view Consultation Information for PatientsCPC015 - Additional Implementation DetailsSolutions MUST comply with the following when implementing this Epic:
CPC002 - view information from the Electronic Patient Record (EPR) of the Patient during Community Pharmacy ConsultationsAcceptance criterion 1: view information from the Electronic Patient Record (EPR) of the Patient during Community Pharmacy ConsultationCPC002 - Additional Implementation DetailsSolutions MUST comply with one of the following when implementing this Epic:
CPC003 - record medications for Patients using dictionary of medicines and devices (dm+d) for Community Pharmacy ConsultationsAcceptance criterion 1: record medications for Patients using dictionary of medicines and devices (dm+d) for Community Pharmacy ConsultationsCPC003 - Additional Implementation DetailsSolutions MUST comply with the following when implementing this Epic:
CPC014 - print NHS FP10DT for Patients' medication for Community Pharmacy ConsultationsAcceptance criterion 1: print NHS FP10DT for a Patient's medication for Community Pharmacy ConsultationsCPC014 - Additional Implementation DetailsSolutions MUST comply with the following when implementing this Epic: CPC004 - alert Health or Care Professional to provide Worsening Advice to Patients for Community Pharmacy Minor Illness ConsultationAcceptance criterion 1: alert Health or Care Professional to provide Worsening Advice to Patients for Community Pharmacy Minor Illness ConsultationCPC004 - Additional Implementation DetailsSolutions MUST comply with the following when implementing this Epic:
CPC005 - notify Health or Care Professional to signpost Patients to registered GP Practice for Community Pharmacy ConsultationsAcceptance criterion 1: notify Health or Care Professional to signpost Patients to registered GP Practice for Community Pharmacy ConsultationsCPC005 - Supporting Information
CPC017 - submit record of Patients Urgent Medicine Supply Service Consultation to registered GP Practice for Community Pharmacy ConsultationsAcceptance criterion 1: submit record of Patients Urgent Medicine Supply Service Consultation to registered GP Practice for Community Pharmacy ConsultationsCPC017 - Additional Implementation DetailsSolutions MUST comply with the following when implementing this Epic:
CPC016 - submit record of Patients Consultation to NHS Business Services Authority (NHSBSA) for Community Pharmacy ConsultationsAcceptance criterion 1: submit record of Patients Consultation to NHS Business Services Authority (NHSBSA) for Community Pharmacy ConsultationsCPC016 - Additional Implementation DetailsSolutions MUST comply with the following when implementing this Epic:
CPC013 - view Health or Care Organisation details using Directory of Services (DoS) for Community Pharmacy ConsultationsAcceptance criterion 1: view Health or Care Organisation details using Directory of Services (DoS) for Community Pharmacy ConsultationsCPC013 - Additional Implementation DetailsSolutions MUST comply with the following when implementing this Epic:
CPC006 - launch the Electronic Prescription Service (EPS) Prescription Tracker page for Community Pharmacy ConsultationsAcceptance criterion 1: launch the Electronic Prescription Service (EPS) Prescription Tracker page for Community Pharmacy ConsultationsCPC006 - Additional Implementation DetailsSolutions MUST comply with the following when implementing this Epic: CPC010 - launch Patient Group Directions (PGDs) for Community Pharmacy ConsultationsAcceptance criterion 1: launch Patient Group Directions (PGDs) for Community Pharmacy ConsultationsCPC010 - Additional Implementation DetailsSolutions MUST comply with the following when implementing this Epic:
CPC013 - view Health or Care Organisation details using Directory of Services (DoS) for Community Pharmacy ConsultationsAcceptance criterion 1: view Health or Care Organisation details using Directory of Services (DoS) for Community Pharmacy ConsultationsCPC013 - Additional Implementation DetailsSolutions MUST comply with the following when implementing this Epic:
CPC006 - launch the Electronic Prescription Service (EPS) Prescription Tracker page for Community Pharmacy ConsultationsAcceptance criterion 1: launch the Electronic Prescription Service (EPS) Prescription Tracker page for Community Pharmacy ConsultationsCPC006 - Additional Implementation DetailsSolutions MUST comply with the following when implementing this Epic: CPC010 - launch Patient Group Directions (PGDs) for Community Pharmacy ConsultationsAcceptance criterion 1: launch Patient Group Directions (PGDs) for Community Pharmacy ConsultationsCPC010 - Additional Implementation DetailsSolutions MUST comply with the following when implementing this Epic:
|
Secondary Artefacts |
The following requirements are overarching across the Capabilities within the Supplementary Care Standard:
|
Full Specification
The Community Pharmacy Clinical Services Supplementary Care Standard links will be provided at a later date.
Assurance Approach
In order to achieve assured status against a Supplementary Care Standard a Supplier must go through an assurance process which includes:
Capability Assessments
Standards Assurance
Some limited Non-Functional Solutions Assurance
First of Type (where necessary from a service perspective)
The assurance undertaken for a Supplementary Care Standard is confined to elements of the software which are concerned with the service in question. Therefore the presence of a Supplementary Care Standard does not necessarily mean that assurance of a whole Supplier Solution has occurred under the DSIC, unless that is stated elsewhere.