Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 7 Current »

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

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?

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?

  

  • No labels

Slack: https://hee-nhs-tis.slack.com/
Jira issues: https://hee-tis.atlassian.net/issues/?filter=14213