Skip to main content

Yira.ai

Home › YIRA MedSense › Case study: Health Assist TPA
Case study · TPA · India
Health Assist Insurance TPA logo

Health Assist Insurance TPA runs YIRA MedSense in production.

Health Assist Insurance TPA Pvt Ltd processes health insurance claims for insurers in India, where every claim arrives with medical histories, lab reports, discharge summaries, bills and hospital tariffs. YIRA MedSense is the document-intelligence layer behind that work: it reads the documents, structures the data and flags cases for review.

100,000+medical documents parsed
5,000+cases flagged for fraud review
100+insurance operations

Figures are across MedSense insurance operations. Medically reviewed by Dr. N. S. Santosh Varma, MBBS, FIIM, FIDM, FICCM · Updated 19 October 2026

See it work
MedSense in 67 seconds · TEST DATA Demo documents only, not real patients.
Prior-record matching for fraud review · TEST DATA Demo documents only, not real patients.
The challenge

Every claim is a stack of documents.

A TPA reviews claims for many insurers and thousands of network hospitals. The work is document-heavy and time-sensitive.

Mixed formats

Scanned PDFs, photos and handwritten medical histories from many hospitals and labs.

Manual review

Medical officers read every page and key data into the claims system.

Hidden repeats

Reused or recycled documents are hard to spot one claim at a time.

Tariff checks

Each hospital has its own rates and room categories to check bills against.

The solution

MedSense as the document layer.

MedSense sits between incoming medical documents and the TPA's claims system and sends structured data by API, so the existing workflow keeps running.

Read

Medical-grade OCR and clinical NLP read histories, lab reports, discharge summaries and bills, including handwriting.

Structure

Diagnoses with ICD-10 codes, drug names, lab values against their ranges and bill lines, as JSON.

Verify and flag

Prior-record matching and ID-photo vs hospital-photo checks flag cases for investigators.

Integrate

Structured output goes to the claims system by API; people make every decision.

Rollout

Live in about 4–5 weeks.

The standard MedSense rollout runs in parallel with the current process before switching over. Timing depends on scope, data access and integration readiness.

Week 1 · Sandbox

Test on real sample claim documents.

Week 2 · Provision

Document types, fields and review rules set up.

Weeks 3–4 · Integrate

Connected to the claims system by API.

Weeks 4–5 · Go live

Run in parallel, then switch over.

A field match is not a fraud determination and a confidence score is not validated accuracy; the TPA's team decides on every claim.

FAQ

About this case study

Which TPA uses YIRA MedSense in production?

Health Assist Insurance TPA Pvt Ltd, an Indian third-party administrator, runs YIRA MedSense in production for medical document work on health insurance claims.

What results has MedSense delivered?

Across insurance operations, MedSense has parsed more than 100,000 medical documents, flagged over 5,000 cases for fraud review and supported 100+ insurance operations.

How long does a MedSense rollout take?

About 4–5 weeks from sandbox to go-live: sandbox on your own documents, provisioning, integration with your claims system, then go-live in parallel with your current process.

Does MedSense replace the TPA's claims system?

No. MedSense reads and checks the medical documents and sends structured data to the existing claims system by API.

Can other TPAs and insurers get the same setup?

Yes. MedSense is available to TPAs, insurers and payers worldwide, with client-managed deployment where documents must stay in the customer's environment.

Get started

Book your demo today.

See MedSense on the documents and fields that matter to your claims team.