Best Claims Records Retrieval Services: 7 Picks for 2027

Short answer: match the service to where the records must land

Claims records retrieval means requesting, collecting, organizing and delivering the medical, billing and claims records an insurer needs to decide a claim, usually from providers the insurer does not control.

Choose by intake model first. If adjusters work inside a claims platform such as Guidewire ClaimCenter, favor a vendor with a named ClaimCenter path, because ordering and status checks in the tool adjusters already use cut handoffs. If your team works through email, spreadsheets and a vendor portal, a standalone portal with clear invoices is usually enough, and an integration can wait. Litigation exposure and volume come second: subpoena-heavy or defense files point to litigation-focused services, and high-volume risk-adjustment work points to a health-plan specialist.

For budget context, a third-party estimate puts the category at Market value: $3.2 billion in 2024 according to Matil.ai (2026). Matil.ai attributes that figure to Market Intelo, and it is a market-size number, not a price you will pay.

TL;DR: shortlist two or three services that fit your claims platform and litigation exposure, get a written rate card and turnaround commitments by record type, and ask for the SOC 2 report itself before you sign.

Key Takeaways

• Only two of the seven services, ABI and Ontellus, name a path into a claims platform on their public pages, so check that first.

• None of the seven publishes a service rate, so every retrieval price is Quote-based; ChartRequest is the only one with published fees, and those cover cancellations and handling.

• Turnaround claims are self-reported and counted differently, so ask each vendor how it defines a turnaround before you compare them.

• Litigation-heavy files suit litigation-focused services, while health-plan chart volume suits Ciox, whose public pages center on health plans.

• A workflow layer can route and track requests, but you still own duplicate protection, escalation, access controls and maintenance.

How we evaluated these services

This is an informed buyer's guide built from public pages, not from hands-on use. We opened each service's official pages and checked vendor claims against a third-party vendor comparison, a platform vendor's press release, and the official documentation of the workflow tools. We left out Retrēv because its own pages describe plaintiff firms as its clients and insurers only as records custodians. The weights below are our analysis, not vendor data.

Checked October 29, 2026: the ChartRequest cancellation fees and the Ontellus turnaround figure were re-opened on that date. The weights are a judgment, so change them if your files are mostly one line of business. Facts in the tables and profiles come from the pages named beside them, and our fit calls and red flags are labeled as judgment.

Feature matrix from public pages

The matrix records only what each public page states. "Not published" means the page does not say, not that the vendor lacks the feature. Two patterns stand out: insurer-facing pages are common, but named claims-system paths are rare, and security evidence is usually a logo or a self-description rather than a report.

What the pricing pages show

None of the seven publishes a service rate, so every retrieval price is Quote-based. American Retrieval's insurance page describes its rates only as "clear, competitive," with no figures. Compex's insurer page mentions flexible billing for enterprise programs without any rate. Ciox's health-plan page lists no rates either.

ChartRequest is the only vendor here with published fees, and they apply to cancelled requests rather than to retrieval itself. The same documentation lists a $49.95 base cancellation charge, $1 per page for the first 100 pages, $0.75 for each page after that, a $4.95 facility rejection fee per rejection, a $3.00 handling fee, and automatic cancellation after 60 calendar days without retrieval, according to ChartRequest (undated). Those fees come from the cancellation policy, so read them as exposure to plan for, not as a service price.

Illustrative only, not a forecast: suppose a carrier cancels 4 requests in a month, each 120 pages long, and 2 requests are rejected by a facility. Using the rates cited above and reading the 100-page tier per request, each cancellation costs $49.95 + $100 + $15 = $164.95, where $15 covers the 20 pages above 100 at $0.75. Four cancellations come to $659.80, the two rejections add $9.90, and the total is $669.70 before any provider copy fees. If the same team builds intake in n8n instead, its error trigger sets execution.retryOf only on retried runs, so the build must check that field before it sends a second request.

The same math, line by line, according to ChartRequest (undated):

Seven vendor profiles

Each profile gives the best fit, the limits we found, what to ask during implementation, and the page we used. Vendor names come first, and each figure carries its source.

American Retrieval

Best fit: insurers that need attending physician statements and claims records through one OCR-searchable portal. Its insurance page describes APS and claims-related retrieval for underwriting, claims evaluation and policyholder services, plus a dedicated account professional. Limitations: the page names no claims platform and no third-party certification such as SOC 2 or HITRUST, and its insurance page gives no rates. Implementation: ask whether requests can be created by API or bulk upload, and ask for turnaround commitments by request type, since the page says only that tracking gives "turnaround estimates." Evidence: insurance page.

