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

• Probably some data quality improvements on one or both of the TIS/TSS side in terms of cleaning up placements when the PM is deleted.

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)

  • Solutions to other problems not yet explored…???

From Rob:

• Placement planning (parallel initiative to improve the TPD transparency of this is a roadmap item ~2yr timeframe)

• General TIS Admin placement management

From Joseph:

• Placement Planning for TPDs? Is that too far off?

• I can see that it could open up better ways of flagging Revalidation issues too. First thought was identifying when doctors (esp. F1) should/shouldn't be connected.

• What do training pathways look like in terms of posts/placements? (Alternatively, would it help clarify the way in which training pathways are standardised for given programme/specialties?)

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

  • (b) edge-cases where a placement can legitimately belongs to more than one programme membership

• Consider NI: is there any (reporting?) benefit to this group of users, since they only use TIS Admin core, not TSS.