diff --git a/source/guides/admin.rst b/source/guides/admin.rst index a29ed3cc4b966a046fa9246ed5c720756e239289..f05f93f0868047b7cf3a9173170e23d9c582bd4c 100644 --- a/source/guides/admin.rst +++ b/source/guides/admin.rst @@ -69,9 +69,8 @@ only very few attributes that can be seen as commonly used at every institute. link to a definition at `bioontology.org `_. -6. Set **privacy levels** of the attribute for **read** and **write** -7. **Order** and **Category** can be used to position the attribute in UI -8. **Statistics rank** can be used to set this attribute as primary or +6. **Order** and **Category** can be used to position the attribute in UI +7. **Statistics rank** can be used to set this attribute as primary or secondary feature that should be presented in statistics of recruitment .. note:: @@ -80,9 +79,9 @@ only very few attributes that can be seen as commonly used at every institute. will show an error warning. Accordingly, you have to deselect a primary or secondary attribute first to select a new one. -9. **Label** should be the actual name of the attribute. Be sure to provide +8. **Label** should be the actual name of the attribute. Be sure to provide translations if Castellum is set to support more than one language -10. If appropriate, fill in all **Attribute choices** (if needed also add +9. If appropriate, fill in all **Attribute choices** (if needed also add translations) that represent the possible values of the attribute and will be used for filtering @@ -107,8 +106,8 @@ Upload a new document 4. Choose the file you want to upload 5. Click on one of the saving options -Now whenever consent is added to a subject, it implicitly refers to this new -version. +Now whenever consent is added to a subject, the user can pick this new version +from a list of all available documents. Deal with the old document -------------------------- @@ -120,10 +119,10 @@ case there is a two step process: 1. Mark the old consent document as **deprecated**. The document is still considered valid but subjects who have agreed to this document will show up in the consent maintenance view (see below). -2. Mark the old consent document as **invalid**. Now all consents related to - this document are void. Subjects who have not been updated to the new - document are no longer available for recruitment and will potentially show - up in the data protection dashboard. +2. Delete the old consent document. Now all consents related to this document + are void. Subjects who have not been updated to another document are no + longer available for recruitment and will potentially show up in the data + protection dashboard. The legal basis for each subject can be found in the subject detail view. diff --git a/source/guides/consent-management.rst b/source/guides/consent-management.rst index 689184fa5ea8e8b9dbbae486c3bbfcbf112d1d1c..31cabf65074769840c21bc260fbbce372606aa76 100644 --- a/source/guides/consent-management.rst +++ b/source/guides/consent-management.rst @@ -9,30 +9,22 @@ Set Recruitment Consent for a Subject ===================================== 1. In subject management > subject details, go to the **Data protection** tab. + In the box, information about the current consent status is shown. All newly + created subjects initially start with **No consent**. When a subject is + created there is initially no information on consent. You can then either + select a consent document or **Consent withdrawn**. -2. Click on the checkbox **Recruitment consent**. It will change the status to - **waiting for confirmation** indicating that there is still an outstanding - final approval (signed consent) by the person. +2. Click on the button **Change**. - .. note:: - - This allows for an asynchronous workflow: On first contact recruiters - can explain the recruitment consent and ask for a *preliminary* approval - by the informed person (in other words: **waiting for confirmation**). - Subsequently, the actual document is given to this person asking them to - read it carefully and sign it. When getting back the signed document - recruiters can click **confirm**. - -3. If the subject agrees, click on **Confirm**. - -4. If the subject rejects the request, clear the checkbox. +3. Select **Consent withdrawn** or the version of the consent document the + subject has agreed to. In the latter case, you can also upload a signed + consent document. .. note:: - Please be aware that subject maintenance lists persons with the status - **waiting for confirmation**. Hence, they may be deleted after some time - waiting (if no other legal basis is given). - + Please be aware that subject maintenance lists persons without recruitment + consent. Hence, they may be deleted after some time waiting (if no other + legal basis is given). .. _subject-consent-maintenance: diff --git a/source/guides/recruitment.rst b/source/guides/recruitment.rst index c7b258447f755ea2f2dcbb9ae456268436417d1d..e67716affb33b0ffd41f6bd60153a585c271be62 100644 --- a/source/guides/recruitment.rst +++ b/source/guides/recruitment.rst @@ -22,7 +22,7 @@ Recruit subjects via phone - **Email**, **Phone number**, a potential **Phone number alternative** and / or the **Address** will be shown to you in the tab **Contacting details**. -5. Contact the potential subject using the specified method +5. Contact the potential subject using one of the listed methods - Please have a look at the **Talking points** that the study coordinator has provided diff --git a/source/guides/study-execution.rst b/source/guides/study-execution.rst index 45bec6f2806a9422abc8f6088fc6ac8e36d25c58..1617da952b9a65c40628748476355613ac62b7aa 100644 --- a/source/guides/study-execution.rst +++ b/source/guides/study-execution.rst @@ -44,7 +44,7 @@ attributes of all participants sorted by a pseudonym. study management as **Exportable recruitment attributes**. You are only allowed to export attributes if your privacy level is matching - those of the *highest rated* attribute and/or participant. + the participant's. If there is more than one study specific pseudonym domain set up in study management you will have to select the domain that should be used for export. diff --git a/source/guides/study-management.rst b/source/guides/study-management.rst index ea50f62f6412955fc40d9b7cc8cc29d0b95c45ab..fa632db0252384ec047ed371f75c610e65b1e37e 100644 --- a/source/guides/study-management.rst +++ b/source/guides/study-management.rst @@ -92,19 +92,7 @@ your study: - Attribute filters - Excluded studies -- Text based inclusion and exclusion criteria - -.. note:: - - At first it may be unclear how to distinguish **attribute filters** and - **inclusion/exclusion criteria**: - - - Attribute filters are applied to subject attributes stored in - Castellum. In other words, this will only suggest matching potential - subjects in recruitment. - - Inclusion and exclusion criteria need to be used when there is no data - available about it in Castellum. Therefore, they must be checked by a - staff member explicitly during recruitment. +- Text based inclusion and exclusion criteria as part of the recruitment text 1. Go to the **Recruitment Settings** tab @@ -112,7 +100,9 @@ your study: You can: - edit the **Recruitment text** (this text will be shown to recruiters - and will be used by them to recruit subjects for your study), + and will be used by them to recruit subjects for your study). Use this + for text based inclusion and exclusion criteria when there is no data + available in Castellum that you could use for an attribute filter - decide whether you wish to set up the **Advanced filtering** (this allows you to create multiple filtergroups that are not linked to each other), @@ -124,6 +114,14 @@ your study: recruiters of your study or if there will be some subjects displayed, in which certain characteristics still have to be queried + .. note:: + Session types may come with specific criteria that have to be checked + every time before appointing subjects to a session. In this case, + you'll see a caret with a label **Criteria for: ** next to the + recruitment text. Clicking on it will show you the text that is always + appended. In other words: You don't have to write this type specific + text by yourself. + 3. By clicking on **Filter** you are able to set filter criteria - select the attribute that should be used for filtering @@ -155,20 +153,7 @@ your study: 4. In **Excluded studies** you can select certain studies in which your subjects must not have participated -5. When you click on **Inclusion/exclusion criteria**, you can add - **additional subject characteristics that should be verified during the - recruitment** - - .. note:: - - Session types may come with specific criteria that have to be checked - every time before appointing subjects to a session. In this case, - you'll see a caret with a label **Criteria for: ** next to the - text field. Clicking on it will show you the text that is always - appended. In other words: You don't have to write this type specific - text by yourself. - -6. To allow recruiters to send batch invitations via e-mail, proceed as +5. To allow recruiters to send batch invitations via e-mail, proceed as follows: - click on **Mail Settings** @@ -184,7 +169,6 @@ your study: It is not intended to send e-mail attachments via Castellum. Instead, links can be inserted as standard text. - Create a geo filter ~~~~~~~~~~~~~~~~~~~ diff --git a/source/guides/subject-management.rst b/source/guides/subject-management.rst index 5dbbbf222c993cae31a3dc1be67466373d1396be..9b2da4bb55581ea3b08a2b8d74c291ad55b366e8 100644 --- a/source/guides/subject-management.rst +++ b/source/guides/subject-management.rst @@ -141,7 +141,6 @@ with a subject. number** and/or **Postal address** - You may want to add **Additional information** for postal address, such as c/o details - - Specify the **Preferred contact method** 2. If the person is not of an adult age or has a legal representative for example due to a disability or illness, select **Has legal representative** diff --git a/source/roles.rst b/source/roles.rst index 924081d884abb17c819408093a9dc7951993ad5c..1024d61469b7e52bcadbf93a312514b5b31293a0 100644 --- a/source/roles.rst +++ b/source/roles.rst @@ -116,7 +116,7 @@ Persons responsible for invitations to studies and the management of appointment should take on the role of **Recruiters** in Castellum. For this purpose, the **Recruiter** can view the contact details of individual subjects to establish communication with them. The **Study Coordinators** will define a recruitment -text and criteria to be clarified in advance, which the **recruiters** should use +text to be clarified in advance, which the **recruiters** should use when recruiting the respondent. To be able to schedule appointments, Castellum provides a calendar which shows available time slots. diff --git a/source/security.rst b/source/security.rst index 7944a6be26f78b05d04f80cae33d5281f516396e..22290ba8ee89d1f9242c0479c4e23e34c02f643e 100644 --- a/source/security.rst +++ b/source/security.rst @@ -63,8 +63,7 @@ Privacy levels ~~~~~~~~~~~~~~ Every subject has a privacy level. A user is only allowed to access that -subject if they have a sufficient privacy level themselves. For recruitment -attributes, you can define separate privacy levels for read and write access. A +subject if they have a sufficient privacy level themselves. A user's privacy level is controlled via the special permissions ``privacy_level_1`` and ``privacy_level_2``. The three levels (0-2) accord to the data security levels of the Max Planck Society.