MedFlow Documentation

MedFlow is a clinical automation platform. It finds patients who are at risk of a care gap, automates the steps of a care pathway to close that gap, and validates whether the gap actually closed.

You build all of this as a Workflow, which has three parts:

Triggerhow work starts→Diagramthe care pathway→Metricsoutcomes you measure

A Trigger decides when work starts, the Diagram is the care pathway that runs, and Metrics track whether it worked. Each part has its own concept guide and API reference:

Part	Start here
Trigger	Triggers · Quickstart
Diagram	Diagram nodes · Diagrams API
Metrics	Metrics · Monitoring runs

Each time a trigger fires, it starts one run of the pathway. The response gives you a runId, which you poll for status until the run finishes.

New here? Start with the Quickstart, read the Architecture, or browse the API, Connections, and Glossary.

How it works

Under every Workflow, MedFlow runs the same loop:

1. Find the patients at risk of a care gap, using search and saved queries.
2. Automate the care pathway that closes the gap, handling the repetitive work so your team can focus on patients (diagram nodes and automated actions).
3. Validate that the gap closed, through metrics and run status.

The building blocks for the pathway come from the Connections catalog: events, automated actions, and data sources.

Browse

TemplatesReady-made workflows for cognitive, genetic, and cardiovascular testing.Browse templates →ConnectionsThe events, automated actions, and data sources you build pathways from.Browse connections →DesignerSketch a custom workflow from tags, actions, and metrics, then send it to us.Open designer →API overviewDiagrams, triggers, runs, search, metrics, webhooks and more information about our API.Open API →

Environments

Environment	Base URL
Production	https://api.medflow.care
Staging	https://api-staging.medflow.care

See the API overview for paths, authentication, and conventions.