This portal provides an open platform for user feedback and product change requests. Anyone can add an idea and remain as a Guest, but please consider signing up so that others can see who has created the ideas!
Note: this is a public facing web portal, any text here can be viewed by anyone over the internet, so please consider carefully the content you wish to share and please do not post anything of a sensitive nature.
To support clinical safety testing in sandpit and live and improve end-user experience the panels in the Interweave Portal need to reflect the YHCR data mapping and standards. This will enable clinical safety officers to review and approve data, streamlining and improving the overall testing and data provision go-live process. It would also be useful to join up the process between planned data provision and panel development, to ensure that panels are available for the display and testing of new data provision.
Marking as shipped as there's a process in place to handle this.
Hi Tara. I believe Emma has clarified a few things around this. I expect there'll be a few niggles to sort out... but the details panels are also being developed to cope and we should see any issues in sandpit first. Sophie is now involved in signing off data, so we should be well covered
The immediate plan for the v2 summary panels only relates to the YHCR tenancies and as such there'll be no impact on end users
Thanks for the update Ian. We've discussed this internally, and I've put the main feedback and questions below:
This would be very helpful to support clinical safety testing of resources to give CSOs the confidence to sign-off.
Are you saying that V2 and V1 panels would be available together in Production? This would be more than a different user experience for data for which the mapping has changed i.e. it may appear as an error in V1 but appear in V2 or vice versa. What's the clinical safety view on this?
The downside of this would be that the data that meets the new standard couldn't just be released into the V1 tenancies as errors would occur. We face this challenge with NLAG discharge summaries, for example, and the choice between going live with correct data mapping but consumers not being able to view this until V2 goes live (c. 6 weeks) or going live with old data mapping until V2 is complete and then going back and changing the mapping again
It would be useful to have the Portal V2 development mapped into the data standards remediation project plan that Adam is managing so we can collectively understand the impacts, dependencies and any short-term mitigations.
Happy to chat through further.
hi
The v2 panels are aligned to the data standards which currently exist and are being developed, we plan to release these into YHCR sandpit w/c 1st August on their own tab, as a short-term measure. This will allow us to receive further feedback and enable CS and data testing
Following a short period of testing, we can also adopt this approach in Production, and other tenancies where a v2 display would be beneficial. The benefit of this approach is that the existing (v1) panels remain and v2 is simply an alternative user experience, albeit one that we would like to make the norm
Feedback on this approach would be welcomed