PICOTS Framework for RWE

PICOTS

extends the classic PICO scaffold of evidence-based medicine with two elements that the randomized-trial world can take for granted but that dominate the validity of a real-world evidence (RWE) study: Timing and Setting. In an RCT the protocol fixes who is randomized, when the clock starts, how long they are followed, and where the data come from.

In a database study none of that is given — it must be reconstructed from claims or EHR records — so PICOTS is less a literature-search heuristic than the master specification from which the eligibility logic, time-zero rule, exposure/outcome algorithms, and the estimand are derived.

Each letter is a contract: P (the cohort and its lookback/washout), I (the exposure strategy and how initiation is coded), C (the reference strategy — usually an active comparator), O (the endpoint and its validated algorithm), T (lookback, washout, induction/latency, grace, follow-up, censoring), and S (the data source(s), care system, geography, calendar window, and the analytic design that ties it together).

Core conceptual distinction

. PICOTS is a framing and specification layer, not an estimation method. Its job is to make the research question answerable and the protocol auditable before any model is fit; it does not, by itself, control confounding, handle time-varying treatment, or define a summary measure.

The single most consequential distinction it enforces is that PICOTS is upstream of the estimand: P + I/C + O pin down three of the five estimand attributes (population, treatment, endpoint); T (timing) informs but does not by itself fix the remaining two — the population-level summary (ATE vs ATT) and the intercurrent-event strategy — which the estimand must still add.

A vague PICOTS therefore guarantees a vague estimand.

Equally, PICOTS is the layer where time-zero is defined — the most common source of avoidable bias in RWE — by forcing T and S to specify exactly when follow-up starts and what enrollment must be observed before it. A second distinction: PICOTS frames a question, whereas the target-trial framework operationalizes that question into a protocol; PICOTS feeds the target trial (eligibility = P + S + T_lookback; assignment = I + C; follow-up + outcome = T + O), it does not replace it.

Pros, cons, and trade-offs

specific and comparative.

• vs an unstructured "research question" paragraph: PICOTS forces each operational decision into the open, exposes the under-specified element (almost always T or S), and makes the protocol reviewable against FDA, ENCePP/EMA, and HTA expectations. Cost: a well-filled PICOTS table can give a false sense of completeness — it names the elements but does not test whether the comparator is clinically interchangeable or whether positivity holds. Prefer PICOTS as the entry point for any RWE protocol; it is nearly free and prevents post-hoc eligibility drift.
• vs PICO (without T and S): plain PICO is adequate for an RCT systematic-review question where timing and setting are fixed by the trials being summarized. In RWE, dropping T re-admits immortal-time and induction/latency errors, and dropping S hides the data-source failure modes (MA-only person-time, EHR leakage) that decide whether the question is even answerable. Prefer PICOTS over PICO for any database study or target-trial emulation.
• vs the target-trial / estimand framework: PICOTS is simpler, faster to communicate, and is the natural front end of both. It is, however, deliberately silent on intercurrent-event handling, the population-level summary (ATE vs ATT), and time-varying confounding — for those you must move down to the estimand and g-methods layers. Prefer PICOTS to scope and align stakeholders first, then refine into a target-trial protocol plus a written estimand. The two are complements, not substitutes.

When NOT to use — and when it is actively misleading or dangerous

.

• As a substitute for an estimand or analysis plan. A complete PICOTS table that omits the intercurrent-event strategy (death, treatment switching, discontinuation) and the summary measure is not a finished design. Treating "we wrote a PICOTS table" as sufficient is how protocols reach analysis with an undefined estimand and an ITT-vs-per-protocol ambiguity discovered only at review.
• When the C element is filled in mechanically. Naming a comparator does not make it valid. If the comparator treats a different indication, a different line of therapy, or systematically different patients, PICOTS will look complete while re-importing confounding by indication and channeling — the bias the design exists to remove. PICOTS does not check interchangeability; clinical review and baseline balance do.
• When T is specified on paper but contradicted by the data's coverage. A 36-month follow-up window in S = commercial claims, where median continuous enrollment is ~2 years, is a specification that the data cannot honor; the gap silently becomes differential administrative censoring. A PICOTS that is internally tidy but incompatible with the chosen S is worse than none, because it confers false confidence.
• For purely descriptive or hypothesis-generating exploration where forcing a single C and a fixed T would prematurely narrow an exploratory aim. Use a looser descriptive frame and reserve PICOTS for the confirmatory question that follows.

Data-source operational depth

.

