Search configuration and extension

Search configuration and extension

Description	Search configuration and extension
Version as of	8.5
Application	Pega Product Composer for Healthcare
Capability/Industry Area	Healthcare and Life Sciences

edit liked pages

Search in PCS

The Pega Product Composer for Healthcare application facilitates the rapid configuration of a healthcare plan because it has several supporting objects (case types) within the application that make up a health plan. These include benefits, benefit sets, grouper, networks, product templates, products, and plans.

Each of these case types has an out-of-the-box default search option. The search feature is completely configurable and requires no code changes for extension.

Smart Update, SBC Mass Generation, and the product and plan process flows are the primary PCS features that update the plan repository. All of these use the standard search feature to identify and select the products and plans to be updated.

Search configuration

As an end user or as an implementation consultant, there is an ongoing need to enhance the default search parameters that are available for each of the PCS objects.The search parameters for all the PCS objects are configured on the Search configuration settings tab of the Product Composer System Configuration page.

As illustrated in the figure above, each PCS object has its own search parameter list, which is configurable.

Extending search parameters

You can extend the search parameters to meet your business needs, as shown in the following examples.

Updating the search parameter with an out-of-the box PCS property

To include the overall plan copay as a search parameter for plans, product templates, or products, follow these steps:

1. Identify the property that represents copayment, for example, .Product.BenefitSetTree.ChildItem.CostShares.AmountValueSelected.
2. Add the property to the plan search fields on the Search configuration settings tab of the Product Composer System Configuration page.
3. Save the configuration page as a private edit or as system configuration.
4. Open the Plans landing page by clicking Plans in the left navigation pane. The new Copay field appears as part of the search.

For each object, you can display the search parameter as part of the default (commonly used) or advanced (less frequently used) search sections. When the page loads for the first time, the Advanced Search section is collapsed by default.

Updating the search parameter with a new property from the implementation layer

If you have added a property, for example, InternalRating to the Enter Details step of the plan wizard, you can use it as search criteria by updating the search parameters:

1. Identify the property that needs to be added to the plan search, for example, InternalRating.
2. Add the InternalRating property to the Plan search fields on the Search configuration settings tab of the Product Composer System Configuration page.
3. Save the configuration page as a private edit or as system configuration.
4. Open the Plans landing page by clicking Plans in the left navigation pane. The Internal rating field now appears as part of the search criteria.

Typically, generating a report or updating an application to include more search parameters requires elaborate collaboration with IT. But because of the configurable design of search in PCS, you have complete control over the search and can update the fields to customize the application to fit your needs.