Komodo Health vs IQVIA: Which Patient Claims Data Fits Your Brand in 2026

Komodo Health vs IQVIA: the short answer

Komodo Health vs IQVIA comes down to what number your team has to defend. Choose IQVIA when the output must reconcile to national and prescriber-level prescription counts, feed incentive compensation or extend outside the US. Choose Komodo Health when you need linked US patient journeys, refreshed daily, for treatment pathways, switching, patient finding and fast cohort questions. Many brands end up licensing both for different jobs, and neither shows what happens to a specialty prescription before it becomes a claim.

Both vendors now publish patient counts in the hundreds of millions, so size alone will not separate them. What separates them is method. IQVIA's prescription audits project national volume from a sample, while its claims assets and Komodo's Healthcare Map count linked, de-identified patient records. Two dashboards built on these sources can disagree on how many patients started therapy last quarter and both be correct on their own terms.

This guide puts each vendor's own published figures side by side, explains open and closed claims in plain terms, shows which source fits which commercial question, and gives you a feasibility test to run on both before signing. It is written for commercial operations, analytics, market access and finance leads at pharma and biotech companies, particularly mid-sized and emerging teams buying patient-level data for the first time.

Open claims vs closed claims: why it matters to the comparison

Most of the confusion in this comparison comes from two kinds of claims data, so it is worth settling them first.

Closed claims come from payers. They cover everything the plan paid for its enrolled members: medical visits, procedures, hospital stays and pharmacy fills. Because you know when a member joined and left the plan, you can say with confidence that a patient had no treatment in a period, which is what persistence, line of therapy and incidence analysis need. The weakness is reach: you only see patients enrolled with the contributing payers, and you lose them when they change plans.

Open claims come from clearinghouses, switches and pharmacies as transactions move through the system. They reach far more patients and prescribers, including people outside any single payer's book, and they show rejected and reversed pharmacy claims that matter for abandonment and reversal analysis. The weakness is completeness: a patient can disappear because the claim went through a channel the vendor does not see, not because therapy stopped.

IQVIA's LAAD Plus page states this trade-off directly: closed claims give comprehensive patient activity but are restricted by payer enrollment, while open claims give broader coverage but may miss blocked products or specialty care. Both vendors now combine open and closed sources. The practical question is how each one handles the gaps, and whether that suits your therapy area.

IQVIA vs Komodo Health by the numbers

The table uses each vendor's own published material, read in October 2026: IQVIA's LAAD Plus product page and Komodo Health's Healthcare Map page and press releases. Neither vendor publishes list prices.

Do not read the patient rows as a ranking. Each vendor defines a patient, deduplicates across sources and counts history differently. IQVIA's own LAAD Plus case study says combining open and closed claims found 15 percent more patients and providers for one client, which tells you how much the count moves with method alone. The only comparison that means anything is a feasibility count on your own market definition, described below.

Which claims data provider fits your question?

Rx measurement

If sales crediting, goal setting and market share have to tie to an industry-standard number, IQVIA's projected prescription audits are the source many US field organisations already build those processes on. Patient-level claims from either vendor will not reproduce those totals, because they count rather than project.

Patient journeys

Linked longitudinal records answer where patients come from, what they were on before and when they stop. Komodo positions the Healthcare Map around exactly this with daily refresh. IQVIA's LAAD Plus answers the same questions with its combined open and closed claims. Run both on your indication before deciding.

Patient finding

For rare and specialty conditions the count of identifiable patients per prescriber decides targeting. Fresh data matters because the window to reach a newly diagnosed patient is short. Score both vendors on patients found and on how many of the top prescribers they surface that your field team already knows.

Global brand

Komodo's Healthcare Map is US data. If your forecasting, market sizing or launch sequencing covers Europe, Japan or other markets, IQVIA is the provider with data in those countries, and a US-only source becomes one input rather than the backbone.

The evaluation scorecard: eight things to test

• Feasibility count on your market

  Give both vendors the same written definition: diagnosis codes, procedure codes, NDCs and date window. Compare patient and prescriber counts, then ask each to explain the difference.

  • Same definition, in writing
  • Split by year and region

• Lag and refresh

  Ask how many days pass between a pharmacy fill or visit and its appearance in your delivered data, and how often history is restated as late claims arrive.

  • Measure on a recent month
  • Ask for restatement rules

• Specialty pharmacy and channel blind spots

  Limited-distribution products often move through pharmacies that do not feed claims vendors fully. Ask each vendor which specialty pharmacies and channels it sees for your product.

  • Name your SP network
  • Compare to your own 867 and SP data

• Continuous enrollment

  Persistence and line of therapy need patients you can follow. Ask how many patients in your cohort have 12 months or more of continuous closed-claims coverage.

  • Count, do not assume
  • Check by payer type

• Tokenisation and linking

  You will want to join claims with hub, specialty pharmacy and CRM data. Confirm which tokenisation provider each vendor supports and whether your existing tokens will match.

  • Name your token provider
  • Ask about expert determination

