Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

From v9.1, OpenSpecimen supports sharing the consent document across the multiple collection protocols.

UseCase:

Many CPs Collection Protocols use the same consent forms. Having ; having duplicates is painful to maintain across languages and versions. Instead, now it would be easier because the because of this new enhancement, consent forms were defined outside and used within the CP.

Once the user upgrades the OpenSpecimen with the v9.1 version, all of their CP level consent forms will automatically be moved to the system level.

...

How to access the System Level Consent documents?

  • Navigate to Home → Consents → View Documents (Screenshot Below)

    Image Added
  • You can see the list of all consent documents used across all the CPs.

  • You can add, update, archive, add revision, and download the consent forms from the list view, same as before.

    Image Added

Since all of the consent document operations are provided at the system level, there is no provision to change the consent document at the CP level. You can only archive the document at the CP level.

How does System Level Consent Document work?

  1. Only super and institute admin users can create and update system-level consent documents. The Institute admin can update the documents created by the institute admin of any institute.

  2. The CP users can use any system-level consent documents in their CPs to capture the patient consent. When the user clicks on the +Add button, OpenSpecimen will show the list of all consent documents present at the system level.

    Image Added

How does Archive consent work at System Level vs. CP level?

  1. When a system-level consent document is archived, it cannot be used in any new associations with the CPs. However

  2. If the Consent Document is used with any patient, the user won't be able to archive that at the system level.

  3. Suppose the Consent Document does not use with ant patient but is added to the CP association. In that case, When a system-level consent document is archived, the existing CP associations will continue to work without any impact.

  4. When a consent document added at the CP level is archived, it cannot be used to capture the patient responses.Added migration scripts to move the documents created at the CP level to the system level and create appropriate CP associations.