If you are updating from 7.x versions to 8.x versions, perform these steps before you follow the steps in Adopting Pega Care Management version 8.7 features.

Enabling custom search properties for indexing

After you update your application, to use the Authorization Search feature, enable the dynamic search setting to use custom search properties.

1. Log in to your application by using the credentials that you previously established.
2. In the navigation pane of Dev Studio, click RecordsSysAdminDynamic System Settings.
3. In the Setting Purpose column, filter and search for indexing/useDataInstances.
4. Click indexing/useDataInstances.
5. Change the value to true.
6. Click Save.

Running the timeline upgrade utility

In Pega Care Management version 8.1, the patient timeline was updated. To display the care patient events that were created before you updated the application, if you are updating from version 7.4 or earlier versions, you need to run the timeline upgrade utility.

You do not need to run the utility if you do not want the cases that were created before the update to appear on the timeline. New events for the cases that are configured on your configuration page and are created after the update appear on the timeline.

1. In the header of Dev Studio, click ConfigureCare Management Configuration, click the Patient events tab, and review the fields in the Timeline events section:
   1. In the Event name column, ensure that you entered the name of the event or the case type such as Admission, Program referral, or Visit (new field in version 8.1).
   2. In the Work class column, ensure that you entered the class name that you defined in your implementation layer.
   3. In the Display date column, enter the date for the events that will appear on the timeline.
2. Based on your data model, to update the EventDetails data transform, complete these steps:
   1. In the header of Dev Studio, enter and search for EventDetails.
   2. On the Data Transform page, review the properties in the Target column and the Source column and make the appropriate changes.
      For example: You might use the Patient property instead of the Primary.pyCustomer property.
   3. Save your changes.
3. Based on your data model, to update the CareEventCMF2 data flow, complete these steps:
   1. In the header of Dev Studio, enter and search for CareEventCMF2.
   2. On the Data flow page, click the Event Summary shape, review the properties in the Source column, and make the appropriate changes.
   3. Click Submit to save your changes.
4. In the header of Dev Studio, enter and search for CMAUpgradeTimeLineUtility74to81.
5. In the Activity row, click CMAUpgradeTimeLineUtility74to81 in the PegaHC-Care-Work-class.
6. Click ActionsRun.
7. In the Run window, click Run.

Verifying access to previous care events on the patient timeline

If you are updating from version 7.4 or earlier versions, verify that you can view the timeline care events that were created before you updated the application.

1. In the header of Dev Studio, click Launch web interfaceCM Care Manager.
2. In the left navigation pane, click Patients.
3. Click a link that corresponds to the patient whose timeline you want to display.
4. In the Patient 360 profile, click the History tab.
5. In the Patient timeline section, click the arrow to the right of the Care menu.
6. Select the check boxes that correspond to the events that you want to display.
7. If you are unable to resolve the situation, go to My Support Portal to request appropriate assistance.

Modifying the skin name

If you are updating from a version prior to version 7.4, you need to modify the skin name so that the application uses the most recent skin. By using the CMA skin, the application can access the latest changes that have been made to the user interface.

1. Log in to the application by using the administrative credentials that you previously established.
2. In the header of Dev Studio, click ApplicationSkin.
3. Click the Inheritance tab.
4. Click Check out and select a ruleset.
5. In the list that is in the Skin inheritance section, enter and select CMA.
6. Click Save.
7. Check in the rule.

Updating existing Intervention Logic template flows

Pega Care Management version 7.4 replaced the AvailableForInterventionLogic property with the pyCategory property, which affected the Intervention Logic template flows. If you are updating from a version prior to version 7.4, you must run the UpgradeCustomFieldsForInterventionLogic rule to modify your existing Intervention Logic template flows.

1. In the header of Dev Studio, search for and select UpgradeCustomFieldsForInterventionLogic.
2. On the Activity: UpgradeCustomFieldsForInteventionLogic page, click ActionRun.
3. In the Run window, click Run.

Verifying the existing flows in an Intervention Logic template

If you followed the steps in the Updating existing Intervention Logic template flows procedure because you are updating from a version prior to version 7.4, verify that the Intervention Logic template flows are available.

1. In the header of Dev Studio, click Launch web interfaceCM Business Analyst.
2. Click New and then click Intervention Logic.
3. Click the Flows field to view a list of the updated flows.
4. If the list of flows does not appear, follow these steps:
   1. Use the Log Files tool to review and correct any errors or warnings that occurred.
   2. If you are unable to resolve the situation, go to My Support Portal to request assistance.

Updating your class tables

If you are updating from a version prior to version 7.4, you must update your class tables because the table mappings for classes changed in Pega Care Management version 7.4.

The following classes have been updated:

• PegaHC-Data-PatientIdentifier
• PegaHC-Data-Diagnosis-DiagnosisCodeType
• PegaHC-Data-PriorAuthCodes
• History-PegaHC-Data-MemberNotesP
• RULE-OBJ-CORR-CM

Export the instance. For information, see Product rules.

Verifying the update of class tables

