Health Insurance Claims Automation API: Glossary of Terms for APAC TPAs
Aadhaar
Aadhaar is the 12-digit biometric identity number issued by the Unique Identification Authority of India (UIDAI) to Indian residents. It is one of the primary KYC documents required in Indian health insurance claims. In TPA operations, Aadhaar OCR must extract the name, date of birth, gender, address, and Aadhaar number from both digital and physical card formats, including masked Aadhaar cards where the first eight digits are deliberately obscured for privacy. Aadhaar extraction accuracy is a material issue for Indian health insurance TPAs, as name mismatches between the Aadhaar card and the policy record are a common source of claim rejection disputes.
Aggregate / Annual Limit
The aggregate or annual limit is the maximum total amount that an insurer will pay for all claims submitted by a single policyholder within a policy year. Once the aggregate limit is reached, the policyholder has no further benefit entitlement until policy renewal. Claims automation systems must integrate with policy administration data to track real-time aggregate limit utilisation per policyholder across all claims in the policy year, and apply the residual available limit as a ceiling when calculating the eligible payable amount for each new claim.
Audit Trail
An audit trail in health insurance claims processing is a chronological, tamper-evident log of every action taken on a claim from initial receipt through to final settlement or rejection. A complete audit trail records when each document was received, when it was classified, which fields were extracted and with what confidence score, which validation rules were applied, what the output was at each stage, which human reviewer (if any) reviewed and edited fields, and when the final output was delivered. Audit trails are a regulatory requirement in most APAC jurisdictions and a practical necessity for dispute resolution, fraud investigation, and insurer reporting. A claims automation API that produces field-level confidence scores alongside extraction output provides a technically defensible audit record that is superior to manually produced claim records.
BNM (Bank Negara Malaysia)
Bank Negara Malaysia (BNM) is the central bank and financial regulator of Malaysia, with supervisory authority over the Malaysian insurance industry including health insurance. BNM’s guidelines on medical and health insurance business, including the MHIT (Medical and Health Insurance and Takaful) framework, govern how health claims must be processed, documented, and reported by insurers and TPAs operating in Malaysia. Claims automation systems deployed for Malaysian TPAs must align with BNM’s documentation requirements and data retention policies, including handling of data subject to Malaysia’s Personal Data Protection Act (PDPA 2010).
BPJS Kesehatan
BPJS Kesehatan is Indonesia’s national health insurance programme, mandated under Law No. 40 of 2004 on the National Social Security System. While BPJS itself operates as a government body rather than through private TPAs, the private health insurance market in Indonesia serves employees and individuals seeking supplementary coverage beyond BPJS entitlements. Understanding BPJS document formats, referral letters, and FKTP (Fasilitas Kesehatan Tingkat Pertama) documentation is important for Indonesian health insurance claims automation, as supplementary claims frequently reference BPJS referrals and must differentiate BPJS-covered components from private insurance-eligible charges.
Cashless Claims
A cashless claim is a health insurance settlement mechanism where the insurer or TPA directly settles the hospital bill on behalf of the policyholder, without the policyholder paying out-of-pocket and seeking reimbursement. The cashless process requires the TPA to issue a pre-authorisation letter to the hospital before or during admission, confirming coverage and setting a sanctioned amount. Automation in cashless claims focuses on the pre-auth stage: validating the policy, checking the diagnosis against covered procedures, and issuing the authorisation within defined TAT thresholds. In India, IRDAI mandates that TPAs process cashless pre-authorisation within one hour for planned hospitalisation and immediately for emergency cases, making speed of document validation a regulatory compliance requirement, not just an operational preference.
Claim Adjudication
Claim adjudication is the formal process by which a TPA determines whether a submitted claim is payable, how much is payable, and under what terms. It involves reviewing the claim documents, verifying policy coverage, applying exclusion clauses, calculating the eligible payable amount net of deductibles and co-payments, and issuing a settlement or rejection decision. Adjudication in APAC health insurance is governed by the terms set by the insurer and, depending on jurisdiction, by regulations from bodies such as IRDAI (India), BNM (Malaysia), or OJK (Indonesia). AI automation contributes to adjudication by ensuring that all documents required for a decision are present and extracted before the claim reaches the adjudicator’s queue, reducing the back-and-forth of incomplete claim handling.
Claim Adjudication Rules Engine
A claims adjudication rules engine is a configurable software component that applies a set of defined business rules, policy terms, and coverage logic to extracted claim data to determine eligibility, payable amounts, and routing decisions. Rules engines are distinct from AI models in that their decisions are fully transparent and auditable. Every decision can be traced to the specific rule that produced it. In a claims automation API architecture, the rules engine receives the structured JSON output from the extraction layer and applies per-policy, per-product, and per-regulator rules to produce an adjudication recommendation. Most APAC health insurance TPAs operate with rules engines configured specifically to the insurers they service, as policy terms vary significantly between carriers.
Claim Completeness Check
A claim completeness check is the validation step that verifies whether all required documents for a given claim type have been received, are legible, and contain the minimum required fields before the claim enters the extraction and adjudication workflow. Incomplete claim submissions, known in TPA operations as NIGO (Not In Good Order), are one of the leading causes of claim processing delays and customer complaints across APAC. An automated completeness check applies document-class-specific rules: an IPD cashless claim requires a hospital main bill, itemised bill, discharge summary, treating doctor’s certificate, and KYC documents, and the system flags the claim for return if any mandatory document is absent or illegible before any extraction is attempted.
Claim Form
A claim form is the standardised document that a policyholder or hospital submits to the TPA to initiate a health insurance claim. Claim forms vary by insurer and claim type. In India, IRDAI mandates use of a standardised health insurance claim form across all non-life insurers, covering claimant details, hospitalisation information, treating doctor details, bank account information for reimbursement, and declaration of other insurance policies (GISPA). In other APAC markets, claim forms are insurer-specific but follow broadly similar structures. Automated OCR extraction of claim forms must handle both printed and handwritten field entries, checkboxes, and multi-section layouts, producing a structured output that populates the TPA’s claims management system without manual keying.
Claim Fraud
Claim fraud in health insurance is the deliberate submission of false, inflated, or fabricated claims to obtain an insurance payment to which the claimant is not entitled. APAC health insurance fraud patterns include phantom hospitalisation (claims for treatment that did not occur), prescription inflation (billing for more medication than prescribed), identity substitution (using another person’s policy to claim for treatment), and hospital-assisted fraud involving collusion between the hospital billing department and the policyholder. AI-assisted fraud detection in claims processing identifies fraud signals at the document level, such as quantity mismatches between a prescription and a pharmacy bill, a discharge summary date that contradicts the hospitalisation period, or a doctor registration number that does not match any valid practitioner record.
Claim Frequency
Claim frequency is the number of claims submitted per covered life or per policy within a defined period, typically one policy year. It is a primary actuarial input for health insurance pricing, reserve setting, and TPA capacity planning. High claim frequency in a corporate group health insurance portfolio may indicate adverse selection, wellness programme gaps, or fraud patterns. TPA operations teams track claim frequency by employer group, geography, hospital, and claim type to identify emerging cost and fraud trends. Claims automation systems that produce structured, machine-readable output at scale enable real-time frequency analysis that would be impractical with manual processing.
Claim Intimation
Claim intimation is the formal notification provided by the policyholder or hospital to the TPA at the time of or immediately following a hospitalisation, initiating the claims process. Most APAC insurers require intimation within 24 to 48 hours of planned or emergency hospitalisation as a condition of cashless or reimbursement benefit eligibility. In automated claims workflows, claim intimation triggers the creation of a claim record in the TPA system and initiates the document collection process. Automated intimation handling via API, email, or portal submission creates an audit-trackable timestamp for claim initiation that is referenced throughout the subsequent processing workflow.
Claim Investigation / Field Investigation Unit (FIU)
A Field Investigation Unit, or FIU, is the operational arm of a TPA or insurer responsible for conducting on-the-ground investigation of suspected fraudulent or high-risk claims. FIU investigators verify hospitalisation facts, interview treating doctors and hospital staff, inspect medical records, and cross-check billing with actual services rendered. Claim investigation is triggered when automated processing flags anomalies: a discharge summary inconsistent with the hospitalisation period, a diagnosis that does not clinically justify the procedures billed, or a policyholder with abnormally high claim frequency. The AI extraction layer provides FIU teams with structured, pre-analysed claim data and specific anomaly flags, enabling investigators to prioritise and focus their field work rather than manually reviewing raw documents.
Claim Leakage
Claim leakage is the financial loss incurred by an insurer or TPA as a result of paying claims that should not have been paid, overpaying eligible claims, or paying at incorrect rates due to processing errors, fraud, or inadequate validation. Leakage is distinct from fraud. It encompasses both fraudulent claims and legitimate claims processed incorrectly. Common leakage sources in APAC health insurance include room rent upgrades billed beyond policy entitlement, consumables charges that are non-payable under the policy, duplicate billing of the same procedure across multiple bill lines, and incorrect application of co-pay or deductible rules. AI-powered claims validation reduces leakage by applying per-policy validation rules at the extraction stage, before the claim reaches the adjudicator.
Claim Register / Claims MIS
A claim register is the master record maintained by a TPA of all claims received, their current processing status, amounts claimed and approved, and final disposition. In larger TPA operations, this is operationalised as a Management Information System (MIS) that provides real-time and periodic reporting to the insurer on claim volumes, TAT performance, rejection rates, fraud flags, and settlement amounts. Claims automation systems that produce structured JSON output enable automated population of the claims MIS without manual data entry, improving the accuracy and timeliness of insurer reporting and reducing the administrative burden on TPA operations staff.
Claim Rejection
A claim rejection is a TPA or insurer decision not to pay a submitted health insurance claim, based on policy exclusions, incomplete documentation, coverage limits being exceeded, failed KYC verification, or detected fraud signals. In APAC TPA operations, claim rejection rates are a tracked operational metric and a driver of policyholder complaints and regulatory scrutiny. Automated pre-rejection validation applied by a completeness check API before the claim enters the adjudication queue distinguishes between claims that are substantively ineligible for payment and claims that have been incorrectly assembled or submitted, reducing unnecessary rejections driven by documentation errors rather than genuine non-coverage.
Claim Settlement Ratio
Claim Settlement Ratio (CSR) is the percentage of total claims received by an insurer in a financial year that were settled (paid) within the same period. It is one of the key public-facing performance metrics used by policyholders and independent aggregators to evaluate insurer reliability. For TPAs, claim settlement ratio is an indirect performance indicator: a high rejection or pending rate attributable to TPA processing delays or documentation errors negatively impacts the insurer’s published CSR and damages the TPA’s service contract standing. Automation reduces the administrative causes of unsettled claims, contributing to improved CSR by shortening processing cycles and reducing documentation-error-driven rejections.
Claims Intelligence API
A Claims Intelligence API is a REST-based application programming interface that accepts raw claim documents as input and returns structured, validated claim data as JSON output. Unlike traditional platform-based claims software that requires replacing or reconfiguring existing TPA systems, an API-first approach plugs into a TPA’s existing workflow without UI changes. The API processes incoming documents through classification, extraction, and validation stages and returns a confidence-scored JSON payload containing patient details, billing line items, diagnosis codes, and document-level metadata. For APAC TPAs, an API-first architecture is significant because it allows rapid deployment, typically four to six weeks, across heterogeneous legacy environments in India, Malaysia, Indonesia, and Singapore.
Co-Payment (Co-Pay)
A co-payment or co-pay is the portion of a health insurance claim that the policyholder is contractually required to pay themselves, expressed as a fixed amount or percentage of the eligible claim value. Co-pay provisions are common in APAC group health insurance plans and in certain government-regulated products. Claims automation systems must extract the eligible claim amount and apply the configured co-pay percentage for the specific policy before producing the payable output, ensuring that the TPA does not pay amounts that the policyholder is responsible for. Incorrect co-pay application in either direction is a source of claim leakage and a frequent dispute trigger.
Concurrent Audit / Process Audit
A concurrent audit in TPA operations is a real-time or near-real-time review of claims being processed, conducted by an internal or insurer-appointed audit team to verify that processing rules, documentation standards, and adjudication guidelines are being applied correctly on an ongoing basis. A process audit is a periodic structured review of the end-to-end claim handling workflow to identify procedural gaps, compliance deviations, and quality failures. For claims automation systems, concurrent and process audits benefit from the structured, timestamped, confidence-scored output that AI extraction produces, providing auditors with a complete and queryable record of every processing decision without reliance on manually maintained audit logs.
Confidence Score
A confidence score is a numerical value, typically expressed as a percentage between 0 and 100, that a claims AI model assigns to each extracted data field to indicate how certain it is that the extracted value is correct. A confidence score of 95% on a patient name field means the model is highly certain the extraction is accurate. A score of 55% on a handwritten medication name indicates the extraction is uncertain and should be reviewed. TPA operations teams configure confidence score thresholds to define which fields and claims pass straight-through to output and which are routed to HITL review. Confidence scores are critical for audit trail documentation, as they provide a basis for explaining why a particular field was extracted as a given value.
Coordination of Benefits (COB)
Coordination of Benefits, or COB, is the process of determining how claims are paid when a policyholder is covered under more than one health insurance policy. Under COB rules, the primary insurer pays first up to its policy limit, and the secondary insurer covers eligible remaining costs up to its limit, with the combined payments not exceeding the actual claim amount. In APAC markets, particularly India where GISPA declarations are used to identify multiple policies, COB processing is a mandatory adjudication step. Automated COB handling requires the claims system to identify all policies declared by the policyholder, determine primary and secondary policy order, extract the settlement data from each, and calculate the correct proportional liability per insurer.
Corporate / Group Health Insurance
Corporate or group health insurance is a health insurance policy issued to an employer or association that covers its employees and, optionally, their dependants under a single master policy. Group health insurance is the primary product serviced by health insurance TPAs in APAC markets. Unlike individual retail policies, group health insurance involves bulk enrolment, frequent mid-year additions and deletions of covered lives, and employer-specific benefit structures that may include enhanced limits, top-up layers, OPD coverage, and maternity benefits not available under standard retail products. TPAs managing corporate group health claims must handle claims from policyholders with varying benefit entitlements within the same employer group, requiring per-employee policy data lookup at the time of each claim.
Data Extraction
Data extraction in health insurance claims refers to the automated retrieval of specific data fields from classified claim documents and their output in structured format. For an IPD hospital bill, extraction produces fields including patient name, policy number, date of admission, date of discharge, treating doctor, diagnosis, room category, room rent, surgeon fees, anaesthesia charges, pharmacy items line-by-line, and total payable amount. Extraction quality is defined by field-level accuracy, that is the percentage of fields correctly extracted across a representative sample of documents, not document-level accuracy. A 98% document-level accuracy means one in fifty documents contains at least one error. Field-level accuracy metrics reveal whether those errors cluster in high-value fields like total amount or low-risk fields like a secondary diagnosis code.
Data Residency
Data residency is the requirement that certain categories of data, particularly sensitive personal data, be stored and processed only within the geographic borders of a specified country or jurisdiction. In APAC health insurance, data residency requirements stem from regulations including Singapore’s PDPA, Malaysia’s PDPA, India’s DPDP Act, and Indonesia’s Government Regulation No. 71 of 2019. For claims automation API deployments across multiple APAC markets, data residency compliance means that claim documents containing Indian policyholder data must be processed and stored on servers located in India, Malaysian data on servers in Malaysia, and so on. Multi-region API deployment architecture is a technical prerequisite for any claims automation vendor seeking to service enterprise TPAs across APAC.
Day Care Procedures
Day care procedures are medical treatments or surgeries that require less than 24 hours of hospitalisation due to advances in medical technology, but which would otherwise have qualified as inpatient procedures. Most APAC health insurance policies extend IPD coverage to a defined list of day care procedures, including cataract surgery, chemotherapy, dialysis, lithotripsy, and certain endoscopic procedures. For TPA adjudication, day care claims require the same document validation as IPD claims, including a treating doctor’s certificate confirming that the procedure was conducted and medically necessary, hospital bills, and discharge documentation, despite the absence of an overnight stay. Claims automation systems must correctly classify day care claim packages and apply day care-specific validation rules rather than standard OPD rules.
Deductible
A deductible is a threshold amount that the policyholder must pay in full before the insurance coverage activates for a claim or for the policy year. In APAC health insurance, deductibles may be applied per-claim or on an annual basis. Claims automation systems must track cumulative deductible utilisation across claims in the same policy year and apply the correct residual deductible to each new claim before calculating the insurer-payable amount. Annual deductible tracking requires the claims processing API to access the policy administration system’s historical claim data, making integration between the claims extraction API and the policy management database a functional requirement, not optional.
Deficiency Letter / Query Letter
A deficiency letter, also called a query letter, is the formal written communication issued by a TPA to a policyholder, hospital, or intermediary requesting missing documents, clarification on specific claim details, or additional information required to process a claim. Deficiency letters are generated when a claim fails the completeness check (NIGO status) or when specific data fields extracted from documents raise questions that require human clarification. In automated workflows, deficiency letter generation is triggered by the completeness validation layer and is pre-populated with the specific missing document names or field clarifications required, reducing the manual drafting effort and ensuring consistent, complete communication to the submitter.
Document Classification
Document classification is the automated process of identifying and labelling each document in an incoming claim package by its type, for example distinguishing a hospital discharge summary from a pharmacy bill, a KYC identity document from a query letter, or an operation theatre note from a vaccination certificate. In a health insurance TPA context, accurate document classification is the prerequisite for all downstream extraction and validation. Misclassification results in wrong fields being extracted, incorrect validation rules being applied, and ultimately erroneous output. For APAC TPAs processing IPD claims, a well-trained classification model must distinguish 25 or more document classes from a single multi-document PDF submission, often where documents have been scanned out of order.
Document Splitting
Document splitting is the automated process of separating a single multi-page PDF or image file, which may contain multiple distinct claim documents scanned together, into individual document units before classification and extraction. In APAC TPA operations, claim submissions frequently arrive as a single PDF containing 20 to 40 pages of mixed document types scanned in no particular order. Document splitting must correctly identify page boundaries between, for example, a hospital main bill that ends on page 7 and a discharge summary that begins on page 8, before each can be classified and extracted independently. Errors in document splitting, such as merging two documents into one or splitting a single document across two units, propagate errors throughout all downstream processing steps.
Domiciliary Hospitalisation
Domiciliary hospitalisation refers to medical treatment taken by a policyholder at home under the supervision of a medical practitioner, when hospitalisation would otherwise have been required but is not possible due to the patient’s condition or unavailability of hospital beds. It is a standard benefit extension in many APAC corporate health insurance policies, particularly in India. Domiciliary claims require specific documentation: a treating doctor’s certificate confirming the medical necessity of home treatment, prescription records, pharmacy bills, diagnostic reports, and nursing attendance records where applicable. Claims automation must apply domiciliary-specific document checklists and validation rules, which differ materially from standard IPD or OPD claim requirements.
Empanelled Hospital
An empanelled hospital is a medical facility that has a formal agreement with a TPA or insurer to provide cashless treatment to policyholders under specific terms. Empanelment involves the hospital agreeing to billing formats, tariff rates, and documentation standards that facilitate straight-through cashless claims processing. For health insurance claims automation, empanelled hospitals are significant because they often submit claims in more standardised formats, reducing document variability and improving extraction accuracy. TPA operations teams maintain empanelled hospital lists and associated billing format profiles, which can be used to configure extraction rules specific to high-volume hospital partners.
Empanelment Agreement
An empanelment agreement is the formal contract between a TPA and a hospital or clinic setting out the terms under which the hospital will provide cashless treatment to the TPA’s policyholders. The agreement defines billing format standards, tariff schedules, documentation requirements, TAT for bill submission, and dispute resolution procedures. From a claims automation perspective, empanelment agreements establish the structured data expectations for high-volume hospital partners, enabling the claims AI to apply hospital-specific extraction templates that improve accuracy for that partner’s billing format.
Family Floater Policy
A family floater policy is a health insurance plan that covers all members of a defined family unit, typically including the policyholder, spouse, and dependent children, under a single combined sum insured that any one member or combination of members can utilise in the policy year. Family floaters are widely sold across APAC retail health insurance markets. For TPA claims processing, family floaters require per-member tracking of individual claim utilisation against the shared sum insured, and each claim submitted under the policy must correctly attribute the patient to a specific covered member, verify that the member’s benefit entitlement has not been exhausted, and calculate the residual sum insured available for the family after the claim is settled.
First Notice of Loss (FNOL)
First Notice of Loss, or FNOL, is the initial report made by a policyholder or insured entity to the insurer or TPA immediately following a loss event, in the context of health insurance typically being a hospitalisation or a significant medical event triggering a claim. FNOL creates the first official record in the TPA’s claims management system and initiates the workflow for document collection, pre-authorisation (for cashless cases), or reimbursement processing. The speed and accuracy of FNOL registration directly impacts the efficiency of all subsequent processing steps. Automated FNOL intake via digital channels, including email APIs and portal integrations, reduces registration time and errors compared to manual phone-based notification handling.
First Pass Resolution Rate (FPRR)
First Pass Resolution Rate is the percentage of claims that are processed to completion without being returned, queried, or escalated after their initial submission and first pass through the processing workflow. A high FPRR indicates that submitted claim packages are complete, that processing rules are correctly applied the first time, and that the claims automation system is accurately extracting and validating data without generating false queries or errors. FPRR is a core QA metric for TPA operations managers. Improving FPRR through automation reduces rework costs, shortens settlement cycles, and improves policyholder satisfaction by eliminating deficiency letter cycles.
Gate 1: Completeness Validation
Gate 1, in a two-gate claims processing model, refers to the first validation checkpoint applied to an incoming claim submission before any data extraction begins. Gate 1 answers a single operational question: does this claim package contain all the documents required for the claim type being submitted? For an IPD reimbursement claim, Gate 1 checks for the presence of the hospital main bill, itemised bill, discharge summary, treating doctor’s certificate, and KYC document. Claims that fail Gate 1 are returned to the submitter with a specific document checklist, preventing incomplete claims from entering and congesting the extraction queue. Gate 1 automation eliminates the manual sorting and rejection workflow that ties up TPA processing teams in the early stages of claim handling.
Gate 2: Extraction and Validation
Gate 2, in a two-gate claims processing model, refers to the AI-powered OCR and GenAI extraction and field-level validation stage applied to claims that have passed Gate 1 completeness checks. Gate 2 extracts all defined data fields from each document in the claim package, assigns confidence scores, applies cross-document validation rules such as verifying that the patient name matches across the hospital bill, discharge summary, and KYC document, and produces a confidence-scored JSON output for delivery to the TPA’s adjudication system. Gate 2 is where claim leakage prevention, fraud signal detection, and structured data creation occur. Claims with field-level confidence below the configured threshold are routed to HITL review rather than proceeding to automatic output.
Generative AI (GenAI) in Claims Processing
Generative AI refers to large language models (LLMs) and multimodal AI systems that can interpret, reason about, and generate content from unstructured inputs. In health insurance claims, GenAI goes beyond OCR’s text extraction by understanding the context and meaning of extracted data. It can infer missing fields, resolve ambiguous document content, cross-reference prescription details against billing line items, identify inconsistencies between a discharge summary and itemised bill, and apply clinical reasoning to flag anomalous claims. When combined with OCR in a two-stage pipeline, GenAI dramatically reduces the volume of exceptions routed to human reviewers by resolving low-confidence fields through contextual inference rather than defaulting to manual escalation.
GISPA Declaration
A GISPA declaration is an India-specific health insurance claim document in which the policyholder declares the details of any other insurance coverage held, enabling the insurer or TPA to apply contribution clause calculations in cases where the insured is covered by multiple health insurance policies simultaneously. Under Indian insurance regulations, where a claim is covered by more than one policy, each insurer pays in proportion to the sum insured. GISPA extraction requires accurate capture of the other insurer name, policy number, sum insured, and declaration signature, all of which are mandatory for multi-insurer claim settlement. Missing or incorrectly extracted GISPA information is a common source of claim hold and payment delay in Indian TPA operations.
Grievance Redressal
Grievance redressal in health insurance refers to the formal process through which a policyholder can raise a complaint about a claim decision, processing delay, or service failure, and receive a structured response and resolution within defined timelines. In India, IRDAI mandates a grievance redressal framework for all insurers and their TPAs, including acknowledgement of grievances within specific TAT and escalation to the Insurance Ombudsman if unresolved. In Malaysia, Bank Negara Malaysia’s Financial Mediation Bureau provides a similar escalation pathway. Automated claims processing reduces the volume of grievances attributable to processing errors, documentation mishandling, and unexplained rejections by producing consistent, rule-based outputs with complete audit trails that support transparent communication with the policyholder.
Health Card / E-Card
A health card or e-card is the identity card issued by a TPA to a covered policyholder confirming membership under a health insurance policy. The health card typically contains the policyholder’s name, policy number, sum insured, coverage validity dates, and the TPA helpline number. It is presented by the policyholder at the time of cashless hospitalisation to initiate the pre-authorisation process. Modern TPAs issue e-cards as digital documents accessible via mobile app or email. Cashless processing workflows that include automated health card OCR at the hospital can pre-populate the claim intimation record without manual data entry, reducing wait times at the cashless desk.
Health Insurance Claims Automation
Health insurance claims automation is the use of AI-powered software to handle the end-to-end processing of health insurance claims with reduced manual intervention. It encompasses document intake, classification, data extraction, completeness validation, policy matching, routing, and output delivery in structured formats. In the APAC context, automation must handle highly varied document types including scanned hospital bills, handwritten prescriptions, identity cards, discharge summaries, and GISPA declarations, across multiple languages including Hindi, Bahasa Indonesia, Bahasa Malaysia, Thai, and Filipino. The goal is to reduce turnaround time per claim, eliminate manual keying errors, prevent leakage, and produce audit-ready structured data for downstream TPA systems.
Hospital Discharge Summary
A hospital discharge summary is a clinical document prepared by the treating physician summarising the patient’s hospitalisation episode, including the admitting diagnosis, treatment provided, procedures performed, medications administered, and the discharge condition and follow-up instructions. In health insurance claims, the discharge summary is a primary document for adjudication, as it provides the clinical basis for validating that the hospitalisation was medically necessary and that the treatment delivered aligns with the charges billed. Automated extraction from discharge summaries must handle semi-structured narrative text, clinical terminology, ICD codes, and physician handwriting, and cross-reference extracted diagnosis and procedure information against the itemised bill to detect inconsistencies.
Hospital Package Rate / Package Billing
A hospital package rate is a fixed, all-inclusive charge agreed between a hospital and a TPA or insurer for a defined medical procedure or hospitalisation episode, covering surgical fees, anaesthesia, consumables, nursing, room, and post-operative care within a single quoted amount. Package billing is common in APAC markets for elective surgeries such as joint replacements, cardiac procedures, and maternity cases at empanelled hospitals. For TPA adjudication, package claims are simpler to validate than itemised bills but require the automation system to confirm that the procedure performed matches the package code agreed, that no additional charges have been billed separately outside the package scope, and that the package rate applied corresponds to the TPA-negotiated tariff for that hospital.
Human-in-the-Loop (HITL)
Human-in-the-loop, abbreviated as HITL, is a claims processing model in which the AI system processes the majority of claim documents automatically but routes specific claims, documents, or fields to a human reviewer when AI confidence falls below a defined threshold, when anomalies are detected, or when the claim value exceeds an auto-approval limit. HITL is not a fallback for AI failure. It is a deliberate, rules-configured escalation layer that ensures human judgement is applied where it adds the most value. In practice, a claims automation API with HITL support will process a 30-document IPD claim, extract all fields automatically, and route only the two documents with low-confidence extraction scores to a human validator, rather than routing the entire claim for manual review. HITL reduces manual review volume by 70 to 90 per cent while maintaining output accuracy.
ICD Codes (International Classification of Diseases)
ICD codes are the standardised alphanumeric codes defined by the World Health Organization (WHO) to classify diseases, conditions, and health-related problems for clinical and statistical purposes. In health insurance claims, ICD-10 codes, the current standard across most APAC markets, are used to identify the diagnosis on the claim form, the discharge summary, and the hospital bill. ICD codes drive critical adjudication logic: they determine whether the condition is covered under the policy, whether it falls under a pre-existing disease exclusion, whether a sub-limit applies, and whether specific surgical procedure codes are payable under the plan. Automated ICD code extraction from discharge summaries and claim forms, including handling of free-text diagnosis descriptions where the attending physician has not recorded a structured code, is a standard capability requirement for enterprise claims automation.
Identity Verification (KYC) in Claims
Know Your Customer, or KYC, in health insurance claims refers to the verification of the policyholder’s identity using official identification documents to confirm that the person receiving treatment is the insured person named on the policy. In APAC markets, KYC documents vary by country: Aadhaar card and PAN card in India, MyKad in Malaysia, NIK (Nomor Induk Kependudukan) on KTP in Indonesia, and NRIC in Singapore. Automated KYC verification in claims processing involves OCR extraction of name, date of birth, and ID number from the submitted identity document, followed by comparison against the policy database. Failed KYC matches are routed for manual review or flagged as potential identity substitution fraud before any payment is processed.
Incurred Claim Ratio (ICR)
Incurred Claim Ratio, or ICR, is the ratio of total claims incurred by an insurer in a financial year to the total premium collected in the same period, expressed as a percentage. It is one of the most closely monitored financial metrics in health insurance, used by regulators, rating agencies, and policyholders to assess insurer financial health and pricing adequacy. For TPAs, ICR is an indirect performance signal: a TPA that allows high claim leakage, approves ineligible claims, or misses fraud signals inflates the insurer’s ICR, which may result in premium increases, policy restructuring, or TPA contract review. Claims automation that reduces leakage and improves adjudication consistency contributes directly to a more accurate and controlled ICR.
In-Patient Department (IPD) Claims
IPD claims are health insurance claims arising from a policyholder’s admission to a hospital for treatment requiring an overnight or extended stay. IPD claims are document-intensive and typically include a main hospital bill, itemised billing, operation theatre notes, discharge summary, treating doctor’s certificate, anaesthetist notes, pharmacy receipts, and supporting KYC documents. In APAC markets, IPD claims also frequently include a GISPA declaration, IRDAI-mandated claim forms in India, room rent receipts, and insurer-specific cashless authorisation documents. Because IPD claim packages can contain 15 to 40 documents in a single submission, automated document splitting, classification, and structured extraction are critical to processing speed. The TrueCover India deployment processed IPD claims across 25 document classes, reducing extraction time from 40 minutes to 5 minutes per claim.
Intelligent Document Processing (IDP)
Intelligent Document Processing, or IDP, is the combined application of OCR, machine learning, and AI reasoning to automatically classify, extract, and validate data from documents without manual configuration per document type. In the context of health insurance TPA operations, IDP handles the full spectrum of claim documents, from standardised cashless claim forms to unstructured handwritten prescriptions from rural clinics, and routes extracted data into pre-defined output schemas. IDP systems are trained on document variations specific to their deployment region. An APAC-trained IDP model understands that a Puskesmas referral letter in Indonesia carries different fields than a GISPA declaration in India, and processes each accordingly without requiring a human to pre-sort the incoming document package.
IRDA / IRDAI (Insurance Regulatory and Development Authority of India)
IRDAI is the statutory body that regulates the insurance industry in India. For health insurance TPAs, IRDAI sets the standards and guidelines for TPA licensing, claim processing TAT requirements, policyholder grievance procedures, and data privacy. IRDAI mandates that TPAs process cashless claims pre-authorisation within one hour and settle reimbursement claims within 30 days of receiving complete documentation. Automation tools deployed by Indian health insurance TPAs must produce output that is compliant with IRDAI’s data and audit trail requirements, and integration with IRDAI’s data exchange standards is a consideration for enterprise-scale deployments.
Itemised Billing
Itemised billing is a hospital billing format in which every charge for the hospitalisation episode is listed separately by service, procedure, medication, and consumable, including unit cost and quantity, rather than as a lump-sum total. Itemised bills are the standard documentation requirement for health insurance claim reimbursement across APAC, and their extraction is one of the most technically demanding tasks for claims automation AI. A single IPD itemised bill may contain 50 to 200 line items spanning multiple pages, requiring accurate per-line extraction of item description, quantity, unit rate, discount, and net amount, along with line-item level validation against policy coverage rules and fraud detection algorithms.
JSON Output
JSON (JavaScript Object Notation) output is the structured data format in which a claims automation API returns extracted claim data to the TPA’s downstream system. Rather than delivering scanned images or unformatted text, a claims intelligence API outputs a machine-readable JSON object containing all extracted fields, their values, confidence scores, and document-level metadata. The JSON schema is typically configured to the TPA’s existing data model, matching field names, data types, and value formats to the receiving claims management system, eliminating the need for manual data re-entry or format conversion. For APAC TPAs integrating with legacy claims platforms, a configurable JSON schema is a prerequisite for API adoption.
Medical Loss Ratio (MLR)
Medical Loss Ratio is the percentage of health insurance premium income that an insurer pays out in health insurance claims and clinical expenses. Regulators in several APAC markets specify minimum MLR thresholds to ensure that a sufficient proportion of premiums are directed toward healthcare rather than administrative expenses. For TPAs and insurers, MLR is a key financial management metric that is directly influenced by claim leakage, fraud, and processing efficiency. AI-powered claims automation improves MLR management by reducing erroneous payments while simultaneously reducing administrative costs, improving the net financial performance of the health insurance book.
MyKad
MyKad is the compulsory national identity card issued to Malaysian citizens and permanent residents by the National Registration Department (JPN). It serves as the primary KYC document in Malaysian health insurance claims and contains the holder’s 12-digit identification number, name, date of birth, address, and photograph. For health insurance TPAs operating in Malaysia, automated MyKad OCR must handle both the front and back of the card and extract fields accurately from both Rumi (Latin script) and Jawi (Arabic script) text where present.
Network Hospital
A network hospital is a hospital or clinic that has a formal tie-up with a TPA or insurer to provide cashless treatment services to policyholders. Network hospitals agree to pre-negotiated tariff rates and billing formats, making their claims inherently more processable through automation. The size and quality of a TPA’s hospital network is a primary competitive differentiator in APAC health insurance. For claims operations, network hospital claims benefit from standardised document formats and known tariff benchmarks, enabling higher straight-through processing rates compared to claims from non-network facilities where billing formats vary widely.
NIGO (Not In Good Order)
NIGO is a claims operations term referring to a claim submission that is incomplete, illegible, or otherwise fails to meet the minimum document or data requirements for processing. NIGO claims create operational friction: they are returned to the policyholder or hospital for resubmission, extending the claim settlement cycle and generating additional administrative touchpoints. In manual TPA operations, NIGO identification happens after a human processor has already reviewed the claim pack, wasting processing time. Automated completeness validation at the intake stage identifies NIGO status before any downstream work begins, reducing the cost of handling incomplete submissions and shortening the overall settlement cycle.
Non-Network Hospital
A non-network hospital is a medical facility that does not have a cashless tie-up with the TPA or insurer. Treatment at a non-network hospital requires the policyholder to pay the hospital directly and subsequently submit a reimbursement claim with all original documents. Non-network claims are operationally more demanding to process than network claims: billing formats are unstandardised, tariff benchmarking is more complex, and the completeness and authenticity of submitted documents requires more rigorous validation. Claims automation systems deployed for non-network reimbursement claims must handle a wider range of document formats and apply more robust fraud detection logic than for network cashless claims.
Non-Payable Items
Non-payable items, also referred to as standard exclusions or inadmissible charges, are specific consumables, services, or charges that an insurer excludes from health insurance claim reimbursement as a matter of standard policy, regardless of whether they are itemised on a hospital bill. In India, IRDAI has issued a standardised list of non-payable items applicable to all health insurance policies, including charges such as toiletries, telephone charges, attendant charges, cosmetic treatments, and certain administrative fees. Claims automation systems must apply the current non-payable items list as a validation rule during itemised bill extraction, flagging or deducting non-payable line items from the eligible claim amount before adjudication.
OJK (Otoritas Jasa Keuangan)
OJK is the Financial Services Authority of Indonesia, responsible for regulating the insurance industry including health and life insurance. OJK regulations govern claim documentation requirements, TAT standards, and consumer protection obligations for Indonesian health insurance TPAs. The Indonesian health insurance market includes both private commercial health insurance and the national BPJS Kesehatan scheme, which covers the majority of the Indonesian population under mandatory national health insurance. TPAs servicing commercial health insurance in Indonesia must ensure their claims processing systems are capable of handling Bahasa Indonesia documents, local health facility billing formats, and OJK-compliant data handling standards.
Optical Character Recognition (OCR)
Optical Character Recognition, or OCR, is the technology that converts images of text, whether scanned, photographed, or in PDF format, into machine-readable digital text. In health insurance claims processing, OCR is applied to hospital bills, prescription receipts, KYC documents, discharge summaries, and handwritten claim forms. Standard OCR performs well on printed, clean documents but degrades significantly on handwritten text, low-resolution scans, or documents in non-Latin scripts. APAC-specific OCR must handle script complexity across Devanagari (Hindi), Jawi (Malay), Bahasa Indonesia, and Thai, as well as the wide formatting variation in hospital bills across different countries. OCR accuracy is typically measured at the field level, not just the character level, and health insurance claims require field-level accuracy of 95% or higher to be operationally useful.
Out-Patient Department (OPD) Claims
OPD claims are health insurance claims for treatment that does not require hospital admission. A typical OPD claim package includes a consultation prescription, a doctor’s prescription or referral letter, pharmacy bills, diagnostic lab reports, and an OPD claim form. OPD claims are higher in volume but lower in document complexity than IPD claims, making them well-suited to straight-through processing via automation. In APAC markets, OPD claims introduce specific challenges around handwritten prescription validation, particularly in India and Indonesia where prescriptions are often handwritten in mixed English and local language, and pharmacy bill line-item extraction, where quantity, unit price, and medication name must be cross-validated against the prescription to detect prescription fraud or bill inflation.
PDPA (Personal Data Protection Act)
The Personal Data Protection Act governs the collection, use, and disclosure of personal data in Singapore (PDPA 2012) and Malaysia (PDPA 2010). Health insurance claim documents contain highly sensitive personal data including medical records, diagnosis information, identity documents, and financial details, making PDPA compliance a mandatory technical and operational requirement for any claims automation system deployed in these markets. API-based claims processing systems must implement data encryption in transit and at rest, role-based access controls, data residency compliance, and audit trail capabilities to satisfy PDPA obligations. In Singapore, the Personal Data Protection Commission (PDPC) enforces these requirements. In Malaysia, enforcement falls under the Ministry of Digital.
PDPB / DPDP Act (India)
India’s Digital Personal Data Protection Act 2023 (DPDP Act) governs the processing of digital personal data in India. For health insurance TPAs and their technology vendors processing claim documents containing sensitive personal data, including Aadhaar numbers, medical records, and financial information, the DPDP Act establishes obligations around data processing consent, purpose limitation, data localisation for certain categories, and data principal rights. Claims automation API deployments in India must implement data handling practices consistent with the DPDP Act, including clear data processor agreements between the TPA and the API vendor.
Policy Exclusions
Policy exclusions are the conditions, treatments, circumstances, or events explicitly listed in a health insurance policy as not covered, for which no claim payment will be made. Standard exclusions in APAC health insurance include pre-existing diseases during the waiting period, cosmetic procedures, self-inflicted injuries, experimental treatments, dental treatment (unless requiring hospitalisation), war or riot injuries, and treatment outside the policy’s geographic coverage area. For TPA adjudication, exclusion checking requires the AI system to cross-reference the extracted diagnosis codes and treatment descriptions against the specific exclusions applicable to the policyholder’s plan, since exclusion lists vary by product, insurer, and underwriting agreement.
Portability (Health Insurance)
Health insurance portability is the right of a policyholder to transfer their existing health insurance policy from one insurer to another without losing accrued waiting period credits for pre-existing diseases or time-bound exclusions. In India, IRDAI mandates portability for all individual and family health insurance policies, requiring the receiving insurer to grant credit for the number of years of continuous coverage held with the previous insurer. For TPA operations, portability-related claims require careful verification of the policyholder’s prior insurance history, coverage continuity, and waiting period status before adjudicating claims that might otherwise be subject to PED or specific disease waiting period exclusions.
Post-Hospitalisation Benefits
Post-hospitalisation benefits are health insurance coverage for medical expenses incurred after discharge from hospital, typically within a specified number of days following the date of discharge, commonly 60 to 90 days. Covered post-hospitalisation expenses include follow-up doctor consultations directly related to the hospitalised condition, prescribed medicines, diagnostic tests ordered during follow-up, and physiotherapy. For TPA claims processing, post-hospitalisation claims must be linked to the original IPD claim they follow, and the diagnosis and treating doctor in the post-hospitalisation claim must be consistent with the original hospitalisation. Automated cross-referencing between the IPD claim record and the post-hospitalisation reimbursement request is required to prevent fraudulent use of post-hospitalisation benefits for unrelated conditions.
Pre-Authorisation (Pre-Auth)
Pre-authorisation is the process by which a TPA reviews and approves a planned medical procedure or hospital admission before it occurs, confirming that the treatment is covered under the policyholder’s health insurance plan. Pre-auth is common in APAC for elective IPD cases, high-cost procedures, and cashless claims at empanelled hospitals. AI-assisted pre-auth automation validates the submitted documents, typically a treating doctor’s certificate, hospital admission form, and initial diagnosis, against policy terms, medical procedure codes, and coverage limits, and generates a sanctioned amount recommendation for the TPA adjudicator. Automated pre-auth reduces the administrative burden on TPA operations teams and shortens hospital waiting times for policyholders.
Pre-Existing Disease (PED)
A pre-existing disease, or PED, is any medical condition or disease for which a policyholder has received diagnosis, medical advice, or treatment before the commencement of their health insurance policy. PED is one of the most consequential concepts in health insurance adjudication across APAC, as insurers typically impose a waiting period of one to four years before claims arising from pre-existing conditions are payable. Inaccurate identification of PED status at the time of adjudication is a significant source of both wrongful rejection (denying valid claims) and claim leakage (paying claims that should be subject to the exclusion). Automated PED detection requires cross-referencing the extracted diagnosis from the current claim against the policyholder’s declared PED history and prior claim records within the TPA system.
Pre-Hospitalisation Benefits
Pre-hospitalisation benefits are health insurance coverage for medical expenses incurred before a hospital admission, within a specified number of days prior to the date of admission, typically 30 to 60 days. Covered pre-hospitalisation expenses generally include diagnostic investigations, specialist consultations, and prescribed medicines directly related to the condition that led to the hospitalisation. For TPA claims processing, pre-hospitalisation expenses submitted as part of an IPD claim must be validated for the required temporal relationship to the admission date, the clinical relevance of the expenses to the admitting diagnosis, and the completeness of supporting documents including referral letters, diagnostic reports, and pharmacy receipts.
Prescription Fraud
Prescription fraud is a specific category of health insurance fraud involving the falsification, alteration, or duplication of prescription documents to inflate OPD claim reimbursements. Common prescription fraud patterns detected by AI in APAC claims include quantity inflation where the pharmacy bill shows 60 tablets dispensed but the prescription says 30, substitution where a generic drug on the prescription is replaced with a branded equivalent at a higher price on the billing, phantom prescriptions billing for drugs not on any prescription in the claim package, and date manipulation where a prescription is dated after the pharmacy bill indicating backward creation. Automated cross-validation between prescription fields and pharmacy bill line items, applied at the extraction stage, is the primary technical control against prescription fraud.
Provider Network Management
Provider network management is the TPA operational function responsible for recruiting, contracting, credentialing, monitoring, and managing the hospitals, clinics, diagnostic centres, and pharmacies that form the insurer’s empanelled network. It includes negotiating tariff rates, maintaining updated network directories, managing hospital performance SLAs, and handling network-level disputes. From a claims automation perspective, provider network management data is a critical input to the adjudication system: the claims AI must query the network database at the time of processing to confirm whether the treating hospital is in-network, what tariff rates apply, and whether any specific billing format standards for that hospital should be applied during extraction.
Quality Audit in Claims
A quality audit in health insurance claims operations is a structured review of a sample of processed claims to verify that the correct adjudication rules were applied, that extracted data matches the source documents, that policy terms were correctly interpreted, and that processing TATs and communication standards were met. Quality audits are conducted internally by TPA QA teams and externally by insurer audit teams. They produce audit findings that identify systemic processing errors, staff training needs, and technology gaps. Claims automation systems reduce quality audit effort by eliminating manual data entry errors and producing consistent, rule-based outputs, while the confidence score and audit trail data produced by the AI system provides auditors with a machine-verifiable record of every extraction and validation decision.
Reimbursement Claims
A reimbursement claim is a post-treatment claim submitted by the policyholder after paying the hospital directly, seeking refund from the insurer via the TPA. Reimbursement claims are the primary claim type for non-empanelled hospitals and outpatient treatment across APAC. They are document-heavy and submitted in inconsistent formats, including scanned bills from varying hospitals, handwritten receipts from small clinics, and identity documents in multiple languages. Reimbursement claim processing is where OCR and GenAI automation delivers the highest operational leverage for TPAs, replacing manual data entry teams with automated extraction pipelines that output structured, validated JSON ready for adjudication.
Repudiation
Repudiation is the formal act by which an insurer or TPA declines liability for a claim, issuing a written repudiation letter to the policyholder explaining the grounds for rejection. Repudiation is a more definitive step than a deficiency letter: it follows a completed investigation and adjudication review, and it represents the insurer’s final position that the claim is not payable under the terms of the policy. Common repudiation grounds in APAC health insurance include non-disclosure of pre-existing disease at the time of policy inception, policy exclusion for the diagnosed condition, breach of policy conditions such as failure to intimate within the required timeframe, or confirmed fraud. Repudiation decisions and their supporting documentary evidence are subject to regulatory review and policyholder grievance escalation, making a complete audit trail essential.
REST API (in Claims Context)
A REST API (Representational State Transfer Application Programming Interface) is the standard integration architecture through which a claims intelligence platform communicates with TPA systems. In a claims automation context, the TPA’s existing system sends a POST request containing the claim document as base64-encoded content or a file URL, and the claims API responds with a JSON payload containing extracted data, confidence scores, and validation flags. REST APIs are stateless, scalable, and compatible with all modern TPA platforms, ERP systems, and workflow engines. For health insurance TPAs across APAC, REST API integration is the lowest-friction path to deploying AI-powered claims processing, as it requires no changes to the existing claims management platform.
Room Rent Capping
Room rent capping is a policy clause in health insurance that limits the insurer’s liability for hospital room rental costs to a specified daily amount or percentage of the sum insured. In APAC health insurance claims, room rent capping has significant downstream implications: many insurers apply a proportional deduction to all related IPD charges including surgeon fees, anaesthesia, and nursing, when the actual room rent exceeds the capped amount, not just to the room rent line item itself. Automated validation of room rent capping requires the claims automation system to extract the actual room type and daily rental from the hospital bill, compare it against the policy’s room rent limit, calculate any proportional deduction applicable to related charges, and flag the claim accordingly before it reaches the adjudicator.
Service Level Agreement (SLA)
A Service Level Agreement, or SLA, is the formal contract between a TPA and an insurer that defines the minimum performance standards for claims processing services, including TAT for pre-authorisation decisions, reimbursement processing timelines, NIGO return turnaround, grievance resolution time, and system uptime. SLAs set the operational accountability framework within which TPA management teams and their technology systems must perform. Breach of SLA thresholds typically triggers financial penalties or contract review provisions. Claims automation directly improves SLA compliance by replacing variable human processing speed with consistent, high-throughput automated extraction and validation that operates within defined processing time windows regardless of claim volume spikes.
Settlement Cycle
The settlement cycle is the total elapsed time from when a policyholder submits a claim to when the payment is received. The settlement cycle encompasses claim receipt, completeness check, document extraction, adjudication, approval or rejection decision, and payment disbursement. In APAC health insurance, settlement cycle length directly impacts policyholder satisfaction, insurer NPS scores, and the TPA’s contract renewal likelihood. Manual settlement cycles average 7 to 14 working days for IPD claims in many APAC markets. Automation-driven settlement cycles that accelerate the extraction and validation stages can compress this to 2 to 4 working days for standard claims where adjudication rules are well-defined.
Straight-Through Processing (STP)
Straight-through processing, or STP, refers to the automated end-to-end processing of a claim from intake to settlement output without any human intervention at any stage. STP is the operational benchmark for low-complexity, low-value claims that meet all completeness and validation rules, carry high AI confidence scores across all extracted fields, and trigger no fraud or anomaly flags. For OPD claims and routine IPD claims from empanelled hospitals with standardised billing formats, STP rates of 60 to 80 per cent are achievable with a well-configured claims automation API. STP rate is a primary KPI for APAC TPA operations heads assessing the ROI of claims automation investment.
Straight-Through Processing Rate (STP Rate)
STP rate is the percentage of total claims processed in a given period that complete the full processing workflow from intake through validated output without any human intervention. STP rate is the headline operational KPI for claims automation projects and directly correlates with cost reduction and TAT improvement. STP rate targets vary by claim type: simple OPD claims from standardised clinic formats may achieve 80 to 90 per cent STP, while complex IPD claims with 30 or more documents and handwritten components may achieve 50 to 70 per cent STP with a well-trained model. The remaining non-STP claims are routed to HITL review and processed by human validators using the AI’s partial extraction as a starting point, significantly reducing the time required for human review even in non-STP cases.
Sub-Limit
A sub-limit is a specific cap within a health insurance policy on the amount payable for a defined category of treatment or charge, even if the overall sum insured has not been exhausted. Common sub-limits in APAC health insurance include caps on ICU room rent, maternity benefits, cataract surgery, psychiatric treatment, and specific high-cost procedures. Claims automation validation must identify the relevant sub-limits applicable to each claim based on diagnosis and procedure codes, apply them in the correct sequence relative to the overall sum insured, and flag any charges that exceed sub-limit thresholds for adjudicator review.
Subrogation
Subrogation is the legal right of an insurer to pursue a third party that caused an insurance loss to the insured, to recover the amount paid under the claim. In health insurance, subrogation applies when the policyholder’s hospitalisation was caused by a third party’s negligence, such as a road traffic accident or workplace injury, and the at-fault party has legal liability for the medical costs. For TPA claims processing, subrogation identification requires the claims automation system to flag claims where the admitting diagnosis or accident description in the claim form indicates third-party causation. Subrogation-flagged claims are handled through a separate recovery process by the insurer’s legal team after initial claim settlement.
Sum Insured
Sum insured is the maximum amount that an insurer will pay in total for all eligible claims under a health insurance policy within a single policy year. It is the fundamental coverage parameter of any health insurance product. For TPA adjudication and claims automation, sum insured is the primary ceiling applied to every claim calculation. The claims automation system must retrieve the current sum insured for the specific policyholder, deduct any prior claims already paid in the policy year, and apply the residual sum insured as the maximum payable for the current claim. In family floater policies, a single sum insured is shared across all covered family members, requiring real-time tracking across all family members’ claims within the policy year.
Third-Party Administrator (TPA)
A Third-Party Administrator, or TPA, is an organisation appointed by an insurance company to manage and process health insurance claims on its behalf. In Asia-Pacific markets, particularly India, Malaysia, Indonesia, Singapore, Thailand, and the Philippines, TPAs sit operationally between the policyholder, the hospital or clinic, and the insurer. They are responsible for verifying claim documents, validating policy coverage, processing reimbursements, and managing cashless settlement at empanelled hospitals. In India, TPAs must hold a valid licence issued by IRDAI to operate. TPAs are the primary buyers and operators of health insurance claims automation technology, and the volume, document diversity, and multi-language nature of APAC claim intake makes automation essential at scale.
TPA License (India)
In India, a TPA must hold a valid licence issued by IRDAI to legally operate as a health insurance TPA. The licence is subject to minimum capital requirements, fit and proper criteria for key management personnel, infrastructure standards for data and IT systems, and ongoing compliance with IRDAI’s TPA Regulations. IRDAI’s TPA regulations were updated in 2016 and subsequently revised to require TPAs to maintain specific standards for claim processing turnaround times, data management, and grievance handling. For technology vendors supplying claims automation systems to Indian TPAs, understanding IRDAI’s requirements for system security, data retention, and audit trail capability is a prerequisite for enterprise contract qualification.
Top-Up and Super Top-Up Policy
A top-up policy is a supplementary health insurance product that provides additional coverage above a defined threshold, known as the deductible or trigger amount, once the base policy’s sum insured has been exhausted. A super top-up policy operates similarly but applies the deductible on a cumulative basis across all claims in the policy year rather than per individual claim. Top-up and super top-up products are widely sold in India as cost-effective ways to extend coverage beyond group health insurance limits. For TPA claims operations, top-up claims require verification that the base policy claims have been settled and that the trigger amount has been reached before the top-up policy liability activates, making cross-policy claims history integration with the base policy TPA a processing dependency.
Treating Doctor’s Certificate (TDC)
A Treating Doctor’s Certificate, or TDC, is a mandatory document in most APAC health insurance IPD and day care claim submissions, in which the attending physician certifies the patient’s diagnosis, the medical necessity of hospitalisation or procedure, the treatment provided, and the discharge condition. The TDC is a primary document for adjudication because it provides the clinical justification for the claim and the physician’s professional attestation of the facts. Automated TDC extraction must capture doctor name, registration number, hospital affiliation, diagnosis, procedure, date of admission and discharge, and the physician’s signature or stamp, and cross-validate the extracted diagnosis against the ICD codes and itemised billing to detect inconsistencies.
Turnaround Time (TAT)
Turnaround time, or TAT, is the elapsed time between a TPA receiving a claim submission and completing the defined processing step: either issuing a pre-authorisation, returning an NIGO notification, or delivering a validated data output for adjudication. TAT is the primary operational KPI for APAC health insurance TPAs and is frequently specified in SLAs with insurers. IRDAI in India mandates specific TAT requirements for cashless pre-auth and reimbursement claims. AI-powered claims automation reduces per-claim processing TAT by eliminating manual data entry from the critical path, replacing it with automated extraction that completes in seconds rather than the 30 to 40 minutes typical of fully manual processing.
Waiting Period
A waiting period is a defined period after the commencement of a health insurance policy during which claims for specific conditions or benefits are not payable. Waiting periods in APAC health insurance include an initial waiting period of 30 to 90 days applicable to all non-accidental claims in the first policy year, a PED waiting period of one to four years for conditions that existed before policy inception, and specific disease waiting periods of one to two years for defined conditions such as hernia, cataracts, joint replacement, and maternity. For TPA adjudication, waiting period validation requires the claims system to calculate the policyholder’s policy vintage at the time of the claim date, verify the applicable waiting period for the diagnosed condition, and confirm whether the policyholder’s continuous coverage history satisfies the required waiting period before the claim is payable.
Webhook
A webhook is an API mechanism that allows the claims automation system to proactively notify the TPA’s system when a processing job is complete, rather than requiring the TPA to repeatedly poll the API for status updates. In asynchronous claims processing workflows, where large IPD document packages may take several seconds to minutes to fully process, webhook callbacks allow the TPA platform to receive a real-time notification containing the extraction results as soon as processing completes. This event-driven architecture reduces API call overhead and enables near-real-time claim processing pipelines at scale.
INSIGHTS & INTELLIGENCE
Thinking on Claims, Documents & TPA Operations
Perspectives and analysis from the InterPixels AI team on health insurance claims automation, document intelligence, and operational efficiency across Asia-Pacific.
