Payer status rules (New)
Menu location: Maintenance menu, Manage Claim Assignments, Payer Status Rules (New)
Overview
Manage Claim Assignments (MCA) is a workflow tool. You can assign released electronic claims to users based on payer status information errors using the legacy Payer Status Rules or the new Payer Status Rules. Use the new Payer Status Rules feature to specify what type of claim status you want to track and assign to a user for review or further action. For example, you may want to assign batch-level claim rejections for Payer A and specific claim-level rejections for all payers. Unlike the legacy rules, the new rules make it easier to create claim assignments for multiple payers and multiple codes. The system uses the new Payer Status Rules feature with your user profiles to automatically assign claims. Plus, only this version of Payer Status Rules supports assignment of payer-specific codes received through the Status Amplifier add-on.
Users can open the claims in their work queue directly from the My Claims panel of the Home page by clicking on Claims assigned to me (rel). These claims automatically open to the History tab. Users can process assigned claims or manually reassign them to other users. (See working with assigned claims for details.) If a claim is assigned to a department, when anyone from that department processes the assignment or manually assigns the claim to another person, the claim is removed from the work queues of all users in the department.
This payer configuration method must be enabled for your site before the system makes user assignments based on your new payer status rules and user profiles. Be sure to contact customer support to enable the MCA Payer Config Method when you are ready to start using these assignments.
All code types list
| Field | Description |
|---|---|
| Status Codes | This code set is the four-digit status code set assigned to released claims by the clearinghouse or by the payer. Examples include 1001 (CLS returned claim) and 7350 (payer rejected claim). |
| 277 Codes | Assign claims based on available 277 category
codes, the two-digit code that indicates whether a claim is acknowledged,
forwarded, finalized, pending, or whether there was an error or request
for additional information. This status depends on the payer's ability
to send reliable 277 claim status transactions. |
| Recon Level | The Recon Level codes are part of the legacy Reconciliation Manager Dashboard. They indicate the automatic movement of your released claims through clearinghouse and payer processing. You may continue to see these codes post to your released claims in the History tab when you switch to using the new Reconciliation Manager Dashboard for payers enabled in Payer Reconciliation Profile Maintenance. This posting continues to support other internal system functionality, but it is no longer applicable since you can use the new dashboard to target a set of claims based on the processing milestone and status. If Reconciliation Manager is not enabled at your site, this option is not shown on your screen. |
| Remit Codes | Remit Codes are the reasons for denial: Adjustment codes and remark codes returned in 835 remit files. |
| Payer Specific Codes | Displays the codes returned by payers through the Status Amplifier add-on option that checks payer portals for status information. |
| Medicare Reason Codes | Medicare Reason Codes are returned by Medicare as reasons for claim denial. The drop down list contains all of the Medicare Error codes with beginnings of their descriptions. At the simplest level, you can create a single rule for All unassigned Denied and another for All unassigned Return to Provider. These two rules will put all denied and RTP claims in the work queue of those users attached to the rule. If you need to route claims with specific errors to a specialist user, create rules for each of those errors. |
Follow these steps to create a new Payer Status Rule:
- Select a code set from the All Code Types drop down list, if desired.
- Click on the desired code to expand the row and activate the payer selection criteria.
- Choose the set of payers you want for claim assignments. Payers must appear in the Payers Selected list to be active for the rule.
- Click the Save button. The system adds the new rule to the Assigned list, and there is a green dot to indicate an existing rule for that code.
To change the payer set for a rule, simply add or delete payers from an Assigned code, and then click the Save button. Use the field with the magnifying glass icon to filter the payer list. For example, type "blue" to list any entry that includes the word "blue."
To delete a rule, select the status code. Remove all the active Payers Selected from the list, and then click the Save button. The system will switch the code from Assigned status to Unassigned status, and the system will no longer make claim assignments based on this code.
Shortcut: Create additional payer status rules
Once you set up a rule for a status code with a set of payers, there is a shortcut to add the same set of payers to another code:
- Locate the rule you want to use as a guideline.
- Click on the status code to expand the row and display the payer selection.
- Click the Copy button to duplicate the list of Payers Selected.
- Locate the status code you want to set up.
- Click the Apply button for that code. The system pastes the list of payers.
You can use the Copy and Apply functions even if the code already has a set list of active payers. The Apply function will overwrite any active previous payer list.
- You need the Workflow: Manage Assignments group function to access and use this feature. This is the same function required to use the standard legacy feature.
- You will also need to set up user profiles to use the new Payer Status Rule assignments.
Reprocess payer status rules
When you update the code set you want to track, you may want to run the Reprocess Payer Status task to force the system to update claim assignments. The system will update assignments for the claims you select. Reprocessing is limited to the past 30 days.