1. Help Center
  2. How To's
  3. Engage - Protocol Editor Articles

A guide to designing protocols in Corti: Setting up “automatic documentation” in the Flow-Value-Collector

One of the key value propositions offered by Engage Triage, is the “automatic documentation” collected as the call taker clicks through the flow.

The way this works is by using Flow Value Collectors (FVC) consistently throughout the protocol-building process, and making sure that the documentation output is concise while also being understandable. The FVC works by collecting all information selected or typed in by thee call-taker during a protocol flow. You can have multiple FVC’s if needed.

Tip: Decide on an overall ruleset for what should be documented. Often it is not necessary to document non-issues. For example “The patient does NOT have a headache” is excessive, while actual issues should be documented, e.g. “patient is feeling slight headache”. However, there can be exceptions, e.g. for more vital questions such as “the patient IS breathing normally”, which should be documented.

The basic steps to follow when setting up the automatic documentation are listed below:

  1. Create your needed FVC(s) in the protocol and configure the right-hand documentation overview (Star-feature).
    1. Create an unconnected view node in the start-branch that can be used as the FVC-node, and add your needed FVC-blocks that should go into the right-hand-side overview.
    2. Remember to turn the view node with your FVC’s into a component by right-clicking and selecting “make component”, for easier usage of them during your protocol work.
    3. In the node overview, tick off the “add quick access to the node in Triage” and observe the small star appear on the node. This node, will now represent the right-hand-side documentation overview.
    Screenshot 2023-09-29 at 14.22.12
  2. Use the FVC(s) consistently as you build the protocol. You do that under the Value publisher config functionality (see picture below). 

Remember to use Custom Text Value when needed. Below picture show a flow where a FVC is added to a question, and has been configured with Custom Text Value to add additional context to the documentation so it does not just say “gun” but “Weapon carried: Gun” so that neither dispatcher, first-arriver or call taker is in doubt what the “gun” relates to.

The {value} is always taken from the option selected within the view node. In the example above the {value} is Gun.

Screenshot 2023-09-29 at 14.11.12

Idea: Dependant on whether you select a complete block or just a select-option in a block, you can decide if you are setting up FVC’s for a single answer or for all the answers. In below picture we are setting it up for all the answers.

3. Test, in the Graph-preview, for every card you build that the documentation appears as you want it to.