YIRA MedSense reads the medical reports, lab results, invoices and provider tariffs behind every health claim in the UAE, turns them into structured data, checks the patient's identity and flags documents that match earlier claims, so claims teams in Dubai, Abu Dhabi and the Northern Emirates review faster.
Medically reviewed by Dr. N. S. Santosh Varma, MBBS, FIIM, FIDM, FICCM · Medical Officer, YIRA MedSense · Updated 12 October 2026
{
"documents": ["medical_report.pdf", "invoice.pdf", "lab_report.pdf"],
"extracted": "diagnoses, ICD-10 codes, drugs, lab values, bill lines",
"identity_check": "ID photo vs hospital photo, confidence score",
"prior_record_match": "flag if fields match an earlier claim",
"output": "structured JSON to your claims system"
}Illustrative output. MedSense prepares the review; your claims system handles submission.
Health insurance in the UAE is mandatory for residents, claims are submitted electronically, and every claim still depends on the medical documents behind it.
Claims move through electronic exchanges such as Dubai's eClaimLink and Abu Dhabi's Shafafiya, but reviewers still open scanned reports and invoices.
Hundreds of clinics and hospitals, each with its own document formats and price lists.
Reused documents, identity substitution and billing above agreed prices are hard to see one file at a time.
Mandatory cover is widening across the emirates, which means more claims for the same claims team.
MedSense does not replace your claims platform or your regulator submissions. It reads the medical documents that sit behind each claim, so your team reviews structured data instead of scans. Structured output goes to your claims system by API, which keeps handling submission and remittance with eClaimLink, Shafafiya or your own payer platform.
| Step | Without MedSense | With MedSense |
|---|---|---|
| Document intake | Scans and PDFs read by hand | Medical reports, lab reports, invoices and tariffs read by OCR and clinical NLP into JSON |
| Medical review | Reviewer reads every page | Diagnoses, ICD-10 codes, drug names and lab values flagged against their ranges |
| Identity | Visual check of an ID copy | ID photo compared with the hospital photo, with a confidence score |
| Fraud, waste and abuse | Found late, in audits | New documents matched against prior records; matches flagged for investigators |
| Provider pricing | Manual tariff lookup | Provider tariffs as procedure-level rate tables, contract rules applied, missing rates shown as NA |
MedSense runs in production at Health Assist Insurance TPA Pvt Ltd in India. It has parsed more than 1 lakh (100,000+) medical documents, flagged over 5,000 fraud cases for review and supported 100+ insurance operations.
Test MedSense on your own sample claim documents.
Set up document types, fields and rules for your portfolio.
Connect by API to your claims or TPA system.
Run in parallel, then switch over.
Timing depends on scope, data access and integration readiness. Client-managed deployment is available, so MedSense can run inside your own infrastructure. A field match is not a fraud determination; your team decides.
No. MedSense reads and checks the medical documents and sends structured data to your claims system by API. Your existing platform keeps handling submission and remittance.
Medical reports and histories (including handwritten notes), lab reports, invoices and provider tariffs, as scanned PDFs, digital PDFs or photos.
Yes. It compares every new document with earlier records, checks the patient's face against the ID photo, and flags matches for your investigators. It does not reject claims on its own.
Yes. Client-managed deployment is available, so documents can stay within your environment. Hosting and data residency are agreed per contract.
Yes. Health Assist Insurance TPA Pvt Ltd uses MedSense in production in India, where it has parsed more than 100,000 medical documents.
About 4–5 weeks from sandbox to go-live, depending on scope, data access and integration readiness.
Tampering and forgery checks can be built for your requirements as a scoped custom module. They are not part of the standard product today.
See MedSense on the documents and fields that matter to your claims team.