Leave a comment at the end of this page or email contact@krishagni.com
Configuring eConsents in CPs
You need to be well-versed with HTML to configure consent forms. The HTML files can be created manually or using online editors like this.
In future versions, we plan to give a UI-based editor within OpenSpecimen to create the consent forms.
- 1 Introduction
- 2 Prerequisites
- 3 Designing the Consent Form
- 4 Examples of Consent Form
- 5 Other Example
- 6 Upload Consent Document in OpenSpecimen
- 7 Adding the Consent Document Form to a CP
- 8 Updating a Consent Form
- 9 Consent Revision (Versioning)
- 10 Archiving Consent Form
- 11 Download Consent
- 12 Sort Consents
- 13 Audit Trails for consent document
- 14 Consents Validation
- 15 Consents Digests
- 16 Reuse Participant Consents
Introduction
eConsent Forms are configured at System level and it contains the following:
HTML text (Text formatting/Image source etc.)
Consent Statements
Custom fields (Text/Dropdowns/Signatures etc.)
Prerequisites
'Allowed File Types' setting
The system setting “Allowed File Types” should have ‘HTML’ as an allowed file type.
Consent Statements
The consent statements are defined at a global level so that they can be reused across CPs. Go to Menu->Consents to define new consent statements. Refer to Coded Consents for more details.
Consent Response Code
A unique concept code for each consent response is mandatory. These codes are used in the consent HTML document for invoking the specific consent response. For example, “Y” for “Yes” response, “W” for “Withdrawn,” etc.
Make sure the concept code is unique for every response.
Custom Fields
The consent form could have fields like consent witness, consent date, e-signatures, etc. These fields are to be added in a custom form attached to the “Consent Document Custom Fields” level. A single form is maintained for consent custom fields across the system to avoid duplicating fields across CPs and making it easy for reporting.
Refer to Create and Edit Formarchivedfor details on how to create a new form.
Refrain from adding duplicate fields. For example, ‘participant name’ is the same as the ‘patient name’.
Designing the Consent Form
The consent form is designed in HTML, since it gives us the flexibility of easy formatting. E.g. use of bullet points, use of text formatting like bold, underline, embed videos/photos, etc.
There are three sections in the consent form:
Formatted text
Header/Footer
Consent statements
Custom fields
Formatted HTML text
This section contains the consent text. For example:
Consent Statements
Consent statement(s) can be added anywhere in the consent form. They can be displayed as a dropdown, radio-button, or checkbox.
For example:
Custom Fields
Details such as signature, date of signature, etc. that were defined in the custom form (step 2 in the “Prerequisites”) can be displayed as below in the consent form.
Examples of Consent Form
Here’s the HTML for the above consent document: The HTML document has a below example of a consent statement, custom fields, signature, and date.
Other Example
Upload Consent Document in OpenSpecimen
Users can upload consent documents in the Consents tab and can access those in the collection protocol. From v9.0, OpenSpecimen will allow using the same consent form in different CPs. The user who has. the access to the Consent can be uploaded or updated consent document in OpenSpecimen.
Adding the Consent Document Form to a CP
Once the HTML is ready, you can upload it for a CP using the below steps.
Updating a Consent Form
The title, version, and HTML content can be updated. It can be done by clicking the “Edit” icon from the consents list page.
From v9.1, OpenSpecimen will not allow updating the consent document if that is used with any patient.
Consent Revision (Versioning)
A consent document can have multiple versions. When a new version is added, the new version is available for old and new participants. The data collected for older version remains in the database and is available for querying.
Archiving Consent Form
If a version of a consent form is not needed, it can be archived. Once archived, the consent document is not available any more for consent response collection. However, if consent is already collected for that version, then it is available for viewing, editing, and reporting.
From v9.0, OpenSpecimen allows archiving the document at the system level and CP level. If the document is archived at the system level, the user won't be able to add that in new collection protocols, but if that document is already used in other CP will work without affecting anything.
Users also allow archiving the document in the collection protocol, and users won't be able to collect any responses for new patients.
System-Level Archive Option:
Navigates to Home → Consent → View Documents
Click on the Archive option
CP Level Archive Option:
Go to the Collection Protocol Overview Page → Consents tab
Download Consent
The consent form’s HTML file can be downloaded and used to edit the form or upload it to another instance or another CP. This saves the re-work of designing the document from scratch.
Navigate to Home → Consent Card → View Documents → Click on the Download button below
Sort Consents
The order of consent documents can be changed using the “Sort” option. If no order is specified, the consent documents will appear in the order that they were added.
Audit Trails for consent document
You can check the audit trails for the consent document. The audit trails show who updated the consent document and when.
Consents Validation
One or more validation rules can be added to ensure that specimens cannot be collected before the participant has consented. These validation rules are defined at a CP level.
To define validation rules:
Go to the CP Overview > Consents > Validations
Click on “Add”.
Field | Description | Options |
---|---|---|
Statement | Coded consent statements | All the consent statements defined for the CP |
Match | Condition for the consent response |
|
Response | Response of the consent statement | Any valid consent response. |
The above rule is to allow collection when the response for C0001 is “Yes”. Click on “Add”.
Follow the above steps to add more than one consent.
In the validations list page, there is another match for multiple consents.
ALL: It allows the collection of visits/specimens when ALL rules are true. Works like “AND” in the query.
ANY: It allows the collection of visit/specimens when ANY one of the rules is true. Works like “OR” in the query.
ADVANCED: This is used for creating a combination of rules using ‘and’ and ‘or’.
For example,
The below will be true if either (consent 1 is yes AND consent 2 is yes) OR consent 3 is yes.
The expression in the box defines the rule which allows collection. It can be edited by clicking on “Edit”.
Consents Digests
OpenSpecimen provides two options to receive the consent digest, which described below. User will get receive the participants and consent document information who consented on that day(within 24hrs).
Site based Recipients? → No, The user has to specify a list of users and those users will get the consent digest email.
Site based Recipients? → Yes, The user has to specify a sites and user groups and those users from groups will receive the digest emails
What information is present in Digest Email?
The digest email has the information on the patient who consented on that day(24hrs) or who updated the consent document on that day for that patient along with the date. Furthermore, you can configure when to send the digest email, like Hourly, Monthly, Daily, On Demand etc.
Reuse Participant Consents
At many centers, participant consents are registered or collected only once as per the IRB guidelines and reused in multiple studies.
From v10.3, A new setting has been added to the CP consents tab, this allows consent responses to be shared between multiple collection protocols, streamlining the consent management process.
Points to remember :
No new consent tiers or documents can be added in the receiver CP.
Consent responses cannot be added/updated via receiver CP registrations.
The participants' consent responses can be seen in the read-only mode in the receiver CPs with the option to print the consent document.
Since the consents for participants is copied to receiver CP, openspecimen users can distribute specimens collected for the receiver CP.
Leave a comment at the end of this page or email contact@krishagni.com