Workflows
A Workflow is the unit you configure in MedFlow. Every Workflow has three parts: a Trigger that decides when work starts, a Diagram that lays out the care pathway, and Metrics that measure the outcome.
Each part has its own concept guide and API reference:
| Part | Where to look |
|---|---|
| Trigger | Triggers, Quickstart, Triggers API |
| Diagram | Diagram nodes, Diagrams API |
| Metrics | Metrics, Monitoring runs |
One note on terminology: in the product UI, pathway or care pathway means the Diagram, not the whole Workflow. You author a pathway as a blueprint in the editor, and a run (runId) is one active copy of that blueprint (sourceId) once work has started. For ready-made clinical workflows, see Workflow templates.
Find · Automate · Validate
Section titled “Find · Automate · Validate”Under every Workflow, the engine runs one loop. Find searches the clinical graph with a query to select the patients or pathways that matter. Automate runs the care pathway for each match, handling the repetitive work so your team can focus on patients, through diagram nodes and automated actions. Validate then measures whether the gap closed, through metrics and run status. Because Find and Validate share the same queries, you measure outcomes against the exact population you acted on.
Lifecycle
Section titled “Lifecycle”- An author builds a blueprint in the diagram editor (see Diagrams).
- A trigger points at that blueprint (
sourceId) and attaches a query, a web trigger, or a webhook. - A run starts whenever the trigger fires, whether from a search or schedule, a web trigger, or a webhook event.
- The run’s
automationStatusmoves through its states until the run finishes. - Metrics show the workflow’s outcomes over time.
Public IDs
Section titled “Public IDs”| ID | Meaning |
|---|---|
triggerId | How work starts (Triggers) |
runId | One pathway run (Runs) |
sourceId | Blueprint the run or trigger came from (Diagrams) |
queryId | Query attached to a trigger (Queries) |
nodeId | Step on a pathway (Diagram nodes) |
automationId | Automated action on a node (Automated actions) |
tenantId / workspaceId | Tenancy (from the API key) |
keyId | API key id on audit events |