Meeting Summary 30th August 2019 - Infrastructure and Design

Meeting between ESR and HEE regarding infrastructure and design

Attendees

• Nazia Akhtar
• Betrand Ugorji
• Craig Elton
• Alan Milsom
• Paul Hoang
• Phil James
• Victoria Hartland
• Alistair Pringle

The discussion took over Skype for business where we had the opportunity to share diagrams and desktops

The conversation started off with Paul attempting to get people on the call on the same page in regards to the creation of Positions in ESR and how Trainees and Posts are created in TIS.
This was done using a diagram that was created to illustrate what was done for the MVP (https://hee-tis.atlassian.net/wiki/spaces/NTCS/pages/532545539/ESR-TIS+Inbound+and+Outbound+flows+MVP)
The discussion was mainly around the reasoning of the reconciliation process, the history and current processes around it.

Paul talked about a new data journey where Position records could be created/updated when Posts are in TIS, this could potentially simplify things in that the reconciliation phase will no longer need to be done, users of ESR will no longer need to create Positions manually while entering the 15+ alphanumeric Post/Deanery Number therefore minimising poor data quality.

It also has the potential for removing the Position Reconciliation type records from the RMT shrinking file sizes and potentially lowering processing required on ESR/The Hub
The conversation quickly turned to the technical challenges and process's that may need to happen for this to work but concluded that further investigation was required

A recap was also done by Alan around the initial designs TIS provided around pushing data straight from The Hub to the Azure blob storage; He shared that it was possible but not yet committed to implementing it for this project

Paul asked a question around possible changes that ESR would like to see and the subject of the Dashboard was brought up. This dashboard would display information on what Positions from ESR failed the reconciliation process. This would ultimately help the ESR support team as they need this information to help Users of ESR
It was mentioned that this feature was already in the backlog and that it would get worked on depending on priorities.
Phil also showed the information already available to some users via metabase regarding this data and the work that was already done to try and share this with ESR but issues with Information Governance blocked it. Further queries are needed to find out what exactly is the issue so that it can be shared

Phil also raised a question regarding the frequency in which ESR can consume data, Victoria mentioned that ESR may be able to process up to twice a day but that was a conservative figure as this will need to be investigated

The meeting ended with a commitment to meet again in approximately 3 weeks