Case Study: RPA - Healthcare

Home
Case Studies
Case Study: RPA – Healthcare

Lab Report Data Extraction

Challenges

Lab System with no API integration for read / write operations with third party applications
Data entry of 400 to 500 Lab reports with minimum 7 and maximum 48 pages on daily basis.
Total FTE: 12 to 17
Need of checker role for random data validation This required additional 3-4 FTE’s
Backlog: 8 days

Apaar Solution

Sampling of Lab reports to create training and test set, basis the available unique formats.
Training was done In data manager using the document understanding package to read data from the Lab Reports
Action Centre activities were used to support manual intervention and retraining of ML packages using the metadata generated during manual intervention.
Retraining of ML packages was scheduled at a frequency of 20 days.
The output received from the ML Program was then updated in the application.

Highlights

Total FTE Saving’s: 15
Backlog: 0 Days
Checker Role: Eliminated

About Apaar

Apaar is a Young, Agile, Responsive and Diverse startup. Our methodology has been consciously to be lean and keeping things simple and focusing on solving complex problems. Out team comes with rich and diverse experience, giving us the advantage of resolving faster and better.

Case Study: RPA - Healthcare

Lab Report Data Extraction

Challenges

Lab System with no API integration for read / write operations with third party applications

Data entry of 400 to 500 Lab reports with minimum 7 and maximum 48 pages on daily basis.

Total FTE: 12 to 17

Need of checker role for random data validation This required additional 3-4 FTE’s

Backlog: 8 days

Apaar Solution

Sampling of Lab reports to create training and test set, basis the available unique formats.

Training was done In data manager using the document understanding package to read data from the Lab Reports

Action Centre activities were used to support manual intervention and retraining of ML packages using the metadata generated during manual intervention.

Retraining of ML packages was scheduled at a frequency of 20 days.

The output received from the ML Program was then updated in the application.

Highlights

Total FTE Saving’s: 15

Backlog: 0 Days

Checker Role: Eliminated

About Apaar

Quick Links

Contact us

114, 115 1st Floor, Building 2(A-3), Sector-1,Milllennium Business Park, Mahape, Navi Mumbai-400710

info@apaarinfosystems.com

+91 72084 92494