Workflows overview
A Workflow has three parts you configure: a Trigger that starts the work, a Diagram that runs it, and Metrics that measure the outcome. This section covers the ready-made workflows, the catalog of building blocks behind them, and a designer for sketching your own.
| Page | Use it to |
|---|---|
| Templates | Browse ready-made workflows (Cognitive, Genetic, Cardiovascular Testing) |
| Connections | Browse Connections: events, automated actions, and data sources |
| Designer | Sketch a custom Trigger, Actions, and Metrics and send it to us |
| Tags | Standard patient and pathway tags for search and queries |
Connections
Section titled “Connections”Connections are the capabilities you attach to a Workflow: how work can start, what a pathway node can do, and how clinical data enters MedFlow. Browse them in the Connections catalog.
| Type | Product label | Role |
|---|---|---|
trigger | Events | Inbound events that can start or feed runs |
automation | Automated actions | Steps on a diagram node. Featured in templates. Custom with practice-level configuration |
integration | Data sources | Syncs that pull or push data into MedFlow |
The Events catalog holds the inbound capabilities a pathway can react to. Binding one of them to a pathway is what an event trigger (type: event) does.
How they fit
Section titled “How they fit”- Find: Data sources keep search data current so search and queries can locate patients and pathways.
- Automate: A trigger starts a run, and the diagram runs automated actions on nodes.
- Validate: Metrics measure whether care gaps are closing.
MedFlow API
Section titled “MedFlow API”| Need | Docs |
|---|---|
| Find patients and pathways | Search |
| Queries | Queries |
| Inspect diagrams and manage triggers | Diagrams, Triggers |
| Fire web triggers and observe runs | Runs, Quickstart |
| Inbound and outbound webhooks | Webhooks |
| Care-gap and outcome numbers | Metrics |
| Auth, scopes, audit | Authentication, Security |