Skip to main content

Suppression

Suggest edit
Updated on August 31, 2021

Prior to the execution of the NetworX adjudication module, claims may first pass through third party clinical editing and/or editing/auditing native to the SCE. If specific claim lines are denied due to an editing process, those identified lines are automatically suppressed, or withheld from inclusion in the API call to NetworX.

The table below represents 3 scenarios in which claim lines are suppressed following claim line denial recommendations: (a) a single line claim with single claim line denial, (b) a multiple line claim, with all lines denied, and (c) a multiple line claim with multiple, but not all lines denied.

In these scenarios, the denied claim lines are suppressed and withheld from the request XML file transferred to NetworX, and upon the return of pricing data from the NetworX XML response file, all claim lines are merged back together before continuing in the adjudication process.

The denial recommendations are identified with discrete event codes in the system, and the presence of those event codes on the suppression configuration table enables the line to be denied. This model allows you to add other event codes to the suppression.

ScenarioAction
Single line claim - line deniedSuppress entire claim
Multiple line claim – all lines deniedSuppress entire claim
Multiple line claim – all lines NOT deniedSuppress denied claim lines – do not send suppressed lines to NetworX

NetworX claim line suppression rules are configured in the SANPClaimLineSuppression decision table shown below.

Note: this decision table can also support the configuration of other attributes used for suppression, such as claim types (institutional vs. professional), action codes, NPI, provider taxonomy, and the presence/absence of rate sheets.

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