Automated Follow Up Actions
Revenue Cycle Transformation
- Capability status
- To be confirmed with PRN
- Transformation phase
- To be confirmed with PRN
- Effort
- To be confirmed with PRN
Current State / What We Learned
Observed today, as captured in the corrected assessment.
In follow up routing rules there are not any “when due” rules defined. (screenshot provided below)
Desired Future State
The target way of working PRN and Raintree are aiming for.
Defining rules for some of the common actions taken by a team member can set these as an automated action, which can free up time for a real person to complete more complex claim follow up activities.
Requirement / Gap
These are not currently in use, but could aid the team.
Raintree Recommended Path
- There is an attachment below that shows the process in a detailed recording: https://drive.google.com/file/d/1GfMiEsw7YKsc8hw2IAlipBfzMBlj6Hhr/view?usp=drive_link
- The suggestion would be to begin with some of the straightforward follow up actions like a sending of medical records and identify when the team is taking this action consistently - Which payors is that done for? What ANSI reason code does that payor process with?
- Once these questions are clearly known a routing rule can be defined to take action automatically on behalf of the team. Below in the workflow to define the rules section, we will see an example for an insurance of Aetna and reason code 252 defined to run an automatic action of “medical records sending”.
Dependencies / Considerations
These would be sent out via fax if possible, so may require a build up of fax numbers for the applicable insurance companies.
Outstanding Questions / Decisions
Not applicable
Evidence


Supporting screenshots from the corrected Detailed Transformation Assessment.
Source
Detailed Transformation Assessment (Corrected)Related opportunities
Related by workstream and subject matter. These are not stated dependencies unless the assessment says so.

