Follow-up
What is Follow-up?
Follow-up is an intelligent workflow designed to re-engage Triage users at appropriate intervals. Its goal is to reassess the status of low-acuity patients and determine if additional medical support is required, thereby aiding in the identification of potentially worsening cases. This workflow enables the comparison of reported symptom progression over time, allows for the addition of new symptoms, and facilitates updated assessments to generate new recommendations. Furthermore, it inquires about users' planned next steps, providing valuable insights into their medical journey and adherence to our recommendations. This interview type supports users and patients, maintains their engagement in their health, and assists in the timely identification of urgent cases.
Key steps described within this workflow (survey):
- User creation
- Patient creation
- Survey creation
- Next steps
How to create Follow-up workflow
Every survey needs an information about 'user' and 'patient'. As the Follow-up survey is intended to be used as extension to a Triage survey, 'user' and 'patient' information can be obtained earlier, in the Triage survey, stored and re-used in the Follow-up survey. If not, a user and a patient must be created separately. Each 'patient' needs to have information about sex and age data filled in, which are the fundamental entities necessary to link a survey to a specific 'user'. Information about dependent can be additionally used. Follow-up surveys require medical evidence collected in a previous survey. It could be either during the Triage interview or Follow-up survey. Collected data can be transferred from the survey summary.
Note that the triage level calculated in the Follow-up survey may differ from the initial Triage level. It can be either lower or higher, depending on the patient's current condition.
A first notification date for a Follow-up survey, is set up manually during the implementation process. Notification dates for subsequent Follow-up surveys will use default values (presented below), unless configured otherwise. The Follow-up workflow is a recurring process, triggered by a previous Follow-up survey. User interaction is determined by the selected contact method. The notification date, and therefore the timing of the Follow-up, is dictated by the triage level from the preceding interview.
Default notification dates in Follow-up
Triage level | Notification date |
---|---|
self_care | 3 days after finished survey |
consultation | 2 days after finished survey |
consultation_24 , and higher | 1 day after finished survey |
Follow-up survey are limited to low-acuity medical cases. Emergency and ambulance triage are excluded.
Steps to creating a Follow-up survey:
1. Identifying a user
A user represents an individual who interacts with the Infermedica platform. It can be obtained from the previous survey (Triage or Follow-up), or created from scratch.
Example request:
curl "https://api.infermedica.com/api/mgp/v1/users" \
-X "POST" \
-H "Authorization: Bearer <ACCESS_TOKEN>" \
-d '{
"email": "user@example.net"
}'
The user_id
from the response to this request is needed for patient creation.
Available attributes:
email
- user email
More information on creating a user can be found here.
2. Identyfing a patient
A patient is an entity representing a person's medical information within the Infermedica system. It can be obtained from the previous survey (Triage or Follow-up), or created from scratch. Each new Follow-up survey is linked to a 'patient'. The data provided through 'patient; directly affects the questions that appear in a Follow-up survey.
Example request:
curl "https://api.infermedica.com/api/mgp/v1/patients" \
-X "POST" \
-H "Authorization: Bearer <ACCESS_TOKEN>" \
-d '{
"sex": "male",
"age": {
"unit": "year",
"value": 20
},
"dependent": true,
"user_id": "c599e21b-3795-4f02-a14e-b46884f8a0c9"
}'
The 'patient' ID from the response to this request is needed to create a 'survey'.
Available attributes:
dependent
- is patient dependent on the user. The valuetrue
means that the survey created for this patient is completed by another person, like a parent or caregiver. For underage patients,dependent
must be set totrue
- if provided earlier, the question about dependent will be omittedsex
- patient sex - can be defined in the Follow-up survey or collected earlierage
- patient age - can be defined in the Follow-up survey or collected earlieruser_id
(required) - related user ID
More information on creating a patient can be found here.
3. Creating a Follow-up survey
A Follow-up survey is an interview process in which patient's medical information from the previous survey is verified and a new medical evidence can be collected.
Example request:
curl "https://api.infermedica.com/api/mgp/v1/surveys" \
-X "POST" \
-H "Authorization: Bearer <ACCESS_TOKEN>" \
-d '{
"sections": [
"followup_questions",
"intent_survey",
"dynamic",
],
"expiration_date": "2024-04-22T11:51:14.198593",
"type": "followup",
"patient_id": "9702c05b-5871-4109-ae2a-82f8c9dad64c",
"evidence": [
{
"id": "s_98",
"choice_id": "present",
"source": "initial"
}
],
}'
Please note that the example above presents only one piece of evidence from the previous survey. Typically, the evidence list is much longer and includes lists of present and absent symptoms, risk factors, and other relevant information.
Available attributes:
type
(required) - survey type -followup
patient_id
(required) - related patient ID, age and sexevidence
(required) - survey's initial symptoms, risk factors and other assessed previously symptomssections
- survey questions sections that will be displayed during the interview. If no data is provided, all sections will be visible. If data is provided, the interview will include only the specified sections along with mandatory questions about sex, age, and dependents (if not provided earlier or during 'patient' creation). The assignment of questions to specific sections is specified in the table in the below.expiration_date
- the expiry date of the interview, after which it will not be possible to complete it
More information on creating a survey can be found here.
Summary of all the questions within the Follow-up survey:
Question id | Survey section | Description |
---|---|---|
dependent | - | Data from a previous survey. Determines if the patient is a dependent. |
sex | - | Data from a previous survey. Determine the demographics of the patient. |
age | - | Data from a previous survey. Determine the demographics of the patient. |
how_are_you_feeling | followup_questions | Evaluates the patient's status since the preceding interview. |
have_you_seen_medical_professional | followup_questions | Determines if the patient had any form of medical support since the last interview. (optional) |
have_you_scheduled_visit | followup_questions | Determines if the patient have scheduled medical consultation since last symptom assessment. (optional) |
full_medical_care | followup_questions | Determines what type of medical care the patient sought. (optional) |
form_of_contact_scheduled | followup_questions | Determines what type of visit patient sought. (optional) |
check_symptoms_now | followup_questions | Determines if the patient wants to re-evaluate their symptoms. |
do_you_still_have_these_symptoms | followup_questions | Determines if the patient still have past symptoms. |
do_you_have_any_new_symptoms | followup_questions | Determines if the patient have any new symptoms. |
symptoms | dynamic | Search and select one or more initial symptoms, includes autocomplete and synonyms. |
what_kind_of_care_are_you_planning | intent_survey | Determines what kind of care the patient is planning to get. |
suggest | dynamic | Suggested symptoms, based on selected symptoms. |
interview | dynamic | Dynamically generated questions, based on the evidence provided. |
4. Next steps
This workflow supports low-acuity patients during their recovery. Re-evaluation of symptoms identifies potential symptom deterioration and the need for medical professional consultation. Follow-up surveys can be conducted for as long as the patient desires. Collected data can be integrated with other systems, such as patient accounts or doctor panels. Integration methods vary depending on the specific solutions used by each organization and must be developed client-side.