RPA Work Smarter, Not Harder
Robotic Process Automation (RPA) - Part 2
RPA Part 2
Explores some of the benefits and pitfalls to be aware of when considering
installing RPA automation.
It is important to keep in mind that RPA by its nature, isn't transforming systems & processes, it is only automating them. Revenue cycle processes should be reviewed closely before installing RPA automation. Otherwise, the risk exists of simply automating bad processes.
Community General Hospital researched ways to streamline manual
actions to decrease response times to patients, vendors, and employees.
Besides improving patient experiences, they wanted to maximize productivity
so their revenue cycle teams could focus on more patient-centric activities while providing a measure of cost reduction.
Patient-centered focus: Direct patient contact was increased due to a decrease in paperwork.
Increased accuracy: Bot error rates are extremely low.
Increased productivity: Tedious, time-consuming manual tasks can be performed anytime.
Reduced costs: Processing became more efficient and faster vs previous manual processing.
Improved process visibility: Tasks performed by software are easily recorded for auditing & reporting.
Regulatory compliance standards met: Bots provide an audit trail history for each step.
Employ flexibility in staffing: Some staff were re-purposed into other roles, no employees lost.
Improved employee morale & experience: Employee workload and stress levels decreased.
No disruption of existing systems: Bots work within any hospital system.
Improved, expedited data analysis
RPA implementations based on alreadyflawed processes will only create further problems. Using unattended RPA to remedy poor processes does not improve the process, it only results in errors and bottlenecks, creating new problems.
Some RPA problems stem from unrealistic expectations. Customers and vendors risk over-hyping the technology. While it is a powerful tool to digitally convert key processes, RPA won't automatically transform the organization or revenue cycle deficiencies.
RPA can eliminate some positions. Only 11% of RPA impacted employees were actually laid off (usually in larger, urban hospitals). The vast majority of staff were re-trained and re-purposed.
Even minor changes in working RPA applications can produce difficulties. New regulations from government/payers requiring minor changes can cost months of work to correct the software in a bot that’s nearly complete.
Positive economic outcomes are not always guaranteed. It may be possible to automate 30% of tasks for the majority of occupations, but that will not necessarily translate into a 30% cost reduction.
Reclaiming Time Through Automation
Guidelines for preserving PPEs can be found at:
CDC Guidelines for Opening Up America Again are found at: