WORKLOAD AUTOMATION COMMUNITY
  • Home
  • Blogs
  • Forum
  • Resources
  • Events
  • About
  • Contact
  • What's new

Case Study: Part 2: Insurance claim acceptance process

7/10/2023

0 Comments

 
Picture
​This is the second part of the 4-part series of blogs covering how HCL Workload Automation can mimic end to end processes on insurance business side.
​In this second blog (2/4), we are looking at the below process and trying to mimic it end to end via HCL Workload Automation. Here’s the link to the first Blog: https://www.workloadautomation-community.com/blogs/case-study-insurance-claim-registration-validation-through-hwa incase you landed on this Page via a Search result.
Picture
An Insurance Claim during the Acceptance process undergoes checks for Completeness with respect to the Claim Form and also with respect to all documentation submitted as part of the Claim, the results of the checks could lead to Email notification being sent to the Contacts or proceed to the next Step.
The next step is if the claim needs to be escalated. The escalation requirement could result in either the escalation sent to a Portal for further review and approval.
Incase escalation is not needed for the Claim Case, it would undergo acceptance check and result in the Claim set to pending incase some further clarifications are needed or result in Claim being accepted and registered into the System.
The data pertaining to the claim form and documentation is already present stored in a Mongo DB and the same is accessed via Docusumo APIs exposed in the foreground, one could also substitute this with an equivalent product like IBM Discovery API, Google Cloud Vision API etc.
Completeness Check of Insurance form data:
The completeness check of Insurance form data is performed via HWA job realized as a RESTFUL GET job which would leverage Docusumo APIs to perform a RESTFUL GET operation to get the data from a Mongo DB (where all data resides):
 
The joblog of this job would be as follows:
Picture
This job would also have conditional Dependencies to determine if the data is complete:
Picture
So, this looks for the keyword “N/A” in the joblog of the job and decides whether the data is complete or if there are missing fields in the Scan done earlier from Docusumo:
Picture
Completeness Check of Insurance Attachment Data:
The Completeness check of Insurance attachment data is done via a by making a RESTFUL GET Call via a HWA Job into the same Mongo DB serviced via an Internal API running in the background:
Picture
​The completeness check of Documentation Data is again validated with Conditional Dependencies defined at the job level where the string “N/A” in the joblog indicates this data was not available in the Scan or is missing, this would result in the Condition “NOTCOMPLETE” getting satisfied:
Picture
If the “NOTCOMPLETE” condition is satisfied, this results in a mailing job to send notification to the Customer via Email to intimate him about the missing data.
Email Notification job for completeness Check of Image Data (Attachment data):
The Mail notification job sends a notification out that the documentation is not complete:
Picture
​CLAIM_ESCALATION Job:
This is realized as Unix Job to check if a Claim Escalation is needed in this case, so the script called evaluates if the value returned is beyond a particular value:
Picture
Picture
There would be conditional dependencies defined where every Return Code is mapped to “REQ”, “NOT_REQ”. So, depending on the Return Code 5 or 0, the corresponding conditions are passed that is Required and Not Required.
Picture
Incase escalation is required, SEND_CLAIM_ESCALATION_PORTAL job is called to do a RESTFUL POST job into the Portal such that the Claim is escalated for further approvals to higher Management in case the amount is beyond a particular value.

MAKE_ACCEPTANCE_DECISION Job:
The MAKE_ACCEPTANCE_DECISION job would run either a AWS Lambda Function or Google Cloud Functions to run in a serverless fashion on AWS or GCP where the evaluation is performed using Analytics in the background or in the form of a Google Big Query job or Azure Data Bricks job to check if the Claim can be accepted based on historical data captured from previous trends or a Custom Function written by the Insurance Company or if it is to be put to “pending” or it can be “Not Accepted”.
Picture
There would be conditional dependencies defined where every Return Code is mapped to either “ACCEPT”, “NOT_ACCEPTED” and “PENDING”. So, depending on the Return Code 127, 37 or 0, the corresponding conditions are passed.
Picture
​SET CLAIM PENDING Job:
This job sets the Claim to pending in the Mongo DB, so that the Claim could further evaluated manually for further checks from the Insurance Company:
Picture
In case “ACCEPT” condition is passed, the Claim is accepted through “RESGITER CLAIM” job & a mail notification is sent out via Mailing job to intimate the Registration of the Claim is completed Successfully.

Whole Flow at HWA Side:
Picture
Picture

Picture
Sriram V, ​Senior Technical Lead
​

I have been working with Workload Automation for the last 14 years , have had a chance to work with 100+ Customers from various industries as an Implementer , SME , India SME in IBM before also getting a chance to directly work on the Product Support Side as a DevOps Engineer on IBM SaaS Offering of the Product ,also had a stint with Lab Services Team developing Conversion Utilities to move from Competition,  have been working as a Technical Advisor on the Product lately on the Tech Sales Side.
View my profile on LinkedIn
0 Comments

Your comment will be posted after it is approved.


Leave a Reply.

    Archives

    June 2025
    May 2025
    March 2025
    February 2025
    January 2025
    December 2024
    November 2024
    October 2024
    September 2024
    August 2024
    July 2024
    June 2024
    May 2024
    April 2024
    March 2024
    February 2024
    January 2024
    October 2023
    August 2023
    July 2023
    June 2023
    May 2023
    April 2023
    March 2023
    February 2023
    January 2023
    December 2022
    September 2022
    August 2022
    July 2022
    June 2022
    May 2022
    April 2022
    March 2022
    February 2022
    January 2022
    December 2021
    October 2021
    September 2021
    August 2021
    July 2021
    June 2021
    May 2021
    April 2021
    March 2021
    February 2021
    January 2021
    December 2020
    November 2020
    October 2020
    September 2020
    August 2020
    July 2020
    June 2020
    May 2020
    April 2020
    March 2020
    January 2020
    December 2019
    November 2019
    October 2019
    August 2019
    July 2019
    June 2019
    May 2019
    April 2019
    March 2019
    February 2019
    January 2019
    December 2018
    November 2018
    October 2018
    September 2018
    August 2018
    July 2018
    June 2018
    May 2018
    April 2018
    March 2018
    February 2018
    January 2018
    December 2017
    November 2017
    October 2017
    September 2017
    August 2017
    July 2017
    June 2017
    May 2017

    Categories

    All
    Analytics
    Azure
    Business Applications
    Cloud
    Data Storage
    DevOps
    Monitoring & Reporting

    RSS Feed

www.hcltechsw.com
About HCL Software 
HCL Software is a division of HCL Technologies (HCL) that operates its primary software business. It develops, markets, sells, and supports over 20 product families in the areas of DevSecOps, Automation, Digital Solutions, Data Management, Marketing and Commerce, and Mainframes. HCL Software has offices and labs around the world to serve thousands of customers. Its mission is to drive ultimate customer success with their IT investments through relentless innovation of its products. For more information, To know more  please visit www.hcltechsw.com.  Copyright © 2024 HCL Technologies Limited
  • Home
  • Blogs
  • Forum
  • Resources
  • Events
  • About
  • Contact
  • What's new