Compex Legal Services

Best fit: carriers that want retrieval, canvassing, IME record delivery and court reporting from one vendor. Its insurer page lists general liability, vehicle and bodily injury, workers' compensation and medical malpractice claims. Limitations: the page lists "Integrations + API's" without naming any claims platform, and its SOC 2 Type II and HIPAA statements come without report details on that page. Implementation: confirm which claims platform the integration supports, and ask whether canvassing is billed per claim. Evidence: insurance carriers page.

ABI Document Support Services

Best fit: carriers on Guidewire ClaimCenter that want to order, receive and sort records without leaving the claims system. Guidewire's press release announced ABI ProConnect as a "Ready for Guidewire" add-on that lets ClaimCenter users request records with claim details filled in, check status, view ABI invoices and use one message center, according to Guidewire (October 14, 2021). Limitations: that release is from 2021, so confirm current support for your ClaimCenter version; ABI's homepage gives no turnaround times, and its AICPA badge does not describe report status. Its eSummary tool sorts records chronologically, which helps adjusters working through long medical files. Implementation: get the current ProConnect version and a written list of supported ClaimCenter releases, and confirm who approves invoices before payment. Evidence: Guidewire press release.

Ontellus

Best fit: carriers and third-party administrators that want retrieval, chronologies and claim evaluation reports from one vendor. Its records-retrieval page says it obtains records through HIPAA authorization, subpoena, stipulation or requests for production, and that it covers all states. Most requests: fewer than 30 business days according to Ontellus (undated). Limitations: its claim to be the only SOC 2 Type II certified records retrieval provider is a self-description, and its pages show no price list. Implementation: set pre-authorized fee amounts by claim type before the first order, because a facility fee above that amount waits for client approval; name the approver; and confirm which Guidewire or Duck Creek release the integration supports. Evidence: records retrieval page.

Lexitas

Best fit: litigation-driven files, such as defense work and subpoena-based or workers' compensation records. Its record-retrieval page describes fast, secure retrieval for attorneys, insurance professionals and corporate legal teams, and it adds Record Insights, which produces AI-enabled chronologies including from handwritten records. Limitations: its figures are a 30–45 day average turnaround and a 98% completion rate, both according to Lexitas (undated), and the page does not explain how completion is measured; it describes no claims-system integration for insurers, and pricing is not published. Implementation: ask how the 98% figure is measured, get fee structures by state, and decide which files go down the litigation path rather than the claims path. Evidence: record retrieval page.

ChartRequest (RecordGateway)

Best fit: insurers that submit batches and want invoices, statuses and a dashboard in one place. The RecordGateway page describes a bulk pull-list template that flags errors before submission, a central dashboard, uniform file naming, and statuses such as Pending, QA Hold and Ordered. Limitations: no service rate is published, the optional API comes without endpoint details, and the page describes no claims-system integration. Cancellation and automatic cancellation rules mean someone has to watch request age. Implementation: ask for the API documentation, the invoice schedule and a service rate in writing, and assign a weekly review of requests nearing automatic cancellation. Evidence: RecordGateway page.

Ciox Health

Best fit: health plans with HEDIS, STARS or risk-adjustment chart volume. Its health-plan page lists HEDIS, RAD-V and STARS record retrieval, and says it codes roughly 3.4 million risk adjustment charts each year, according to Ciox (undated). Limitations: the page's commercial audiences are health plans, life insurers, law firms and government, with no property-and-casualty carriers, and the page gives two different client counts, so ask for a current figure. A third-party ranking describes Ciox's rates as contracted, with enrollment required, so budget for a contract rather than a per-order fee. Implementation: ask whether the commercial product covers non-health claims and what enrollment requires. Evidence: health plans page.

Stitching it together: Zapier, Make, n8n, or your own build

Many small carriers will try to assemble this in Zapier, Make or n8n, or build it in-house, and that can be a sound choice. Those tools can keep run histories, retry failed steps, route errors to a handler and log what happened, which supports audit evidence when you configure them. The buyer still designs and owns observability, duplicate protection, escalation paths, access controls and ongoing maintenance.

Zapier shows errored runs with an Errored status and offers replay and custom error handlers. Its automatic protection is strict: Auto turn-off: 95% of runs errored in 7 days according to Zapier (undated). The same help article gives Team plans a 24-hour grace period after notice and Enterprise plans 72 hours, according to Zapier (undated).

