Skip to main content

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

Configuring the orchestration selection table

Updated on April 26, 2021

The orchestration configuration table, Derive orchestration, can be found under Orchestration configuration in the Orchestration section of the Delegated rules menu in the portal. To view or update this table, select the gear icon.

This will then present the Derive orchestration decision table which can be modified and saved utilizing the standard Pega development process. This table can be extended by clients to add new fields, but is delivered with the following columns:

Manual adjustmentThis identified if the claim has been manually or mass adjusted based on a flag populated during the manual or mass adjustment process
Claim frequency typeThe frequency code submitted on the claim. This may also be the last character of the bill type. For example: 1 (admit through discharge), 7 (replacement of prior claim)
Claim transaction typeThe type of transaction being submitted. For example: CH (chargeable), RP (reporting), 31 (Medicaid reclamation/subrogation)
Claim payer IDThe payer ID submitted on the claim
Claim form typeThe type of claim being submitted. For example: P (professional), I (institutional), D (dental).
ReturnThe name of the orchestration being selected based upon the values in the table

The Smart Claims Engine provides an error handling orchestration if no orchestration is found through the selection. This sets the event code SGB-0048 – Orchestration not found. This event code will also set if the name of the orchestration returned by the decision table is not found in the configured list of orchestrations.

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