London Research
- Adewale Adekoya
Current Connection AS-IS diagram
Pain Points/Challenges/Successes
Downloads: Tableau/GMC Connect sometime is slow and apps down
Reports Comparison: Takes more than 2hrs every Monday to run reports and do analysis
Current Connection App: Our process don't align with the bulk connect and disconnect in the current app.
Current Connection App: The way the user interface in the system is displayed in the current connection only makes individual connection and disconnection easy not bulk. The functionality of the current system is superior compare to the old but the user interface of the old is better.
Current Connection App: 'Current Connection Tab' Need more filters to be able to use but not currently in use because it's currently reflecting summary of all the 4 offices in London and there is no way to give a summary of each region- To filter by offices/regions/DBs, Programme etc
Current Connection App: Discrepancy is fairly displaying the logics but need to display more fields/information without going into individual details. if there could a 'Note' (notes are currently added on spreadsheet) and last time the doctor was was in a programme (that will help to see that Admin have to do something like 'outcome 6')
Communication with Doctors: Currently going back to doctors to connect - F1 is horrible with this. - Thinking out TSS can help here
Connection and Disconnection in the process: Disconnection is the big problem here because of the long list. Email sent to them and LO don't hear from them may be because of wrong email. If we can flag and disconnect after a period (deadline to be determine)? If bulk disconnect can be done after comparing GMC and Tableau report. GMC report is the unique value hear for disconnection; From the list of doctors to be disconnected (must have cross referenced the two reports)-> GMC Registered RO - Owner and they don't have 1. They don't have current region/office/owner (current LETB) 2. No current programme membership 3. No current programme (Programme data and 4. Checked against revalidation Report (Outstanding report -N)- Automation will be good.
Connection and Disconnection in the process:Foundation Doctor when they get to F2 (they have licence and assigned an RO)- because they don't understand many of the terminologies used on connection even though they are explained to them in a letter, they are connected using the TIS Reval by filtering by programme. They a letter is sent to them how to manage their connection themselves.
Failed GMC updates Tab: Used because of bulk connection
10. Filtering and Sorting: Ability to filter fields they want to see.
11. Connection and Disconnection in the process:Doctors can connect several times- GMC do write LO of this if frequent
12. Communication with Doctors: TSS have done Notification: Contacting doctors directly in connections
Questions/Assumptions/Key Points
Assumptions/ Key Points | Question | Raised by |
|---|---|---|
Key Point: Doctors need to be connected from the day 1 of their programme. This goes through series of persistent contacting of doctors to connect themselves using GMC connect |
|
|
Key Point: Doctors that have heard their ARC, period of grace and completed their training need to be disconnected but still connected |
|
|
Key Point: On the spreadsheet, if N/A against the programme owner that means an error and has to be investigated. If matches that get marked as OK |
|
|
Key Point: Reval Leads give doctors first 3months to connect themselves in GMC connect and remind doctors about 3 times via email and if they don't connect, they are connected by the Reval leads Doctors might not action this because of many reasons
|
|
|
Key Point: Foundation doctors are bulk connected via GMC connect when they get to F2. | Are they through GMC connect or through TIS Reval? |
|
Key Point: London don't touch the Current Connections tab only set up for people that works solely on connections not for people that work on other stuff. Lat result to go into it. |
|
|
Key Point: GMC send an email if someone is connected or disconnected - Maybe a dashboard here rather than depending on the Mondays reports |
|
|
Key Point: Possibility of Trainee connecting multiple time after disconnection from Reval Leads. GMC have got a way of detecting this and message LOs who then contact the trainee.
|
|
|
Priorities arranged in order
Improve filtering and Sorting as everyone will benefit from it
Improve way of disconnecting
Improve way of connecting
Note in connection
Hide- Just a least but could be better
Notes
Filtering- by Programme (already on), by region, by DB, By programme owner,
Sorting: GMC submission date- Very important, Current Programme name, DB and Programme Membership.
Current connection tab: Low priority. if can filter to know the number connected per each region/office
Template
Related content
Slack: https://hee-nhs-tis.slack.com/
Jira issues: https://hee-tis.atlassian.net/issues/?filter=14213