Skip to Main Content
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.

Status Future consideration
Created by Mark Filby
Created on Nov 7, 2022

Central Shared Document upload mechanism

Current requirements for Integration with the YHCR are expensive, resource heavy and technically challenging for many organisations with existing resources. Alternative options would be good to support different options for sharing information, developed once, centrally. These could be standard applications deployed to providers to utilise such as the National MESH mailboxes, supporting the transfer of data sets but also supporting documents such as Discharge letters, Respect document, care summaries etc. or centrally hosted environments into which providers could drop such documents in for upload.

  • Attach files
  • Admin
    Ian Clucas
    Reply
    |
    Nov 9, 2022

    hi Mark, we appreciate that data provision is complex and challenging, the question is how could we simplify? and we are exploring a few areas

    • process improvements - journey mapping workshops are planned to understand all the pain points and opportunities for improvement

    • tooling to help with FHIR mapping

    • tooling to help with testing data against our FHIR profiles

    • building a FHIR query capability in Console, which will perform a similar job to Postman

    Where data sets exist at a national level we are utilising things like MESH mailboxes, e.g. PDS download, but outside of this your suggestion seems to be at odds with our federated model of connecting local providers and retrieving data on demand, rather than from a repository, and not persisting any data

    Happy to discuss further as our model is not 'written in stone' but is currently one of our guiding principles