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.
Users may not be aware of business rules/logic used to populate information resources.
This applies to both organisation data providers and proprietary sources (e.g. S1 non-GP feeds).
This may mean that users misinterpret information or trust in the completeness of data is eroded.
| As a | Portal user |
| I would like | to see a description of the data provided including any caveats or rules applied |
| So that | I can make an informed decision about how I use the information |
| User contact | Toby Page |
|
Other information
Informed by initial testing on S1 non-GP units, but also applies to organisation feeds (e.g. how can we communicate the logic used for social care episode load/retention?). Could be an admin function where a description can be added to provider/resource definitions...? |
|
The example I gave was for UHL a document resource - MAR Chart - where we currently caveat, in the notifications, that this document does not contain discharge medications.
Clarified that the high level disclaimer configuration work would not be a suitable solution for the issue that has been presented. This is a request to be able to apply caveats for data providers so we can indicate what limitations are present in the data. This would need to be at resource level.
@Guest @Guest we mentioned on the call that we have specific use cases for this? Please can you outline them below so we can use them to assess an appropriate solution.
@Guest we presented the prototype for the configurable disclaimer previously. Although not panel level, does this give you a reasonable solution to the problem you have presented?
@Natalee Pearson is putting together user research on this and will feedback to the team when complete..