Extending and leveraging data extract report

From PegaWiki
Extending and leveraging data extract reports / This is the approved revision of this page, as well as being the most recent.
Jump to navigation Jump to search

Extending and leveraging data extract report

Description Extending and leveraging data extract reports
Version as of 8.7
Application Pega Product Composer for Healthcare
Capability/Industry Area Healthcare and Life Sciences

The benefit coding and QC teams need a 360-view across the product repository in order to review the configurations across multiple products and plans.

To serve such QA requirements, PCS provides data extract reports. These reports provide a quick view of all the products and plans configured in the system and can be a great tool for visual or automated QA across the product repository. They provide a single view of all the plans and benefits and the associated cost shares. The data output can be rendered in a Microsoft Excel spreadsheet or saved to a database. By using the built-in extensions, you can extend these reports to include client-implementation properties.

There are two types of reports:

  • High level - Summary report
  • Detailed - Cost share detail report

Detailed information about these reports can be found at https://community.pega.com/knowledgebase/articles/pega-product-composer-healthcare-implementation-guide/86/extracting-pega-product-composer-healthcare-data-and-generating-reports

Adding new properties

Out of the box reports only cover the properties that are shipped out with PCS. Any new properties added by the implementation team would not be included in these reports automatically. But these reports are configurable and can be easily extended to include the necessary implementation layer properties. Listed here are the rules which are shipped out of the box with PCS that facilitate the extension of the Extract reports. The summary report focuses on the overall metadata properties, which are associated with the high level plan description.

The cost share report focuses on the detailed cost shares associated with the benefits within each network in the plan. Depending on the type of property to be added (whether metadata or cost share), the corresponding report is to be extended using the rules below.

List of rules for Data Extract extensions

Before you begin

While the summary report is available as an excel attachment, the plan cost share report, given its complexity and the size of the data being reported, is only available as a data type of "Extract". You can see the output of these reports via Dev Studio --> Data types --> Extract --> records.

So any updates (new properties added) to this report, will also be displayed via the same output as above. For example, the client team has few properties that they would like to add to the Plan Cost share report. For any such properties, the ExtractPlanCostShareDetails_EXT activity should be used to populate the new properties to the correct clipboard page. This extension activity is called by the out of the box flow, while generating the report. So the implementation team only needs to add the necessary properties to this activity. The rest would be addressed by the application.

Cost share extract report output

Similarly the ExtractPlanSummary_Ext activity should be used to populate any metadata\high level plan properties that the implementation team wants to configure.


Having a clear understanding of the extension points for the summary and cost share reports, gives the implementation team the necessary tools to configure and extend these out of the box reports to include any new implementation layer properties.