Skip to main content


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

Prerequisites

Updated on January 26, 2021

Before you begin, ensure that you complete the required items.

Pega Product Composer for Healthcare Pega Product Composer for Healthcare Pega Product Composer for Healthcare Pega Product Composer for Healthcare Pega Product Composer for Healthcare Pega Product Composer for Healthcare Pega Product Composer for Healthcare Pega Product Composer for Healthcare

Steps for each of these prerequisites are described in the sections that follow.

  • Ensure that the default encoding of the application server is UTF-8, which is required for proper SBC PDF document generation.
    Note: System administrators can provide information to complete this prerequisite.
  • Have the administrator enable the SBC configuration
  • Add the Document management portal name to your access group
  • Initialize the company name and logo
  • Upload a file containing your company logo
  • Optional: Change the binary rule for two default company logos
  • Add the document approval privilege to the role in your access group
  • Enable the deletion option for a generated SBC document from products and plans
  • Delegate rules for modification of SBC configuration settings
  • Modify the settings for SBC
  • Optional: View delegated rules for reference

Steps for these two prerequisites are described in the referenced sections.

Note: SBC documents are not available for product templates. Only products and plans allow the generation of the SBC document.

  • Ensure that you have created the products from which you generate the SBC. To create a product, see Configuring a product.
  • Ensure that you have created the plans from which you want to generate the SBC. To create a plan, see Configuring a plan.

Enabling SBC operation

Enable the SBC operation on the configuration page. Only administrators can set the parameter for enabling or disabling the creation of the SBC templates and documents.

If you do not enable SBC operation:

  • Steps 6 and 7 are not available in the product and plan wizards.
  • You can review the SBC data, but you are not able to update it.
  • If you are copying a template, creating a new version of a template, or creating a plan from a product, the SBC data is copied to the new entity.
  1. In Dev Studio click ConfigureProduct composer system.
  2. Click the Flow settings tab and scroll to the SBC Configuration section.
  3. Click On.
    When you configure the SBC setting to On:
    • Steps 6 (Select SBC Metadata) and 7 (Edit SBC document) are present in the product and plan wizards
      Steps in the product and plan wizards
    • At the end of step 7, you can click Finish.
  4. Click ActionsSave as system configuration.

Adding the Document management portal name to your access group

Unless you are installing Pega Product Composer for Healthcare for the first time, you need to add the new DocMgmt portal that was introduced in this release to all applicable access groups so that they can perform the tasks that are related to the SBC template.

The following table includes tasks for existing access groups and new access groups:
To add the new portal to existing access groups
  1. In the navigation pane of Dev Studio, click RecordsSecurityAccess groups.
  2. On the Access groups page, search for your access groups.
  3. For each existing access group:
    1. Click the name of the access group.
    2. On the Edit Access Group page, in the Available portals section, click the Add portal link.
    3. From the auto-complete list, click and select DocMgmt.
    4. Click Save.
    5. Repeat these steps for each access group.
For access to the new portal for new access groups
  1. Copy the following two new access groups to your implementation layer and rename them accordingly:
    • HC-USA-PCS:DocTemplateManager

      Document template manager access group

    • HC-USA-PCS:DocTemplateUser

      Document template user access group

  2. Ensure that these access groups point to your application.

Initializing your company name or logo

In the Plan overview tab of the SBC document, you can choose to display your company name or company logo. You need to modify the InitializeCompanyDetailsEXT data transform.

Before you begin: Review the content of the original InitializeCompanyDetails data transform so that you are familiar with the properties.
  1. In the Dev Studio search box, enter InitializeCompanyDetailsEXT, and then press Enter.
  2. Click the Data Transform rule.
  3. Save the InitializeCompanyDetailsEXT data transform in your application ruleset.
  4. Based on whether you want to display the company name or the logo, perform these steps:
    1. Set .DisplayCompanyName to either true or false (default value false).
    2. Set .DisplayCompanyLogo to either true or false (default value true).
    If you set .DisplayCompanyName to true, enter your company name in the .CompanyName target field. If you set .DisplayCompanyLogo to true, upload your logo. For more information, see Uploading and displaying your company logo, described in this section.
  5. Check in the rule, and then click Save.

