CQFlow Nodes

Each flow diagram must have exactly one start node.

There can be many end nodes within a diagram, but every flow path must finalize in an end node.

A Sub-Flow is a flow embedded inside another flow. It can be used to modularize a flow diagram, and to create reusable components.

Narrative nodes are used for informational purposes. They can be used to provide documentation and other context about the flow.

The True/False node branches between a True/False execution. True or False must be chosen. The decision point can either be calculated on the backend, or chosen by the user.

The Branch node branches between 2 or more flows paths. Exactly one path must be chosen. Which path is chosen can either be calculated on the backend, or chosen by the user.

The logic tree node allows for a series of AND/OR statements to be defined and constructed into a tree. It can be useful for modelling eligibility or exclusion criteria. The final result branches between a True or False code path.

A fully embedable customizable form. The form itself is built on the backend flow implementation server, and is NOT built inside this UI editor. This generally serves as input for complex and dynamic form inputs such as lab results.

A form field is a single input field. It can be used for simple inputs such as text, numbers, quantities, multi-choice options, or dates. These inputs can then be used by control flow nodes at later points.

The Emit data node is how information is passed back to the caller of the CDS flow. It is the final data response of the flow. It can include recommendations, tasks to be performed, or any other final output

An action to be triggered, such as a medication or lab test order.