Symphony Health vs IQVIA: Choosing Prescription Data After the HealthVerity Deal

Symphony Health vs IQVIA: the short answer

Symphony Health vs IQVIA is a choice between the incumbent prescription data many US field organisations already run on and a challenger that gives you negotiating leverage and now sits inside a company built around linked patient data. Choose IQVIA when your goals, incentive compensation and share reporting must tie to the number your peers, analysts and board already quote, or when you need data outside the US. Consider Symphony Health, now owned by HealthVerity, when you want prescriber-level Rx data linked to medical claims and EMR records under one contract, or when price and flexibility matter more than matching the industry reference number.

Both vendors sell prescriber-level prescription data built from pharmacy transactions with an estimate for the pharmacies they do not see. Neither publishes list prices. The gap between them is less about raw coverage than about method, ownership and what each number has already been used for inside your company. Switching is possible, but it moves territory credit, and that is where most switches go wrong.

This guide sets out each vendor's own published figures, explains what the May 2026 HealthVerity acquisition changes for Symphony customers, shows which source fits which commercial question, and gives you a parallel-run method to test a switch before it reaches anyone's bonus. It is written for commercial operations, sales operations, analytics and finance leads at mid-sized and emerging pharma and biotech companies.

What changed in 2026: HealthVerity now owns Symphony Health

Symphony Health has changed hands three times in under ten years, and each change matters to anyone signing a multi-year data contract.

• September 2017: PRA Health Sciences completed its acquisition of Symphony Health Solutions, agreed in August 2017 for an upfront cash payment of $530 million, according to PRA's SEC filings.
• July 2021: ICON plc completed its roughly $12 billion acquisition of PRA Health Sciences, and Symphony became part of ICON's data business.
• May 2026: HealthVerity announced on 8 May 2026 that it had completed the acquisition of Symphony Health Solutions Corporation from ICON. Financial terms were not disclosed, and HealthVerity's chief executive, Andrew Kress, leads the combined company.

HealthVerity's announcement describes the deal as joining Symphony's commercial insights and scale with HealthVerity's real-world clinical data and patient identity solutions. The Symphony product names (PatientSource, PrescriberSource, PayerSource, Metys, Symphony FLEX, Vantage and Symphony HealthCloud) still appear on HealthVerity's site, and the announcement does not say any product is being retired.

For a buyer, three practical questions follow. Will the Symphony data you license today keep its definitions, history and delivery format? Will prescriber and patient identifiers change as the two companies merge their identity layers? And does the combined company now offer linked Rx, medical claims and EMR data under one contract that previously needed two or three? Ask all three in writing at your next renewal.

IQVIA vs Symphony Health by the numbers

The table uses each vendor's own published material: IQVIA's Xponent fact sheet (2024) and prescription information pages, ICON's Symphony Health product page as published before the sale, and HealthVerity's May 2026 acquisition announcement. We read them in October 2026. Coverage percentages are each vendor's own claims and are not measured the same way.

Do not rank the vendors on these rows. A retail coverage percentage tells you how much of the market a vendor sees before estimation, not how accurate its estimate is for your product. A brand sold mostly through mail order, long-term care or a limited specialty pharmacy network can have very different real coverage from either headline figure. The only comparison that settles it is a test on your own market, described below.

Which prescription data fits your question?

Incentive pay

If reps are paid on prescriber-level volume or share, the data has to be stable, defensible and accepted by the field. IQVIA positions Xponent for setting goals and basing compensation and contests on volume, share and growth, and many US sales organisations already run IC on it. Symphony describes PrescriberSource as supporting targeting and incentive compensation within specific geographies. Either can work; changing source mid-plan year is the risk.

Targeting

For deciding who reps see and how often, what matters is whether the data ranks the same prescribers at the top of your market. Both vendors sell prescriber-level data for this. Score them on overlap with the top deciles you already call on, and on prescribers your field team knows are writing but one source misses.

Patient context

If brand and access teams want to see why a prescription was written and how it was paid, linked Rx, medical claims and EMR data is the point. This is where the HealthVerity combination is aimed, and HealthVerity states that three out of four patients with an Rx are linked to a diagnosis. IQVIA answers the same need with separate patient-level claims products.

Global brand

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

The evaluation scorecard: eight things to test

• Your market, not theirs

  Send both vendors the same written market definition: products, NDCs, competitors, prescriber specialties and time window. Compare national volume, share and prescriber counts, and ask each to explain the gap.

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

• Top prescriber overlap

  Rank prescribers by volume in each source and measure how many of the top 10 percent appear in both. Low overlap means call plans and targets will change if you switch.

  • Overlap by decile
  • Check the misses by name

• Channel coverage for your product

  Ask each vendor what share of your product's volume it sees directly in retail, mail, long-term care and specialty, rather than the headline market figure.

  • Name your SP network
  • Compare to your 867 data

