Mass update (deprecated)
Use the Pega Product Composer for Healthcare Mass Updates wizard to make changes across multiple entities at one time instead of performing updates on individual entities. You can add, update, or remove new and existing benefits and groupers within a set of selected target benefit sets, product templates, products, and plans.
Review the information in this section to determine whether you want to perform a mass update or update entities individually. It describes how the mass update process handles inheritance and default benefits.
Inheritance
You can add or remove groupers and benefits or modify existing groupers and benefits
to change data such as cost shares, copayments, coinsurance, deductibles, and other
data, such as limits and authorization requirements. The data that you change for
the groupers and benefits is propagated to the targeted product templates, products,
or plans that you choose.
| Action | Result |
| Add groupers or benefits | The inheritance is maintained. For example, a new healthcare regulation requires the addition of the new healthcare benefit, Telemedicine, to all small group HMO and preferred provider organization (PPO) plans. Use the Mass Updates wizard to add the benefit to all the plans at one time. The benefit inherits the network cost shares. |
| Modify existing groupers or benefits | The inheritance from the parent entity is broken. Changes that you make when performing a mass update overwrite the data in the targets that you select. This feature does not maintain the existing data and creates a new version for the updated data. For example, if you change the copayment for the pediatric dental benefit from $10 to N/A for a plan during a mass update, the copayment is overwritten and has the value of N/A. There is no versioning that maintains the copayment of $10 prior to performing a mass update. In this case, the mass update process works successfully if you are using it to correct errors. However, if you need to maintain the data from different versions, do not use it. Instead, update the entitiesindividually. |
| Remove an existing benefit or grouper | The benefit or grouper is removed from the selected target benefit sets, product templates, products, and plans. |
Default benefits
In Pega Product Composer for Healthcare 8.3, the introduction of the default benefit in a benefit category affects the mass update results. The following table provides descriptions and examples.
| Action | Result |
| Add a benefit or grouper | The Mass Updates wizard automatically includes the benefit category that you specified during benefit configuration. |
| Remove a default benefit or grouper from a product template, product, or plan | The next benefit or grouper in the benefit category becomes the default. For example, if the magnetic resonance imaging (MRI) benefit is the default benefit for the Diagnostic services benefit category in a product template, and you remove it from the product template during a mass update, the computed axial tomography (CAT) scan, which is the next benefit in the benefit category, becomes the default benefit. |
| Update an existing benefit or grouper by disassociating it from a benefit category | If it is the only benefit category that is associated with that benefit, you must have another benefit category available. For example, if you disassociated the MRI benefit from Benefit Category A, you must add another benefit category, for example, Benefit Category B, during the mass update. Then the MRI benefit becomes the default benefit of Benefit Category B. |
Previous topic Troubleshooting Next topic Performing a mass update