Versions Compared

Old Version 4

changes.mady.by.user Rob Pink

Saved on

compared with

New Version Current

changes.mady.by.user Rob Pink

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Background

We have had a range of meetings that have helped us understand more about revalidation and we have worked through the logic that underpins Connections.

We have agreed that the focus of the team will be on Revalidation, specifically:

  • Developing improved filtering in Recommendations so that the function can be used by all teams effectively.

  • Developing Connections

  • Also (for information) doing work on the data flows between Revalidation and GMC as that understanding is a prerequisite for the Connections work.

Purpose of the meeting -

  1. To describe the problem we are trying to solve with Connections and agree MVP.

  2. To give a steer an operational problem.

Agenda

  1. Recap on a meeting on 12 August 2022 --- Edit - User session on Connections 12/08/22 - New TIS Confluence Space - Confluence (atlassian.net)

  2. What’s the problem we are trying to solve and MVP definition + some some more questions

  3. Edit - User session on Connections 12/08/22 - New TIS Confluence Space - Confluence (atlassian.net)

MVP questions

Question

Notes 1

Answer

1

What is the problem we are trying to solve by having a Connections function?

  • Why is GMC Connect not sufficient?

  • We know that docs have to be connected to a designated body (DB)

  • We know that teams need to maintain a list of connected doctors and this a statutory requirement.

  • We understand GMC Connect provides rudimentary functions and that teams want a “one-stop-shop” in TIS

  • We believe teams want a definitive list of connected doctors

1

< 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

  • Linked to the above…
    Is Connections about managing discrepancies e.g. where something is different / changes and who is / is not connected.

3

What is the MVP that will enable all teams to use Connections (if that’s what we agree)

Quick questions

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?

  

6

Does this frame Connections, as a statement?
”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”

GMC can add the doctor.