/
2018-02-28 Meeting notes

2018-02-28 Meeting notes

Owned by Tim Whitlock (Deactivated)
Last updated: May 14, 2018 by foghorn_leghorn (Unlicensed)

Date

Attendees

Goals

  • Review tasks
  • Set Goals
  • AOB

Discussion items

ItemWhoNotes
Review Of tasks

Tim Whitlock (Deactivated)

  • foghorn_leghorn (Unlicensed) is still waiting on NHSBT to respond having answered queries raised.
  • foghorn_leghorn (Unlicensed) indicated that though the Vascular access has matching has been completed there is a possible problem with the queries that work out the earliest period beacuse we now collect aki/ckd data. The current queries have not been updated to take into account the extra data and may return an incorrect result.
  • rapolas (Unlicensed) has been clearing off some outstanding RaDaR tickets currently looking at the consents indicator which shows which consent and whether reconsenting is required due to patients age.
  • The BCH demo is done and waiting review and feedback from Fiona Braddon (UKRR) (Unlicensed).
  • foghorn_leghorn (Unlicensed) released the validation code but had to revert it as some fixes that had been marked as done were not correctly tested causing problems. These issues have now been fixed and he is now concentrating on
    Error rendering macro 'jira' : Unable to locate Jira server for this macro. It may be due to Application Link configuration.
  • George Swinnerton reported that he had to run the next NHS England report by the end of the week.
 Patientview

 George Swinnerton

 Patientview has now set up publishing accounts on Apple and Google for their apps so can now release their Patientview App. This may have implications on the resources required on the servers but no discussions or conversations have been had about this.

There has been an enquiry from Harlow about sending Diabetes data. Afzal has suggested they should use the pv api directly thus avoiding the sftp server approach.

Development ProceduresTim Whitlock (Deactivated)

foghorn_leghorn (Unlicensed) has started some procedural documents formalising JIRA ticket actioning. Covering the expected development process and minimum development testing that should be done before pushing to bitbucket. This will need to be further developed to include a code review process ( probably using fisheye)

Action items