Accelerating innovation

The community review as clinical trial

When 200 PKU patients reviewing three different medical foods generates a three-arm pragmatic comparison conducted at home. The line between consumer review and real-world evidence is the line of structure and provenance, both of which are engineering choices.

A pragmatic clinical trial evaluates a treatment under real-world conditions rather than under the idealized protocol conditions of an explanatory trial. The pragmatic trial accepts variability in patient adherence, comorbidity, concurrent medication, and care setting, in exchange for evidence that more closely reflects what the treatment will actually do in the population that receives it.

A community review system that captures structured product reviews from the affected community for rare disease products begins to resemble a pragmatic clinical trial when it reaches sufficient scale. Two hundred PKU patients reviewing three different medical food products, with each review structured to capture diagnosis, severity, duration of use, adherence pattern, biochemical impact, gastrointestinal side effects, and overall assessment, generates a three-arm pragmatic comparison conducted by patients in their own homes.

No trial protocol was filed. The dataset still is what the dataset is. The dataset is comparative real-world evidence on the products in question, generated by the population that uses them, with the structure that supports comparison.

What separates a structured review from an unstructured one

The difference is engineering, not philosophy. An unstructured review captures qualitative experience in a free-text form that humans read and that aggregation tools cannot reliably analyze. A structured review captures the same qualitative experience plus structured fields that aggregate computationally.

The fields required for the dataset to function as comparative evidence include the product (with manufacturer, formulation, and dose where applicable), the condition (with subtype where relevant), the contributor's clinical context (severity, comorbidities, concurrent treatments, age range), the duration of use, the outcome being evaluated (the product's intended use), the side effects experienced, and the overall assessment.

The fields are simple. The implementation is engineering. The platform that captures them is the platform that produces the dataset. The platform that captures only the free-text narrative produces consumer reviews; the platform that captures the structured fields produces real-world evidence. The line is the absence or presence of those structured fields.

The free-text narrative is not deprecated by the structured fields. The qualitative experience captured in the contributor's own words is the part of the review that other contributors find most useful and that researchers cannot generate from structured data alone. The platform supports both. The structured fields generate the dataset. The narrative generates the human read of what the dataset means.

What the dataset becomes when scaled

Three transitions happen as the structured review dataset accumulates contributors.

At small scale, dozens to a few hundred reviews per product, the dataset functions as enriched consumer feedback. A prospective buyer reading the reviews gets richer information than the unstructured equivalent provides. Comparative claims at this scale are anecdotal, because the sample size does not support generalization.

At intermediate scale, hundreds to a few thousand reviews per product across multiple conditions, the dataset begins to support comparative effectiveness questions. Aggregate metrics on adherence, biochemical outcomes, and side effect rates have enough sample size to be informative. Cohort comparisons across products, controlled for condition severity and demographic features, become possible.

At larger scale, with thousands of reviews per product over years of use, the dataset crosses into real-world evidence territory. Aggregate analyses meet methodological standards that regulators and payers recognize. The dataset supports formal cost-effectiveness analyses, post-market surveillance contributions, and regulatory submissions in jurisdictions that have established real-world evidence frameworks.

The transition between the scale tiers depends on three things: the rate of contributor enrollment, the rate of review submission per contributor, and the duration of the contributor's engagement. Each is an engineering and design problem on the platform side. The platform that solves these is the platform that produces the dataset. The platform that does not solve them produces consumer feedback that does not aggregate into evidence.

What the regulatory frameworks accept

The FDA's real-world evidence frameworks have evolved substantially since the 21st Century Cures Act in 2016. Real-world data is now defined formally and includes patient-generated data with appropriate provenance. Real-world evidence derived from real-world data is acceptable for specific regulatory purposes including post-market surveillance, label expansion in some cases, and supporting role in efficacy determinations under defined conditions.

The standards required for patient-generated data to qualify as real-world data include data quality (completeness, accuracy, consistency), provenance (who contributed, when, under what consent), and traceability (the audit trail that lets a regulator verify the data). The standards are achievable in a structured review platform. The standards are not achievable in unstructured consumer feedback systems.

The regulatory acceptance of structured review data as real-world evidence is the working frontier. Several FDA documents from 2024 onward explicitly contemplate patient-attributed data of the kind a structured review platform produces. The agency's appetite is positive. The infrastructure that meets the standards is the part that has not been built consistently.

What this means for the manufacturer

The medical food manufacturer that has operated for forty years without comparative outcomes data faces a different market when the data exists. The company whose formula performs worse than its competitor on objective metrics does not have a defense against the data. The company whose formula performs better has a competitive advantage that the previous market could not surface.

The market dynamic is the dynamic that has been absent in rare disease product markets for the entire history of the products. Comparative effectiveness data, generated by the population that uses the products, structured for aggregation, accessible to prospective buyers, and durable across product cycles, is the dynamic that creates the pressure to improve products that has been missing.

The pressure does not arrive through legislation, advocacy, or institutional buyer power. It arrives through the data the customers generate. The platform that captures the data is the platform that produces the pressure. The pressure is the structural shift the rare disease product market has needed for decades and has not been built to produce.