HIC: Preliminary {ANO|PRO}CHI Aliasing Support

[szwells]

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.

[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?

[agilo]

Updated status, related task in progress