NI Sync

Infra: Iteration 1 (3-6 weeks), Iterations 2-7 ()

Stipulation

Ways to split vertically?

Software Iteration 1: 6-12 weeks?, Iterations 2-7: ?

Reval

Permissions

MVP:

click to edit

Iteration 1: New VPC (couple of days)

Iteration 1: Peering connections (one day)

Iteration 1: Creating ECS service (couple of days)

Sync has to be done on GMC number

Iteration 1: Message broker service (1-4 weeks)

Iteration 1: Pipelines (couple of days)

NI CDC (dependent on having somewhere for the changes to go - broker) (one week)

Message writer / enricher / filter / everything! (4-12 weeks - could start before all the infra is in place). For a skeleton record (2-6 weeks)

Message reader (Iteration 1: 1-3 weeks)

Switch to UUIDs (could start soon) (Iteration 1: 3-7 weeks, Iteration 2-7: 4-16 weeks)

Dependent on knowing what phases of data we can sync? (James to advise)

Iteration 1 - admin able to see skeleton record (GMC no and person details) between entities: shared reference service

Iteration 2-7 - full sync of a trainee record when a trainee moves between entities

Developing in iterations - first one may be deliverable quite "quickly"

click to edit

Iteration 2-7: Scaled availability zones - dependency on doing the same for HEE in advance

New (1-2 weeks)

Moving (2-4 weeks)

click to edit

Iteration 1: New reference RDS database (one week)

UUIDs (already introduced as part of migration). To be used as primary ID

NDW export - as long as old IDs are going to NDW, downstream should be safe

Leave manager - being re-procured (April ish) - will be creating new system IDs

Track changes reports - use Placement IDs

Operations & Access

All requested HEE Reval Admins are onboarded and administering the Revalidation process from the new Reval service (Reval, Concerns and Connections)

HEE Reval Admins do not need to access GMC Connect to carry out any Revalidation functions.

(Note: for MVP, reporting on Reval via NDW is not yet in place)

Support and future development to be prioritised alongside

Application

Connections: admins will be able to

Add a new connection via the Add Connection filter. DONE

Remove an existing connection via the Remove Connection filter. DONE

Review connections discrepancies via the Exceptions filter. IN PROGRESS - permissions work ongoing

Ignore connections discrepancies that do not require any action via the Hidden filter

These actions will be limited per local office permission set, and only to particular roles

Recommendations: Admins will be able to

Draft and Review a new Recommendation, depending on their role and local office

Submit a Recommendation, depending on their role and local office

Review previously drafted and submitted Recommendations

Concerns: Admins will be able to

Review and update previously entered Concerns per Trainee

Add a new Concern to a Trainee’s record