Date

03 Jun 2019

Attendees

Goals

Review outstanding tasks
Identify any tasks Rapolas needs to complete before leaving

Discussion items

Item

Who

Notes

Outstanding Tasks

Tim Whitlock (Deactivated)

Simplified contacted last week seeking a response on how to send CHI numbers in for checking against our database (ideally they would like them to be traced but that cannot be done using the tracing we have access to) George Swinnerton will follow up and let them know to send the CHI number. in the same position that the NHS number is returned and set up the copy jobs to return the more extensive data this week.
George Swinnerton had a phone call with Tim the developer focusing on producing the timeline data. This is probably the most complicated aspect and is the critical element before we can produce an extract. George Swinnerton suggested that he could do some of the simpler items alongside this and has received some diganosis examples. He i snow awaiting some real patient versions for checking. He will follow up this week.
Schema versioning has not yet been added. George Swinnerton will add it in to the current version this week. Moving forwards the version should be updated when changes are made to the schema. An associated changelog should be kept so whats changed is documented. It was noted that the validation code has a number of schemas in the code base. These already have a version and updated date element however these don't appear to have been updated since the code base was moved from SVN to git. George Swinnertonwill look at this as well.
No progress on the Study groups
rapolas (Unlicensed) hasn't had any feedback on the revised report and how satellite codes should be displayed. He will follow up.
No progress has been made on incorporating the RaDaR extract improvements in the Nurture extract code base.
All the RaDaR servers are now running postgres 11 with no known issues. Upgrading was done using the upgrade admin tool without incident.
George Swinnerton will arrange a meeting with Tim this week now he is back from his holiday.
The NHSBT file has now been processed and imported.
The UKRR Extract needs some documentation on the design philosophy, how to include extra elements etc. Now that Rapolas is leaving.

Rapolas Departure

Tim Whitlock (Deactivated)

Before Rapolas leaves the UKRR we need to ensure we have adequate developer documentation for all the areas he has/is working on. This documentation should be sufficient for a new starter to get up and running with out all the background knowledge that the team members have. It should detail build,deployment methods, and development notes where appropriate/helpful. In some cases it will be a case of reviewing current information and modifying as required. Areas identified are;

RaDaR (live, staging,demo,international) differences if any between versions, notes on data export, adding extra screens/fields etc.

STAR database codebase/development/deployment process. How does this differ from RaDaR etc.

UKRDC -desktop development environment set up, UI design/development/deployment any notes on adding elements etc., How to deploy updates to UI/API

AKI reports/code deployment

Surveys report design/running of it, error gui build design use

Stevie notes about how it is built/deployed etc.

Transplantfirst

Tracing

Action items

George Swinnertonlook at the versioning on the Validation codebase schemas which don't appear to have been updated since the move to Bitbucket 10 Jun 2019
rapolas (Unlicensed) create some documentation on the UKRR Extract code. Including details of design philosophy and how extra data items intended to be added etc. 10 Jun 2019
rapolas (Unlicensed) to look at documenting the processes/code identified 24 Jun 2019

Browser not supported