• Delivery into your stack

  Platform, flat files, Snowflake share or API: confirm the format, schema documentation and whether you can load it into your own warehouse.

  • Ask for a sample schema
  • Check incremental loads

• Permitted use

  Licences restrict which agencies may touch the data, whether prescriber-level output can go to the field and what happens to derived tables when you leave.

  • List every vendor that needs access
  • Read termination terms

• Total cost of the term

  Licence, extra therapy areas, platform seats, AI or analytics add-ons, integration build and the analyst time to reconcile against your existing numbers.

  • No public list prices
  • Price integration separately

How to test Komodo and IQVIA before you sign

A worked example: three numbers for the same quarter

The figures below are illustrative, chosen to show the pattern rather than taken from any client. Picture an emerging biotech with one specialty brand, a limited specialty pharmacy network and a 30-person field team. Its board asks a simple question: how many new patients started therapy last quarter?

• Specialty pharmacy data shows 1,050 first fills shipped. This is the closest to a true count for the product, but it says nothing about competitors or where patients came from.
• A projected prescription audit shows 1,200 new-to-brand prescriptions. Projection adds an estimate for pharmacies outside the sample, and a written prescription is not a shipped fill, so this number runs higher.
• Linked patient claims show 840 identifiable new patients. Some fills went through channels the claims vendor does not see, and some patients failed the linking or privacy rules, so this number runs lower.

None of the three is wrong. The mistake is putting them on one slide without saying which question each answers. In this example the sensible set-up is: specialty pharmacy data for operational counts and time to therapy, the projected audit for share and incentive compensation, and patient claims for where patients come from and how long they stay. Once the definitions are written down, the gap between the numbers becomes a known, stable adjustment instead of a debate in every brand review.

For this company the larger cost was not either licence. It was building the warehouse layer that holds all three sources with shared definitions, which we describe in our guide to the pharma commercial data warehouse, and linking patients across them with tokens, covered in patient tokenization in specialty pharma.

Common mistakes when buying claims data

• Comparing headline patient counts

  Hundreds of millions of patients across the US tells you nothing about your indication. Only a feasibility count on your definition does.

• Expecting claims to match the audit

  Counted claims and projected audits answer different questions. Pick which number each team reports and document the bridge between them.

• Ignoring the specialty channel

  If your product ships through a limited network, claims can undercount it. Check your SP network against each vendor's coverage before you trust a share number.

• Buying the platform before the question

  An analytics environment or AI assistant is useful once you know what you need answered. License the data that answers your top three questions first.

• Leaving out integration

  Data that cannot join to your CRM, hub and pharmacy feeds becomes a separate set of slides. Budget for the joins as part of the purchase.

• Long first contracts

  Your needs change at launch, label expansion and loss of exclusivity. Keep the first term as short as the vendor allows and renegotiate with usage evidence.

Komodo Health alternatives, and when you need neither

IQVIA and Komodo are not the only patient-level sources. On 8 May 2026 HealthVerity completed its acquisition of Symphony Health from ICON, combining HealthVerity's data exchange and patient identity platform with Symphony's commercial claims and market data, according to HealthVerity's announcement. Teams that already use tokenised data from several suppliers often evaluate it alongside the two incumbents. The same test applies to any of them: one written definition, the same feasibility count, and a check against data you already trust.

You may need neither yet if you are pre-commercial and your questions are about epidemiology rather than prescribers, in which case a one-off study through a vendor's services team or published literature may be enough. The same applies if your product moves entirely through a small specialty pharmacy network, where your own SP and hub data, cleaned and linked, already answers most operational questions. Our specialty pharmacy data analytics work starts there.

You likely need both if you sell globally and also run detailed US patient journey work, or if incentive compensation runs on IQVIA audits while brand and medical teams want daily-refreshed pathway analysis. That is workable, provided one warehouse holds the definitions and every report states its source. If you are also choosing HCP reference data, read our Veeva OpenData vs IQVIA OneKey comparison, since prescriber identifiers from your reference data need to link to whichever claims source you pick.

How Greenwolf helps

We do not resell Komodo, IQVIA or any other data provider and we are not paid by them, so our only interest is that the data fits your questions and your systems. Our founder came up through pharma commercial operations consulting at ZS, and our pharma commercial analytics practice builds the layer that sits between licensed data and the people who use it.

On a claims data decision we write the market definition with you, run the feasibility test on both vendors, score the results and map the integration into your warehouse. After you sign, we build the pipelines, link claims to hub, specialty pharmacy and CRM data through your tokenisation provider, and deliver patient journey analytics dashboards on agreed definitions. For a specialty therapy provider whose identifiers did not line up across sources, clean identifiers and automated pipelines cut manual reporting work by 60 to 80 percent. All of it sits within our wider specialty pharmacy analytics practice.

Questions about Komodo Health and IQVIA