1. HCP-Consent Overview

Cognipharma HCP-Consent allows clients to collect and centralize eConsents and integrate them with CRM and email marketing platforms.

Each client has their own “Tenant” where all the client websites are configured. The client eConsents are linked to this tenant and will be the same for all the client websites. This means that the consent is provided, by the end-user, to a Company / Legal Entity.

The eConsents can be used independently of the user id registration/login flow and have their own dataset. They can also be linked to the registration/login flow if the client wishes, and be requested on these processes flows.

The client back office is where all customizations and business rules are done for the eConsents configurations and look and feel.

Consent Structure & Configurations

Each consent definition will reside in a consent definition, one or more consent header linked to this definition, and each consent header will have one or more consent lines (the type of consent content the user will be signing in) and also one or more channels (the type of communication the user can select to be contacted or not for each of these consent lines, e.g. email, mobile phone, etc.) These eConsents will be created in a matrix: N consent lines x M channels. The presentation of this matrix will depend on the configurations you have done in the back office.

Configuration

In your own tenant configuration it’s possible to present the eConsent for a set of professions (e.g. HCP eConsent or All users eConsent) and also the type of the eConsents: double opt-in or single opt-in. The process flow of the eConsents capture will be different based on this selection type.

Here’s an example of an eConsent presentation, with the consent definition, consent headers, consent lines and channels already configured:

On the configuration of the eConsent headers, the client has the option to choose if the channels defined for communication can be individually selected (opt-in or opt-out) by the user or are all selected as a group for the corresponding consent lines. Also as an option on the configuration backoffice for the consent headers, the client can choose if the eConsents selected by the user are mandatory, i.e., the user has to explicitly select an opt-in or opt-out, or if the selection made by the user will be optional, i.e., if the user checks an option, then it will be set as an opt-in and if the user does not check an option, then it will not be considered for communication by that consent line/channel. On this last option (optional selection by the user), if the channels are all presented for the user (manual channels selection), there is also the option to pre-select a channel for all the consent lines, this will correspond as an opt-in already selected when the eConsents matrix are presented to the user.

In the figures below it is possible to see these 4 matrix combinations.

Manual channel selections with mandatory choices:

Manual channel selections with optional choices (where email was configured on the backoffice as a pre-selection):

Group channel selections with mandatory choices:

Group channel selections with optional choices:

Also on the configuration backoffice it’s possible to set the expiration time of an eConsent. If set, the system will prompt for a renewal of the consent given when the consent expires (or when it’s about to expire).

en_US