Versions Compared

Old Version 4

changes.mady.by.user Rob Pink

Saved on

compared with

New Version 5

changes.mady.by.user Rob Pink

Saved on

Key

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

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.

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

12

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?

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”.