Leaders Insights
Leaders Insights

Stay at the top of your field, a little every day.

DomainsMarketingDataFinanceAI
ResourcesLearnTestToolsBlogGlossary
© 2026 Leaders Insights — All rights reserved.
Tracks/Data in biotech and medtech/Data landscape, quality and metrics/Sourcing and licensing external datasets
2/5+150 XP

Data landscape, quality and metrics

5Mapping the biotech and medtech data landscape+1506Sourcing and licensing external datasets+1507Measuring data quality with sector-specific metrics+1508Governing data with FAIR and stewardship metrics+1509Benchmarking analytics and measurement standards+150

Sourcing and licensing external datasets

Sourcing and licensing external datasets

A hospital data science team wants to model 30-day readmission risk after cardiac stent placement. They can license Optum's de-identified claims for roughly the cost of a senior hire, or they can spend nine months negotiating access to MIMIC and stitching together SEER records for free. Both paths are defensible. Choosing wrong burns a year and a budget, and sometimes a regulatory audit.

This lesson is about that choice: when to buy external data, when to build access to public sources, and how to judge fitness for regulated use.

The four datasets you will meet constantly

Before comparing, know the players. These four appear in almost every biotech and medtech data conversation in the US.

SEER (Surveillance, Epidemiology, and End Results): a cancer registry run by the US National Cancer Institute. It covers roughly 48% of the US population across selected states and regions (as of recent NCI documentation, verify current coverage). Free, high quality, gold standard for cancer incidence and survival. Weak on treatment detail and comorbidities.

MIMIC (Medical Information Mart for Intensive Care): de-identified ICU data from Beth Israel Deaconess Medical Center in Boston, published via PhysioNet. Free, but single-institution. Extremely rich (vitals, labs, notes, waveforms) for tens of thousands of ICU stays. Great for method development, poor for national generalizability.

Optum claims: a large commercial and Medicare Advantage claims dataset sold by Optum (part of UnitedHealth Group). Covers hundreds of millions of lives over time. Claims tell you what was billed, not what clinically happened. Commercial license, priced per project or subscription.

MAUDE
(Manufacturer and User Facility Device Experience): the FDA's database of medical device adverse event reports. Free, public, essential for device safety signals. Notoriously messy: voluntary reporting, duplicates, and no denominator (you know the number of reported failures, not how many devices were in use).

Buy versus build: the real tradeoff

"Build" here means investing staff time to access and engineer free or low-cost public data. "Buy" means licensing a commercial dataset that arrives cleaned and documented.

The decision is not mainly about money. It is about four axes.

Coverage

Ask: does the source represent the population you will deploy on?

MIMIC is one Boston ICU. If you train a sepsis model there and deploy in a rural Texas hospital, expect drift. Optum skews toward commercially insured and Medicare Advantage members, so it underrepresents Medicaid and the uninsured. SEER covers cancer well but only in its registry regions.

A concrete rule: match the source population to your target population on age, payer mix, and geography before anything else.

Cost

Public data is free to download but expensive to use. Commercial data is expensive to license but cheap to use.

Worked example. Suppose licensing Optum for a one-year project costs an estimated 250,000 dollars (illustrative, not a quoted price). Building equivalent access from public sources needs 2 data engineers for 6 months.

Loaded cost per engineer/month (fully burdened) = 18,000 USD (estimate)
2 engineers x 6 months x 18,000 = 216,000 USD
Plus 40,000 USD compliance/legal review
Build total ≈ 256,000 USD

The headline costs are similar. The tiebreaker is what you get: the built version is bespoke and you own the pipelinepipelineAll active sales opportunities across the stages of the sales process, together with their combined potential value and probability of closing.View full definition →; the bought version is faster and vendor-supported but recurring. Model the second year, not just the first.

Consent and legal basis

This is where regulated use lives or dies.

