Search
Request a Quote

Drug-Diagnostic Co-Development: Why It Matters

Resource Article | Integrated CDx Development

Drug-Diagnostic Co-Development: Why It Matters

A companion diagnostic and its corresponding therapy are operationally separate products, yet their evidence is interdependent. The drug program defines the treatment hypothesis and clinical population; the diagnostic defines how that population is identified. If assay development lags, changes late, or measures a different biomarker interpretation than the trial used, both programs can face enrollment delays, bridging burdens, and uncertain labeling.

Co-development aligns therapeutic, biomarker, assay, regulatory, clinical, manufacturing, and commercialization decisions from the beginning. This article explains why synchronization matters, where programs commonly diverge, and how enzyme and reagent controls support a reliable transition from exploratory testing to an approved treatment-linked assay.

The Drug and Test Share One Clinical Hypothesis

The central question is whether a defined biomarker result identifies patients for whom a therapy is safe and effective. The therapy’s mechanism supports the hypothesis, but the diagnostic result operationalizes it. Biomarker definition, specimen, cutoff, test failure rules, and timing must therefore agree with the clinical protocol and proposed labels.

A biomarker may begin as an exploratory variable and later become an enrollment requirement. That transition changes the assay’s role. Research-use performance may be adequate for hypothesis generation but not for treatment selection. Co-development recognizes this shift early enough to establish design controls, representative specimens, locked algorithms, critical-reagent supply, and regulatory interactions before pivotal evidence depends on the test.

Stage-gated drug diagnostic co-development model

Figure 1. Companion diagnostic development and regulation concomitant with drug therapy development and regulation. (Luo et al., 2016)

What Must Be Synchronized

WorkstreamDrug program questionDiagnostic dependency
Target and biomarkerWhich biology predicts benefit or risk?Analyte, method, specimen, and decision rule
Clinical strategyWho enters or is stratified in the trial?Enrollment test availability, turnaround, invalid handling
Evidence planWhich endpoints support the therapy claim?Analytical validity and clinical performance of the test
RegulatoryWhat are submission and review milestones?Coordinated interactions, modules, labeling, and responses
ManufacturingWhen are clinical and commercial lots needed?Controlled enzyme/reagent supply and comparability
LaunchWhere and when will therapy be available?Laboratory access, training, logistics, reimbursement readiness
LifecycleHow will new claims or populations be added?Change control, bridging, new specimens, platforms, or cutoffs

Begin with a Joint Development Plan

One set of linked decisions

A joint plan identifies owners, interfaces, evidence dependencies, decision gates, and fallback paths. It should cover biomarker assay evolution, clinical sample access, regulatory meetings, investigational testing, diagnostic validation, manufacturing scale-up, submission timing, and launch readiness.

Dependencies should be explicit. For example, cutoff selection may require clinical outcomes; pivotal enrollment may require a locked assay; commercial transfer may require sufficient retained specimens for bridging. Drug–diagnostic co-development support is designed around these connected milestones.

Control Assay Evolution Before Pivotal Use

Early assays often change as biomarker knowledge improves. Primers, antibodies, enzyme mixes, platforms, software, specimen requirements, and cutoffs may evolve. Change is expected, but uncontrolled change makes it difficult to connect trial results to the final commercial test. Each version should be documented with its samples, performance, algorithm, and role in clinical decisions.

A fit-for-purpose research assay can support discovery. Before an assay determines trial enrollment or treatment assignment, the team should define analytical acceptance criteria, training, quality controls, invalid-result procedures, and change governance. The goal is not premature freezing; it is preserving traceability and scheduling necessary bridging while specimens and clinical data are still available.

Clinical Trial Operations Depend on Diagnostic Reliability

Enrollment

Turnaround time, tissue sufficiency, screen-failure rate, and invalid results affect recruitment and site performance.

Interpretation

Sites need clear specimen, result, retest, and conflict-handling instructions that match the protocol.

Specimen bank

Consent, chain of custody, quality, storage, and outcome linkage preserve material for cutoff work and bridging.

Prevalence estimates should come from representative populations and the intended assay where possible. A lower-than-expected positivity rate can expand screening needs; a high invalid rate can bias enrollment. Central versus local testing changes logistics and variability. Trial simulations using realistic prevalence, sample failure, and turnaround assumptions help expose bottlenecks before activation.

Enzyme and Reagent Readiness

Critical enzymes may influence sensitivity, specificity, stability, or lot consistency. A clinical program should not depend on poorly characterized or non-scalable material. Specifications need to connect identity, purity, activity, contaminants, formulation, storage, and functional performance to the assay. Supplier changes, process changes, and formulation changes require notification and risk-based bridging.

CDx assay transfer and manufacturability assessment can reveal scale-up risks, while enzyme scale-up and technology transfer supports commercial readiness. Stability planning should include clinical-trial duration, shipping, laboratory storage, on-board use, and launch inventory—not only an initial feasibility window.

Regulatory and Labeling Alignment

Regulators evaluate the therapeutic and diagnostic evidence in relation to each other. The intended-use population, biomarker definition, specimen, cutoff, and limitations should be consistent across protocol, statistical plan, diagnostic submission, drug submission, and proposed labeling. Teams should plan coordinated questions and avoid assuming that conclusions reached for one product automatically settle the other.

When the clinical trial used a test different from the final CDx, bridging may address analytical agreement and the likely clinical impact of discordance. The required evidence depends on the nature of the differences and available samples. Early agency interaction is especially important for novel analytes, composite algorithms, limited specimens, decentralized testing, or development paths that cannot launch the diagnostic at the same time as the therapy.

