April 2023 Newsletter

April showers bring May Flowers! And let us tell you, it is raining automation opportunities at CampTek Software! We've heard from so many of you wanting to try new products like Task Mining and Intelligent Document Understanding - the outreach is overwhelming... but you won't hear complaints from us. We're equally as excited to utilize these technologies to make your spring cleaning even more effective.

We even flew to Florida with our partner, Indico Data, to meet with a customer around the possibilities of Document Understanding and RPA!

Think about all the time you'll save this summer!

-The CampTek Team

Pictured below from left to right: Bob DiSciullo, VP of Sales, CampTek Software; Bobby Doyle, Sr. Strategic Account Executive, IndicoData; Peter Camp, CTO & Founder, CampTek Software; MaKayla Jennings, Solutions Specialist, IndicoData.

Welcome to CAMP a weekly podcast by CampTek Software where we'll cover all things automation and robotic process automation (RPA). You'll hear from various members of the CampTek team on topics such as Citizen Development, How to Prepare for a Scope Call, What RPA Can Mean for You, and so much more! Check out our first two episodes on YouTube, Linkedin, or Transistor!

Hear from our Senior Intelligent Automation Project Manager, Joyce Zhang, and Director of Customer Operations, Gretchen Hyslip as they discuss Document Understanding and what that means for RPA.

RPA is Still Cutting Edge... to Most

It’s been a bit since the halcyon days of 2017/2018 when RPA landed on the radar of analysts like Gartner, large Global Service Integrators (GSIs), and the rest of us that developed business models to serve the incoming demand for this technology. I credit UiPath for providing the marketing and vision to move RPA into the “mainstream”. Many will say those days are over and we have moved onto new technologies like ChatGPT and generative AI. What I will say is that RPA is yesterday’s news for those that are on the cutting edge. Frankly, those people are only interested in bleeding edge technology and are not interested in how well it gets implemented or supported. 10 years ago it was the “cloud”. 20 years ago it was “web services”. 30 years ago it was the “internet and web sites”. Each is a vital part of our ecosystem, but they didn’t come about quickly.

RPA is the same way. As I have said in the past, it’s been around for close to 40 years in some capacity. Technology and the platforms have come a long way. But the fact remains that the baseline technology has not been adopted at the scale that many had anticipated. My thought is while COVID may have moved the needle for some to adopt it, many were constrained by budgetary issues and eventually leadership turnover to really get it used. It delayed the adoption and didn’t move it along any faster, as had been the common narrative. At this point, most decision makers (i.e., CIO, CTO, COO, CEO, CFO) are aware RPA to some degree but many haven’t pulled the trigger to really get it implemented.

Some of the inhibitors to RPA adoption include:

C-Suite executives are old school. They have been burned too many times by new technologies that look good in a demo only to find themselves eft with massive amount of tech debt. They are mentally and financially exhausted chasing the carrot that never came to be.
It’s unfamiliar and requires a leap of faith and trust that these “bots” can actually do the job. This correlates to point #1 to some degree.
The board and the C-Suite are onboard but struggle to think about use cases that have ROI. The lack of trust both internally and externally makes it hard to strategize. Inhibitions about being able to stand up an internal Center of Excellence (COE) is another barrier to entry.
The actual cost of licenses, implementation and ongoing support is too high compared to hiring people to do the same task.
Finally, are there use cases that do EXACTLY what our company needs?

These are all valid questions and inhibitions. I believe they are coming from a place of uncertainty and fear. Both are common in the classic cycle of an early adopter. The group that thinks RPA is yesterday’s news would fall more in the innovator track in that they are constantly looking for the latest thing.

Uncertainty can lead to inaction, and it will eventually leave those that don’t move forward, behind. I have been in this space for 20+ years and I know how RPA can be successfully implemented and most importantly supported. Bots need to be managed either by a company like mine, CampTek Software, or a highly dedicated and agile internal COE. Support is absolutely crucial. Every bot should be developed to be supported. In addition, fully formed and mature use cases should be chosen before or during the automation journey. It’s important to understand where we are now, so we can move forward.

-Peter Camp, CTO & Founder

Current Challenge:

The posting of checks is an extremely complicated but mission critical process for healthcare providers.

A large provider with 16 Orthopedic Clinics and 49 surgeons had been struggling to keep up with the daily requirement of posting substantial amounts of payments. Timeliness is essential and the burden on the current staff was of major concern. After an exhaustive selection process, CampTek Software was chosen to build and provide continued support for the automation of this critical process.

Presently a staff of 20 people go through their daily work queues to make sure these remittances get posted in a timely and accurate manner. The process has a large amount of business rules and exceptions that need to adhere to and accounted for. Not only is this a challenging workflow but trying to maintain a fully trained staff to keep up with it was a problem due to the current state of the labor market.

Solution:

CampTek Software was able to access and open 10 million files and convert 4 million files and 100,000 encounters from CPSI to EPIC/OnBase. The whole process from migration to hosting and ongoing support is managed by CampTek Software’s experienced managed services team. The estimated manual process takes an FTE roughly a minute for each record. The automation time per file is about half of that at 30 seconds. With no human errors. If an FTE were to complete all this work, the total time working 24/7 would be 5,208 Days or 125K Hours. The FTE gained capacity is $3,125,000.

In addition, CPSI, the legacy system can now be sunset and no further ongoing costs will be incurred by the provider.

CONTENT

Additional Resources

RPA is Still Cutting Edge... to Most

RPA Payment Posting Case Study

Real RPA Case Studies, Real Verifiable Solutions

Industries: Healthcare (applicable to all industries)

Systems: NextGen, Waystar

About Us

Services

Case Studies