Skip to main content


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

About voiding or cancelling Medicaid Subrogation Demand claims

Updated on April 26, 2021

Based on the value in the Type of Bill field, Pega Smart Claims Engine for Healthcare voids or cancels Medicaid Subrogation Demand claims.

Frequency code = 7

  • If the frequency code of the Type of Bill value is 7, Pega Smart Claims Engine for Healthcare automatically voids or cancels the previously submitted Medicaid Subrogation Demand claim, and replaces it with a new claim. In the Claims History tab, you can see the link between a new Medicaid Subrogation Demand claim and the previously submitted claim.
  • If the status of the previously submitted Medicaid Subrogation Demand claim is not Resolved - Completed, Pega Smart Claims Engine for Healthcare changes the status to Resolved - Cancelled.
  • If the status of the previously submitted Medicaid Subrogation Demand claim is Resolved - Paid Status, Pega Smart Claims Engine for Healthcare changes the status to Resolved - Voided.
  • If Pega Smart Claims Engine for Healthcare cannot find the original Medicaid Subrogation Demand claim, it pends the current Reporting claim for user action.

Frequency code = 8

  • If the frequency code of the Type of Bill value is 8, Pega Smart Claims Engine for Healthcare automatically cancels or voids the original Medicaid Subrogation Demand claim.
  • If the status of the previously submitted Medicaid Subrogation Demand claim is not Resolved - Completed, Pega Smart Claims Engine for Healthcare changes the status to Resolved - Cancelled.
  • If the status of the previously submitted Medicaid Subrogation Demand claim is not Resolved - Paid, Pega Smart Claims Engine for Healthcare changes the status to Resolved - Voided.

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.

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

Close Deprecation Notice
Contact us