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 Planned
Created by Chintan Chokshi
Created on Nov 14, 2024

Console - Provider Resource onboarding change

As per the current process, the data providers have to add the resources they are providing based on the FHIR resource type. the same is used to generate the Data-available report that is published on the Interweave website.

Issue: The current product does not represent the derived Interweave profiles, so, the data is not represented correctly. e.g. Social care Support Reason is displayed under Condition.

Proposal: Add another column/option that provides the user to select the name of the available derived profiles, so that the data is displayed correctly.


PS: Not sure how the current list of resource type is populated, but the information of Resource Type / Profile name is available in Metadata store.


  • Attach files
  • Chintan Chokshi
    Reply
    |
    Nov 20, 2024
  • Stephen Handley
    Reply
    |
    Nov 20, 2024

    @Chintan - I can see benefits in this, however it might also be worth considering similar use cases, such use of Type/Class/Code to filter data available. For example a Hospital may be live with Outpatient and Inpatient Encounters ... but not with ED ones (which might be sourced from a separate application). In the current set up, it is not possible to keep Outpatient and Inpatient Encounters 'Public' whilst ED ones go through clinical safety.
    Data such as Social Care Assessments and Vital Sign Observations, could be similar, in that Data Providers may gradually add new types, but using the same profile.

    1 reply