A Stage-Gated Co-Development Model

  1. Discovery: establish biological rationale and evaluate biomarker measurability.
  2. Feasibility: select platform, specimen, preliminary cutoff approach, and critical reagents.
  3. Clinical readiness: define assay version, site workflow, controls, supply, and investigational-use responsibilities.
  4. Pivotal execution: monitor assay performance, deviations, invalids, and sample accountability.
  5. Validation and submission: complete analytical studies, clinical analyses, manufacturing evidence, and coordinated dossiers.
  6. Launch and lifecycle: assure test access, training, complaint handling, change control, and expansion strategy.

Common Failure Modes and Practical Controls

Late platform changes create bridging work; unclear biomarker definitions create data inconsistencies; limited tissue prevents repeat testing; underdeveloped reagents create lot drift; and separate timelines can leave an effective therapy without a ready test. These problems are connected and should be managed in one risk register.

Useful controls include a cross-functional governance group, common terminology, versioned assay specifications, a decision log, reserved specimens, backup supply, predefined change thresholds, and integrated milestone reviews. Biomarker assay feasibility and prototype development can test assumptions early, while CDx technical documentation and regulatory support helps preserve traceability as the program matures.

Questions to Ask at Every Program Review

  • Does the current test measure the biomarker definition used in the therapeutic hypothesis?
  • Will the finalized assay, specimen, cutoff, and algorithm match pivotal clinical use?
  • Are critical enzymes and reagents controlled, scalable, stable, and available for the program timeline?
  • Are enough representative specimens reserved for validation and bridging?
  • Do protocol, statistical analysis, diagnostic plan, and proposed labels use consistent rules?
  • Could diagnostic turnaround, access, or invalid rate limit clinical trial or launch success?
  • Have recent changes been assessed across both products rather than within one functional team?

Development Controls for Drug-Diagnostic Co-Development: Why It Matters

Whatever platform or specimen is selected, development should begin with a written link between intended use and analytical requirements. Define the patient population, biomarker, specimen, treatment decision, reportable result, turnaround expectation, and use environment. Then identify the failure modes that could change classification: target loss, nonspecific signal, amplification bias, reagent drift, interference, software error, or an invalid result that delays therapy. This risk map determines which enzyme attributes and assay controls deserve the most attention.

Feasibility experiments should include representative clinical material as early as possible. Purified templates and synthetic controls are valuable for isolating variables, but they do not reproduce fixation damage, low tumor fraction, endogenous inhibitors, sample heterogeneity, or extraction carryover. A staged study can begin with controlled materials, add individual challenges, and then confirm performance in specimens spanning the intended range. Samples near the cutoff are especially informative because small shifts in recovery, background, or signal can change the treatment category.

Critical enzymes should be specified by more than catalog activity. Identity, purity, concentration, specific activity, contaminating nuclease or protease limits, formulation, storage, and functional performance may all be relevant. The release method should use conditions that predict performance in the diagnostic reaction. When the vendor activity assay and CDx chemistry differ substantially, an assay-level incoming or bridging test can provide a more direct control. Multiple lots should be evaluated before pivotal use so the acceptance range reflects manufacturing variation rather than one favored batch.

Robustness studies intentionally vary parameters that will move in practice: reaction time and temperature, pipetting, sample input, operator, instrument, reagent lot, shipping excursion, and storage duration. Interference studies should use justified concentrations and combinations of endogenous substances, collection additives, medications, and process residuals. Controls must fail when the vulnerable step fails; an abundant control target may remain positive even when a low-copy clinical target is lost.

Finally, document changes across the full measurement system. A new enzyme lot, buffer, primer pool, conjugation process, extraction kit, instrument, or software version can alter analytical performance even if the intended use is unchanged. Risk-based comparability should focus on the attributes most likely to affect the cutoff and claimed range. Preserving retained samples, reference materials, version history, and a predefined bridging strategy makes lifecycle improvements possible without breaking the connection to the clinical evidence.

Questions for Design Review

  • Does the assay measure the same biomarker definition used in the therapeutic hypothesis and clinical protocol?
  • Are the specimen pathway and enzyme system challenged with realistic low-input, damaged, inhibited, and near-cutoff samples?
  • Can each control distinguish extraction, conversion, amplification, detection, instrument, and interpretation failures?
  • Do raw-material specifications predict final assay behavior, and are multiple lots represented?
  • Are cutoff, invalid, repeat, and discordant-result rules prespecified and understandable to users?
  • Can the critical reagents be manufactured, shipped, stored, and supported for the clinical and commercial timeline?
  • Is every change traceable to an analytical, clinical, labeling, and regulatory impact assessment?

These questions keep development centered on the treatment decision rather than isolated technical metrics. They also create a common language for biomarker, clinical, regulatory, quality, manufacturing, and supplier teams.

Conclusion

Drug–diagnostic co-development matters because a biomarker-guided therapy can succeed only if the right patient is identified with a reliable, available test. Joint planning preserves the link between biology, clinical evidence, assay performance, manufacturing, and labeling. It also gives teams time to solve reagent, specimen, bridging, and access problems before they become critical-path launch risks.

Build the Enzyme System Around the CDx Requirement

Creative Enzymes supports diagnostic enzyme selection, engineering, formulation, conjugation, analytical evaluation, and scale-up for molecular and immunoassay CDx workflows.

References

Online Inquiry

For research and industrial use only, not for personal medicinal use.

Submit