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

Is 'informed consent identification code' really a 'data item'? #5

Open
yongqunh opened this issue Feb 23, 2017 · 6 comments
Open

Is 'informed consent identification code' really a 'data item'? #5

yongqunh opened this issue Feb 23, 2017 · 6 comments

Comments

@yongqunh
Copy link
Member

The ICO term 'informed consent identification code' (ICO_0000044) is currently under 'data item'. Is it really a 'data item'?

@cstoeckert mentions that this should be an information content entity (ICE), but may not ba a data item since data item is for real data, and the informed consent identification code differs somehow.

See a similar DUO issue:
EBISPOT/DUO#3

This issue was raised out of a joint DUO and ICO meeting on 2/23/2017.

@linikujp
Copy link
Member

linikujp commented Feb 23, 2017 via email

@cstoeckert
Copy link
Contributor

See also Tracker item 2

@cstoeckert
Copy link
Contributor

cstoeckert commented Mar 16, 2017

@mbrochhausen
Copy link

The definition is: "a data item that shows a unique identification code for an informed consent". It is not clear what this class is intended to represent.

@mbrochhausen
Copy link

The consent codes represented by DUO (probably these are examples thereof: http://journals.plos.org/plosgenetics/article/figure/image?size=large&id=10.1371/journal.pgen.1005772.t001) are not data items. They are related to claims and obligation (or directive information content entities.

@mbrochhausen
Copy link

Also, we need to revisit 'informed consent rule specification'. It looks like a class that was created before d-acts was adopted and it will clash or at least provide double representation once we use d-acts in full swing.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants