This page summarises Teams feedback and helps manage how this is being taken forward.
No | Sequential number for ref |
When | When first raised on Teams for easy cross reference |
Who | Who raised feedback |
What | Very brief summary |
Answer | Very brief summary |
Action | What we are doing about it? Is is with UR, ticked up etc. |
When | Who | What | Answer | Action | |
|---|---|---|---|---|---|
| 1 | 8 June 16:07 | Pepe | Obligation to maintain right connections | Rob to add to UR page the legal and policy drivers for Connections | Rob updated UR page - User session on Connections 12/08/22 |
| 2 | 8 June 17:56 | Katy (NW) | Drop Bilklis and Nichola from the Private Beta | Acknowledged | Rob updated the Leads spreadsheet User groups and Leads.xlsx |
| 3 | |||||
| 4 | 12 June 10:02 | Katy (NW) | Using DB codes is confusing | Acknowledged and picked up by UR | TIS21-4655 - Getting issue details... STATUS |
| 5 | 12 June 09:14 | Katy (NW) | Hide e.g. Associate Deans - connected but hidden and adding and removing (presumably from hidden) | Acknowledged and picked up by UR | Open |
| 6 | 12 June 09:16 | Katy (NW) | Send to GMC comes up as “Save”, but should be “Submit” so it’s clear what's happening? | Acknowledged and picked up by UR | Make a ticket |
| 7 | 12 June 09:16 | Katy (NW) | Filtering and sorting | Acknowledged and picked up by UR Filtering by programme name and now just a case to confirm other filtering and sorting needs. Already have some feedback requirements which are obvious and offer continuity from V1. |
TIS21-4635
-
Getting issue details...
STATUS
|
| 8 | 12 June 09:16 | Katy (NW) | F1 doctors - remove as not part of revalidation - auto hidden | Acknowledged and picked up by UR Prioritise this so we can move forward. Noting architectural decsion. | TIS21-4154 - Getting issue details... STATUS |
| 9 | 12 June 08:45 | Katy (NW) | Dummy record removal | All have the role of 'placeholder'. Some legitimate doctors will have role as NULL. Normally use | Ticket up |
| 10 | |||||
| 11 | 13 June 10:16 | Katy (NW) | “Flag” to show worked on a record. | Has this come up in UR? | Need to fully understand and define user story |
| 12 | 13 June 10:24 | Katy (NW) | How records in discrepancy are pulled through - placement or programme | Cai → So discrepancies currently come through where there is any mismatch between the DBC of the current programme on TIS and the DBC reported by GMC, if that helps? Note - Every trainee should be in a placement, even within the “period of grace” (PoG). We use the Programme End Date rather than latest Curriculum End Date (rather than CCT) (query) | What is current? |
| 13 | 13 June 10:42 | Katy (NW) | Screenshot of repeated trainee Bokhari (7399152) + couple of other duplicates | Has been investigated - data issue rather than a bug. | TIS21-4662 - Getting issue details... STATUS + Data Issue |
| 14 | 13 June 11:40 | Katy (NW) | Why trainees appearing on list **** | Is linked to #13 | |
| 15 | 13 June 11:15 | Katy (NW) | 2 programmes listed when not dual trainee | When multiple programme son TIS we don’t send back the DB. When two progs in same DB then show in discrepancy list.
| Further investigate Discussion session |
| 16 | 13 June 11:13 | Kate (NW | |||
| 17 | 15 June 10:00 | Katy(NW) | DB Still appears as HENW-Old Abbreviation. | Acknowledged by Rob Could be handled in the FE. Linked to #4 | Highlighted as Insight from UR Session. |
| 18 | 15 June 10:13 | Katy(NW) | Positive Feedback-much quicker to add and disconnect via TIS than direct on GMC connect which is a positive | Acknowledged and picked up by UR | Positive Feedback |
Add Comment