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 #6838 (closed)

Opened 9 years ago

Closed 8 years ago

HIC: Preliminary {ANO|PRO}CHI Aliasing Support

Reported by: szwells Owned by: szwells
Priority: minor Milestone: OMERO-4.4
Component: General Keywords: n.a.
Cc: hic@… Story Points: n.a.
Sprint: 2012-01-31 (7) Importance: n.a.
Total Remaining Time: 0.0d Estimated Remaining Time: n.a.

Description

In order to support:

  • reversibility
  • patient assurance over use of their data
  • auditing over which projects touch which patients
  • differential display of data

we will provide support for aliasing enabling the following:

  • BiMapped? use of {Ano|Pro}CHI such that instances of associated ProCHIs are replaced by their AnoCHI
  • For a given {Ano|Pro}CHI & a suitably authorised user:
    • Retrieve and display an alias table showing all projects utilising the data associated with that Pro or Ano CHI

This enables us to answer the following kinds of questions:

  • For a given ProCHI:
    • what is the parent AnoCHI?
    • What projects has this patient's data been associated with?
  • For a given AnoCHI:
    • What projects have used this patients data?
    • What are the ProCHIs associated with this AnoCHI?

&, during auditing, to reverse project anonymisation in a fine-grained way to enable the auditor to see to what extent an individual patient's data has been used in subsequent projects.

Change History (5)

comment:1 Changed 9 years ago by jmoore

This all sounds more or less, Simon. Of course, there could be a mental model mismatch but for the moment let's assume this bimapper is usual functionality. In terms of first steps, I think we should/could focus on:

  • A way to create/manage new "dictionaries" ("bimaps", "mapping tables",...; I won't concentrate on the naming yet.)
    • Do we just start off with one per project?
    • Will we need FS to get this working?
  • A way to assign permissions to the entire dictionary, and possibly rows.
    • Does this happen via the XML?
    • Do we need other specific row-level control?
    • Is it enough for anyone with a hashed anon-chi to be allowed to access that row? (I'd think this may be sufficient. In an (e)mail to patients, this value could be provided with the caveat: "This represents your password to the system. Do not share it with anyone."
  • A way to access a table using the dictionary.
    • Do we do the term replacement during the queries?
    • Do we do the term replacement during the return value parsing?

comment:2 Changed 8 years ago by agilo

  • Status changed from new to accepted

Updated status, related task in progress

comment:3 Changed 8 years ago by szwells

  • Summary changed from HIC: {ANO|PRO}CHI Aliasing Support to HIC: Preliminary {ANO|PRO}CHI Aliasing Support

comment:4 Changed 8 years ago by szwells

  • Milestone changed from Unscheduled to OMERO-Beta4.4
  • Sprint set to 2012-01-31 (7)

comment:5 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.88120 sec.)

We're Hiring!