Use case · Triggered delivery

Trigger on an event, deliver automatically

An admission, discharge, or new result lands — and the right instrument reaches the right patients the same moment, with no worklist to work and no manual outreach.

The scenario

Every discharge gets a follow-up — automatically

You want every patient discharged from inpatient to get a follow-up assessment within 48 hours. Doing it by hand means someone watches the discharge feed, figures out who qualifies, sends the instrument, and then chases the results — and patients slip through whenever the queue backs up.

ModeClosed loop

Follow-up worklist
  • JD · 4821 PROMIS-10 · concern Needs review
  • BR · 7756 PROMIS-10 · normal Responded
  • EM · 1032 PROMIS-10 Sent

How it works here

The event does the work

  1. Trigger

    A discharge event arrives from the record and starts the workflow instantly — no schedule to wait on, no queue to watch.

  2. Select cohort

    The rule confirms the patient qualifies and has not already had the instrument in the last 48 hours.

  3. Act

    The right instrument — a PROMIS-10 follow-up — is delivered to each patient the moment they qualify.

  4. Route

    The scored result returns to the chart, updates the panel, and alerts the care team when a threshold is crossed.

The outcome

No worklist, no gaps, no chasing

Because the workflow reacts to the event itself, there is nothing to work by hand — no one watches a feed or reconciles who was missed. Every qualifying patient is reached the same moment they qualify.

And the loop closes on its own: the scored result routes back to the record, updates the population, and surfaces the patients who need a clinician’s attention — so the team spends its time on the results that matter, not on moving instruments around.

Wire a trigger to a cohort to an action, then let the workflow run on its own.

Put your follow-ups on autopilot.

Event-driven across the record

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