In the US, HIPAA (Health Insurance Portability and Accountability Act) governs protected health information. De-identified data (under HIPAA's Safe Harbor or Expert Determination methods) can be used more freely. SEER, MIMIC, and Optum are all de-identified, but the standards and residual re-identification risk differ.

In Europe, GDPR (General Data Protection Regulation) is stricter. Health data is a "special category" requiring an explicit legal basis. "De-identified" under HIPAA is not automatically "anonymized" under GDPR; if re-identification is reasonably possible, GDPR still applies. A US claims dataset licensed for a European trial can trigger a compliance gap here.

MIMIC requires a specific step: completing the CITI (Collaborative Institutional Training Initiative) human subjects research training and signing a data use agreement on PhysioNet before download. Free does not mean frictionless.

The PhysioNet credentialing process is a good concrete example of what a real DUA (data use agreement) looks like.

Fitness for regulated use

If your output supports an FDA submission, a label claim, or a reimbursement dossier, the bar rises sharply.

The FDA increasingly evaluates RWE (real-world evidence) drawn from RWD (real-world data) like claims and registries. Their guidance stresses data relevance and reliability: provenance, completeness, and whether the data captures the clinical concept you claim to measure.

MAUDE illustrates the trap. It is perfect for hypothesis generation ("are we seeing more reports of lead fractures?") and useless as a rate ("our failure rate is X"), because it has no denominator. Using MAUDE to claim a failure rate in a regulatory filing is a classic fitness error.

🎬 [VIDEO: "Real-World Evidence in Regulatory Decision-Making" - youtube.com - FDA and academic overview of how RWD sources are evaluated for submissions]

A quick scoring framework

Score each candidate source 1 to 5 on the four axes, then weight by your use case.

| Axis | SEER | MIMIC | Optum | MAUDE |

|---|---|---|---|---|

| Coverage | 4 | 2 | 4 | 3 |

| Cost efficiency | 5 | 5 | 2 | 5 |

| Consent clarity | 5 | 4 | 3 | 4 |

| Regulated fitness | 4 | 2 | 4 | 2 |

These are illustrative judgments for a typical US analytics project, not universal truths. A method-development team would weight coverage low and richness high, flipping MIMIC's attractiveness. Build your own weights before you score.

For a regulatory submission, weight "regulated fitness" heavily and Optum or SEER pull ahead. For an early algorithm prototype, weight cost and richness and MIMIC wins.

Knowledge check

1. A team needs to model national cancer survival trends and requires the highest-quality incidence and survival data, even if treatment detail is thin. Which dataset is the best fit?

2. Why does the excerpt caution that claims data 'tell you what was billed, not what clinically happened'?

3. MAUDE is described as having 'no denominator.' What analytical limitation does this create?

MULTIPLE CHOICE

4. Select ALL correct answers. A dataset is 'free' like MIMIC but described as poor for national generalizability. Which reasons support this concern?

Select all the correct answers.

MULTIPLE CHOICE

5. Select ALL correct answers. When deciding between licensing commercial data versus building access to public sources, which trade-offs does the lesson emphasize?

Select all the correct answers.

Linkage: the hidden third option

Often the answer is neither pure buy nor pure build. It is linkage.

Tokenization lets you join datasets on de-identified patient tokenstokensA token is the basic unit of text that language models process, often a word fragment, whole word, or punctuation mark rather than a single character.View full definition → without exposing identities. Vendors like Datavant provide this brokering. You can link SEER cancer records to Medicare claims (the real, established SEER-Medicare linked dataset, maintained by NCI and CMS) to get incidence plus treatment plus cost in one view.

SEER-Medicare is worth knowing as a template: it solves SEER's weakness (thin treatment data) by joining to CMS (Centers for Medicare and Medicaid Services) claims. Coverage is limited to the Medicare-age population, so generalizability to younger patients is poor. Every linkage buys richness and costs generalizability somewhere.

Practical due diligence checklist

Before signing any license or downloading any public set, get written answers to:

  • Provenance: where did each record originate, and through how many hands?
  • Refresh cadence: is this a static extract or updated quarterly? Claims lag 3 to 6 months for adjudication (estimate).
  • De-identification method: Safe Harbor or Expert Determination? Who certified it?
  • Denominator: can you compute a rate, or only counts? (The MAUDE lesson.)
  • Right to use for your purpose: many DUAs forbid commercial use or FDA submission. Read the clause.
  • Geographic scope: does the license cover use by your European affiliate under GDPR?

A one-page answer to these six questions prevents most expensive mistakes.

Key Takeaways

  • Match population before price. Coverage mismatch (single-site MIMIC, commercially-skewed Optum) causes model drift that no budget fixes later.
  • Free data has real cost, and buy versus build often converges on similar totals. Run the worked calculation across two years, including compliance and engineering time.
  • De-identified under HIPAA is not anonymized under GDPR. A US license can leave a European compliance gap; check geographic scope in the DUA.
  • Judge fitness by the claim you will make. MAUDE generates hypotheses but cannot supply a failure rate; SEER and Optum carry more weight for RWE submissions to the FDA.
  • Consider linkage as the smart third path. SEER-Medicare and tokenized joins buy richness, but each linkage trades away some generalizability. Name that tradeoff explicitly.

Previous

Mapping the biotech and medtech data landscape

Next

Measuring data quality with sector-specific metrics