Questions raised for the Revalidation users at the meeting 22 August. These are a “starter” from my quick notes. Can we build this up, please?
| Question | Answer |
|---|
1 | Is a core purpose of Connection the management of discrepancies | |
2 | Who disconnects doctor at the end of his/her programme? | |
3 | What function does Connections serve? <is it a definitive list of connected doctors and management of discrepancies>? | |
4 | Does an admin need to know why a discrepancy has been flagged? | |
5 | Are there only two ways a doctor can be connected - by a HEE admin or by the doctor themselves? | |
So teams can The sessions with the users were to address the Product team queries around Connections and its tabs.
...
Question/Query/Concern | Response from London | Response from Thames Valley and North West | Comment |
|---|
Why Connections? | Doctors have to be connected to BD to work as a doctor. Part of terms and condition to start training;Though this will not stop them from training. Nothing to do with ARCP but doctors must be connected Doctors are connected to their training programme
| GMC expect doctors to be connected to an employer/DB Legal obligation Current way of doing it is difficult. Reconciliation of connection with GMC connect Not many use the Discrepancy report which tries to reconcile who should/shouldn't be connected Joint obligation btw Admin/Doctor to ensure correct list of connection
| RP - is the purpose of Connections:
”So teams can see a definitive list of doctors and their designated body association, and easily manage of their connection state i.e. connected, or disconnected”. |
User Journey (Old Reval) | London not using Old Reval for Connection | No action before login into TIS-Admin Login into old TIS- Reval via TIS Admin Go to Connection discrepancies to Remove connection or create connection (this contains the list of current connection) Every month, list of discrepancies is transferred into a spreadsheet to check for more details about individual doctor in TIS Admin.
 Pain Point: Opportunity: | Action: How do we minimise inaccuracy in TIS? Can we do that through logic? RP - what info on TIS is misleading / inaccurate? Meeting: Accept. |
User Journey (GMC Connect and TIS- Reval ) | (Before login into system) Users generate mega report via NDW on who’s is finishing/CCT- ARCP outcome 6 - Run report 3 months to finishing. Each Local specialty has its spreadsheet/report Check doctors under Notice in TIS-Reval Compare the two reports (Under Notice from TIS- Reval and the Local specialty spreadsheet so see who needs connected or disconnected Login into GMC connect to do the disconnection or bring forward doctor already connected to appear under Notice No action after using the system
 Pain Point: People connected to wrong RO/Trust (To be considered in discrepancies) Doctor not disconnecting themselves when they finish (To be considered in discrepancies) Doctors not connecting themselves (To be considered in discrepancies). If a doctor connect himself 2 weeks or more than the programme start date - they are disconnected by Admin No way of knowing if a doctor has connected himself somewhere else (To be considered in discrepancies).
Opportunity: If people connected correctly we don't miss them. | To add connection No action before login Login into GMC connect the default page is under notice doctors' list Select Add doctor on the LHS put the doctor GMC number to search doctor Select reason for adding connection Submit
To Remove connection No action before login Login into GMC connect the default page is under notice doctors' list Select All doctor on the LHS Click remove doctor towards the end of the individual doctor’s row
Note: Good thing about using GMC is that some doctors are not on TIS but in GMC - GMC connect is used to add connection for such doctor. 
Pain Point: Only displaying All doctors and can only add or remove doctor's connection Only displaying All doctors and can only add or remove doctor's connection Can't view list of historic connection except by individual search
Opportunity: Historic Connection Tab in new TIS Reval Bulk add/remove connection Able to hide doctor from list
| Action: To be considered for discrepancies People connected to wrong RO/Trust <what do we send to the GMC. Could the doctor connect themselves to the wrong RO/Trust – Should doc be moved to discrepancy? GMC web service user guide? How does a LO resolve GMC send wrong>
Doctor not disconnecting themselves when they finish
<the programme end should send doctor to discrepancy for action>
Doctors not connecting themselves but If a doctor connect himself 2 weeks or more than the programme start date - they are disconnected by Admin <discrepancy>
No way of knowing if a doctor has connected himself somewhere else ????? is there any other system doctors uses to do connection apart from GMC connect? <we don’t think so>
< Users is there any circumstance where a trainee is not on TIS>? |
What Admin will be able to do in connection tabs
| Current Connections: Just see doctors connected to the DB Historic Connections: Not adding any Value Discrepancies: Add/Remove connections Hidden: Can't think of anything why we need it | Current Connections: See list and Disconnect Historic Connections: Just view Discrepancies: Connect disconnect, Hide and add Note- Reason for Hidden? Hidden: Unhide and add Note- Reason for Hidden | Action: Redesign of update connection (MVP) and bulk connection (Post MVP?) Priority: Current connection and Discrepancies tabs (MVP?). Hidden and Historic Post MVP? <Incline towards TV/NW – features already developed> |
UI Design - Doctor detail page | Programme History: No value added Connection History : Yes want to see Update Connection : Yes want to see | Programme History: No value added Connection History : Yes want to see Update Connection : Yes want to see | Action: To remove the programme History from the new design |
...