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.
Currently in Console, it is only possibly to set a FHIR Resource as 'Public'. 'Clinical Safety', or not enabled.
P-I-229 has suggested an enhancement, whereby Interweave Profiles would be used instead of the base FHIR Resources. However, that does not overcome the issues faced when data providers want to start sharing a new feed of data within an already Public Resource/Profile, and need to go through a controlled clinical safety process.
Example 1
Trust is live with Inpatient & Outpatient Encounters, but then develop a feed for Emergency Attendances (which are sourced from a separate line of business). As soon as the ED Encounters are POSTed to the local FHIR Store, they will be available to Data Consumers. However, the Trust would not want to release that data until it had been Clinically Safety Tested in Production, and the full ED Data backload has been competed.
Example 2
Trust is live with Radiology DiagnosticReports, but then develop a feed Pathology. As above, they would not want any Pathology ones to appear until they had been Clinically Safety Tested the backload was compete.
| As a | As a Data Provider |
| I would like | Restrict / Enable the sharing of data based on a specific rule (e.g. a FHIR Query with the codes that can be shared) |
| So that | So that I can switch on new feeds, of an already 'Public' Resource/Profile, in a safe and controlled manner |
|
Other information
Not sure if Policies could be used to achieve this (see Section 2 in DESIGN PAPER #008 – DATA ACCESS AND CONSENT MANAGEMENT V2.0) |
|
