back to work

Pharmaceutical data-matching platform

A three-month launch that reduced regulatory data-review time by 99% across more than 50,000 FDA product records.

UC Law Center for InnovationSep 2025 — Jun 2026Product Manager · architecture, roadmap, validation, telemetry2 engineers · 1 ML specialist · 1 researcher · 2 sponsorsproduction
99%reduction in review time
50K+FDA records reconciled<2 minpipeline runtime90%lower token consumption

The reconciliation problem

Researchers spent three working days reviewing 50,000+ records. A full-LLM approach added hours of latency and unsustainable API cost, while early deterministic rules produced too many false positives.

Research managers reconciling monthly FDA Orange Book updates across fragmented source systems.

My product scope

  • Designed the tiered matching and LLM-routing architecture
  • Created the PRD, user stories, roadmap, and acceptance criteria
  • Translated research constraints into validation and exception workflows
  • Delivered Firebase authentication and Google Analytics telemetry
  • Coordinated production rollout and post-launch measurement

A deterministic-first architecture

source data50K+ recordsinconsistent fields
deterministic rules95% resolvedstrictly calibrated
remaining 5%
LLM proposaloptional human review

Six discovery sessions shaped a tiered engine that standardized 25–30 attributes, resolved 95% of records deterministically, and routed only ambiguous cases to an LLM and review queue.

Where automation should stop

evaluation framework

Optimize for trustworthy automation, not maximum automation

production workflow95% deterministicstable cases resolved without an LLM
ambiguity route5% LLM fallbacksource evidence remains visible
failure modecostproduct responsefalse positive match

incorrect data enters downstream research

tighten agreement thresholds

ambiguous record

rules cannot defend a match

route to the LLM and review state

source conflict

automation cannot resolve evidence

preserve source fields for a researcher

The matching workbench

matching workbenchrecord comparison
batch 04 · 50k records
source record
drug namecardiovex
exact
ingredientmetoprolol
exact
strength50 mg
exact
dosage formtablet
partial
applicationANDA 20481
exact
deterministic matchconfidence 0.98matched automatically
candidate record
product namecardiovex
exact
active ingredientmetoprolol
exact
strength50 mg
exact
dosage formoral tablet
partial
applicationANDA 20481
exact
ambiguous example dosage form and application conflict
rules inconclusiveLLM fallbackhuman review

A sanitized reconstruction of the interface where researchers inspect evidence, resolve ambiguity, and export matched records.

Product decisions

Reserve the LLM for ambiguity

Resolve stable cases with deterministic rules and route only the remaining 5%. The tiered architecture reduced latency, token consumption, and audit risk.

Alternative considered: Send all 50K+ records through an LLM or keep the workflow fully manual.

Trade-off: Explicit rules required calibration and maintenance, but cut token consumption by 90%.

Recalibrate before scaling

Tighten agreement thresholds after false-positive testing. Incorrect matches were more costly than leaving an ambiguous record for review.

Alternative considered: Accept the first-pass rule set or add broader fuzzy matching.

Trade-off: Stricter rules preserved a small review queue but made automated decisions more defensible.

Outcome

Review time

Regulatory data-review time fell by 99% during the first 30 days after launch.

Runtime

Pipeline execution dropped from two–three hours to under two minutes across 50K+ records.

Cost

Routing only ambiguous cases reduced LLM token consumption by 90%.

measurement notes

Definitions and sources are shown so every result can be examined in an interview.

99% less review time

Measured during the first 30 days after launch against the prior three-working-day review workflow.

95% deterministic coverage

Share of 50K+ FDA records resolved by calibrated deterministic rules before LLM routing.

under two minutes

Observed full-pipeline runtime, reduced from a two–three-hour baseline.

90% lower token consumption

Measured reduction after replacing full-LLM processing with ambiguity-only routing.

The highest-value AI decision was defining where not to use AI: deterministic rules handled scale, while the LLM handled ambiguity.