Consent
The following objects capture different types of consent details in Komodo Care Connect:
Consent (
mvn__PJN_Contact_Point_Type_Consent__c) captures patient consent.Channel Consent (
mvn__PJN_Channel_Consent__c) captures contact information consent.Data Use Purpose (
DataUsePurpose) captures additional details for the above records as well as all other types of consent.
Users can easily check whether or not a patient has given consent by referencing the indicator icons in the Contact Information component and the Consents related list. These indicator icons are calculated in real time based on the Channel Consent records' privacy consent status and effective to and from dates.
Warning
In order for the opt-in indicator icon to appear on the Channel Consent record when the mvn__PJN_Privacy_Consent_Status__c value is "Opt In," the mvn__PJN_Effective_To__c date and time must be populated and not yet have passed.
Capture consent with DocuSign
Komodo Care Connect ships with the DocuSign Apps Launcher package to provide users with a one-click solution for requesting and capturing electronic signatures (eSignatures). The one-click solution can be used on any object, such as the Consent object to capture consent. For information on how to set up and configure the one-click functionality, reference DocuSign electronic signature. For guidance on how to set up and configure the integration on the Consent object specifically, reference the example below.
DocuSign configuration step | Platform | Entity | Sample value |
|---|---|---|---|
DocuSign | Template name field |
| |
Role field |
| ||
Salesforce | Lightning action on the Consent ( |
| |
Lookup field on the DocuSign Status ( |
| ||
Salesforce | DocuSign One Click Setting ( | Reference Table 103, “Sample consent mvn__DocuSign_One_Click_Setting__mdt record” below. | |
DocuSign One Click Recipient ( | Reference Table 104, “Sample consent mvn__DocuSign_One_Click_Recipient__mdt record” below. | ||
DocuSign OneClick Envelope Update ( | Reference Table 105, “Sample consent mvn__PJN_DocuSign_OneClick_Envelope_Update__mdt record” below. |
Field label | Sample value |
|---|---|
Label |
|
Matching Rule | {
"AllTrue": [
{
"path":"attributes.type",
"operator":"Equals",
"value":"mvn__PJN_Contact_Point_Type_Consent__c"
},
{
"path":"mvn__PJN_Privacy_Consent_Status__c",
"operator":"Equals",
"value":"Not Given"
}
]
} |
Email Subject |
|
Email Message |
|
Template Name |
|
DocuSign Status Lookup to Object |
|
Field label | Sample value |
|---|---|
Label |
|
DocuSign One Click Setting | The DocuSign One Click Setting metadata record created above (i.e., |
Type |
|
DocuSign Role |
|
Path to Recipient Email |
|
Path to Recipient Name |
|
Field label | Sample value |
|---|---|
Label |
|
DocuSign One Click Setting | The DocuSign One Click Setting metadata record created above (i.e., |
Envelope Event |
|
Field to Update |
|
Value |
|
If the one-click solution is set up on the Consent object, then when a user clicks on the Lightning action on a Consent page layout, a modal will open and find the corresponding DocuSign One Click Setting (mvn__DocuSign_One_Click_Setting__mdt) metadata record. From there, the appropriate DocuSign envelope will be created and sent to the designated recipient(s). Additionally, a DocuSign Status (dfsle__EnvelopeStatus__c) record will be created and related to the Consent record. If the document is sent successfully, then the modal will display a success message and close automatically after three seconds. If there are any errors with the process, such as an invalid envelope due to a missing email address, the modal will display an error message for the user to resolve.
Note
The DocuSign OneClick Envelope Update custom metadata type cannot set dynamic values, so you may wish to create a custom flow to set more complex values on the source Consent record, such as the current date on the mvn__PJN_Effective_From__c field.