Automated actions
An automated action is a system step that MedFlow runs on a diagram node, such as placing an order in an EHR, messaging a patient, or updating a record.
Every connection is named for the work it represents, not the technical call behind it. You place a step like “create lab order” or “message patient,” and MedFlow handles the translation to the underlying system. This is true across the whole Connections catalog: events, actions, and data sources all read as steps a clinical or business user would recognize, not as API endpoints.
A care pathway is a mix of human steps and system steps, and each system step runs one or more of these actions. Browse the full set in the Connections catalog, or start from a ready-made Workflow template.
In the product
Section titled “In the product”- Place actions on nodes inside swimlanes. See Diagram nodes.
- Featured actions ship in Workflow templates. Custom actions need practice-level configuration.
- See the full list in the Connections catalog.
At runtime
Section titled “At runtime”When a trigger starts a run, MedFlow works through the pathway node by node, running the automated action on each system step. The path is not always a straight line. For example, a Decision node can branch it, a Wait node can pause it, and a Queue node can run a series of steps. What happens at one step (a lab result, a patient response, an eligibility check) decides which step comes next. Track progress through the run’s automationStatus. See Monitoring runs for how to poll it.