Skip to main content

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

Step 8: Managing code groups

Updated on September 18, 2020

To configure a custom code set, you must create an open ruleset and create or modify the rules listed in the following table.

  1. If you have imported the Pega Foundation for Healthcare demo application and sample operators as part of installation, log in to the application as Administrator@PegaHealthCodes using the password that you specified when you enabled this operator; to enable Pega-provided operators, see Enabling operators.

    Otherwise, complete the following steps to create a new operator ID:

    1. Log in to Dev Studio by using the operator ID [email protected] and the password that you specified for that operator.
    2. Save a copy of the existing [email protected] operator, and give it a name that identifies it as an code management administrator operator.
    3. Add PegaHealth:Administrators access group to the new operator record. Click the radio button to the left of the access group to select it as the default access group.
    4. Save the new operator record.
    5. Log in as the new operator that you created.
  2. Create a new rule set, for example: MyCodeGroups version 01-01-01.
  3. Add MyCodeGroups ruleset to the PegaHealthCodes application stack
  4. Select Configure > Healthcare > Configuration to navigate to the landing page.
  5. Select MyCodeGroups ruleset and its version in the Code Group Settings and click Save.

For additional information, see the Managing Code Groups in the Foundation application guide in the Pega Foundation for Healthcare application. The Application guide can be referenced from Records > Application Guide > Managing Code Groups in the Foundation.

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