Use case · Cohort & registry

Build a registry from the chart, keep it current

Describe the patients who matter as a clinical rule, and EVAL matches them from live chart data into a registry that maintains itself — no report to re-run, no spreadsheet to reconcile.

The scenario

A diabetes registry that never goes stale

Your team wants every patient with poorly-controlled diabetes on one panel — but the list is out of date the moment it's built. New labs land, problems resolve, patients transfer, and someone has to keep re-querying the chart to know who actually qualifies today.

ModePopulation only

Diabetes registry
  • DW · 3410 A1c 9.4 · two readings Enrolled
  • HK · 8852 A1c 9.1 · two readings Enrolled
  • PN · 1207 A1c 8.8 · improving Candidate

How it works here

From a rule to a living panel

  1. Trigger

    A nightly refresh re-evaluates the rule against the latest chart data — no one kicks it off by hand.

  2. Select cohort

    Patients whose A1c crosses 9.0 on two readings enter the registry; those who improve or resolve drop off automatically.

  3. Act

    Download the panel as CSV for the care team, or open it as a live worklist in the registry builder.

  4. Route

    Hand the same cohort to an automation so qualifying patients flow straight into outreach or an assessment.

The outcome

One rule, always-current, zero maintenance

A registry built this way is never a snapshot. Because the rule reads the chart directly, the panel reflects the population as it is right now — every new lab, resolved problem, and transfer is already accounted for the next time it runs.

The care team stops reconciling lists and starts working the patients. Cohort, panel, and registry are the same object at different sizes, so the panel you download is the exact set an automation can act on — nothing is re-derived or lost in a hand-off.

Compose clinical predicates into a registry that stays current without anyone maintaining it.

Build your first registry in minutes.

Matched against live clinical data

  • EHR Reads across EHRs
  • FHIR Standards-based data
  • HIPAA Compliant by design