...
What value would establishing this linkage unlock for TIS and TSS? [various]
What non-technical obstacles exist that have prevented the relationship being made in the past? Are these obstacles still valid? How could they be addressed? [no particular obstacles, just not part of legacy system]
Technical issues to investigate:
Are there business rules which could be used to define this relationship? [yes]
Do we have the data in TIS to be able to process these business rules? [yes]
What would the data model look like (one-to-many, many-to-one, many-to-many)? [1 PM → many placements]
What other attributes are needed to be stored with a given linkage, if any? [date, possibly metrics of strength of auto-linkage]
Given existing legacy data, are there rules we should use to exclude some programme memberships placements from being automatically linked, because the relevant data is unreliable / low quality? [likely to be poor auto-linkage of pre-2017 data, greatest interest is in current / future placements / PMs]
Are there cases where manual intervention is required to (de)link a placement from a programme membership, and should this functionality be available to LOs or trainees or both? What user role(s) would have this ability in TIS? Should the data be authored / owned by TIS or TSS? [LOs would specify the link, data owned by TIS, user roles TBD]
What restrictions are needed on the creation of these independently of each other? That probably goes for the validation with any changes too.
Can the linkage between a placement and a programme membership change, and if so what would trigger this change (e.g. delinking a placement if the programme membership start date changes)? Are there any specific notifications that would need to be raised for downstream processes or reporting when these events happen? Also think about deletion.
What would the TIS and TSS data structures look like (and for TSS in particular, how might the trainee profile need to be remodelled)? [TIS: a linking table, TSS: TBD]
For tis-trainee-sync, what would the implications be for (a) cascading changes to related records within tis-trainee-sync and (b) raising events for downstream processes
In rough estimate (e.g. developer-weeks), how much effort would be required to implement this in TIS and in TSS?
Business value and blockers:
TSS business value:
Onboarding journey can become a proper tracker.
From Andy:
...
Improved reliability of placement/programme matching in @Kav's reports, likely some other benefits there as well
...
Better UX for trainee's filling in Form R Part B - narrow down type's of work to only those that are relevant to the form-linked PM
...
TSS
...
From Kav:
improved ease and accuracy in answering data requests relating to grade, WTE, OOP and more
From Naz:
FormR is big pain point at the moment for trainees - if we can capture the right details on formR, upfront, then trainees will have less to add.
TIS Admin business value:
From James:
...
Immediate value:
More robust reporting on such topics as:
Counts of numbers per training specialty, grade, WTE, PlacementSpecialty, Site, Trust. Currently overlapping Placements/ProgrammeMemberships and no link to programme make it not possible to isolate the placement data to those corresponding to the training specialty being analysed. This can only be done through broad assumption or manual manipulation
Validation reports to resolve above issues with Placement/ProgrammeMembership dates
Often requested by data leads/analysts for their reporting in regions so potential unknown benefit to be explored
Potential future value (linkage will allow developments of the below but only if pursued)
...
Validation on ProgrammeMembership - Placement Dates
...
Automatic extension of ProgrammeMembership Dates for placements
...
LTFT changes on Placement - ProgrammeMembership Dates/Creation
...
Placement Grade - Programme Membership Specialty Validation. Would help streamline GMC ARCP Return.
...
Site Approvals for Programme Numbers (Sites are approved for training of a specialty via the Programme Number of the Programme of a ProgrammeMembership)
...
?
...
From Rob:
Placement planning (parallel initiative to improve the TPD transparency of this is a roadmap item ~2yr timeframe)
General TIS Admin placement management
Historic context and blockers:
...
Intrepid data model did not have this linkage, which is why TIS did not inherit it. Otherwise no specific blockers.
Data model may need to be designed flexibly to accommodate
...
(a) historic data which may never be linked and
...
...