User Story #6330 (new)
Opened 13 years ago
Last modified 13 years ago
HIC: Dataset Silo layer — at Initial Version
| Reported by: | adjudson | Owned by: | |
|---|---|---|---|
| Priority: | minor | Milestone: | Unscheduled |
| Component: | General | Keywords: | n.a. |
| Cc: | Story Points: | n.a. | |
| Sprint: | n.a. | Importance: | n.a. |
| Total Remaining Time: | n.a. | Estimated Remaining Time: | n.a. |
Description
So far we have focused on the project silo model. The data for which was manually anonymised, extracted and transfered from the mssql servers on the NHS network at HIC to the HIC/OMERO server on the UNI network.
It is going to be useful for other stories that we develop the dataset silo model as a parent layer of the project silo within this pilot.
The dataset silo is a complete anonymised mirror of the nhs datasets held on the mssql servers at HIC. The project silos are then prepared on a project-by-project basis from the dataset silo all within the HIC/OMERO architecture. This will include anonymisation, data cleaning and modelling steps.
Josh, has developed a diagram (attached) outlining the proposed structure and the relationship with existing tickets.
Each of the clinical data files we've provided from the GoDARTS project represents a dataset. For instance the separate files for SMR, RX (prescribing), BIOCHEM, etc are all separate datasets. I think the only way we can work this in terms of the pilot project governance is to use the GoDARTS data as the real data and create a mass of fake data based on the schemas. These would then form the dataset silo, from which we can rebuild the project silo and test that users only get to work with the project data they are supposed to.
The audit trail should allow dataset inspection e.g. which project have used smr... In theory a data owner (the custodians, patients or caldicotts) may want to see how safe our model is or who is using 'their' data.
Another feature that the steering group are interested in exploring through this is the embedding of risk prediction models, privacy impact assessments and disclosure controls. These are mechanisms that are being discussed in the SHIP blueprint as ways to facilitate risk based & proportionate data governance. Once the next blueprint draft/final copy is available I'll update this story.
