Skip to main content

Programs

Programs represent the distinct patient journeys for different products, therapeutic areas, and geographic locations. Programs are created via custom metadata and mapping jobs. Enrollment into a program is stored in the Case object of CarePlan record type.

Note

If a program errors after an enrollment, reference Troubleshoot care plan creation issues.

Custom metadata and objects

The following custom metadata types facilitate the implementation and management of programs. The corresponding objects store the captured data.

Note

"Program problem" and "stage" may be used interchangeably while "program case" and "activity" may be used interchangeably.

  • Program (mvn__PJN_Program__mdt) defines the program journey that patients can enroll in. Each program must have a corresponding Care Program (CareProgram) object that must be manually created during program setup, while data for each care plan is captured in the Case object of CarePlan record type.

  • Program Problem (mvn__PJN_Program_Problem__mdt) defines the attributes of the stages that comprise a program. Data for each stage is created in the Problem (HealthCloudGA__CarePlanProblem__c) object.

  • Program Case (mvn__PJN_Program_Case__mdt) defines the activities within each stage of a patient's journey. Data for each activity is captured in the Case object of PJN_Activity record type.

  • Program Case Dependency (mvn__PJN_Program_Case_Dependency__mdt) defines the dependency between different activities within a single stage. No specific object is used to capture the dependencies between activities. However, a dependent Case record of PJN_Activity record type will initiate once the Status field on all preceding activities' Case records is Closed or Cancelled.

mvn__PJN_Program__mdt ERD

After the necessary metadata records are created, you then need to create mapping jobs to properly configure the program.

Mapping jobs

Program problems and program cases both require a number of attributes to be defined when specific actions occur. For example, when a program problem is created, a start date must be set, and when a program case is created, a record type must be defined and a description must be added. Program-related mapping jobs help map and stamp field attributes to stages and activities to facilitate this process.

The Table 86, “Program builder mapping jobs” below lists the baseline Mapping Job (mvn__PJN_Mapping_Job__mdt) metadata records that the backend Mapping Engine needs in order to run without errors. A sample configuration is shown as well. Additional custom mapping jobs can be created to set other attributes automatically.

Table 86. Program builder mapping jobs

Action

Metadata type

Target Field API Name

Program Problem API Name_Create

Program Problem

Warning

This mapping job does not have any associated mappings but is needed for the Mapping Engine to run successfully.

Program Problem API Name_Start

Program Problem

mvn__PJN_Date_Started__c

Program Problem API Name_Close

Program Problem

mvn__PJN_Date_Closed__c

Program Problem API Name_Skip

Program Problem

mvn__PJN_Date_Closed__c

Program Case API Name_Start

Program Case

  • Description

    Example of a mapping job record for Case_Start activity to Description field.

  • Priority

  • Type

  • RecordTypeId

  • HealthCloudGA__DueDate__c

  • Owner (if not the Case Plan Owner)

Program Case API Name_Skip

Program Case

PJN_Cancellation_Reason__c



Program creation summary

In summary, the steps for creating a program are as follows:

  1. Create a Program (mvn__PJN_Program__mdt) metadata record.

  2. Create a Program Problem (mvn__PJN_Program_Problem__mdt) metadata record.

  3. Create a Program Case (mvn__PJN_Program_Case__mdt) metadata record.

  4. Create a Program Case Dependency (mvn__PJN_Program_Case_Dependency__mdt) metadata record, if applicable.

  5. Create the following four Mapping Job (mvn__PJN_Mapping_Job__mdt) metadata records, along with other mapping-related metadata records as needed, for each program problem:

    1. _Create

    2. _Start

    3. _Close

    4. _Skip

  6. Create the following two Mapping Job (mvn__PJN_Mapping_Job__mdt) metadata records, along with other mapping-related metadata records as needed, for each program case:

    1. _Start

    2. _Skip

Program Visualizer

To ensure that a program has been built correctly, you can use the Program Visualizer to review the structure of the program. The Program Visualizer provides a visual presentation of a program based on the metadata records and mappings that have been implemented, showing the order in which program problems occur and the dependencies that exist between program cases.

Note

To access the Program Visualizer via the App Launcher in Komodo Care Connect V2 and above, users must be assigned the KCC - Feature - Program Visualizer (PJN_Feature_Program_Visualizer) permission set, which is in the MVN Admin (MVN_Admin) permission set group.

To access the Program Visualizer via the App Launcher in Komodo Care Connect V1, users must be assigned the KCC - Program Visualizer (PJN_Program_Builder) permission set.

Program Visualizer custom metadata types