Diagram nodes
A MedFlow diagram is the care pathway: composed of nodes and swimlanes. Automated actions on nodes call EHRs, messaging tools, and other capabilities from the Connections catalog.
Swimlanes
Section titled “Swimlanes”Swimlanes come first: each lane represents one owner of the work, whether that is clinic staff, a specialty team, an EHR, a lab, a patient channel, or MedFlow automation. You lay out the lanes, then place nodes inside them.
- A Swimlane is the lane itself, who owns the steps drawn inside it.
- A Contact is assigned to a swimlane. Across runs that assignment can differ, for example each patient in a cohort or each patient’s primary provider, while the pathway shape stays the same.
- A Team groups swimlanes that work together, such as a care team.
- Swimlane
Owner lane for pathway work
Clinic staff, patient, EHR, system automation
- Contact
Person or org on a swimlane
A specific patient, provider, organization
- Team
Group of related swimlanes
Care team, clinic pod, specialty group
Node types
Section titled “Node types”MedFlow has nine pathway step types. The shapes below match the ones you see in the diagram editor.
- Task
Work someone or something performs
Lab order, referral, vitals, fax, eligibility check
- Meeting
People meet before the path continues
Care-team huddle, outreach call, appointment
- Decision
Branch on Yes, No, or custom outcomes
Consent obtained? Eligible? Screen positive?
- Report
A summary from prior steps
Encounter note, claim status, assessment score
- Object
A trackable thing on the pathway
Device, implant, specimen kit, medication
- Queue
Holding place before the next step
Waitlist, referral inbox, prior-auth queue
- Milestone
Marker for a major phase
Intake complete, screening done, gap closed
- Wait
Pause until time or an event
Lab result, ADT discharge, document signature
- Diagram
Open another care pathway
Continuation in another care pathway
Nodes and Connections
Section titled “Nodes and Connections”| On the pathway | In the catalog |
|---|---|
| Node type | Shape and meaning of the step |
| Automated action | What MedFlow executes on that node |
| Event | What can start a run that enters the pathway |
| Data source | How search data stays current |
Example: a Task titled “Create Patient Case” may run the athenaOne Create Patient Case action. A Wait may sit until a Lab Result event advances the run.
FHIR mapping
Section titled “FHIR mapping”A clinical entity in the graph is a resource: a patient, an encounter, an observation, and so on. Resources are what Find searches, and they are distinct from the pathway step nodes above. When MedFlow shows a resource on a pathway, its FHIR resource type maps to a diagram node or swimlane: