Skip to main content


         This documentation site is for previous versions. Visit our new documentation site for current releases.      
 

Moving lab and measurement data to the observation class

Updated on December 6, 2021

If you are updating from a version prior to 7.4, you must complete this procedure. Previously, Pega Care Management 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.

Pega Care Management Update Guide
Before you begin: Ensure that you have already imported the Pega Care Management application file.

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.
  • Previous topic Verifying the care program data in the PegaHC-Data-Program class
  • Next topic Verifying the lab and measurement data in the PegaHC-Data-Observation class

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us