Interweave Portal - Ideas

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.

Add a new idea Subscribe
Status Future consideration
Created by Toby Page
Created on Feb 18, 2022

RELATED IDEAS

Extract and structure information from S1 Community HTML feeds

It would be very useful if information in HTML views (based on GPC) derived from S1 Community units could be 'un-picked' to create structured resources so that they can be aggregated in the appropriate panel.

The fact that GP Connect currently presents information in a separate part of the portal (HTML views) is causing concern for clinicians (and creating safety hazards). Providing community data in another place will exacerbate this problem.


  • Attach files
  • Mark Filby
    Reply
    |     Nov 3, 2022

    With many patients Community and Urgent care provision will be more regular and up to date information than the GP record, representing the at times daily care provision for patients, it's therefore important that the GP record is not seen in isolation. An example would be with the advent of the Virtual Wards held in Community records, patients could be receiving medications which would contraindicating to meds that might be provided in ED should they be transferred. Currently limited ToC mechanisms which this could support may not adequately mitigate this risk.

  • Toby Page
    Reply
    |     Feb 22, 2022

    Thanks Ian. Yes, I'm sure the HTML views will add value as a first iteration.

    The second iteration would add lots of value though (and mitigate risks of users missing information) - particularly if we could extract things like coded observations using known SNOMED code sets. e.g. Extracting coded values from clinical templates recorded in S1 community units and present in the Observations panel. That would be a game-changer for us.


  • Admin
    Ian Clucas
    Reply
    |     Feb 22, 2022

    hi Toby, as per the recent email:

    As a first iteration, unless there is an agreement that this is not valuable - the intention is to display the HTML views as presented, and therefore separate. Consumers and Portal tenants can of course choose whether or not to take this particular data feed.

    A second iteration can then be considered in terms of how information could be extracted from the HTML views and blended into existing panels. Unlike NHSD, TPP do not have any restrictions on how we display the data, but the technical feasibility and user experience still need to be evaluated.