SUS+ User Group - digital.nhs.uk · Web viewQ. DOC asked for more information on the two severity three incidents that failed the SLA in September. ... with no extraordinary submission

Copyright © 2016 Health and Social Care Information Centre.NHS Digital is the trading name of the Health and Social Care Information Centre.

SUS+ User GroupNational Data Services Development Agenda and Minutes18th October 2017

SUS+ User Group

Table of Contents

Meeting details 3Agenda 3Actions 3Feedback from and to the SUS Programme Board 3Current SUS+ Service update 3Organisation Data Services (ODS) 5SUS+ Development Update 6AOB 7Attendance 7Next meeting 8

Copyright © 2017 Health and Social Care Information Centre.NHS Digital is the trading name of the Health and Social Care Information Centre. 2

SUS+ User Group

Meeting detailsDate 18th October 2017

Time 10:30 - 13:30

Location TSQ Bevan, Ground Floor, 1 Trevelyan Square, Boar Lane, Leeds, LS1 6AE

Remote access WebEx – Detailed in the calendar entry

Support contact Joanna Warwick – [email protected]

AgendaItem Agenda Item Presenter Schedule1 Welcome and apologies Chair 10:30

2 Review of previous meeting actions and minutes Chair 10:35

3 Feedback from and to the SUS Programme Board Chair 10:40

4 Current SUS+ Service Update Mark Stangroom 10:45

5 SUS+ Development Update Steve Fenner 11:15

6 Organisation Data Services (ODS)Michael Presence / Danny Ruttle

11:45

7 Any other business All 12:15

8 Meeting close All 12:30

ActionsReview of previous meeting actions and minutes.Minutes of the previous meeting were agreed.

Feedback from and to the SUS Programme BoardSH confirmed that the revised SUS+ User Group TOR have been amended slightly and are being presented back to the SUS board today for approval.

Current SUS+ Service updateMS confirmed that there have been no SUS+ service issues this month. There were 65 million records submitted during September with 3,376 interchanges. Volumes were typical of those expected at this time of year. There was 100% availability across the SUS+ Service during September.

The old SUS system was fully decommissioned on 11th September 2017. Q. DOC asked for more information on the two severity three incidents that failed the SLA in September.


SUS+ User Group

A. MS confirmed that the SLA was not met due to waiting for the weekly release. A severity three SLA has a turnaround time of five working days, and waiting for the weekly release date pushed the two incidents past this timeframe.

Inbound processing submissions showed a fairly regular pattern of activity, with no extraordinary submission of records or processing. The outbound processing graph showed a large delay on the 21 September.

Q. AN asked why the longest extract was double that of the previous month on the outbound submissions slide? A. MS confirmed that this was due to the queuing system, and larger extracts were held in the queue. Q. AB asked if the team were looking at the preference of extracts over submissions in April next year, and the daily requirement for ECDS as this needs to take priority. A. SF confirmed that the team need to work out the sequence payments associated with daily submissions, however, he didn’t think that daily ECDS submissions would delay the extracts significantly, but is something that needs to be worked out. AB stated that when ECDS is submitted it has to be processed within that day and therefore there is a need to know straight away if there are any issues. They would not be able to have submissions waiting for a day or longer. He also stated that NHSI are going to want to see ECDS daily within a timely fashion.MB also raised that there could potentially be some issues around April / May 2018 as HES, ECDS daily and the download and refresh of data will all be happening around the same period.AN asked if the team had done some profiling or load simulations to try and simulate what is going to happen. It was confirmed that the team have carried out volume and performance testing based on the busiest day plus 20-25 percent, however this was more of a system saturation test. AN proposed that simulation needs to take place, so that a plan can be put in place to avoid any issues happening in April 2018 when the pattern is due to change. SF confirmed that they would need to set some parameters for testing and asked that DSCROs report how they see their download patterns changing and what they anticipate for the year end so that this information could then be used to look at how the system could be tested. JB presented the attached slides which showed the SUS+ extract behaviours and performance at inclusion (19 September to 21 September). The graph showed that the majority of extracts had a run time of under 1 minute, with 1287 extracts running under 5 minutes and 40 extracts taking longer than 20 minutes.DOC felt that there had been a gap in the discovery phase of SUS+ as user experience was not taken into account. With the old SUS system DSCROs were getting extracts within 2 working days of the inclusion date, however, the current SUS+ system does not meet this, and is therefore not performing as well as the previous SUS system in this area. It was asked that the team revisit the SUS+ SLA, and that the team needed to be transparent with Commissioners on what the SLA is for the time to receive extracts, as there appears to be no clarity at present. It was confirmed that SUS+ is running faster overall however, it was not


SUS+ User Group

meeting DSCRO experience requirements, meaning that some user experience is worse. JB confirmed that there needed to be some discussions around this and how the system can be changed to improve this area originally which was not recognised and a gap in the discovery phase.Action: SF to arrange for future proof testing of the SUS+ system and put a plan in place to allow for the changes that will be introduced in April/May 2018, including liaising with ECDS to define their delivery schedules and expectations. AN confirmed that he could field people to help the team with the testing if needed.Action: SF to provide future SUS+ profiling / evidence to show what will happen when the changes are introduced in April/May 2018. This information is to be provided for the next meeting of the User Group. Action: MS to check Service Management SLAsAction: AB/SH to present at the October Programme Board the proposal for SUS+ future proof testing for the forthcoming changes in 2018, and put forward the DSCRO SLA proposal of a 24 hour turnaround. SF did confirm that if they stopped producing pbr elements of the SEM extracts, this would speed up the SEM extracts by around 30 percent, and therefore asked that DSCROs consider this as an option and let SF know if this would still meet their needs.Presented by: Mark StangroomAccompanying material:

