The accounts receivable team maintains a tracker with the list of Denied Claims. The team regularly follows up with the Insurer and the Insured for relevant updates. Whenever there is an update in the Denial Claims list, the team logs in to the GMPS web application, searches for the account, and makes the necessary changes (add/ remove/ swap insurance, move patient balance, etc.). The process is performed whenever there is a change in AR, making it repetitive, error-prone, and time-consuming.
Nalashaa’s RPA team worked on building a robot to do the same work as the customer support team. The team divided the process into 2 parts.
The bot logs into the tracker and accesses the Denial Worklist containing the list of available batches and checks for action codes.
It then accesses the GPMS application and identifies the respective transaction by its Date of Service and the Due Amount as mentioned in the tracker.
Based on the code in the tracker, the bot processes one of the following 7 actions.
The bot checks for process validations at every stage and sends alerts for any exceptions.
Pre RPA | Post RPA | |
---|---|---|
FTE | 5 | 1 |
Number of transactions per day | 90 | 600 |
Time per transaction | 15 minutes | 3 minutes |
Accuracy | 77% | 98% |
To choose the right RPA support for your business, we would like to understand your needs better. The form below is a great way to start that!