MINIMUM SYSTEM SPECIFICATION (MSS)

Size: px

Start display at page:

Download "MINIMUM SYSTEM SPECIFICATION (MSS)"

Gavin Todd
5 years ago
Views:

1 MINIMUM SYSTEM SPECIFICATION (MSS) PROCESSES AND PROCEDURES FOR NHS WALES COMPLIANT SYSTEMS [Summary Document]

2 MSS Scheme Development Processes and Procedures 1.0 PURPOSE This document describes the NHS Wales Assurance Process for the Welsh Minimum System Specification (MSS) for primary care systems. MSS has two functions for GP clinical/prescribing systems: 1. An MSS Compliance Standard for NHS Wales-specified functionality, according to released versions, linked to the contractual requirements of the GMS Systems and Services Framework Agreement published by NHS Wales; 2. An MSS Assurance Process and steps required between NHS Wales and the system supplier to reach the compliance standard and deployed functionality. MSS has two functions for CP patient/dispensing systems: 1. An MSS Compliance Standard for NHS Wales-specified functionality, according to released versions, linked to the Essential Service requirements of the Community Pharmacy Contractual Framework; 2. An MSS Assurance Process and steps required between NHS Wales and the system supplier to reach the compliance standard and deployed functionality. MSS Compliance MSS Compliance standards are defined and specified by the NHS Wales Informatics Service (NWIS). The Primary Care Informatics Programme (PCIP) of NWIS is responsible for implementing agreed sets of common, compliant standards for all its primary care contractor patient/clinical systems. System suppliers can successfully gain MSS Compliance by successful advancement through the MSS Assurance process. MSS Assurance The MSS Assurance process was established to support current and future MSS Compliance standards of NHS Wales, through NWIS. IM&T MSS P&P1 Issue 01 Page 2 of 10

3 MSS Scheme Development Processes and Procedures The MSS Assurance Process is based on the core elements of the NHS Connecting for Health Common Assurance Process CAP for clinical systems. The purpose of this document is to explain the activities involved in the request process, to assist anyone who applies to understand and perform their role and responsibilities. 2.0 MSS STEERING GROUP (GP SYSTEM REQUIREMENTS) The MSS for GP System Suppliers (MSS-GP) is developed and maintained by the MSS Steering Group, led by members of the Primary Care Informatics Programme with wider input from key stakeholder groups within NWIS, plus clinicians, LHBs and system users and suppliers. The Design & Compliance Steering Group will act in the capacity of process sponsors, providing greater governance and quality assurance to the overall MSS assurance process. The main responsibilities of the group are: To oversee development of a process that assures the definition, development, implementation and operation of GP clinical systems information technology solutions the MSS Process Ensure quality assurance to the overall MSS process Review new requirements proposed for entry into the MSS, ensuring that there is a sound business justification for proposed changes, and to agree the final scope of release to GP IT Suppliers for development In collaboration with the Primary Care IM&T Programme, ensure an effective controlled project environment is being enforced to deliver benefits to General Practice and NHS Wales Review testing outputs to confirm GP IT System compliance status Act as point of escalation for any issues raised To work in collaboration with the GP Systems Purchase Consortium and the Systems User Reference Group in assessing GP clinical system requirements To provide a link to the National Architecture Design Board To liaise with other home countries e.g. the English CAP-GP programme and Scottish SEF Group, to keep up to date with UK developments To assist in disseminating agreed system developments back to the stakeholder groups. IM&T MSS P&P1 Issue 01 Page 3 of 10

4 MSS Scheme Development Processes and Procedures 3.0 MSS STEERING GROUP (CP SYSTEM REQUIREMENTS) The MSS for CP System Suppliers (MSS-CP) is developed and maintained by a Design Assurance Group, led by members of the Primary Care Informatics Programme, with wider input from key stakeholder groups within NWIS, plus clinician and supplier input. The Design Assurance Group will act in the capacity of process sponsors, providing greater governance and quality assurance to the overall MSS assurance process. The main responsibilities of the group are: To oversee development of a process that assures the definition, development, implementation and operation of CP patient/dispensing systems information technology solutions the MSS Process Ensure quality assurance to the overall MSS process Review new requirements proposed for entry into the MSS, ensuring that there is a sound business justification for proposed changes, and to agree the final scope of release to CP system suppliers for development In collaboration with the PCIP, ensure an effective controlled project environment is being enforced to deliver benefits to Community Pharmacy and NHS Wales Review testing outputs to confirm CP system compliance status Act as point of escalation for any issues raised To provide a link to the National Architecture Design Board, if applicable To liaise with other home countries e.g. the English CAP-GP programme and Scottish SEF Group, to keep up to date with UK developments To assist in disseminating agreed system developments back to the stakeholder groups. IM&T MSS P&P1 Issue 01 Page 4 of 10

