Extending the Pega Product Composer for Healthcare application
Based on your organization's needs, you can extend application-provided features such
as metadata, entity keys, networks, and benefit mapping. You can also extend data validation
activity rules and union data. A benefit, the basic building block in Pega Product Composer for Healthcare, is made up
of benefit definition options. You can dynamically configure additional benefit definition
options and configure the code groups needed for the benefit mapping definition. You can easily extend Pega Product Composer for Healthcare entity attributes or
metadata. For example, you can add or remove a line of business. The following list shows the metadata fields that you can extend and the name of the
corresponding class: Sometimes, you must change a key of a Pega Product Composer for Healthcare class to
meet the business need of a client. For example, you might want multiple instances of the same
product in different lines of business. In this case, you cannot use the Pega-provided keys. You
must change the key that represents the line of business. Because much of the provider network information is stored in third-party systems,
client teams configure new networks when needed or extend existing ones to drive the sales and
servicing of their plans. Then they associate the networks with the plans. Use the listed extension activity rules in the table below to add validation fields
that you need for the PCS Import flows. The main activity rule calls the extension activity rule
at run time. For additional information about activities, see Activities. In Pega Product Composer for Healthcare, you might want to add other fields that
describe basic information to entities to meet your business needs. For example, you can add
the Purpose for creation field to the benefit entity to provide more
information about why you are configuring the benefit.
Pega Product Composer for Healthcare provides some fields, called user-defined fields, where you
can customize the values for the options. Configuring benefit mapping
Extending entity metadata
Changing the key of an entity
Extending a network
Extending data validation activity rules for PCS Import
Extension activity rule Call from this activity rule Description ValidatePrimaryExcelFieldsEXT ValidatePrimaryExcelField Use this activity rule to validate the main
properties that are required for the PCS import flows. ValidateDatesAndStatusEXT ValidateDatesAndStatus Use this activity rule to validate the
overlapping dates of the consumed entities, for example, a benefit being added
to a benefit set. If there is not at least one day overlapping between the
benefit and the benefit set, a validation error occurs and the benefit is not
accepted. This activity rule also checks for rejected or retired statuses of
entities. ConvertingDatesForPolicyTermEXT ConvertingDatesForPolicyTerm Use this activity rule to validate the dates
that you entered for policy terms in the PCS import flows. GroupPolicyListEXT GroupPolicyList Use this activity rule to group all the rows
that are related to one policy into a single list. BenefitDataLoadValidationsWrapperEXT BenefitDataLoadValidationsWrapper Use this activity rulactivity rule to validate all the
business functionality that is related to the PCS import flows for benefits and
call all post-activities from the main flows. AutoDataLoadGrpValidationEXT AutoDataLoadGrpValidation Use this activity activity rule to validate all the
business functionality that is related to the PCS import flows for groupers and
call all post-activities from the main flows. ADLBenefitSetValidationWrapperEXT ADLBenefitSetValidationWrapper Use this activity rule to validate all the
business functionality that is related to the PCS import flows for benefit sets
and call all post-activities from the main flows. NetworkValidationsWrapperEXT NetworkValidationsWrapper Use this o validate allactivity rule business functionality
related to the PCS import flows for networks and call all post-activities from
the main flows. PolicyTermsValidationsWrapperEXT PolicyTermsValidationsWrapper Use this activity rule to validate all the
business functionality that is related to the PCS import flows for policy terms
and call all post-activities from the main flows. Adding new properties to entities
Entity Class Section Benefit Rule-HC-PCS-Benefit BenefitClientConfiguration Policy Term Rule-HC-Term PolicyTClientConfiguration Policy Rule-HC-Policy PolicyClientConfiguration Grouper Rule-HC-PCS-Grouper GrouperClientConfiguration Benefit set Rule-HC-PCS-BenefitSet BenefitSetClientConfiguration Network Rule-HC-PCS-Network NetworkClientConfiguration Product template Rule-HC-PCS-Product TProductClientConfiguration Product Rule-HC-PCS-Product PProductClientConfiguration Plan PegaPCS-Data-Plan ContractClientConfiguration Plan bundle PegaPCS-Data-Bundle BundleClientConfiguration Extending user-defined fields
Previous topic Extracting Pega Product Composer for Healthcare data and generating reports Next topic Extending union data