...
Question | Notes 1 | Answer | |
---|---|---|---|
1 | What is the problem we are trying to solve by having a Connections function?
|
| < How connections fits in with the day to day. < are teams manually disconnecting / connecting 1325 < in an ideal work doctors manage connections, but in reality teams need to intervene to maintain the connected list. < teams who manage programmes are not necessarily the teams who manage reval. < discrepancies used to manage connection and disconnected. Discrepancy list compared with GMC. < discrepancy list is the work to action to address differences et al. < how d you know what action to take? Doc should be connected / disconnected. Data differences. < Teams need control over connections < current on legacy / spreadsheet. < connected doctors - does this different from all doctors list? < hidden doctors - hiding from coming up as a discrepancy. AD connected. < 1347 is knowing why a doctor is flagged as discrepancy - is that important? Why the doctor has appeared in the discrepancy list - clear whether things connected or disconnected. Problem - doctors cannot be relied upon to manage their own connections and TIS data not always up-to-date. < MVP - definitive list of doctors currently connected to a DB, as mirrored on GMC connect, and the ability to manage discrepancies / connected/disconnected. |
2 | Is a core purpose of Connection the management of discrepancies |
| |
3 | What is the MVP that will enable all teams to use Connections (if that’s what we agree) |
...
2 | Who disconnects doctor at the end of his/her programme? | Should be the doctor, but often the team. Not auto. | |
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? |
| GMC can add the doctor. |