Sprint 13 Review (2020-03-03 to 2020-03-17)

ESR:

1. Existing system
2. Bi-directional - Type 5 notifications

Other:

Replica sets and Transactions

Omar Mirza (Unlicensed)

Where we were at the start of the sprint:

• Initial infrastructure and revalidation app setup.
• A mock service which serve as a GMC Connect has been setup.

Where we are now:

• Integrate new Client app with GMC Connect.
• Pulling doctors information from GMC Connect to new Revalidation app.
• Add endpoints into Mock application which reflect current GMC Connect implementation.
• Created initial view of under notice trainees list page using mock data

All training programmes should be approved by the appropriate regulator, College or other approval giving body or individual. In the case of GP programmes this also includes the practice site and trainer.

As a HEE Admin, the user wants to be able to record and maintain Sites approval periods against sites
So that they can ensure Approved sites are used to manage placements on TIS and meet the standards set out by the GMC

The Approval fields for Sites are not currently on NDW. Those fields have been added to the NDW ETL and sent to NDW
so that report can be prepared using those fields.

This story is specifically for recording of Start and end dates against Site reference - to inform whether sites are current and approved for use.

For MVP, it was suggested to cover only GP sites and trainers approvals. Both of them are released by now.

LIVE DEMO

Security vulnerability fixes

TIS

Where we were

• A new tool, Sonarcloud, was set up to help analyse the quality of our code across several metrics.
• Sonarcloud identified 22 security vulnerabilities across our analysed TIS services.

Where we are now

• 10 security vulnerabilities fixed in "TIS Core Services".
• 12 issues remain across six services.
  • 9 "critical"
  • 3 "minor"

Where we were

• Investigation had been done to identify the approach for filtering records shown in TIS (e.g. trainees, posts) based on whether the data belonged to NI or HEE.
• Initial changes were made to our User Management tool to add an "Entity" selection between HEE and NI.

Where are are now

• Progress has been made on the User Management side to allow correct propagation of the "Entity" selection to the relevant user records.
• We had some concerns about the approach for filtering the records, after further investigation it was determined that the proposed approach would not be suitable.
  As a result we were unable to achieve our original plans to forward the implementation of this, instead focusing on formulating a new, more secure, approach.
• We now have a new approach which more closely follows standard practices and have implemented a working proof of concept.