Notice: In order to edit this ticket you need to be either: a Product Owner, The owner or the reporter of the ticket, or, in case of a Task not yet assigned, a team_member"

User Story #6446 (closed)

Opened 9 years ago

Closed 8 years ago

HIC: Data Governance Research

Reported by: szwells Owned by: szwells
Priority: minor Milestone: Unscheduled
Component: General Keywords: n.a.
Cc: hic@… Story Points: n.a.
Sprint: n.a. Importance: n.a.
Total Remaining Time: 0.0d Estimated Remaining Time: n.a.

Description (last modified by szwells)

A key element of the OMERO/HIC project is to ensure that the governance of data is managed using methods appropriate to the nature of the stored data. This involves a number of elements, e.g. working with & potentially replacing existing functionality & workflows at HIC. Furthermore, this aspect of the problem domain is ill defined with competing approaches (UK wide) and very little agreement even over the requirements of governance for medical related datasets.

This story collects information relating to how we define & achieve satisfactory governance of HIC datasets within OMERO/HIC.

Governance Feature Priorities

  1. Audit of use
  2. Embedded disclosure control, privacy impact assessments (proportional risk)
  3. Support annual audit
  4. Compliance with study protocol and implications of sanctions
  5. Consent – opt out/in

Governance Stakeholders

The following diagram illustrates the three main stakeholders concerned with HIC dataset governance:

Stakeholders concerned with the governance of HIC datasets

Attachments (1)

governance_stakeholders.png (39.3 KB) - added by szwells 9 years ago.
Stakeholders concerned with the governance of HIC datasets

Download all attachments as: .zip

Change History (8)

comment:1 Changed 9 years ago by jmoore

  • Cc hic@… added; hic removed

Changed 9 years ago by szwells

Stakeholders concerned with the governance of HIC datasets

comment:2 Changed 9 years ago by szwells

  • Description modified (diff)

comment:3 Changed 9 years ago by szwells

  • Description modified (diff)

comment:4 Changed 9 years ago by jmoore

Simon, does it make sense to put this story & tickets into 4.3.2? i.e. will it be finished on that scale?

comment:5 Changed 9 years ago by szwells

Not a bad idea. Am happy to keep adding info to the documentation ticket #6453 as it comes up & to use discussion on #6447 #6449 #6451 to further identify what we need for those XML schema. Once agreed we can close those tickets. There are non that should hang around longer than this milestone.

comment:6 Changed 9 years ago by agilo

  • Status changed from new to accepted

Updated status, related task in progress

comment:7 Changed 8 years ago by szwells

  • Resolution set to fixed
  • Status changed from accepted to closed
Note: See TracTickets for help on using tickets. You may also have a look at Agilo extensions to the ticket.

1.3.13-PRO © 2008-2011 Agilo Software all rights reserved (this page was served in: 0.101914 sec.)

We're Hiring!