2019-12-16 Meeting notes

• Validation release. Tickets
  Error rendering macro 'jira' : Unable to locate Jira server for this macro. It may be due to Application Link configuration.
  and  Unable to locate Jira server for this macro. It may be due to Application Link configuration. haven't yet been completed it appears despite agreement during Wednesday's Validation Meeting that they would be done by Friday. George Swinnerton will do  Unable to locate Jira server for this macro. It may be due to Application Link configuration.  today. He will also look at Unable to locate Jira server for this macro. It may be due to Application Link configuration.  and see if it has been completed or not. james.griffin (Unlicensed) was due to complete this before he went on Holiday on Friday. A Release will be made later today incorporating both tickets if possible. Otherwise RR-53 will be held over for the next release. Uncompleted tasks can be moved to the new sprint January 2020 which will be discussed on Wednesday at the Validation Meeting.   
• Andrew Atterton has put  Unable to locate Jira server for this macro. It may be due to Application Link configuration.  on staging RaDaR for final signoff by Fiona. She has since confirmed it is OK and can now be deployed to live.
• Fiona Braddon (UKRR) (Unlicensed) confirmed the order the outstanding tickets need to be adressed. They are:
  Unable to locate Jira server for this macro. It may be due to Application Link configuration.
  Unable to locate Jira server for this macro. It may be due to Application Link configuration.
  Unable to locate Jira server for this macro. It may be due to Application Link configuration.  
  Unable to locate Jira server for this macro. It may be due to Application Link configuration.
  Unable to locate Jira server for this macro. It may be due to Application Link configuration.
• Andrew Atterton confirmed he was still working on the restoration of the deleted patient  Unable to locate Jira server for this macro. It may be due to Application Link configuration. . He is currently testing restoring on his development setup. Since Staging has the patient still present it will need careful testing before trying on live as staging is not available. Ideally the best test is to use a dump of live and test the restore there locally.
• George Swinnerton hasn't yet removed the orphaned PV memberships. He has had an issue with how to identify them. The orphaned memberships were created when the  NHS number for a patient is incorrectly entered and then it is corrected. This will leave a PV membership for the incorrect NHS number on the UKRDC. So all that needs to happen is the records that only have a PV membership need to have their NHS number checked with PV if not present then they are orphaned.
• The updated SQL Alchemy code with changes to manage the jtrace records correctly has now been tested on dev and not caused any issues in the UI etc. so is ready for deployment to staging. If this is successful it can then be deployed to live. 
• The latest NHSBT file has been completed. Retha Steenkampraised an issue with the current CAG renewal which now requires security assurances from all data suppliers. Currently NHSBT have not provided sufficient assurance for CAG so for the next NHSBT file it will be necessary to check whether we are allowed to link to the data or if CAG has not yet been satisfied. George Swinnertonthen reported he had had an email asking how to automate gpg from NHSBT. George Swinnertonwill reply.
• No updates for Kings. However George Swinnertonhas heard from Renalware Tim who has said Barts intend to submit the first two quarters via their old system. This may just push any issues to the third quarter extract. George Swinnertonwill request a full feed from them to see if all the required data has been migrated and try and anticipate any issues. This has been brought about because not all 2019 data has been migrated to their new system. Barts have also been sent the sftp details to send files but don't appear to have progressed that yet.
•  Retha Steenkamplet everyone know about the vascular access changes. They are reducing the data values required  to ERF12, QHD20, ACC19, QBLGE. If these values are being submitted then the sites will no longer need to do a separate spreadsheet. This will need to be discussed as part of the validation meeting on Wednesday. Currently the ACC block isn't loaded and some thought will need to be given to how this can be done and what will need to be loaded besides the required field. In January those sites who are not submitting the required fields will receive a reduced vascular access spreadsheet. There is a need to get the data for 2018 for Shalini to analyse. George Swinnertonsuggests 

There have been a few tickets for AKI the main one is that the library that should identify the delimiter in the "csv" files has failed on one file. George Swinnertonsorted this by putting quotes round the fields in the file and then it was picked up properly. This may need some changes to the code if it happens frequently.

The AKI RAG calculation has changed so will need adjusting when the details are known.