FDA Participation Guidance: Build a Distinct Handoff for Rare-Disease Re-Enrollment (2026)
TL;DR
FDA's December 2025 Revision 1 of Enhancing Participation in Clinical Trials recommends examining eligibility restrictions and reducing participation burdens while protecting safety and study objectives. These are nonbinding recommendations. They give sponsors questions to resolve in trial design; they prescribe no universal EDC rule, randomization stratum or re-enrollment cap. [1]
For rare-disease programs, the guidance discusses re-enrollment from an early-phase study into a later randomized trial in limited circumstances. It preserves medical and scientific appropriateness, anticipated safety and the expectation that earlier treatment has not changed the disease course. It also identifies selection bias: earlier participants who tolerated or benefited from treatment may be more likely to return. [1]
The operational task is to keep later-trial re-enrollment, an open-label extension and expanded access distinct. Each has a different purpose and decision path. EClinCloud's proposed handoff links the authorized clinical decision, prior-exposure evidence, new study participation and analysis plan without inventing an automatic eligibility rule or a cross-study identity mandate.
Broadening starts with a justified trial decision
The participation guidance addresses clinical trials intended to support new drug applications or biologics license applications. It discusses demographic and non-demographic characteristics, including comorbidities, organ dysfunction, disability and rare conditions. Its recommendation is to examine whether an exclusion serves participant safety or the study objective and to consider modifying unnecessary restrictions. [1]
That question belongs in the protocol-development process. A study team may decide that an exclusion remains justified, that a more specific measure is appropriate, or that a broader population can be studied using a suitable design. The electronic system implements the authorized decision. A newly published guidance document supplies no authority for a builder to alter an active study's eligibility rules.
There is a useful distinction between a design recommendation and a testable build specification. "Review prior-exposure exclusions" is a design task. "Record the prior study and the clinical review required by this protocol" is a possible build task after the sponsor defines the rule. Converting the first statement directly into a binary system rule would skip the scientific decision that the data need to preserve.
The guidance also recommends reconsidering restrictions as knowledge of the investigational product develops. Available safety, metabolic and interaction information can affect the rationale for exclusions. The implementation record should consequently identify which protocol version and approved rationale apply to a particular screening decision. [1]
This report concentrates on the rare-disease handoff. Disease-specific eligibility thresholds, including the separate oncology guidance discussed in EClinCloud's eligibility report, require their own drug- and protocol-specific assessment. Repeating a broad eligibility template across those settings would obscure the distinct decisions.
Distinguish three routes before configuring the workflow
FDA discusses rare-disease re-enrollment, open-label extensions and expanded access in different contexts. The distinctions affect the study record as well as the participant conversation. [1] [2]
| Route | Purpose and source boundary | Operational question to settle |
|---|---|---|
| Re-enrollment into a later randomized trial | A new trial participation decision in the limited rare-disease circumstances described by the guidance | What prior exposure and medical/scientific assessment does the later protocol require? |
| Open-label extension | A study arrangement the guidance recommends considering after early-phase studies, with broader inclusion criteria | Which extension protocol, eligibility, consent and follow-up plan apply? |
| Expanded access | Treatment use of an investigational drug under its applicable criteria, rather than the ordinary trial-evidence purpose | Which treatment-use authorization and records apply, and how are they distinguished from trial enrollment? |
The table is an operational synthesis of the guidance and expanded-access framework. It supplies no automatic right to treatment, extension enrollment or later-trial entry. [1] [2]
A participant completing an early study may be considered for more than one future option. The study team should identify the actual route and its conditions before it creates a new visit schedule or randomization record. A generic status called "continued participation" can collapse an extension, a new randomized trial and treatment access into the same operational category.
The distinction is also important for communications. A description of an available extension should reflect the approved design and access conditions. It should avoid implying guaranteed investigational treatment or implying that prior participation itself establishes eligibility for a later trial.
For a system partner, the first question is therefore about the authorized pathway. Once that is clear, the team can specify which records are new, which prior evidence is relevant and which decisions require review. The technology has a defined recordkeeping and workflow role within that process.
Keep prior exposure and the new decision separate
The rare-disease section gives a specific reason to examine earlier treatment: it may affect safety, the disease course and interpretation of later trial findings. It also asks sponsors to consider how selection of earlier tolerators or responders may affect the safety assessment. The proportion re-enrolled, considered with the population's safety and tolerability information, can inform that assessment. [1]
Those observations justify a study-specific prior-exposure plan. They establish no universal percentage cap, mandatory stratification scheme or fixed list of EDC fields. The protocol, statistical analysis plan and medical review determine which information is needed and how it will be used.
EClinCloud proposes organizing the handoff around four distinct objects:
- The earlier participation and exposure evidence that the later trial is authorized to use.
- The later trial's applicable eligibility criteria and required clinical assessment.
- The new participation decision, including the relevant protocol and consent context.
- The analysis treatment of prior exposure and re-enrollment under the approved plan.
The distinction prevents a prior participant's historical "eligible" status from being reused as the later trial's decision. It also lets a reviewer identify uncertainty in the earlier record without silently converting it into a favorable answer.
Identifiers need their own design. A sponsor may need an appropriately controlled way to relate records across studies, but the participation guidance creates no instruction to reuse a single USUBJID across every study. The data standards, privacy permissions, consent and authorized identity-management process need to be assessed together. A common person relationship and a study-specific participation record are different concepts.
The implementation should also retain the difference between known prior exposure, no known exposure and insufficient information. Where the protocol requires a medical assessment, the workflow should preserve its status and authorized outcome. Randomization requires the authorized assessment outcome as well as completion of the relevant data fields.
Compare prior-treatment situations before authorizing the new handoff
These are guidance-derived hypothetical cases for a later rare-disease trial. Actual clinical thresholds and eligibility decisions remain with the approved study process. The medical/scientific assessment must address the guidance's conditions and the later protocol. [1]
| Prior-study situation | Question for the authorized review | Distinct downstream output |
|---|---|---|
| Earlier treatment is documented and the required review supports that prior treatment did not alter the disease course | Are the other safety, scientific and protocol conditions also met, with selection of prior tolerators/responders considered? | Record the protocol-specific review outcome; permit the next operational step only when the authorized conditions are satisfied |
| Earlier treatment may have a persistent effect on disease course | Does the evidence support the condition described by FDA for the proposed re-enrollment approach? | Keep the question with the medical/design owner; the review must establish that the condition is met, beyond completion of an exposure field |
| The earlier study remains blinded and treatment assignment is restricted | Who, if anyone, is authorized to review necessary prior information without compromising the continuing blind? | Give blinded downstream staff only the approved minimum decision information; keep transfer of the prior assignment subject to the authorized disclosure process |
| The earlier exposure or relevant assessment is incomplete | What evidence is missing and who can lawfully obtain and assess it? | Preserve a pending/unknown outcome and route the unresolved assessment; avoid converting missing evidence into a favorable eligibility answer |
Proposed review outputs, conditional on the actual study design. They distinguish an evidence-supported decision, a consequential prior effect, a blinding constraint and an information gap. [1] [3]
Privacy permission and maintenance of the study blind are separate controls. The plan should identify the authorized medical or other appropriately independent reviewer of potentially unblinding information, the minimum output available to the blinded team, and the access and decision records retained. Access to or unblinding of the earlier assignment requires authorization under the earlier trial's applicable process. Any access or disclosure must follow the applicable protocol, permissions and authorized process. ICH E6(R3)'s data-governance and blinding principles supply the general boundary; it prescribes no universal cross-study identifier or automatic transfer architecture. [3]
For example, “assessment pending” may be sufficient for the receiving workflow to pause the next authorization while the restricted reviewer resolves the question. The system need not display the old assignment to every person who can see that status. The study team must also assess whether a proposed status or message would indirectly reveal protected information; document how the proposed outputs preserve the blind in the actual workflow.
The earlier record and the later participation decision remain distinct even after the review is complete. A later protocol amendment may change what must be assessed; retain the earlier exposure and permission history alongside the new decision. For an applicable US IND amendment, use the responsible clinical/regulatory assessment under 21 CFR 312.30, including its separate immediate-hazard provision. [4]
Keep accessibility decisions attached to the selected route
FDA also discusses flexible visits, electronic communication, record transfer with appropriate consent and ways to reduce travel burden. These options need study-specific evaluation of safety, assessments and the study objective. The oncology eligibility report covers a different disease-specific application; its thresholds should not be imported into the rare-disease comparison above. [1]
Electronic consent can support an authorized process, but a remote signature alone establishes neither understanding nor permission for every cross-study disclosure. Retain the consent and discussion arrangements appropriate to the participant and distinguish those permissions from any continuing-blind restriction. [1] [5]
Method and limits
This report reads the final December 2025 Revision 1, particularly its eligibility, burden-reduction and rare-disease sections, alongside the relevant expanded-access, protocol-amendment and electronic-consent sources. It distinguishes nonbinding recommendations from cited regulations and from EClinCloud's proposed implementation controls. [1] [2] [4] [5]
The scenarios are hypothetical. The analysis contains no patient-level data, measured recruitment effect or validated re-enrollment algorithm. Broad counts from trial registries or guidance catalogues would provide no evidence that a particular design needs a given system control, so those counts have been excluded.
For an EClinCloud study-services discussion, bring the proposed participation route, protocol criteria, prior-exposure questions, consent context and analysis needs. Ask the implementation team to show one complete and one unresolved handoff across the required study systems. That gives the sponsor a concrete acceptance exercise while preserving medical, statistical and regulatory decision ownership.
Sources
1. FDA. Enhancing Participation in Clinical Trials — Eligibility Criteria, Enrollment Practices, and Trial Designs, final guidance, Revision 1, December 2025. Sections II–IV; nonbinding recommendations.
2. Electronic Code of Federal Regulations. 21 CFR part 312, subpart I: Expanded Access to Investigational Drugs for Treatment Use. Treatment-use framework and applicable criteria.
3. FDA. E6(R3) Good Clinical Practice, September 2025, section 4 on data governance and the applicable blinding safeguards.
4. Electronic Code of Federal Regulations. 21 CFR 312.30: Protocol amendments, including paragraph (b). Applicable amendment and implementation conditions.
5. FDA and OHRP. Use of Electronic Informed Consent in Clinical Investigations — Questions and Answers, December 2016. Electronic-consent processes and participant understanding.
