Skip to main content

Educational programs and care plans

Programs can either be educational or therapeutic and are distinguished by the Type (mvn__PJN_Type__c) picklist field on the Care Program (CareProgram) object. Depending on the selected picklist value, any Care Plan (Case) record that relates to the Care Program record will also be designated as either an educational or therapeutic care plan.

Note

Unless otherwise specified, "care plans" generally refers to "therapeutic care plans."

Educational programs and care plans differ from therapeutic programs and care plans in the individuals that they support; while the former targets those who are interested in learning more about a drug program (i.e., consumers), the latter targets those who are already on the given drug or therapy (i.e., patients). Most of the user flows for searching for and enrolling individuals into educational and therapeutic programs are the same. However, there are a few setup steps and special considerations to keep in mind when working with consumers:

  • Consumers must provide marketing consent to be added to Komodo Care Connect. For setup instructions, reference Step 1. Decide on a marketing consent strategy.

  • Consumers should be enrolled into educational programs and care plans. For setup instructions, reference Step 2. Create an educational program and care plan.

    • If a consumer is enrolled into a therapeutic program instead of an educational program, the consumer will automatically be converted into a patient (i.e., the Account record type will change from PJN_Consumer to PJN_Patient) and the Conversion DateTime (mvn__PJN_Conversion_DateTime__c) field on the Account record will be updated accordingly. Out of the box, the Conversion DateTime field is not included in any Account or Person Account page layouts.

    • If an educational program is converted into a therapeutic program (i.e., the Type field on the Care Program record is changed from Educational to Therapeutic), the consumers on the educational care plans will not automatically be converted into patients. You will have to manually convert every consumer on the related care plans to patients.

    • Do not use Salesforce's standard Convert button on Lead records to convert consumers to patients.

  • Consumers can be converted from Lead records to Person Account records and be found in Account Search. For setup instructions, reference Step 3. Convert leads to accounts.

1. Decide on a marketing consent strategy

Individuals who wish to learn more about a drug program must express interest by consenting to receive marketing materials. Your business should consider how to capture marketing consent when intaking information about these individuals into Komodo Care Connect. For instance, you may use Salesforce's web-to-lead service to let individuals submit their information via an online form or you may load data from an event attendee list. Regardless of how the information is captured, these individuals will be stored as Lead records of the PJN_Consumer record type and referred to as "consumers."

Note

Only admin users can manually create new PJN_Consumer Lead records. To add consumers without web-to-lead:

  1. In the App Launcher, search for and select Leads.

  2. Click New.

  3. Enter the name and status of the consumer as well as any other relevant information.

  4. Click Save. The Lead record that is created will be of the PJN_Consumer record type.

2. Create an educational program and care plan

Consumers should be enrolled into educational programs, which are distinguished from therapeutic programs by the Type (mvn__PJN_Type__c) picklist field on the Care Program (CareProgram) object. Out of the box, the Type field is not included in any Care Program page layouts and does not have a default value.

To add the Type field to the PJN_Program Care Program page layout:

  1. In the Object Manager, search for and select Care Program.

  2. In the lefthand navigation, click Page Layouts.

  3. Select the PJN_Program Layout.

  4. Drag and drop the Type (mvn__PJN_Type__c) field into the page layout.

  5. Click Save.

To identify a care program as an educational program:

  1. In the App Launcher, search for and select Care Programs.

  2. In the list of Care Program records, click the care program to be identified as an educational program.

  3. Edit the Type field and select the Educational picklist value.

  4. Click Save.

Care Plan records that are created and related to the educational Care Program record will subsequently be identified as educational care plans.

3. Convert leads to accounts

To facilitate the searching and enrolling of consumers into educational programs, Lead records of the PJN_Consumer record type can be converted into Person Account records also of the PJN_Consumer record type. Conversions are performed via the Lead Convert Service (PJN_LeadConvertService) Apex class, which can be called from either a flow or the PJN_LeadSearchHdlr custom handler, as well as the Individual Record Type Mapper (HealthCloudGA__IndividualRecordTypeMapper__mdt) custom metadata type. Any contact information on the Lead record will become Contact Information (mvn__PJN_Contact_Information__c) records related to the new Person Account record.

Note

To access the Lead Convert Service Apex class, users must be assigned the KCC - Feature - Marketing Consent (PJN_Feature_Marketing_Consent) permission set.

Warning

The Lead Convert Service has a bulk convert limit of 100 records.

3a. Configure Account Search to use the PJN_LeadSearchHdlr custom handler

Account Search can be configured to use the PJN_LeadSearchHdlr custom handler so that Lead records are automatically converted to Person Account records when a user searches for and selects a consumer in Account Search. To do so, configure Account Search as if you are adding the Lead records as an integration with an external database by creating the following Interface Handler (mvn__Interface_Handler__mdt) metadata record and using the PJN_LeadSearchHdlr as the search handler.

Table 87. Required Lead Consumer Search mvn__Interface_Handler__mdt metadata record

Field label

Required value

Active

true

Class

PJN_LeadSearchHdlr

Class Namespace

mvn

Context

Account Search

Criteria

Leave blank

Interface

mvn.PJN_AccountSearchIntf

Sequence

1



3b. Map the PJN_Consumer record types

When Lead records are converted to Person Account records, the PJN_Consumer record type from the former can be mapped to the PJN_Consumer record type on the latter. To do so, create the following Individual Record Type Mapper (HealthCloudGA__IndividualRecordTypeMapper__mdt) metadata record.

Table 88. Required Person Account - Consumer HealthCloudGA__IndividualRecordTypeMapper__mdt metadata record

Field label

Required value

Individual Record Type Mapper Name

PJN_Consumer_Person_Account

Account Record Type

PJN_Consumer

Record Type Namespace (Account)

mvn

Lead Record Type

PJN_Consumer

Record Type Namespace (Lead)

mvn



Warning

Out of the box, the Person Account (Person_Account) and Person Account - Patient (PJN_Patient_Person_Account) Individual Record Type Mapper metadata records have been provided for the PersonAccount and PJN_Patient Account record types, respectively. The Person Account metadata record is required by Health Cloud. Do not delete the Person Account metadata record and do not create another Individual Record Type Mapper metadata record with the "Person Account" label.

3c. Configure PJN_Consumer as a supplement to PJN_Patient

You do not have to configure Account Search to include the PJN_Consumer record type as an additional tile as long as it is marked as a supplement to the PJN_Patient record type. This means that when you select a consumer in Account Search to enroll them into an educational program, the consumer will appear under the Patient tile instead of a separate Consumer tile. A consumer can therefore be enrolled into an educational program from a new Request (Case) record and then Account Search the same way a patient is enrolled into a therapeutic program.

To mark the two record types as supplements of one another:

  1. Navigate to the Account Type Setting (mvn__PJN_Account_Type_Setting__mdt) custom metadata type.

  2. Click the metadata record that manages the PJN_Patient record type in Account Search.

  3. Ensure that the Supplemental Account Search Record Types (mvn__PJN_Supplemental_Acct_Search_Rec_Types__c) field is populated with PJN_Consumer. If not, update the metadata record as appropriate.

Note

Out of the box, AccountId Case Field Configuration (mvn__PJN_Case_Field_Configuration__mdt) metadata records have been provided for the PJN_Patient and PJN_Consumer Account record types. The record type of the Account on the Account Name (AccountId) field of the Care Plan (Case) record will determine which AccountId Case Field Configuration metadata record is used to create the relationships and care team for the individual.