...

Consent documents are to be designed in HTML. They are to be uploaded at CP level

Create eConsent document

An HTML document containing at least one coded consent statement needs to be uploaded in the “Consents” tab of a collection protocol. These consents are to be set up per CP.uploaded as HTML documents at CP level. These documents can contain a detailed explanation and answers of general questions, followed by at least one consent statement and the details of the consenting participant.

Create eConsent document

Prerequisites

1. Coded consent statement should be defined in the “Consents” of the OpenSpecimen instance. In case it isn’t, please refer to this wiki page to add the coded consents: Coded Consents

2. Identify the fields for which information is to be recorded along with consent responses. For instance, the e-signature, the full name as provided in identity proof, the date of signature etc. These fields are to be added in a “Consent Custom Fields” form attached at “Consent Document Custom Fields” level. In order to add different control types to the custom form, refer this wiki page.

   Few pointers to keep in mind:

   1. Refrain from adding repetitive controls to the form. For example, ‘participant name’ is the same as the ‘patient name’ is the same as the ‘full name of the participant’. One control can be used by changing the captions as needed in the HTML.

   2. A single “Consent Custom Fields” form is maintained across the system and the fields from this form can be used across all CPs in the system. The relevant fields that are to be used in the consent document are to be defined in the consent HTML.

   Once the fields have been added to the form, they have to be defined in the HTML to add it to the consent document (detailed steps under this)

...