Skip to main content

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

How values are populated in Pega Product Composer for Healthcare entity fields

Updated on April 12, 2021

A key feature of the Pega Product Composer for Healthcare application is its inheritance patterns. Inheritance describes how values for certain properties are shared within and across various entities.

Pega Product Composer for Healthcare

The application uses inheritance in entity creation and updates. For example, when you change a value for a parent entity, Product A, PCS automatically updates the value for the child entities, Plan A, Plan B, and so on, unless you have overridden the original value in the plan (the child entities), and therefore have broken the inheritance.

Although Pega Product Composer for Healthcare uses three different inheritance patterns, there are some exceptions throughout the processes. Some of the entity fields receive copied data instead of inherited data. The topics in this section describe when data is copied to fields versus when fields inherit data. Other sections describe the three inheritance patterns.

You can override inherited values. However, keeping the automatic inherited values saves you time when you have many updates, such as during portfolio renewal.

The following table shows the PCS items and the category that applies to each item:

CopyInheritance pattern 1Inheritance pattern 2

(Item is configured at the network level)

Inheritance pattern 3

(Item is configured at the benefit level)

Product template valuesX
Required and covered fieldsX
Benefit categoriesX
Lifetime maximumXX
Out-of-pocket maximumXX
Annual maximumXX

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. is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us