Step-by-step instructions to guide users through the case survey process

[AliciaRaber]

Feature Description

Process oriented SORMAS Guide for case survey.

Problem Description

Actual process for case survey is that after the creation of a visit for a case is to change in the different tabs (entering data in symptoms, epidemiological data, facility data if necessary, case data if necessary and further tasks. This caused a lot of time for exaaminers. Outcome is also that data quality for crucial information is poor.

Proposed Change

Trigger for start oft he SORMAS Guide is the process of the task CASE_ISOLATION Step 1: Check personal data (including the possibility of edit). Title for window with reference text: Please check personal information or make changes if necessary /ger → Next step In case of edit of personal data especially facility data: Trigger field for customization and change of infrastructure data Trigger field for entering data if person is in health facility (hospitalization status). → Next step Input mask for symptoms (including that every field who state „Yes“ triggers yes and not triggered triggered as „No“ in symptom tab in SurvNet). Title for window with reference text: Please ask for symptoms /ger → Next step Trigger field for case classification (default E.). Title for window with reference text: Please specify the case classification /ger→ Next step Input mask for health state including note field. Title for window with reference text: Please ask for previous or existent diseases /ger→ Next step Input mask for vaccination. If vaccinated: Trigger field for entry of vaccination data. Logical field for one or two vaccinationdoses including date fields for first and second vaccination. Including fields for vaccineName and dropdown fields. Title for window with reference text: Please ask for vaccination status /ger If UNVACCINATED → Next step Input mask for epidata including new entry field in order to file expisitory data. Trigger for field new entry → Specify exposition. Title for window with reference text: Please ask for expository data /ger → Next step Trigger field for new task. In order to continue COVID survey our process provides a new task to conclude the survey. After creation of the task the guided process for case isolation is over.

Possible Alternatives

Feel free to suggest alternatives

Additional Information

SORMAS Guide was proposed at 15th of october 2021. Please feel free to contact me at any time if you have further question.

[marko-arn]

This would be good and prevent that the users forget to enter details at some point of Sormas, but I think it is a bunch of work to do for that.

[kwa20]

@MateStrysewske This is the issue I briefly talked to you about today. I think it could serve as a concept issue under which we can discuss details for then to determine subsequent issues. Some main points I could see for this feature would roughly be the following:

• Configurations > user guides UI
  • templates to configure guide pages to navigate the user through - admins would have to choose from entity dependent variables to display in respective slides in pop-up step-by-step instructions
    • Could include specific configurations like headings and instructions
  • configuring of associations for tasks, task context, task type, related entity
  • archiving of guides or reassigning guides to different or multiple associated task types etc.
• Implications on tasks > trigger of execution to start the process
  • execution status?
  • how to handle triggering of executions by multiple users?
• logic for storing entered data temporarily (backend?)
  • users should be able to navigate back and forth through the steps to allow checks and corrections