Synthetic clinical data reality check—not so fast, data replacers

In Part 1 of this blog post, we mapped healthcare’s market for clinical data—a.k.a “Real World Data” or RWD. We looked at a bunch of the key components, including: The different types of clinical data, including who owns usable data (providers, payers, EHR vendors, multi-source aggregators). 

Amanda Berra
Amanda Berra
Updated Sep 2, 2025 13 min read

Quick rewind: Our tour of the clinical data market that ended in a cliffhanger

In Part 1 of this blog post (linked below if you missed it!), we mapped healthcare’s market for clinical data—a.k.a “Real World Data” or RWD. We looked at a bunch of the key components, including: The different types of clinical data, including who owns usable data (providers, payers, EHR vendors, multi-source aggregators). Why health systems have found what seems like a proprietary “data goldmine” to be so hard to monetize. And, how third-party aggregators have stitched together nationwide, longitudinal data sets that life-science, tech and payer buyers are willing to pay for. And THEN came the cliffhanger: in theory, AI can now generate statistically identical, privacy-risk-free “synthetic” data sets.  Essentially, generated data that has all the characteristics of RWD, but isn’t RWD. On paper, synthetic clinical data seems to solve a lot of the pain points associated with the real thing—HIPAA worries, consent barriers, data breach headlines, six-figure license fees—so…is the market for actual clinical data about to be ruined? Today we tackle that question head-on.

Missed part 1 on the “Real World Data” market? Catch up by clicking here.

Let’s talk.

Questions? Want to learn more about what Union can do for you? We’d love to hear from you.