16 like 0 dislike
616 views
in Open Science by (95 points)

I work with governmental register data, which includes sensitive information about individuals, and therefore cannot make datasets available to the public lest I risk violating the privacy of my subjects. Even though the data are anonymised, it contains information such as addresses and dates of medical prescriptions that should not be made public. I myself need to work inside a secure computer lab and don't have free access to these data. What are the possibilities for open science in this case?

Edit: My terms of use prohibit any sharing of the dataset with others not authorised to use the data. I am not allowed, in addition, to transfer the data from the computer where they are supposed to be analysed.



This post has been migrated from the Open Science private beta at StackExchange (A51.SE)
by (95 points)
0 0
That seems useful, but storing that dataset in a VCS repository is out of question. I don't have control over the way in which it is stored at the main database, only over the files that are delivered to me. In addition, I have agreed to not store the data extractions that I receive anywhere else than the computer where I'm supposed to analyse it. The terms of use prohibit sharing data with others, even if it is encrypted.

This post has been migrated from the Open Science private beta at StackExchange (A51.SE)
by (685 points)
0 0
If you're using VCS repository to store your data, you may consider encrypting the sensitive data. See: [BlackBox](https://github.com/StackExchange/blackbox) for more details.

This post has been migrated from the Open Science private beta at StackExchange (A51.SE)

2 Answers

12 like 0 dislike
by (1.2k points)
 
Best answer

Great question! Unfortunately, I think there are not going to be great answers. Three ideas have come up in my discussions with users of registry data:

Describe data access procedures completely: Be as transparent as you possibly can be about how you acquired the data, how others can acquire them, and what the policies and costs associated with acquisition would be.

Show everything that you can: While you cannot share the raw data, you can likely share a considerable amount of information from the data. For example, you can include descriptive statistics and graphics that convey the univariate and multivariate patterns in the data. You may also be able to share certain aggregated statistics (e.g., data aggregated at a block or city level).

Offer to collaborate: You may have privileged access to data (i.e., other simply will not be able to access it). In that case, to the extent allowed by data access rules, you should offer the ability to run analyses for others and collaborate with them using the data. This would mean that even your critics can use the data in a meaningful public exchange of ideas, even if the data themselves cannot be made public.



This post has been migrated from the Open Science private beta at StackExchange (A51.SE)
by (95 points)
0 0
These seem to be the most pragmatic solutions to my problem.

This post has been migrated from the Open Science private beta at StackExchange (A51.SE)
1 like 0 dislike
by (175 points)

While you can't share the data or the sensitive bits, you can share your results for whatever analyses you're doing.

For each analysis you make of the data, check your results. Remove any identifying or sensitive information, and then publish what you've got.

If others contact you about your results, and ask what your data was, you just have to make very clear that you have the data as part of your job, which gives you access to some sensitive material. If put nicely, no reasonable person will complain about the fact that you can't share it with them.



This post has been migrated from the Open Science private beta at StackExchange (A51.SE)

Ask Open Science used to be called Open Science Q&A but we changed the name when we registered the domain ask-open-science.org. Everything else stays the same: We are still hosted by Bielefeld University Library.

If you participated in the Open Science beta at StackExchange, please reclaim your user account now – it's already here!

E-mail the webmaster

Categories

...
https://openscience.uni-bielefeld.de/25/how-to-deal-with-sensitive-individual-data-in-open-science
openscience.uni-bielefeld.de
crawl=CC-MAIN-2019-26
45046
application/http; msgtype=response
sha1:W3ZT3SIMDLSDH7TYZDU4LUS2DVQ6OFXI
<urn:uuid:c3e0988e-b238-4f6e-8433-dbd44ef0671c>
2019-06-17T21:35:38Z
129.70.43.86
text/html
sha1:6OWAVLU6N3REENT5RLRQ46IAHDC7YO3D
<urn:uuid:ea1cf2b8-8700-4619-bcce-4e5be31871f4>
https://openscience.uni-bielefeld.de/25/how-to-deal-with-sensitive-individual-data-in-open-science
response
<urn:uuid:b9423a84-c266-4d9f-8bef-9ffed6e665b2>
isPartOf: CC-MAIN-2019-26
publisher: Common Crawl
description: Wide crawl of the web for June 2019
operator: Common Crawl Admin (info@commoncrawl.org)
hostname: ip-10-166-231-116.ec2.internal
software: Apache Nutch 1.15 (modified, https://github.com/commoncrawl/nutch/)
robots: checked via crawler-commons 1.1-SNAPSHOT (https://github.com/crawler-commons/crawler-commons)
format: WARC File Format 1.1
conformsTo: http://iipc.github.io/warc-specifications/specifications/warc-format/warc-1.1/