From c5ef5ea7881bf3bea8081a84a53a84fef54b912f Mon Sep 17 00:00:00 2001 From: TiG Date: Thu, 22 Apr 2021 09:54:47 +0200 Subject: [PATCH 1/4] revise initial checkbox interaction --- source/guides/consent-management.rst | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/source/guides/consent-management.rst b/source/guides/consent-management.rst index a3d66f8..03804a4 100644 --- a/source/guides/consent-management.rst +++ b/source/guides/consent-management.rst @@ -5,9 +5,9 @@ Set Recruitment Consent for a Subject 1. In subject management > subject details, go to the **Data protection** tab. -2. Click on the checkbox **Recruitment consent**. It will not be checked - immediately. Instead it indicates that you are waiting for confirmation - from the subject. +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. 3. If the subject agrees, click on **Confirm**. -- GitLab From 625b8527a7fe815f1be2ec4a8a0ae1b1b2eb4a5b Mon Sep 17 00:00:00 2001 From: TiG Date: Thu, 22 Apr 2021 09:55:11 +0200 Subject: [PATCH 2/4] add note explaining async consent workflow --- source/guides/consent-management.rst | 9 +++++++++ 1 file changed, 9 insertions(+) diff --git a/source/guides/consent-management.rst b/source/guides/consent-management.rst index 03804a4..f1c6054 100644 --- a/source/guides/consent-management.rst +++ b/source/guides/consent-management.rst @@ -9,6 +9,15 @@ Set Recruitment Consent for a Subject **waiting for confirmation** indicating that there is still an outstanding final approval (signed consent) by the person. +.. 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. -- GitLab From 5fa864a3ddd54163518a1870d26797d8867b9263 Mon Sep 17 00:00:00 2001 From: TiG Date: Thu, 22 Apr 2021 10:02:38 +0200 Subject: [PATCH 3/4] add note on clearing waiting --- source/guides/consent-management.rst | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/source/guides/consent-management.rst b/source/guides/consent-management.rst index f1c6054..582e072 100644 --- a/source/guides/consent-management.rst +++ b/source/guides/consent-management.rst @@ -22,6 +22,12 @@ Set Recruitment Consent for a Subject 4. If the subject rejects the request, clear the checkbox. +.. 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). + .. _subject-consent-maintenance: -- GitLab From d37d599c9b44a264a2039dab387cbe8584257ced Mon Sep 17 00:00:00 2001 From: TiG Date: Mon, 26 Apr 2021 11:34:35 +0200 Subject: [PATCH 4/4] indent first note --- source/guides/consent-management.rst | 16 ++++++++-------- 1 file changed, 8 insertions(+), 8 deletions(-) diff --git a/source/guides/consent-management.rst b/source/guides/consent-management.rst index 582e072..2d1eb0a 100644 --- a/source/guides/consent-management.rst +++ b/source/guides/consent-management.rst @@ -9,14 +9,14 @@ Set Recruitment Consent for a Subject **waiting for confirmation** indicating that there is still an outstanding final approval (signed consent) by the person. -.. 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**. + .. 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**. -- GitLab