Background
A Service Standard is being introduced to describe the Community Pharmacy Clinical Services service, including the associated features and operating capabilities.
Introduction to Service Standards
A new class of Standard is being introduced into the Digital Services for Integrated Care (DSIC) environment; the Service Standard.
What is a Service Standard?
A Service Standard is a DSIC representation of the required components of a discretely delivered 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 Service 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.
What is a Service Standard used for?
The purpose of a Service 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.
The Service 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.
Service Standard Structure
A Service 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 Service Standard and are necessary for the safe and effective operation of the service as a whole).
Outline Plan
The Service 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 Consultation information for Patients
12/01/2024
CPC010 - access Patient Group Directions (PGD)
31/01/2024
CPC017 - submit records of Patient Consultations to their registered GP Practice
31/01/2024
Summary of Change
Community Pharmacy Consultation Capability |
Epic and Acceptance Criterion Titles |
CPC001 - verify Patient information using Personal Demographics Service (PDS)Acceptance criterion 1: verify Patient information using Personal Demographics Service (PDS)CPC001 - Additional Implementation DetailsSolutions MUST comply with the following when implementing this Epic:
CPC002 - view Patient Clinical Information held outside of the Health or Care OrganisationAcceptance criterion 1: view Patient Clinical Information held outside of the Health or Care OrganisationCPC002 - Additional Implementation DetailsSolutions MUST comply with one of the following when implementing this Epic:
CPC003 - record medicine and medical device details for a PatientAcceptance criterion 1: record medicine and medical device details for a PatientCPC003 - Additional Implementation DetailsSolutions MUST comply with the following when implementing this Epic:
CPC004 - notify Health or Care Professional to provide worsening advice to Patient for Minor Illness ConsultationAcceptance criterion 1: notify Health or Care Professional to provide worsening advice to Patient for Minor Illness ConsultationCPC004 - Additional Implementation DetailsSolutions MUST comply with the following when implementing this Epic: CPC005 - notify Health or Care Professional to signpost Patient to registered GP PracticeAcceptance criterion 1: notify Health or Care Professional to signpost Patient to registered GP PracticeCPC005 - Supporting Information
CPC006 - access Electronic Prescription Service (EPS) Prescription TrackerAcceptance criterion 1: access Electronic Prescription Service (EPS) Prescription TrackerCPC006 - Additional Implementation DetailsSolutions MUST comply with the following when implementing this Epic:
CPC010 - access Patient Group Directions (PGD)Acceptance criterion 1: access Patient Group Directions (PGD)CPC010 - Additional Implementation DetailsSolutions MUST comply with the following when implementing this Epic:
CPC011 - record Patient consent to participate in a ConsultationAcceptance criterion 1: record Patient consent to participate in a ConsultationCPC012 - record Patient consent to sharing data with Health or Care OrganisationsAcceptance criterion 1: record Patient consent to sharing data with Health or Care OrganisationsCPC013 - retrieve Health or Care Organisation details using Directory of Services (DoS)Acceptance criterion 1: retrieve Health or Care Organisation details using Directory of Services (DoS)CPC013 - Additional Implementation DetailsSolutions MUST comply with the following when implementing this Epic:
CPC014 - print NHS FP10DTAcceptance criterion 1: record information for NHS FP10DTAcceptance criterion 2: print NHS FP10DTCPC014 - Additional Implementation DetailsSolutions MUST comply with the following when implementing this Epic: CPC015 - manage 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:
CPC016 - submit records of Patient Consultations to the NHS Business Services Authority (NHSBSA)Acceptance criterion 1: submit records Patient Consultations to the NHS Business Services Authority (NHSBSA)CPC016 - Additional Implementation DetailsSolutions MUST comply with the following when implementing this Epic:
CPC017 - submit records of Patient Consultations to their registered GP PracticeAcceptance criterion 1: submit records of Patient Consultations to their registered GP PracticeCPC017 - Additional Implementation DetailsSolutions MUST comply with the following when implementing this Epic:
|
Secondary Artefacts |
The following requirements are overarching across the Capabilities within the Service Standard:
|
Full Specification
The Community Pharmacy Clinical Services Service Standard links will be provided at a later date.
Assurance Approach
In order to achieve assured status against a Service 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 Service Standard is confined to elements of the software which are concerned with the service in question. Therefore the presence of a Service Standard does not necessarily mean that assurance of a whole Supplier Solution has occurred under the DSIC, unless that is stated elsewhere.