Add documentation to your care flow

Record why a care flow is built the way it is, so the clinicians who use it later understand the reasoning behind it.

Building a care flow means deciding what actions, steps and data collection to include. The clinicians who use that flow in practice were usually not in the room for those decisions, so documentation carries the reasoning to them and travels with the care flow.

Record the decisions and the evidence behind them

The choices made, and why. Especially the ones that look arbitrary from outside.
Clinical publications backing a decision, so the evidence sits next to the thing it justifies.
Context the clinician needs to work the flow confidently.

Write what a colleague changing this flow in a year would need to know to avoid undoing something deliberate.

Document at the level the decision belongs to

Open the care flow, step or action to document, and write the documentation in its side pane.

A reason that applies to the whole flow belongs on the flow rather than repeated on every step.

Documentation is not a sticky note

The two look similar and serve different purposes:

Documentation is durable: it's for whoever uses or maintains the flow later.
Sticky notes are for the author during the build.

Next steps

Next: Add a sticky note for the reminders that shouldn't outlive the build.