Financial Services > Insurance
Health Insurance
Medical coverage systems including individual health, group health, Medicare, Medicaid, and specialty health products
₹73,000 Cr
India Health Insurance Market
$1.2 Trillion
US Health Insurance Market
50M+
Claims Processed Daily
500K+
IT Professionals
What Engineers Miss When They First Enter Health Insurance
Health insurance technology sits at the intersection of healthcare and financial services, combining the data sensitivity of medical records with the transactional precision of banking. Every claim processing decision is simultaneously a financial event (money moving from insurer to hospital) and a clinical event (a patient receiving care under coverage terms). The systems that make these decisions in real time — pre-authorisation engines that approve or deny procedures before they happen, adjudication engines that calculate what the insurer pays versus what the patient owes — have to be correct, auditable, and fast enough that a cashless hospitalisation does not become a cash payment because the pre-auth was delayed.
India's health insurance landscape is shaped by the Ayushman Bharat scheme and its companion network, PM-JAY, which together make India's government health insurance programme one of the largest in the world by covered population. The NHCX (National Health Claims Exchange) that IRDAI has mandated for standardised claims exchange between insurers and hospitals represents a significant infrastructure shift: moving from bilateral integrations between each insurer and each hospital (hundreds of separate API integrations) to a centralised exchange with a standardised FHIR-based data format. Engineers who understand NHCX implementation are genuinely scarce.
The TPA (Third Party Administrator) model adds a layer of complexity unique to the Indian health insurance market. TPAs are intermediaries who manage hospitalisation claims on behalf of insurers — they verify member eligibility, approve pre-authorisations, and process reimbursement claims. This means the data flow for a single hospitalisation claim may pass through the patient's insurer, the TPA's system, and the hospital's billing system — with each system maintaining its own record of the same event, and reconciliation failures between these records generating the disputes that take months to resolve.
What Teams Actually Do Day To Day
- 1Build the member enrollment and benefits administration platform: policy purchase and member addition workflows, coverage effective date management, pre-existing condition waiting period tracking, benefit limit monitoring (sum insured consumed, sub-limits for specific conditions), and the ID card and policy document generation.
- 2Implement the pre-authorisation system: receiving pre-auth requests from hospitals via the insurer's provider portal or via the NHCX exchange, applying coverage policy rules (is the procedure covered, is the hospital in-network, is the sum insured sufficient?), returning an approval or query within the regulatory timeline, and tracking approved treatments through to claim receipt.
- 3Build the claims adjudication engine: receiving claim documents (discharge summary, bills, investigation reports), extracting claim line items, applying deductibles and co-payments per the policy terms, checking for duplicate claims, and calculating the eligible reimbursement amount — with an audit trail for every decision that supports IRDAI inspections.
- 4Integrate with hospitals via NHCX and bilateral APIs: sending eligibility verification responses, receiving pre-auth requests and claim submissions in FHIR format, pushing status updates back to hospital billing systems, and managing the dispute workflow for claims where the hospital disagrees with the adjudication.
- 5Build the fraud detection layer: identifying unusual billing patterns (upcoding, phantom procedures, suspiciously similar claims from the same hospital), flagging providers with statistically anomalous claim rates for investigation, and managing the exclusion list of providers whose cashless empanelment has been suspended.
One End-to-End Flow: A Cashless Hospitalisation Claim
A cashless hospitalisation for a planned surgery involves pre-authorisation approval before admission, real-time treatment tracking during the stay, and final claim settlement after discharge — all coordinated between the hospital, TPA, and insurer.
Patient verifies eligibility and initiates cashless request
Before admission for a planned surgery, the patient's family visits the hospital's insurance desk. The hospital's staff verify the policy number, validate coverage via the TPA's eligibility API, and submit a pre-authorisation request with the diagnosis, proposed procedure, and estimated cost.
Systems Involved
Hospital billing system, TPA eligibility API, pre-auth submission portal
Where It Usually Breaks
Eligibility verification failures are most common for family floater policies where the sum insured has been partially or fully consumed by a claim earlier in the year. The hospital staff may see 'active policy' in the basic verification but not know the remaining sum insured is insufficient for the planned procedure.
Pre-authorisation is reviewed and approved
The TPA's medical team reviews the pre-auth request against the policy's coverage terms. Elective procedures may require clinical review; emergency admissions are approved immediately. The approved amount, room category, and any sub-limit caps are communicated back to the hospital.
Systems Involved
TPA pre-auth processing system, insurer policy rules engine, medical reviewer queue
Where It Usually Breaks
Pre-auth approvals that specify room category limits create disputes at discharge when the patient actually occupied a higher-category room. The insurer deducts proportionately from all bills (not just room charges) based on the room category ratio — a rule that most patients do not understand until they receive their final payable amount.
Interim pre-auth updates as treatment proceeds
For longer hospitalisations, hospitals submit interim enhancement requests when the estimated treatment cost exceeds the original pre-auth amount. The TPA reviews and approves enhancements. ICU admissions, complications, or extended stays require separate enhancement approvals.
Systems Involved
TPA enhancement request processing, insurer rules engine
Where It Usually Breaks
Enhancement approval delays during a hospitalisation create a practical problem: the hospital may continue treatment while the enhancement is pending, then hold the patient at discharge while waiting for the augmented pre-auth. This creates pressure on families at an already stressful time.
Discharge and final bill submission
At discharge, the hospital generates the final bill and submits it with the complete documentation package (discharge summary, all investigation reports, pharmacy bills, procedure certificates) to the TPA via the portal or NHCX. The TPA adjudicates the claim against the pre-auth approval and policy terms.
Systems Involved
Hospital discharge billing, document management, NHCX or TPA portal submission, adjudication engine
Where It Usually Breaks
Missing documents in the claim package are the most common cause of claim delays. Discharge summaries that are not signed by the treating doctor, investigation reports that are photocopies rather than originals, or bills that do not match the pre-auth approved amounts all generate queries that delay settlement.
Payment is made to hospital and patient receives settlement statement
The TPA approves the settled claim amount and instructs the insurer to pay the hospital directly (cashless). The hospital receives the settlement within the regulatory timeline. The patient receives a claim settlement statement showing the total bill, the insurer's payment, any deductions applied, and any patient liability.
Systems Involved
Insurer payment processing, NEFT to hospital, claim settlement letter generation
Where It Usually Breaks
Discrepancies between the hospital's expected settlement (based on the pre-auth) and the actual payment (after adjudication deductions) create hospital-side disputes. If the gap is significant, the hospital may seek to recover the difference from the patient, contradicting the patient's understanding of their cashless coverage.
Technology Architecture — How Health Insurance Platforms Are Built
The diagram below reflects how production Health Insurance systems are structured at scale — nine layers from client channels through edge security, API gateway, domain microservices, polyglot data stores, async event streaming, analytics, external partners, and cloud infrastructure. Solid arrows show synchronous REST/gRPC calls; dashed arrows show async event flows via Kafka or a message queue.
Industry Players & Real Applications
🇮🇳 Indian Companies
Niva Bupa Health Insurance
Standalone Health Insurer
Java/Spring, Oracle, MuleSoft
Formerly Max Bupa, digital-first approach
Star Health Insurance
Standalone Health Insurer
Java, Oracle, Custom TPA
Largest standalone health insurer in India
ICICI Lombard Health
General Insurer - Health Vertical
Guidewire, AWS, Microservices
Part of ICICI Lombard General Insurance
HDFC ERGO Health
General Insurer - Health Vertical
Duck Creek, Azure, React
Digital claims settlement focus
Bajaj Allianz Health
General Insurer - Health Vertical
Custom PAS, Oracle, Angular
Extensive hospital network
Manipal Cigna
Joint Venture Health Insurer
Cigna Global Platform, AWS
US healthcare expertise with Indian market
Aditya Birla Health
Standalone Health Insurer
Modern Cloud Native, GCP
Focus on chronic disease management
MediBuddy
Health Tech Platform
Python/Django, PostgreSQL, React
Digital health platform with insurance
🌍 Global Companies
UnitedHealth Group
USALargest Health Insurer
Custom Platforms, Optum Analytics
Optum technology subsidiary
Anthem (Elevance Health)
USABlue Cross Blue Shield
HealthEdge, AWS, Facets
Serves 47M+ members
Cigna
USA/GlobalGlobal Health Services
Express Scripts Platform, Cloud Native
PBM integrated model
Aetna (CVS Health)
USAIntegrated Health Company
Custom + CVS Integration
Pharmacy-health integration
Kaiser Permanente
USAIntegrated Care Provider
Epic, Custom Analytics
Payer-provider integrated model
BUPA
UK/GlobalInternational Health Insurer
Guidewire, Azure, React
Present in 190+ countries
Allianz Health
Germany/GlobalInternational Health
Allianz Global Platform
Part of Allianz Group
Oscar Health
USAInsurTech Health
Full Cloud Native, ML/AI
Technology-first health insurer
🛠️ Enterprise Platform Vendors
HealthEdge
HealthRules Payer, Source
Modern core admin platform
Cognizant TriZetto
Facets, QNXT, NetworX
Legacy market leader, large install base
Guidewire (formerly EIS)
HealthSuite
Cloud-native health platform
Edifecs
XEngine, Smart Trading
EDI and interoperability specialist
Cotiviti
Payment Accuracy, Analytics
Claims accuracy and analytics
Change Healthcare
InterQual, Clearinghouse
Now part of Optum
Availity
Revenue Cycle, Essentials Pro
Multi-payer platform
Inovalon
ONE Platform, ABILITY
Cloud-based data analytics
Core Systems
These are the foundational systems that power Health Insurance operations. Understanding these systems — what they do, how they integrate, and their APIs — is essential for anyone working in this domain.
Business Flows
Key Business Flows Every Developer Should Know.Business flows are where domain knowledge directly impacts code quality. Each flow represents a real business process that your code must correctly implement — including all the edge cases, failure modes, and regulatory requirements that aren't obvious from the happy path.
The detailed step-by-step breakdown of each flow — including the exact API calls, data entities, system handoffs, and failure handling — is covered below. Study these carefully. The difference between a developer who “knows the code” and one who “knows the domain” is exactly this: the domain-knowledgeable developer reads a flow and immediately spots the missing error handling, the missing audit log, the missing regulatory check.
Technology Stack
Real Industry Technology Stack — What Health Insurance Teams Actually Use. Every technology choice in Health Insuranceis driven by specific requirements — reliability, compliance, performance, or integration capabilities. Here's what you'll encounter on real projects and, more importantly, why these technologies were chosen.
The pattern across Health Insurance is consistent: battle-tested backend frameworks for business logic, relational databases for transactional correctness, message brokers for event-driven workflows, and cloud platforms for infrastructure. Modern Health Insuranceplatforms increasingly adopt containerisation (Docker, Kubernetes), CI/CD pipelines, and observability tools — the same DevOps practices you'd find at any modern tech company, just with stricter compliance requirements.
⚙️ backend
Java/Spring Boot
Core administration, claims processing, enterprise services
Python/FastAPI
ML models, analytics, clinical decision support
.NET Core
Provider portals, member-facing applications
Node.js
API gateways, real-time eligibility services
🖥️ frontend
React/Next.js
Member portals, provider portals, admin dashboards
Angular
Enterprise admin applications, clinical workbenches
React Native/Flutter
Mobile member apps, digital ID cards
🗄️ database
Oracle
Core admin systems, claims data warehouse
PostgreSQL
Modern cloud-native platforms, microservices
MongoDB
Clinical documents, unstructured provider data
Redis
Real-time eligibility caching, session management
🔗 integration
MuleSoft/Dell Boomi
Enterprise integration, EDI processing
Apache Kafka
Event streaming, real-time claim notifications
FHIR R4 APIs
Healthcare interoperability, CMS compliance
X12 EDI
HIPAA-mandated transactions (834, 835, 837)
☁️ cloud
AWS (Healthcare)
HIPAA-compliant hosting, S3 for documents
Azure Health
Azure API for FHIR, healthcare data lake
Google Cloud Healthcare API
FHIR stores, medical imaging
📋 compliance
HIPAA
Privacy Rule, Security Rule, EDI standards
IRDAI Guidelines
Indian insurance regulatory compliance
CMS Interoperability
Patient access, provider directory APIs
Interview Questions
Q1.What is the difference between a deductible, copay, and coinsurance?
Deductible is the amount a member must pay before insurance begins paying (e.g., $1,000/year). Copay is a fixed amount paid per service (e.g., $25 for doctor visit). Coinsurance is a percentage of the allowed amount (e.g., 20% after deductible). These are cost-sharing mechanisms in the benefit design.
Q2.Explain the 837 and 835 EDI transactions in health insurance.
837 is the Health Care Claim transaction used by providers to submit claims electronically (837P for professional, 837I for institutional). 835 is the Electronic Remittance Advice sent by payers to providers showing payment details, adjustments, and denial reasons for claims.
Q3.What is Coordination of Benefits (COB) and how does it work?
COB determines the order of payment when a member has multiple insurance coverages. The primary payer pays first based on their benefit rules. The secondary payer then pays remaining eligible costs. Order is determined by rules like birthday rule for dependents, active employee vs retiree, etc.
Q4.How does prior authorization work in health insurance systems?
Prior authorization is pre-approval required before certain services. Provider submits request with clinical documentation. System checks against medical necessity criteria (InterQual, MCG). Auto-approval for routine cases meeting criteria, else clinical reviewer evaluates. Approved auth is linked to claims for payment.
Q5.What is FHIR and why is it important in healthcare IT?
FHIR (Fast Healthcare Interoperability Resources) is a modern API standard for exchanging healthcare data. It uses REST APIs and JSON/XML formats. CMS mandates FHIR APIs for patient access to claims data. It enables interoperability between payers, providers, and patient apps.
Q6.Explain the claims adjudication process in health insurance.
Claims adjudication involves: 1) EDI validation of 837 format, 2) Eligibility verification, 3) Duplicate check, 4) Auth verification, 5) Provider/network validation, 6) Medical policy edits, 7) Pricing using fee schedules, 8) Cost-share calculation, 9) COB if applicable, 10) Payment determination. Automated rules engine handles most claims (auto-adjudication).
Glossary & Key Terms
EOB (Explanation of Benefits)
Document sent to member explaining what was billed, allowed, paid by insurance, and member responsibility
COB (Coordination of Benefits)
Process of determining payment order when member has multiple insurance coverages
OOP Max (Out-of-Pocket Maximum)
Maximum amount member pays in a year; after reaching this, insurance pays 100%
PCP (Primary Care Physician)
Member's main doctor who coordinates care and provides referrals in HMO plans
NPI (National Provider Identifier)
Unique 10-digit identifier for healthcare providers used in all transactions
UCR (Usual, Customary, Reasonable)
Method to determine allowed amount for out-of-network claims based on geographic area
ERA (Electronic Remittance Advice)
Electronic version of payment explanation sent to providers (835 transaction)
CARC/RARC
Claim Adjustment Reason Codes and Remittance Advice Remark Codes explaining payment adjustments
TPA (Third Party Administrator)
Company that handles claims processing and administration for self-insured employers
ASO (Administrative Services Only)
Arrangement where insurer provides admin services but employer funds claims
SBC (Summary of Benefits and Coverage)
Standardized document explaining plan benefits in uniform format
MLR (Medical Loss Ratio)
Percentage of premiums spent on medical care vs administration; ACA requires 80-85%