• Claims (FFS commercial / Medicare FFS): Each PICOTS element becomes code lists plus date logic. P and S jointly set the continuous-enrollment requirement (medical + pharmacy across the full T lookback) so that a "washout" reflects true absence of fills, not unobserved person-time. Failure mode: Medicare Advantage enrollees lack adjudicated FFS claims — utilization and outcomes are largely invisible — so MA-only person-time masquerades as a clean washout and as event-free follow-up; restrict to Parts A/B/D (or a commercial medical+pharmacy benefit) and exclude MA-only spans. I/C from NDC + `days_supply` (watch 90-day mail-order and free samples distorting episodes); procedures from CPT/ICD-10-PCS. Differential competing risks: in elderly claims cohorts, death competes with the outcome and may differ by exposure arm, so a T/O that ignores the competing event biases cumulative incidence — specify it in O, not just the model.
• EHR: P and O can be sharpened with labs, vitals, staging, and notes (NLP), an advantage over claims for a narrow P. But capture is visit-driven: a patient who seeks care elsewhere is differentially lost, so T must define observation windows explicitly and treat loss to follow-up as potentially informative. I is the order/administration, not a dispensing — link to pharmacy fills to confirm the patient actually started, or a "new user" by order may never fill.
• Registry: Cleanest for P (disease severity, stage) and adjudicated O (recurrence, death dates); typically weak for complete I/C utilization and exact timing. Link to claims for the full fill history and to a death index to firm up T (censoring).
• Linked claims–EHR–vital records: The ideal substrate (EHR severity + claims completeness + reliable mortality), but linkage introduces selection (only the linkable subset, which may not match the target P) and order/fill/service date discrepancies that must be reconciled before T can assign a defensible time-zero.

Worked example (oncology new-user cohort, claims logic)

P: adults ≥18 with incident advanced NSCLC, no systemic anticancer fill or administration in a 12-month lookback (= incident/first-line), and 365 days of continuous medical + pharmacy, FFS-observable enrollment before index. I: initiate pembrolizumab + pemetrexed — defined by NDC/HCPCS J-codes; index_date = the first administration/fill of the regimen after the qualifying NSCLC diagnosis.

C: initiate a platinum doublet (regimen code list), same eligibility and the same time-zero rule applied identically. O: overall survival (death from any cause via discharge status + a linked mortality index; a non-fatal claims-only proxy is insufficient for OS).

T: time-zero at regimen initiation; a 30-day induction excludes events plausibly present before treatment could act; follow until death, disenrollment, end of data, or 36 months; for an as-treated contrast, censor at a switch or at last `days_supply` end + a pre-specified 90-day grace, with inverse-probability-of-censoring weights because discontinuation is likely differential by arm; specify death as a competing event for any non-mortality secondary endpoint. S: US commercial + Medicare FFS claims (e.g., Optum/MarketScan-style), 2018–2023, mortality-linked, MA-only person-time excluded, analyzed as a new-user active-comparator cohort with target-trial-emulation structure.

The same six rows, ported to a distributed network (Sentinel/PCORnet via OMOP), keep the question fixed while each site re-maps the code lists and re-checks enrollment semantics — which is exactly the reproducibility PICOTS exists to buy.

Decision diagram

flowchart TD
  Q[RWE question] --> P[P: cohort + lookback/washout<br/>incident disease, continuous enrollment]
  Q --> I[I: exposure strategy<br/>NDC/HCPCS, initiation rule]
  Q --> C[C: active comparator<br/>same indication, same time-zero]
  Q --> O[O: endpoint + validated algorithm<br/>+ competing events]
  Q --> T[T: lookback, washout, induction,<br/>grace, follow-up, censoring]
  Q --> S[S: data source, design,<br/>geography, calendar window]
  P --> EST[Estimand<br/>population]
  I --> EST
  C --> EST
  O --> EST
  T --> EST
  T --> TT[Target-trial protocol<br/>eligibility / assignment / follow-up]
  S --> TT
  EST --> Plan[Reviewable, reproducible<br/>RWE protocol + SAP]
  TT --> Plan

gantt
  title PICOTS Timing (T) made explicit for one new initiator (claims)
  dateFormat YYYY-MM-DD
  axisFormat %b %Y
  section P + S
  Continuous FFS enrollment + disease/exposure-free lookback :done, look, 2023-01-01, 2023-12-31
  section I/C time zero
  First qualifying fill/administration -> arm assignment :milestone, t0, 2024-01-01, 0d
  section T windows
  Induction (events excluded) :crit, ind, 2024-01-01, 30d
  On-treatment follow-up (days_supply + grace) :active, fu, 2024-01-31, 700d
  section Censoring
  Disenroll / death / switch / end-of-data :milestone, cen, 2025-12-31, 0d

Worked example

Scenario

A health outcomes team at a pharmacy benefit manager wants to know whether adults with type 2 diabetes who start a GLP-1 receptor agonist have fewer hospitalizations for heart failure over the following year compared with adults who start a DPP-4 inhibitor. Before pulling any data, the team fills in a PICOTS table to make sure every decision is written down and agreed upon. The table below shows each element and the specific answer the team records.

Dataset

