definitions_management_details.md 3.07 KB
Newer Older
Ewa Smula's avatar
Ewa Smula committed
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
---
layout: page
title: Definitions management details
permalink: /manual/definitions_management_details/
order: -1
---

<small>
[User guide]({{ "/manual/" | relative_url }}) &raquo; [*6 Definitions Management (**GO BACK to main page**)*]({{ "/manual/#6-definitions-management" | relative_url }})
</small>

---

<br>

## 6 Definitions Management
{:.no_toc}

* TOC
{:toc}

---

<br>

DAISY *Definitions* module allows for the management of *Contacts*, *Cohorts* and *Partners*. Here we only discuss what information is held in these definitions.

<!-- <a name="COH_M"></a> -->
### 6.1 Cohorts Management
Cohort is a study that collects data and/or bio-samples from a group of participants (e.g. longitudinal case-control or family studies). A cohort is linked to the creation of data and is considered its ultimate source.

In order to effectively handle data subjects' requests, as per GDPR, it is crucial that an institution keeps track of what data it keeps from which cohorts. Inline with this, DAISY allows maintaining a list of *Cohorts* and link  *Datasets* to *Cohorts*.

The information kept on cohorts can be seen in the associated *Editor Page* seen below. Cohorts are expected to have a *Title* unique to them, and they are  linked to one or more *Cohort Owners*, which are that are Principle Investigators, Clinicians running the study. Cohorts owners are kept as *Contacts* in DAISY. In order to maintain a controlled list of cohorts, the administrator for the DAISY deployment may assign an accession number to the *Cohort*, which would be the unique identifier for this Cohort.  <br />

<span style="display:block;text-align:center">![Alt]({{ "img/cohort_edit_form.png" | relative_url }}){:width="800px"}</span>


 <!-- <a name="PAR_M"></a> -->
### 6.2 Partners Management

A *Partner* is a research collaborator that is the source and/or recipient of human data. Partners are also legal entities with whom contracts are signed. Clinical entities that run longitudinal cohorts, research institutes, or data hubs are all examples of Partners.
In accordance, when maintaining *Dataset* source info, *Dataset* transfer info or when creating *Contract* records, you will be asked to select Partners.

The information kept on partners can be seen in the associated *Editor Page* seen below.

<br />
<span style="display:block;text-align:center">![Alt]({{ "img/partner_edit_form.png" | relative_url }}){:width="800px"}</span>

<!-- <a name="CONN_M"></a> -->
### 6.3 Contacts Management

Ewa Smula's avatar
Ewa Smula committed
53
*Contacts* are people affiliated with the external partner institutions (e.g. collaborator principle Investigators, project officers at the EU).    
Ewa Smula's avatar
Ewa Smula committed
54
DAISY keeps the contact details (e.g email address, affiliations) of external collaborators related to the *Projects*, *Datasets*, *Cohorts* and *Contracts*.
Ewa Smula's avatar
Ewa Smula committed
55

Vilem Ded's avatar
Vilem Ded committed
56
Standard information is kept on contacts as can be seen in the associated *Editor Page* given below.
Ewa Smula's avatar
Ewa Smula committed
57
58
59
60
61
62
63
64
65
66

<br />
<span style="display:block;text-align:center">![Alt]({{ "img/contact_edit_form.png" | relative_url }}){:width="800px"}</span>


<br>

---
<div style="text-align: right"> <strong><a href="#top">Back to top</a></strong></div>
<br />