We have been looking at the Connections work for some time, mainly preparatory work around logic, data flows and evaluation what’s been done, including with some revalidation leads.
An MVP is usually described as a product with just enough features to enable users to start using it, validate that it works and act as the springboard for further - informed - iterative development.
Our work with Connections is unusual because lots of work has already been done. So perhaps not MVP, but more developing what’s been done to make it usable.
We did consider starting again but felt that was too onerous. Therefore, this is what we are proposing to do, and we are seeking support and input so that we can work in detail start to deliver the necessary change.
From previous meetings, we took away this statement of the revalidation leads MVP need.
“Definitive list of doctors currently connected to a Designated Body, as mirrored on GMC connect, and the ability to manage discrepancies / connected/disconnected.”
How do you want to approach this?
I would prefer we developed a narrative around what this MVP will entail - with a list of items
We will
...
Preserve the current structure with lists Current Connections; Historic Connections; Discrepancy; Hidden
...
We will remove the All list? Remove from view in case it needs to be reinstated at a future date.
...
The Current connections tab will contain a list of all connected doctors derived from GMC and augmented with TIS data.
...
The current connections tab fields rationalised based on current feedback
...
In the Connection details page the admin can disconnect
...
The discrepancy tab ---
_______
Our proposal for the “MVP”
In Connections, we will hide the columns Historic Connections, All and Hidden.
Focus 1 - Current Connections
This will be made Read Only
We will rationalise the columns and remove e.g. Programme Owner, Start date etc., based on existing feedback.
We will remove Programme membership history, but keep Connection history (as per feedback)
We will remove interaction (e.g., you won’t be able to remove connections, at this point)
Focus 2 - Discrepancies
This will be made Read Only
As with Current connections, we will rationalise columns, remove Programme membership history and interaction removed.
The bulk of our work will be to ensure the data is correct, based on the previous conversations around logic etc…
Focus 3 - Interaction
We will enable the ability for users to remove and add connections.
Future work will be based on building out the above based on value to you and your priorities which you will be able to help set.
Future Questions / issues
Architecture of connections – question over whether we should start from scratch with a new build rather than iterate current.
Current iteration has tech debt and end-to-end tests to be added
What should show in current connections tab? User feedback required.
Current connections two triggers for change = TIS perception and GMC extract.
Agree performance data
GMC connect review
Discrepancy tab is the unique non-GMC Connect capability