Make's help article says run-history retention depends on your pricing plan and gives no day count, so check Make's pricing before you assume how long failed runs stay visible. n8n's execution list filters failed runs and offers a retry that resumes from saved state, but completed nodes keep their results while the failed node reprocesses all of its input items, so check the target app for duplicates before you retry, according to n8n (undated).

US Tech Automations could configure a proposed intake workflow for this, and what follows is a design, not a deployed system. The trigger is a new records need on a claim, such as a status change in the claims system or a row added to an intake sheet. The action checks required fields (claim number, provider, date range and authorization type), formats the request for the vendor's order template, and places it in an approval queue; the output is a logged request with a status ID in the claim notes or a shared sheet. The prerequisite is an export or API from the claims system that exposes claim numbers and status changes. Its public pages name Gmail, Google Sheets, HubSpot, QuickBooks and Stripe, and no claims-system connector, so that connector would need to be scoped separately. Human review sits at two points: approval before anything is sent, and approval for any fee above the amount an adjuster pre-authorized.

A second proposed workflow would run daily. The trigger is a scheduled check; the action pulls each vendor's status export or invoice file, matches items to claim numbers, and flags requests that are open past your threshold or close to a vendor's automatic cancellation; the output is an exceptions list in a shared sheet that a claims supervisor reviews before any payment. Its prerequisite is a status export or API key from each vendor. ChartRequest mentions an optional API, and most public pages we opened do not describe one, so confirm each before you design the flow.

When NOT to use US Tech Automations

Skip a custom layer when one service already covers the job. If your adjusters live in Guidewire ClaimCenter and order a modest number of files, a vendor add-on such as ABI's ProConnect is simpler than building a connector you must maintain. If you need affidavits, certified copies or subpoena handling, a litigation-focused service is the right buyer, because a workflow layer does not replace a records custodian or a legal process. If you send only a few requests a month through a vendor portal, that portal's status page and invoice may be enough, and a workflow adds a system to maintain.

Who this is for

This guide is for an owner or operations lead at a small insurer who is close to choosing a service and needs a shortlist they can verify, not a platform rebuild. It fits carriers and third-party administrators with mixed claim types.

Red flags: you need health-plan HEDIS or risk-adjustment chart review, which points to a specialist such as Ciox; you need litigation-grade proof such as certified copies with no legal team involved; or you expect a fixed monthly price, since none of the seven publishes a service rate.

Glossary

• Custodian: the provider, facility or agency that holds a record and must release it.

• Attending physician statement (APS): a treating physician's report on a patient, often requested for underwriting or claim evaluation.

• Canvassing: searching for providers and treatment a claimant did not disclose.

• Chronology: a date-ordered summary of records used to evaluate a claim.

• Pre-authorized fee: a fee ceiling set in advance; anything above it needs client approval before the vendor proceeds.

• SOC 2 Type II: an independent CPA report on a service provider's controls over a period of time; ask for the report, not the badge.

• Idempotency: a design that stops a retry from creating a duplicate request.

Decision checklist

1. Name the claims system and version the service must connect to.

2. Get a written service rate, rush terms, provider copy-fee handling and cancellation rules.

3. Ask for turnaround by record type and how the vendor counts it.

4. Request the SOC 2 Type II report or HITRUST letter, not only the logo.

5. Set pre-authorized fee amounts by claim type and name the approver.

6. Assign a weekly review of stalled requests, cancellations and invoices.

Frequently asked questions

Which service fits a small insurer on Guidewire ClaimCenter?

Start with ABI ProConnect or Ontellus, the two whose public pages name a ClaimCenter path, and confirm current support for your version in writing.

Does any of these services publish a price for retrieval?

No; none of the seven publishes a service rate, and ChartRequest publishes only cancellation and handling fees, so request a written rate card from each vendor.

How long does retrieval take?

The published turnaround figures, covered in the profiles, are self-reported and counted differently, so ask each vendor how it defines a turnaround before you compare them.

Is a SOC 2 badge enough evidence?

No; ask for the report, its audit period and any exceptions. Ontellus calls itself the only SOC 2 Type II certified records retrieval provider on its page, which is a claim to verify rather than a finding.

Can we build this in Zapier, Make or n8n instead?

Yes, for routing, tracking and alerts, since those tools keep run histories and error handlers when configured; but you must design duplicate protection, escalation, access controls and maintenance yourself.

Conclusion

For most small carriers the decision turns on where records must land and what you can verify in writing. Shortlist two or three services that fit your claims platform and litigation exposure, get a service rate and turnaround commitments by record type, and read the SOC 2 report before signing. If you want a custom layer that routes requests and reconciles exports, see how US Tech Automations configures this against your own systems and approval points, and confirm the prerequisites first.