Show a list of lumabotFlows

the ID of the patient who filled out the answers for this flow.

The completion status of the lumabot flow under the patient's perspective, knowingly:

• started: when the patient started answering at least one question, but hasn't finished the flow yet;
• completed: the patient has finished answering all the questions and cannot edit the flow anymore.

the date/time when the patient finished all the responses of this flow.

the ID of an appointment related to this flow.

the ID of a fileUpload related to this flow.

deprecated: custom lumabot flow url, basically to identify any patient in survey monkey, an external flows service that's not being used anymore by Luma.

The code of the current question the patient was last shown, before answering it. Such a code must be the content of any questions[x].id, or success. Usually this will contain each id, in sequence, but patients can go back and forth. Also, flows can have jump logic, and some questions might not be displayed to the patient. When the flow is completed, this is updated to success.

the ID of the template of questions that was displayed for the patient.

the name of the template of questions used as a basis for these flow answers. See lumabotFlowTemplates.

The language in which the flow was answered by the patient.

IP address of the patient who filled out the flow.

PreviousLumabotFlow and nextLumabotFlow will be used to make it possible for flows to be able to jump to another flow with another template so we can reduce the number of unecessary questions in a single flow, which should help with organization and performance. One flow must call the jump template, at which time we create a new lumabotFlow and set the previous flow ID on its previousLumabotFlow property.

PreviousLumabotFlow and nextLumabotFlow will be used to make it possible for flows to be able to jump to another flow with another template so we can reduce the number of unecessary questions in a single flow, which should help with organization and performance. One flow must call the jump template, at which time we create a new lumabotFlow and set the new flow ID on the first flow's nextLumabotFlow property.

The ID of the root account user.

Flag for logical deletion where 1 means deleted.

The ID of the user who created this object.

The ID of the user who updated this object.

The date/time when this object was created.

The date/time when this object was updated.

How many items to fetch per page

Response properties which will be replaced by the referenced objects, separated by commas.

Response properties that should be returned, separated by commas.