5 MSS Scheme Development Processes and Procedures 4.0 PROCESS MAP IM&T MSS P&P1 Issue 01 Page 5 of 10

6 5.0 DETAILED STEPS The following table describes the detailed steps to be performed and responsible parties during the MSS process. Step Input Activity Output Who Sponsor creates a A request form is completed The completed form is passed on to Sponsor 1 request the MSS Office 2 Completed Request Form The request form is Filtered and validated Checked Request Form If information is found to be inaccurate the request will be rejected and the process would move to step 6 If all information is correct the form can be passed on to the Steering Group step 3 MSS Office 3 Checked Request form The request is reviewed and funding checked If funding has been identified it goes to step 5 If funding has not been identified it goes to step 4 Steering Group 4 Un-Identified funding request The funding side of the request is reviewed to see if it is viable The checked request form is then passed on to the MSS Office Purchase Consortium 5 Checked request form The request is then checked to see if it is ready for Publication If the form is ready for publication it goes to step 7 If it has failed its review with either the Steering Group or Steering Group

7 MSS Scheme Development Processes and Procedures the Purchase Consortium it goes to step 6 6 Failed Request Form Feedback / Clarification to Sponsor Request failed The Sponsor may have an opportunity to reapply with a new request form MSS Office and Sponsor 7 Request ready for Publication The information is then published in the Maturity Model including the Change Control information Maturity Model published The request can move on to Step 8 MSS Office 8 Published Request The specification from the request is then published Specification Submitted to suppliers MSS Office 9 Submitted Specification The Design is created and submitted to the Sponsor Submitted Design System Suppliers 10 Submitted Design Design is reviewed Approved Design goes to step 11 Unapproved design goes back to step 9 Sponsor 11 Approved Design Authority is given to Proceed The Sponsor and System Supplier can then move to step 12 IM&T MSS P&P1 Issue 01 Page 7 of 10 Steering Group

8 MSS Scheme Development Processes and Procedures The System Supplier can move on to step Authority to Proceed The Sponsor and System Suppliers then agree on a deployment plan Agreed Deployment Plan Submitted to Steering Group Sponsor and System Supplier 13 Authority to Proceed Development The system can now be developed Developed System System Supplier 14 Developed System Build The system can now be built Built System System Supplier 15 Built System Suppliers Initial Testing is carried out to iron out any problems and check it is up to standard Tested System System Suppliers 16 Tested System Witness Testing will be performed and witnesses will be supplied by the sponsor to confirm the results are accurate Witness testing completed Report generated and checked by sponsor before moving to step 17 Sponsor 17 Witness testing The Witness testing Report is If the Witness Testing is MSS Office IM&T MSS P&P1 Issue 01 Page 8 of 10

9 MSS Scheme Development Processes and Procedures Report reviewed deemed Successful it moves on to step 18 If the Witness Testing has failed it is moved back to steps 12 and Successful Witness Testing Approval can now be given Approval Granted Steering Group 19 Approval Granted 1 st of Type Deployment Testing can begin A relevant practice is chosen to host the pilot The system supplier has to ready the practice in terms of equipment and training before this starts The whole process has to be documented throughout the pilot Deployment Testing Completed Report generated and passed to Steering Group for review System Suppliers 20 Completed Deployment Testing and report The report is reviewed and it is decided weather or not to give the Authority to Deploy If Authority to Deploy is given the request moves on to step 21 If it failed to get authority to Deploy then it must move back to step 19 IM&T MSS P&P1 Issue 01 Page 9 of 10 Steering Group

10 MSS Scheme Development Processes and Procedures 21 Authority to Deploy given A Milestone Certificate will be granted to successful Systems milestone certificate issued Information passed on to WIGSB Steering Group 22 Milestone Certificate Full Rollout This enables the system supplier to offer the new system to GP s this system then goes as an offering in the contract schedule Full Rollout If a supplier fails to meet the maximum deployment timescale they risk losing compliance status System Suppliers IM&T MSS P&P1 Issue 01 Page 10 of 10

EPS Implementation Group. Terms of Reference

EPS Implementation Group. Terms of Reference EPS Implementation Group Programme ETP DOCUMENT RECORD ID KEY Sub-Prog / EPS / JIT Project TBC Prog. Director Ian Lowry Prog. Manager Rachel Version 1.0 Habergahm Author Kieron Martin Version Date 1 st