Connections MVP

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

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.

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