Get lumabotFlow by id

Luma's internal ID of an object.

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.

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

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 form yet;
• completed: the patient has finished answering all the questions and cannot edit the form anymore.

type of the lumabot flow template

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

The internal staff's management status for a completed flow, serving the purpose of organizing which answers were analysed by a staff member or not.

• open: the flow was completed by a patient but not seen by any staff member yet;
• in-progress: a staff user is analysing the answers;
• closed: the flow has been completely analysed by a member of the staff team.

the ID of a staff user who analysed the responses of this completed flow and changed its processingStatus.

the date/time when a staff user analysed the responses of this completed flow and changed its processingStatus.

the ID of an appointment related to this form.

deprecated: custom lumabot flow url, basically to identify any patient in survey monkey, an external forms 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 responses.page[0].questions[x].id, or success. Usually this will contain each id, in sequence, but patients can go back and forth. Also, forms can have jump logic, and some questions might not be displayed to the patient. When the form 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 form answers. See lumabotFlowTemplates.

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

IP address of the patient who filled out the form.

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

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