Hybrid Effectiveness-Implementation Studies

Definition and scope

Studies that deliberately combine clinical-effectiveness and implementation research objectives, with distinct questions, units, outcomes, and analyses for the clinical intervention and implementation strategy. The target population, use, and analysis remain protocol decisions; this card explains the choices and their consequences rather than approving a study.

Operational specification

Specify the clinical intervention separately from the strategy used to implement it. State the primary aim and hybrid type: effectiveness-focused with implementation observation, dual effectiveness/implementation testing, or implementation-focused with clinical outcome observation. Record implementation context, adoption, reach, fidelity, costs, and patient outcomes with appropriate denominators.

Analysis and diagnostics

Match randomization and inference to the unit receiving each intervention or strategy, often clinics or systems rather than patients. Combine quantitative and qualitative evidence under an explicit integration plan. Examine implementation exposure, fidelity, and context without conditioning a primary randomized clinical effect on post-randomization fidelity by default.

When NOT to use and common errors

Do not call a clinical trial hybrid solely because uptake was reported. An implementation strategy is not the clinical intervention itself. Adoption among participating clinics does not establish reach among all eligible patients or transportability to another system.

Worked example and implementation boundary

A synthetic implementation study has 20 eligible clinics; 12 adopt the intervention under a defined adoption rule. Calculate clinic-level adoption, without treating it as patient reach or clinical effectiveness. Clinic adoption is 0.60, or 60%. Patient reach and clinical outcomes require their own denominators and analyses. The code performs that explicitly stated calculation with synthetic inputs. It is not a complete fitted analysis and does not demonstrate the identification assumptions, estimate sampling uncertainty, or certify application in another population.

Data-source and reporting requirements

Preserve the provenance, dates, units, and observation rule for each input. Claims capture services and transactions under observable benefits; absence of a record is not proof that an event or resource use did not occur. EHR and registry measurements depend on the collection process and may miss care outside the system. Linked sources add reconciliation and selection questions. Primary collection can improve a missing domain but still requires valid measurement and follow-up. Report which of these limitations affects the stated use, which evidence supports the chosen inputs, and what remains uncertain.

Worked example

Scenario

A synthetic implementation study has 20 eligible clinics; 12 adopt the intervention under a defined adoption rule. Calculate clinic-level adoption, without treating it as patient reach or clinical effectiveness.

Dataset

Synthetic inputs with units defined in the scenario; no patient data.

Steps

Result

Clinic adoption is 0.60, or 60%. Patient reach and clinical outcomes require their own denominators and analyses.

Trade-offs

Code example

adopting_clinics = 12
eligible_clinics = 20
result = adopting_clinics/eligible_clinics
assert abs(result - 0.6) < 1e-9
print(result)

adopting_clinics <- 12
eligible_clinics <- 20
result <- adopting_clinics/eligible_clinics
stopifnot(abs(result - 0.6) < 1e-9)
print(result)

data worked_example;
  adopting_clinics = 12;
  eligible_clinics = 20;
  result = adopting_clinics/eligible_clinics;
  put result=;
run;

Citations

1. [1]Curran GM, et al. Effectiveness-implementation Hybrid Designs. Medical Care. 2012.
2. [2]Skivington K, et al. A new framework for developing and evaluating complex interventions: update of Medical Research Council guidance. BMJ. 2021.