Presented by: Jonathan BlissAccompanying material:

Organisation Data Services (ODS)Mike Presence, Lead Business Analyst presented the attached slides which detail what progress the Organisation Data Change Project has made to date.Conversations arising from the slides were as follows: AN asked if the project were liaising with UK Health Dimensions. MP confirmed that the team were already in contact with them. The User Group also stated that the team need ensure that NHS England and Health are also engaged.The slides detailed the timeline for the project, which showed that engagement was due to start in late November 2017 and finish by 18 March 2018. The project output will be a report to the NHS Digital Executive Management Team which will highlight the high level impacts of the changes across the health and


SUS+ User Group

social care system, and details the appropriate options for next steps. The report is due to be completed by 27 April 2018. Presented by: Mike PresenceAccompanying material:

Danny Ruttle, Senior System Designer, presented the attached slides on the ODS API Suite, which details the reasons for delivering an API, the advantages, and what will be included in the ODS API suite. The timeline included in the slides showed that there would be a wider release of the Service before the end of 2017, a Connect-athon is planned for February 2018 with a fully live service before the end of March 2018.It was confirmed that CSV would continue until the end of November 2021. In April 2020 the first new codes will be issued, however, only new codes will be allocated for anything new.Presented by: Danny RuttleAccompanying material:

SUS+ Development UpdateSF presented the attached slides, which detail what has been released this month, improvements planned for November and a SUS+ three month forward view. Discussions arising from the slides were as follows:AB and SH raised concern that the mandate given by the Programme Board cannot be fulfilled as the User Group are not getting the input into any prioritisation of development, and decisions on the prioritisation were being made outside of the User Group, which was not what was agreed at the Programme Board. They also raised that the interchange tracker/DQ appears to have been downgraded, however, they were not aware of this. SF confirmed that the team are receiving requests from a high level to do other work that was previously not done in SUS and some of it also has its own funding. The User Group confirmed it would be helpful to know who had requested that specific items need prioritising and that the Programme Board should have sight of this also.The Group felt that there were currently too many routes into the prioritisation list. AB confirmed that any proposals should be brought to the User Group for ranking on the prioritisation list and then taken to the Programme Board for a decision.


SUS+ User Group

Action: AB/SH to raise at the Programme Board, the lack of User Group involvement in the SUS+ development prioritisation, and ask for clarification/agreement on the process.

Presented by: Steve FennerAccompanying material:

AOBAN advised that DSCROs have already looked at the possibility of dropping SEM pbr from extracts, however, they did discover that there were some differences, and some information was missing. AN confirmed that if this was lined up so that all the information was added to the pbr extract then he could see no issue in dropping the SEM pbr extracts.AN confirmed that DSCROs need the ECDS full specification. AN raised concern around the use of JSON files as a priority over CSV, as DSCROs and providers cannot currently use JSON.

Attendance

Attendee Organisation Attendance

Andy Banks (AB)Chair NHS West Sussex Foundation Trust In personStuart Howard (SH) Blackpool Teaching Hospitals In personDan Taylor Countess of Chester Hospital NHS Trust In personLizzie Poole University Hospital Nottingham RemoteAndy Norman (AN) North East London DSCRO In personMark Bridges (MB) Central Midlands DSCRO In personGary Hardcastle York Teaching Hospital NHS Trust In personChris Taylor North England DSCRO RemoteDave Parsons Royal Surrey County NHS Foundation

Trust RemoteKath Yates NHS England In personNeil Hawes Spire Healthcare RemoteJames Sheffield South Devon and Torbay CCG RemoteJulian Hamer Optum UK RemoteMal Skelton Hull and East Yorkshire Hospitals NHS

Trust RemoteDavid O’Callaghan (DOC) North West DSCRO RemoteUchenna Anumadu Herts Valleys CCG RemoteJonathan Bliss (JB) NHS Digital In person


SUS+ User Group

Beverley Harris (BH) NHS Digital In personJames Salt (JS) NHS Digital In personSimon Robinson (SR) NHS Digital In personMark Stangroom (MS) NHS Digital In personStacey Handley NHS Digital In personSteve Fenner (SF) NHS Digital RemoteJason Brian NHS Digital RemoteMichael Presence (MP) (Agenda item 6 only)

NHS Digital In person

Danny Ruttle (DR)(Agenda item 6 only)

NHS Digital In person

Next meetingDate 15th November 2017Time 10:30 - 13:00Location TSQ Bevan, Ground Floor, 1 Trevelyan Square, Boar Lane,

Leeds, LS1 6AERemote access WebEx - TBC Support contact Joanna Warwick – [email protected]


mailto:[email protected]

Documents

SUS+ User Group - digital.nhs.uk · Web viewQ. DOC asked for more information on the two severity three incidents that failed the SLA in September. ... with no extraordinary submission