Page Properties | ||||||||
---|---|---|---|---|---|---|---|---|
| ||||||||
|
Page Properties | ||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||||||
|
Background
A Service Supplementary Care 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.
Summary of Change
...
Community Pharmacy Referral Management Capability
...
Epic and Acceptance Criterion Titles
CPRM001 - receive Referral for a Patient from a Health or Care Organisation
Acceptance criterion 1: receive Referral for a Patient from a Health or Care Organisation
CPRM001 - Additional Implementation Details
Solutions MUST comply with the following when implementing this Epic:
Inbound GP Referral Standard
Interoperability Standard TBC (likely to be NHS approved Standard e.g. Booking and Referral Standard (BaRS))
Inbound 111 Referral Standard
Utilising Interoperability Toolkit (ITK) Standard for referrals from 111 TBC
Community Pharmacist Consultation Service data specification TBC
CPRM002 - notify Health or Care Professional of a new Referral
Acceptance criterion 1: notify Health or Care Professional of a new Referral
CPRM003 - manage inbound Referrals
Acceptance criterion 1: view Patient Referral information
Acceptance criterion 2: sort Referrals
Acceptance criterion 3: amend Referral Status
CPRM004 - flag overdue Referrals
Acceptance criterion 1: flag overdue Referrals
CPRM005 - manage Patient Referral information
Acceptance criterion 1: record Patient Referral Information
Acceptance criterion 2: amend Patient Referral information
CPRM005 - Additional Implementation Details
Solutions MUST comply with the following when implementing this Epic:
Community Pharmacist Consultation Service data specification TBC
Pharmacy Contraception Service data specification TBC
Community Pharmacy Blood Pressure Check Service data specification TBC
CPRM006 - refer a Patient to a Health or Care Organisation
Acceptance criterion 1: refer a Patient to a Health or Care Organisation
...
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 Details
Solutions MUST comply with the following when implementing this Epic:
Personal Demographics Service (PDS) Standard
CPC002 - view Patient Clinical information held outside of the Solution
Acceptance criterion 1: view Patient Clinical information held outside of the Solution
CPC002 - Additional Implementation Details
Solutions MUST comply with one of the following when implementing this Epic:
Summary Care Record application (SCRa) can be utilised until automatic re-direction to National Care Records Service (NCRS)
GP Connect Access Record/National Record Locator Service (NRLS)/National Care Records Service (NCRS) TBC
Appropriate Standard likely to be based on GP Connect Access Record/NRLS/NCRS for new integrations (i.e. those which are NOT currently deployed into an operational environment)
Shared Care Records TBC
CPC003 - record medicine and medical device details for a Patient
Acceptance criterion 1: record medicine and medical device details for a Patient
CPC003 - Additional Implementation Details
Solutions MUST comply with the following when implementing this Epic:
Pre-configurable medicine and medical device details will adhere to SCCI0052: Dictionary of medicines and devices (dm+d)
CPC004 - notify Health or Care Professional to provide worsening advice to Patient
Acceptance criterion 1: notify Health or Care Professional to provide worsening advice to Patient
CPC005 - notify Health or Care Professional to signpost Patient to GP
Acceptance criterion 1: notify Health or Care Professional to signpost Patient to GP
CPC006 - access Electronic Prescription Service (EPS) Tracker
Acceptance criterion 1: access Electronic Prescription Service (EPS) Tracker
CPC006 - Additional Implementation Details
Solutions MUST comply with the following when implementing this Epic:
Access to be provided to Open the EPS Tracker on Electronic Prescription Service (EPS) Prescription Tracker
CPC007 - access NICE Clinical Knowledge Summaries (CKS)
Acceptance criterion 1: access NICE Clinical Knowledge Summaries (CKS)
CPC007 - Additional Implementation Details
Solutions MUST comply with the following when implementing this Epic:
Access to be provided to NICE Clinical Knowledge Summaries (CKS)
NICE Clinical Knowledge Summaries (CKS) is available for:
Community Pharmacist Consultation Service (Minor Illness)
Community Pharmacy Blood Pressure Check Service
Pharmacy Contraception Service
CPC008 - access Contraception advice tools
Acceptance criterion 1: access Contraception advice tools
CPC008 - Additional Implementation Details
Solutions MUST comply with the following when implementing this Epic:
Access to be provided to at least one of the following:
CPC009 - access BMI calculator
Acceptance criterion 1: access BMI calculator
Info |
---|
CPC009 - Supporting Information
|
CPC010 - access Patient Group Directions (PGD)
Acceptance criterion 1: access Patient Group Directions (PGD)
CPC011 - record Patient consent for participating in a Consultation
Acceptance criterion 1: record Patient consent for participating in a Consultation
CPC012 - record Patient consent to sharing data with Health or Care Organisations
Acceptance criterion 1: record Patient consent to sharing data with Health or Care Organisations
CPC013 - 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 Details
Solutions MUST comply with the following when implementing this Epic:
Directory of Services (DoS) Standard TBC
CPC014 - print NHS FP10DT
Acceptance criterion 1: print NHS FP10DT
CPC014 - Additional Implementation Details
Solutions MUST comply with the following when implementing this Epic:
CPC015 - manage Consultation information for a Patient
Acceptance criterion 1: record Consultation information for a Patient
Acceptance criterion 2: send notification to Patient’s registered GP Practice
Acceptance criterion 3: view Consultation information for a Patient
CPC015 - Additional Implementation Details
Solutions MUST comply with the following when implementing this Epic:
Consultations to be recorded in accordance with:
Professional Record Standards Body (PRSB) Community Pharmacy Standard
Records Management Code of Practice for Health and Social Care 2021
NHS Data Security and Protection Toolkit (IT Supplier)
Community Pharmacy Blood Pressure Check Service data specification TBC
Community Pharmacist Consultation Service data specification TBC
Outbound GP Notification Message Standard
Interoperability Standard TBC (likely to be NHS approved Standard e.g. GP Connect Update Record) to send notification to a Patient’s registered GP Practice
CPC016 - share a record of a Patient’s Consultation to the NHS Business Services Authority (NHSBSA)
...
CPC016 - Additional Implementation Details
Solutions MUST comply with the following when implementing this Epic:
Developer Guide to the NHS Business Services Authority API for Contraception claims TBC
BSA Claims and Reporting Interoperability Standard TBC
...
Secondary Artefacts
...
The following requirements are overarching across the Capabilities within the Service Standard:
Non-Functionals
IT platform Suppliers are required to provide helpdesk support for the following periods:
Monday to Friday: 8am – 6pm
Weekends: 8am – 2pm
Bank holidays: Response within 24 hours
Information Governance
Only authenticated users should access the IT platform. i.e. Pharmacists (and technicians where appropriate.
Practitioners should register using their full name (as registered with GPhC) and GPhC number.
Where onward referral is applied, Pharmacists must ensure that Patients consent to data being shared with new organisation.
Service Management
Issues affecting service provision must be acknowledged within 24 hours.
Issues reported by users, that affect service provision, must be reported to the NHS National Helpdesk as soon as possible.
IT issues affecting service availability and planned outages should be reported to the National Service Desk (NSD) by calling 0300 303 5035 or by emailing ssd.nationalservicedesk@nhs.net.
The incident report should include all data fields as defined in the service Data Specification. The completed form must be sent as PDF to the [pre-configured] NHSmail address of the CPCS Service Manager.
The IT platform must generate a monthly return to send to each NHS Trust to satisfy key performance indicators: KP10, KP11 and KP13.
Full Specification
The Community Pharmacy Clinical Services Service Standard links will be provided at a later date.
all Capabilities, Epics and Interoperability Standards. The Capability; ‘Consultation Management - Community Pharmacy’ and Standards ‘NHSBSA Claims & Reporting’ and ‘Directory of Services (DoS) - Urgent and Emergency Care’ will be mandated as part of the Supplementary Care Standard.
Outline Plan
The following Epics in the 'Consultation Management - Community Pharmacy' Capability have associated dates attached by which Suppliers must be compliant:
E00625 - manage Community Pharmacy Consultation Information for Patients
12/01/2024
E00637 - launch Patient Group Directions (PGDs) for Community Pharmacy Consultations
31/01/2024
E00631 - submit records of Patient Consultations to registered GP Practice for Community Pharmacy Consultations
31/01/2024
Summary of Change
Community Pharmacy Clinical Services Supplementary Care Standard: New Supplementary Care Standard added |
|
Consultation Management - Community Pharmacy: New Capability added |
|
NHSBSA Claims & Reporting: New Standard added |
|
Directory of Services (DoS) - Urgent and Emergency Care: New Standard added |
|
Full Specification
Community Pharmacy Clinical Services Supplementary Care Standard
Consultation Management - Community Pharmacy
NHSBSA Claims & Reporting
Directory of Services (DoS) - Urgent and Emergency Care
Assurance Approach
In order to achieve assured status against a Service Supplementary Care Standard a Supplier must go through an assurance process which includes:
...
The assurance undertaken for a Service Supplementary Care Standard is confined to elements of the software which are concerned with the service in question. Therefore the presence of a Service Supplementary Care Standard does not necessarily mean that assurance of a whole Supplier Solution has occurred under the DSIC, unless that is stated elsewhere.