Uploading and displaying your company logo

If you choose to display your company logo and not your company name, you need to upload the logo.

Note: The SBC default company logo image is sourced from the webwb/SBCDefaultCompanyLogo.png binary file rule.
Before you begin: Ensure that you have performed the steps in Initializing your company name or logo.
  1. In the Dev Studio search box, enter SBCDefaultCompanyLogo, and then press Enter.
  2. Click the Binary File rule.
  3. Save the binary file rule in the appropriate ruleset of your implementation application.
  4. In the binary file rule that you just saved, click Upload file.
  5. Choose an image from the local file system, upload it, and save it to your implementation layer.
    The logo displays in the Plan overview tab of the SBC template. It is the default logo for all templates.
  6. To make the changes effective for the current operator, in the web browser, clear the cache.

Optional: Changing the binary rule for two default company logos

You can upload a different logo if you do not want to always use the default logo. For example, an organization might have two legal entities. One handles the PPO and the other handles the HMO. The PPO entity might use the default logo for their templates, but the HMO entity might want to use a different default logo.

Before you begin: Review the content of the original InitializeCompanyDetails data transform so that you are familiar with the properties.
  1. In the Dev Studio search box, enter InitializeCompanyDetailsEXT, and then press Enter.
  2. Click the Data Transform rule.
  3. Save the InitializeCompanyDetailsEXT data transform in your application ruleset.
  4. Set the values for the following properties:
    • CompanyLogoPath (Default value: webwb/SBCDefaultCompanyLogo.png
    • DefaultCompanyLogoApp (Default value: webwb)
    • DefaultCompanyLogoFileName (Default value: SBCDefaultCompanyLogo)
    • DefaultCompanyLogoFileType (Default value: png)
  5. Click Save.

Adding the approval privilege to the role in your access group

Unless you are installing Pega Product Composer for Healthcare for the first time, you need to add the new ApproveDocTemplate privilege that was introduced in this release to all applicable access groups who need to approve SBC templates.

Create a new role or update any of the existing applicable access role to include the ApproveDocTemplate privilege. You can do one of the following:

  • Create a new role - create a new role and add the dependency to the out-of-the-box HC_USA_Product_Composer:DocTemplateApproval access role.
  • Update an existing access role - open the applicable access role and add the ApproveDocTemplate privilege.
  1. In the navigation pane of Dev Studio, click RecordsSecurityAccess groups.
  2. On the Access groups page, search for your access groups.
  3. For each existing access group for which the document approval is applicable:
    1. Click the name of the access group.
    2. On the Edit Access Group page, in the Available roles section, click the Add role link.
    3. From the auto-complete list, click and select the access role that has been designated for SBC template approval.
    4. Click Save.
    5. Repeat these steps for each access group.

Enabling the deletion option for a generated SBC document from products and plans

Unless you are installing Pega Product Composer for Healthcare for the first time, you need to add the new DeleteAnySBCDocument privilege that was introduced in this release to all applicable access groups so that they can delete an SBC PDF document from a product or plan.

You can create a new role or update any of the existing applicable access role to include the DeleteAnySBCDocument privilege. You can do one of the following:

  • Create a new role - create a new role and add the dependency to the out-of-the-box HC_USA_Product_Composer:DeleteAnySBCDocument access role
  • Update an existing access role - open the applicable access role and add the DeleteAnySBCDocument privilege
  1. In the navigation pane of Dev Studio, click RecordsSecurityAccess groups.
  2. On the Access groups page, search for your access groups.
  3. For each existing access group for which the document deletion is applicable:
    1. Click the name of the access group.
    2. On the Edit Access Group page, in the Available roles section, click the Add role link.
    3. From the auto-complete list, click and select the access role that has been designated for deleting an SBC document from the product or plan.
    4. Click Save.
    5. Repeat these steps for each access group.

Tags

Pega Product Composer for Healthcare 8.5

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

Visit the Support Center

Did you find this content helpful?

Yes
No

Want to help us improve this content?
Suggest an edit

We'd prefer it if you saw us at our best.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us