1. Healthcare Analytics
  2. Process
  3. Cohort construction to validation
Process · Cohort construction to validation

Cohort construction to validation

Build a cohort revision, load its deidentified facts and accept or reject each one.

Step by step

  1. Check the snapshot Outcomes Analyst

    Outcomes Analyst confirms the source snapshot covering the cohort window is Fresh and its record count matches the extract. A Stale or Failed snapshot goes back to the Data Engineer.

    • Freshness confirmed
    • Updates Source snapshots
  2. Configure the cohort Outcomes Analyst

    Outcomes Analyst creates the cohort with its number, name, cohort date, organization, owner, outcome definition and source record ID. It starts at Configured.

    • Cohort revision created
    • Updates Outcome cohorts
  3. Construct the cohort Outcomes Analyst

    Outcomes Analyst starts the construction workflow from the Healthcare Analytics Overview page or by hand. It deduplicates by operation key, records an operation run with numbered steps, writes the state history entry Status: Configured → Collecting and opens a pending review decision when approval is required.

    • Run recorded, review opened
    • Updates Operation runs, Operation steps, State history, Review decisions
  4. Load the facts Outcomes Analyst

    Deidentified outcome facts are loaded against the cohort with their source reference, observation date, counts and consent basis. Each starts at Outcome = 'Pending'.

    • Facts pending acceptance
    • Updates Deidentified outcome facts
  5. Accept or reject Outcomes Analyst

    Outcomes Analyst moves each fact Outcome: Pending → Accepted or Pending → Rejected and attaches supporting evidence documents.

    • Facts decided, evidence attached
    • Updates Deidentified outcome facts, Evidence documents
  6. Mark the cohort validated Outcomes Analyst

    When every fact has an outcome and the counts reconcile with the snapshot, the cohort moves Status: Collecting → Validated and the change is written to state history.

    • Cohort ready for analysis
    • Updates Outcome cohorts, State history

Where it usually breaks

And how to keep it from happening.

  • Construction is started twice and two runs or two review decisions appear for the same revision.
  • A reloaded extract duplicates facts because the source reference was not used as the match key.
  • Facts without a consent basis are accepted into the cohort.
  • The cohort is marked validated while facts are still pending.
Outcomes Analyst
, Data Engineer, Clinical Reviewer.

Set up Healthcare Analytics your way.

Start free, then use Proto to change fields, steps and approvals before your team goes live.

How to get started