Pre-visit patient form

Healthcare

Where this process begins.

The appointment is booked, but the clinician has no context before the visit. The care team needs to know the reason for the visit, whether the patient has consulted about it before, current symptoms and their duration, medications, and allergies. Collecting this during the appointment takes time away from care.

For clinics and practices that want to make better use of consultation time with organized information in advance.

Process map

From the initial need to the team’s next step.

1. A need arisesThe person needs to start a request or report what happened.
2. Automatic invitationOnce the appointment is confirmed, the patient receives the pre-visit form.
3. Guided questionsThe patient completes a WitAsk WhatsApp Flow with the reason for the visit, symptoms, medication, and allergies.
4. A visit with contextThe information is organized in Zendesk so the clinician or the team can find the complete form before seeing the patient.

Industry details

What the team needs to know.

Case follow-up

The information arrives ready for action.

A medical visit starts with the relevant clinical information available before the patient arrives. The answers are gathered so the responsible team can review the case and decide what to do next.

The fields and destination of the form depend on the healthcare center's configuration.

Other situations

Ways to adapt the workflow.

Featured case in action

An example of the complete workflow.

1. Automatic invitation

   Once the appointment is confirmed, the patient receives the pre-visit form.

2. Guided questions

   The patient completes a WitAsk WhatsApp Flow with the reason for the visit, symptoms, medication, and allergies.

3. A visit with context

   The information is organized in Zendesk so the clinician or the team can find the complete form before seeing the patient.

The fields and destination of the form depend on the healthcare center's configuration.