PICOTS table: each row is one element of the framework, filled in for the heart-failure hospitalization question.

Steps

Result

The fully framed research question is: Among commercially insured adults age 18 or older with type 2 diabetes and no prior GLP-1 or DPP-4 use in the preceding 12 months, does initiating a GLP-1 receptor agonist reduce 12-month heart-failure hospitalization rates compared with initiating a DPP-4 inhibitor, evaluated in US commercial claims (2019-2023) with a new-user active-comparator cohort design? Every word in that sentence traces back to a specific row in the PICOTS table, so any reviewer can see exactly which decision produced each word — and flag any box they disagree with before analysis begins.

Trade-offs

Runnable example

from dataclasses import dataclass, field

@dataclass
class PICOTS:
    # P — cohort + lookback/washout. Drives the eligibility query and continuous-enrollment rule.
    population: str            # e.g. "adults >=18, incident advanced NSCLC (>=1 inpatient or >=2 outpatient ICD-10 C34.* >=30d apart)"
    lookback_days: int         # disease/exposure-free lookback that defines 'incident'; e.g. 365
    enrollment_rule: str       # e.g. "continuous medical+pharmacy FFS A/B/D across [index_date-lookback, index_date]; exclude MA-only spans"

    # I / C — exposure and comparator strategies. Become NDC/HCPCS/CPT code lists + the time-zero rule.
    intervention: str          # e.g. "first administration of pembrolizumab+pemetrexed (HCPCS J9271 + J9305) after NSCLC dx"
    comparator: str            # e.g. "first administration of a platinum doublet (regimen code list); same time-zero rule"
    index_date_rule: str       # e.g. "index_date = first qualifying fill/administration; assign arm from that claim"

    # O — endpoint + validated algorithm + competing events.
    outcome: str               # e.g. "overall survival (death any cause)"
    outcome_algorithm: str     # e.g. "discharge status + linked national mortality index; claims-only proxy insufficient for OS"
    competing_events: str = "" # e.g. "death is a competing event for any non-mortality secondary endpoint"

    # T — every clock decision. The most under-specified PICOTS element in RWE.
    induction_days: int = 0    # exclude events in [index_date, index_date+induction_days)
    grace_days: int = 0        # allowable gap before an as-treated episode is considered ended (days_supply end + grace)
    max_followup_days: int = 0 # administrative cap; 0 = until disenroll/death/end-of-data
    censoring_rule: str = ""   # e.g. "censor at disenrollment, death, end of data, switch, or discontinuation+grace (apply IPCW)"

    # S — data source(s), design, calendar window, geography.
    setting: str = ""          # e.g. "US commercial + Medicare FFS claims, mortality-linked, 2018-2023, MA-only excluded"
    design: str = ""           # e.g. "new-user active-comparator cohort with target-trial-emulation structure"
    databases: list = field(default_factory=list)  # e.g. ["MarketScan-style commercial", "Medicare FFS"]

    def validate(self) -> list[str]:
        """Gate the protocol: every element must be filled, and T/S must be internally consistent."""
        problems = []
        for fld in ("population", "enrollment_rule", "intervention", "comparator",
                    "index_date_rule", "outcome", "outcome_algorithm", "setting", "design"):
            if not str(getattr(self, fld)).strip():
                problems.append(f"PICOTS '{fld}' is unspecified — resolve before building the cohort.")
        if self.lookback_days <= 0:
            problems.append("Timing: lookback_days must define the incident/washout window.")
        if self.max_followup_days and self.max_followup_days > 730 and "commercial" in self.setting.lower():
            problems.append("Timing/Setting mismatch: follow-up exceeds typical commercial enrollment "
                            "(~2y) -> differential administrative censoring risk.")
        if not self.censoring_rule.strip():
            problems.append("Timing: censoring_rule unspecified -> undefined person-time and estimand.")
        return problems

Citations

1. [1]Whitlock EP, Lopez SA, Chang S, Helfand M, Eder M, Floyd N. AHRQ Series Paper 3: identifying, selecting, and refining topics for comparative effectiveness systematic reviews. Journal of Clinical Epidemiology. 2010;63(5):491-501.
2. [2]Hernán MA, Robins JM. Using big data to emulate a target trial when a randomized trial is not available. American Journal of Epidemiology. 2016;183(8):758-764.

1. [3]Langan SM, Schmidt SA, Wing K, et al. The reporting of studies conducted using observational routinely collected health data statement for pharmacoepidemiology (RECORD-PE). BMJ. 2018;363:k3532.

1. [4]Berger ML, Sox H, Willke RJ, et al. Good practices for real-world data studies of treatment and/or comparative effectiveness: recommendations from the joint ISPOR-ISPE Special Task Force on real-world evidence in health care decision making. Pharmacoepidemiology and Drug Safety. 2017;26(9):1033-1039.