Skip to main content

ClaimsXten response display

Suggest edit
Updated on August 31, 2021

The SCE provides information on the ClaimsXten responses at both the claim and the claim line levels.

Claim level

The response from ClaimsXten is displayed at the claim (case) level. Under the Actions menu, select View claim history, then select the ClaimsXten tab on the pop up.

The SCE captures and displays both the XML request to (the inbound file to ClaimsXten) and the XML response from (the outbound file to SCE) ClaimsXten; this is captured each time the claim is submitted to ClaimsXten.

The Claim tab on the pop up displays an action codes mapped to the claim based on the ClaimsXten response under the Action codes section:

You can view errors returned from ClaimsXten by selecting View all in the Payment information slot on the right side of the claim user interface, clicking the Info from external system hyperlink, and selecting the ClaimsXten tab:

The same section of the claim user interface captures information related to payment calculations – each Case ID may be expanded to view the details of the ClaimsXten recommendation:

Claim line level

ClaimsXten responses are also displayed at the claim line level. To review the claim line level data, scroll to the Claim lines slot on the user interface and click on the hyperlinked claim line number. The claim line details are displayed. In the Execution result slot, click the Info from external system hyperlink, and select the ClaimsXten tab.

Expanding a row displays additional details.

The screenshot below shows an example of ClaimsXten response received with a certainty of Apply and claim line action of Add, resulting in the addition of a new claim line.

SCE also displays errors at the claim line level:

If the ClaimsXten response is mapped to an event code via the CXTResponseToSCECodes decision table, this will also be assigned to the claim and visible on the UX.

Did you find this content helpful? YesNo

Have a question? Get answers now.

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

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