If you followed the steps in the Updating your class tables procedure because you are updating from a version prior to version 7.4, verify the update of class tables that occurred in the Pega Care Management version 7.4 update.

1. In the header of Dev Studio, search for and open each of the following class instances:
   • PegaHC-Data-PatientIdentifier
   • PegaHC-Data-Diagnosis-DiagnosisCodeType
   • PegaHC-Data-PriorAuthCodes
   • History-PegaHC-Data-MemberNotesP
   • RULE-OBJ-CORR-CM
2. If the records do not appear:
   1. Use the Log Files tool to review and correct any errors or warnings that occurred.
   2. If you are unable to resolve the situation, go to My Support Portal to request assistance.

Moving data for existing care programs to a new class

Pega Care Management has a new data class, PegaHC-Data-Program, that contains the care program values. If you are updating from a version prior to version 7.4, you must move the data for existing care programs from the PegaCare-CarePlan rule to the PegaHC-Data-Program class. To do this, run the UpgradePrograms rule that is provided when you import the application bundle.

1. In the header of Dev Studio, search for and open the UpgradePrograms rule in the PegaClinical ruleset.
2. Click ActionRun .
3. In the Run window, click Run.

Verifying the care program data in the PegaHC-Data-Program class

If you followed the steps in the Moving data for existing care programs to a new class procedure because you are updating from a version prior to version 7.4, verify the care program data to ensure that it is stored in the new PegaHC-Data-Program class.

1. In the header of Dev Studio, click Launch web interfaceCM Business Analyst.
2. In the CM Business Analyst portal, click New and then click Program.
3. To see the list of programs, click the Programs link on the header.
4. If the records do not appear:
   1. Use the Log Files tool to review and correct any errors or warnings that occurred.
   2. If you are unable to resolve the situation, go to My Support Portal to request assistance.

Moving lab and measurement data to the observation class

If you are updating from a version prior to version 7.4, you must complete this procedure. Previously, Pega Care Management version 7.21 stored lab and measurement records in the PegaHC-Data-LabResults and PegaHC-Data-Measurement classes. Pega Care Management now supports Fast Healthcare Interoperability (FHIR) APIs. This means that the Logical Observation Identifiers, Names, and Codes (LOINC), which is a universal standard, is used to store the lab and measurement records in the PegaHC-Data-Observation class.

The FHIR standard identifies medical laboratory observations, nursing diagnosis, nursing interventions, outcomes classification, and patient care data sets. By moving the data to this class, you can electronically gather and exchange clinical results such as laboratory tests, clinical observations, outcomes management, and research results.

To move the existing records from the PegaHC-Data-LabResults and PegaHC-Data-Measurement classes to the PegaHC-Data-Observation class, perform the following steps to run the MoveVitalAndLabToObservtions rule. This rule is provided when you import the application bundle.

1. In the header of Dev Studio, search for and open the GetVitalLoincCode decision table.
2. To save this rule to the ruleset that corresponds to your implementation layer, click Save as and complete the form. For additional information, see About Decision tables.
3. On the Decision Table: page, review the vitals, such as height and weight, which you captured in your application.
   1. If a vital sign is not listed in the table, you need to add it. For additional information, see About Decision tables.
   2. To find the corresponding LOINC code, on the Patient 360, click the Clinical tab. In the All list, select Vital Signs.
   3. Search for the vital sign to which you are mapping. The LOINC code is displayed next to the name of the vital sign.
4. Save and check in the rule.
5. In the header of Dev Studio, search for and open the GetLoincCode decision table.
6. To save this rule to the ruleset that corresponds to your implementation layer, click Save as and complete the form.
7. On the Decision Table page, review the laboratory results such as Albumin or Alkaline, which you captured in your application.
   1. If a laboratory result is not listed in the table, you need to add it. For additional information, see About Decision tables.
   2. To find the corresponding LOINC code, on the Patient 360, click the Clinical tab. In the All list, select Laboratory.

   Search for the laboratory result to which you are mapping. The LOINC code is displayed next to the name of the laboratory result.

8. Save and check in the rule.
9. Search for and open the MoveVitalAndLabToObservations rule in the PegaHC ruleset.
10. Click Action > Run.
11. In the Run window, click Run.
    A window displays a success message. To test the results, see Verifying the records in the PegaHC-Data-Observation class.

Verifying the lab and measurement data in the PegaHC-Data-Observation class

If you followed the steps in theMoving data for existing care programs to a new class because you are updating from a version prior to version 7.4, perform this task to ensure that the lab and measurement data was moved.

1. In the header of Dev Studio, click LaunchCM Care Manager.
2. In the CM Care Manager Portal, search for a patient that you know has lab or measurement records, and open the patient profile.
3. Click the Clinical tab.
4. To display lab and measurement records, select All from the list in the top section.
5. Click on a lab or measurement record to display the data.
6. If the records do not appear, follow these steps:
   1. Use the Log Files tool to review and correct any errors or warnings that occurred.
   2. If you are unable to resolve the situation, go to My Support Portal to request assistance.