AI Real-World Evidence Regulatory Strategy Playbook

A pharma company has an approved drug with a narrow indication. Physicians are using it off-label in a broader population. The company wants to expand the label using real-world evidence from electronic health records and claims data rather than conducting a new RCT. FDA's RWE framework allows this in specific circumstances.

When to use this playbook

• Use this playbook when the decision looks like the situation above: A pharma company has an approved drug with a narrow indication.
• It is a fit when you have source files in hand and need a structured, reviewable analysis — not a generic chat answer about "Real-World Evidence Regulatory Strategy".
• Do not use it as a substitute for licensed, legal, clinical, or authorized official judgment in the domain.

What you'll need

• Current approved label and indication
• Description of the off-label use population (size, demographics, prescribing patterns)
• Available RWE data sources (EHR database, claims database, patient registry)
• FDA Real-World Evidence Framework guidance documents
• Comparable label expansions supported by RWE

Attachments: Documents (Documents)

You are a regulatory affairs director developing a real-world evidence strategy for label expansion. I am attaching:

Work only from the attached source files. If a conclusion is not supported, say so.

Produce:
1. Assess whether this indication expansion qualifies for RWE support under FDA's framework: what conditions must be met (existing drug, same mechanism, data quality)?
2. Design the RWE study: what data sources, what study design (observational, pragmatic trial), what endpoints, and what confounding controls are needed?
3. Identify the data quality requirements: what FDA expects for EHR/claims data reliability, completeness, and validation before it will accept a regulatory submission.
4. Assess the likelihood of FDA acceptance based on comparable RWE label expansions and current agency posture.
5. Tell me whether to pursue a full sNDA with RWE, request a meeting with FDA's RWE team first, or conduct a hybrid RWE/RCT design.

Call out where independent models are likely to disagree, and list follow-up documents a reviewer should request.

What to expect

• RWE pathway eligibility assessment
• RWE study design with data sources and endpoints
• Data quality requirements and validation plan
• FDA acceptance probability based on precedents
• Strategic recommendation: sNDA, pre-submission meeting, or hybrid design

Review before you act

• Validate this output against source files before relying on it: Assess whether this indication expansion qualifies for RWE support under FDA's framework: what conditions must be met (existing drug, same mechanism, data quality)?.
• Validate this output against source files before relying on it: Design the RWE study: what data sources, what study design (observational, pragmatic trial), what endpoints, and what confounding controls are needed?.
• Validate this output against source files before relying on it: Identify the data quality requirements: what FDA expects for EHR/claims data reliability, completeness, and validation before it will accept a regulatory submission.
• Validate this output against source files before relying on it: Assess the likelihood of FDA acceptance based on comparable RWE label expansions and current agency posture.
• Confirm every cited figure, date, counterparty, or requirement against the attached originals — models compress and can drop a qualifier.
• Treat disagreement between models as a review item, especially on classification, materiality, and recommended next action.
• Do not authorize an operational, clinical, legal, credit, or enforcement action solely because the models agree.