• Lag, cadence and restatement

  Confirm how many days pass between dispensing and delivery, whether data arrives weekly or monthly, and how history is restated when late transactions arrive.

  • Measure on a recent month
  • Get restatement rules in writing

• Identifiers and reference data

  Prescriber IDs must join to your CRM and HCP master. Check whether each feed carries NPI and which reference data it maps to, especially if you use Veeva OpenData or IQVIA OneKey.

  • Sample file before signing
  • Count unmatched prescribers

• Permitted use

  Licences limit which agencies can use the data, whether prescriber-level output can go to the field, and what happens to derived tables when the contract ends.

  • List every third party
  • Read termination clauses

• Ownership change terms

  For Symphony in particular, ask how the HealthVerity integration affects product continuity, identifiers, history and support during your term, and whether you can exit if definitions change.

  • Continuity commitments
  • Change-of-definition clause

• Total cost of the term

  Licence, extra markets or history, platform seats, integration build, and the analyst time to reconcile a new source against numbers the business already reports.

  • No public list prices
  • Price the parallel run

How to test a switch from IQVIA to Symphony (or back) before it touches pay

A worked example: what a switch does to territory credit

The figures below are illustrative, chosen to show the pattern rather than taken from any client. Picture a mid-sized company with one primary care brand and one specialty brand, 120 sales territories and incentive pay based on prescriber-level share growth. Finance wants to know whether moving prescription data from IQVIA to Symphony would save money without damaging the comp plan.

The team loads 18 months of history from both sources into its warehouse and maps them to the same prescriber master and alignment.

• Nationally, the two sources differ by 3 percent on total prescriptions for the primary care brand. Leadership would accept that.
• By territory, the spread is wider. Most territories differ by under 5 percent, but 14 differ by more than 10 percent, mostly where a large mail-order or long-term care account sits.
• By prescriber, 82 percent of the top-decile prescribers appear in the top decile of both sources. The other 18 percent would drop out of, or newly enter, the call plan.
• For the specialty brand, both sources undercount against the company's own specialty pharmacy shipments, so neither is used for that brand's pay. It moves to SP data with a documented bridge.

The simulation shows that 9 of 120 territories would change payout tier on identical rep performance. That is the real cost of switching, and it is why the company either negotiates the savings it needs to justify a careful transition at the plan-year boundary, or uses the test results to negotiate a better renewal with the incumbent. Either outcome is a better position than a renewal signed without the comparison.

The larger cost in this example is not either licence. It is the warehouse layer that holds both feeds against one prescriber master, which we describe in our guide to the pharma commercial data warehouse.

Common mistakes when choosing prescription data

• Comparing headline coverage

  A retail coverage percentage is not accuracy for your product. Test on your own market definition and channels.

• Switching mid plan year

  Changing the data under an active comp plan changes payouts for the same performance. Switch only at a plan boundary, after a parallel run.

• Ignoring the specialty channel

  For limited-distribution products, both vendors may undercount. Your own specialty pharmacy and 867 data is often the better source for those brands.

• Skipping the prescriber master

  If the new feed does not join cleanly to your HCP master and CRM, the difference you see is a matching problem, not a data problem.

• Assuming nothing changes after an acquisition

  Ownership changes can bring new identifiers, merged products or new contract terms. Ask for continuity commitments in writing.

• Using the comparison only once

  A documented bridge between sources is useful every year at renewal, and when a new team asks why two reports disagree.

Symphony Health alternatives, and when you need neither

IQVIA and Symphony are the best-known US prescription audit providers, but they are not the only data a commercial team can use. For patient-level journeys, switching and persistence, claims vendors such as Komodo Health compete directly, which we compare in Komodo Health vs IQVIA. For prescriber reference data, the choice between Veeva OpenData and IQVIA OneKey affects how easily either prescription feed joins your CRM.

You may need neither if your product moves entirely through a small specialty pharmacy network. In that case your own SP dispense, status and 867 data, cleaned and linked, is closer to the truth for your brand than any projected audit, and our specialty pharmacy data analytics work starts there. A pre-commercial company asking market sizing questions may also be better served by a one-off study than a standing licence.

You may need both if incentive pay runs on one source while brand or access teams want linked Rx and claims from the other. That works, provided one warehouse holds the definitions and every report names its source.

How Greenwolf helps

We do not resell IQVIA, Symphony Health, HealthVerity 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 between licensed data and the people who use it.

On a prescription data decision we write the market definition with you, load both vendors' history into your warehouse against one prescriber master, reconcile them from national down to prescriber, and simulate goals and incentive pay on each. After you decide, we build the pipelines, connect the feed to your CRM through Veeva CRM data integration or Salesforce, and deliver brand and territory dashboards on agreed definitions. For a specialty therapy provider whose identifiers did not match across sources, clean identifiers and automated pipelines cut manual reporting work by 60 to 80 percent. All of this sits within our wider specialty pharmacy analytics practice.

Questions about Symphony Health and IQVIA