As part of the version 7.4 update, perform these tasks.

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.

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.

You need to update your care team data because the care team model was changed during this release. List-based properties were replaced with scalar property instances of the PegaHCCMF-Data-Party-Contact and the Link-Contact classes for care team members.

The following list-based properties in the Report definition: ContactsByCategory of the PegaHCCMF-Data-Party-Contact class are no longer used:

• .Role(1).RoleDescription
• .Address(1).PhoneNumber
• .Address(1).Fax
• .Address(1).Email
• .Address(1).PhoneNumberExtension

These new scalar properties replace the properties in the above list:

• .CareTeamPrimaryRoleDescription
• .CareTeamPrimaryPhoneNumber
• .CareTeamPrimaryFax
• .CareTeamPrimaryEmail
• .CareTeamPrimaryPhoneNumberExtension

Follow these steps to update your care team:

1. In the header of Dev Studio, search for and select the RefactorCareTeamMemberDetails rule.
2. Click ActionsRun.
3. In the Run window, click Run.

You can verify that properties in the care team data are now scalar properties.

1. In the header of Dev Studio, click Launch web interfaceCM Care Manager.
2. In the left panel of the CM Care Manager portal, click Patients.
3. Search and open a patient by clicking on the Patient ID.
4. Click ActionsPrint/Download.
5. In the Show print options dialog box, select the Care team details check box and click Print.
6. If the records do not appear on the Care Team details page:
   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 Portalto request assistance.

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

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.

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.

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.

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.

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.