AIToday
Large Language ModelsAI in HealthcareAmazon AI BlogPublished: Sep 22, 2026, 04:00 JST

EXL Medical IDP cuts claims review from 100+ minutes

EXL Medical IDP cuts claims review from 100+ minutes

3 Key Points

  1. What happened

    EXL Medical IDP, built on AWS, combines Xtrakto.AI document processing with the EXL Insurance LLM to extract, summarize, and query medical records. EXL says it reduced review time from over 100 minutes per case to hours.

  2. Why it matters

    Claims adjusters and underwriters spend over 100 minutes per case manually reviewing records, so automating extraction and summarization could free them for judgment work, with human-in-the-loop validation at critical stages.

  3. What to watch

    The results are from internal benchmarking by EXL and a large healthcare payer deployment, so the gains hinge on whether confidence thresholds and human validation keep quality stable as case volume scales.

WHO IT HITSThis lands on insurance claims adjusters, life underwriters, and healthcare payer nurses and care coordinators who manually review hundreds of pages of medical records per case, potentially shifting their work from retrieval to judgment and exceptions.

Not sure about something? Ask the AI

Summaries like this, in your inbox every morning.

Context & Analysis

The EXL Medical IDP solution addresses a longstanding operational problem in insurance and healthcare: medical records are long, unstructured, and full of specialized clinical terminology that demands domain expertise to interpret. EXL, a data analytics and AI provider serving Fortune 500 organizations for over 25 years with more than 50,000 professionals globally, built the solution on AWS to keep model development and production inference under one roof. The pipeline combines Xtrakto.AI, a template-agnostic document processing application that uses computer vision, NLP, and agentic AI workflows, with the EXL Insurance LLM, a domain-specific model fine-tuned on nine years of insurance claims operations data comprising over 13,500 records. Amazon SageMaker AI hosts the training and inference, while Amazon Bedrock provides access to general-purpose foundation models for broader language tasks.

A key design choice was fine-tuning rather than prompting general-purpose models. EXL argues that prompting alone cannot consistently handle insurance-specific tasks such as medical record annotation, economic and non-economic damages summarization, and negotiation guidance. The fine-tuning used Parameter-Efficient Fine-Tuning with Low-Rank Adaptation on SageMaker AI, which adapts the model without modifying all parameters of the base model. In internal benchmarking by EXL, the fine-tuned model performed well on tagging, summarization, question-answering, and reasoning, assessed with automated metrics and blind review by three insurance subject-matter experts. The pipeline also includes responsible-AI controls built into the deployment, such as content-filtering and grounding checks, source-level traceability, and de-identification procedures that align with HIPAA requirements.

A large healthcare payer deployed the solution to replace fragmented manual workflows, connecting systems including EPIC, CarePort, and Predictal through a single API-led orchestration. The results reported by EXL include reduced manual effort, accelerated member outreach, and increased clinical bandwidth without additional headcount. The outcome likely hinges on whether the confidence-based routing and human-in-the-loop validation continue to maintain data integrity as case volumes grow, since the solution is designed for augmentation rather than replacement of human expertise. For claims adjusters, underwriters, and care coordinators, the promise is less time on data retrieval and more time on judgment, though the reported gains come from EXL's internal benchmarking and a single payer deployment.

FAQ
What AWS services does the EXL Medical IDP solution use?
It runs on Amazon SageMaker AI for model training and inference, Amazon Bedrock for general-purpose foundation models, Amazon Textract for OCR, AWS Step Functions for orchestration, and Amazon S3 for data storage, among other AWS services.
How does the solution maintain accuracy in a regulated healthcare environment?
Generative outputs pass through content-filtering and grounding checks, every response links back to source data for traceability, and fields with confidence scores below a configurable threshold are routed to human validators. De-identification procedures align with HIPAA requirements.
What were the results for the large healthcare payer that deployed the solution?
The payer's nurses and care coordinators, who were spending over 100 minutes per case on manual data retrieval and clinical summary preparation, saw reduced manual effort, alleviated operational bottlenecks, accelerated member outreach, and increased clinical bandwidth without additional headcount.
Amazon AI BlogRead Original Article

Get the latest Large Language Models news every morning

For example, today's edition would include:

  • Professor bans devices to keep AI out, citing SwiftHacker News · 33m ago
  • Meta's Muse tops ChatGPT's first 12 daysTechCrunch AI · 33m ago
  • OpenAI forms math advisory group after Navier-Stokes breakthroughTechCrunch AI · 33m ago

AI-summarized, only the topics you pick — one digest a day via Email, LINE, or Slack.

Free · 30 seconds with Google · unsubscribe anytimeWhat is AIToday? →

Ask AI

Ask AI anything about this article. Q&As are published on this page for other readers too.

Related Articles

Next articleMicrosoft AI's Mustafa Suleyman: regulation not automatically bad