Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Extend human page by different types of data acquisition #1266

Conversation

vildead
Copy link
Contributor

@vildead vildead commented May 24, 2023

No description provided.

@Nazeeefa Nazeeefa added the contentathon Contentathon related issues and PRs label May 24, 2023
@vildead vildead marked this pull request as ready for review May 24, 2023 10:39
@vildead
Copy link
Contributor Author

vildead commented May 24, 2023

  • ❌ move content from Human data domain page to GDPR compliance

The change will be submitted in new MR

tiny wording/grammar fixes
* In most cases, you should get **informed consents** from your research subjects.
* The [Global Alliance for Genomics and Health (GA4GH)](https://www.ga4gh.org) has recommendations for these issues in their [GA4GH regulatory and ethical toolkit](https://www.ga4gh.org/genomic-data-toolkit/regulatory-ethics-toolkit/), see for instance the [Consent Clauses for Genomic Research](https://drive.google.com/file/d/1O5Ti7g7QJqS3h0ABm-LyTe02Gtq8wlKM/view?usp=sharing).
* The acquisition of data must be legal.
* **Receiving data/samples directly from data subjects** requires in most cases **informed consents**.
- An informed consent is an agreement from the research subject to participate in and share personal data for a particular purpose. It shall describe the purpose and any risks involved (along with any mitigations to minimise those risks) in such a way that the research subject can make an informed choice about participating. It should also state under what circumstances the data can be used for the initial purpose, as well as for later re-use by others.
- Consider describing data use conditions using a machine-readable formalised description such as the Data Use Ontology [DUO](https://github.com/EBISPOT/DUO). This will greatly improve the possibilities to make the data FAIR later on.
Copy link
Collaborator

@Nazeeefa Nazeeefa May 31, 2023

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think the link for DUO mentioned here is https://github.com/EBISPOT/DUO not necessary, as it is mentioned later on under solutions. If we want to add link here then it should be pointed to a general resource on DUO or explicity mention that it's (GA4GH) Data Use Ontology (DUO).

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

fixed in e405830

@pinarpink pinarpink merged commit 4787fea into elixir-europe:master Aug 23, 2023
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
contentathon Contentathon related issues and PRs
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants