SORMAS-Foundation · MaMH20 · Jun 13, 2021 · Jun 18, 2021 · Jun 18, 2021
diff --git a/LICENSE b/LICENSE
diff --git a/README.md b/README.md
diff --git a/docs/.vuepress/config.js b/docs/.vuepress/config.js
@@ -0,0 +1,47 @@
+module.exports = {
+    title: 'SORMAS Glossary',
+    description: 'Just playing around',
+    themeConfig: {
+        nav: [
+            { text: 'Home', link: 'homepage/' },
+            { text: 'Guide', link: 'https://www.sormas-oegd.de' },
+
+            {
+                text: 'Languages',
+                ariaLabel: 'Language Menu',
+                items: [
+                    { text: 'English', link: '/language/english/index' },
+                    { text: 'German', link: '/language/german/index' },
+                    { text: 'French', link: '/language/french/index' }
+
+                ]
+
+            },
+
+        ],
+        sidebar: {
+            '/homepage/':[
+                'dashboard_directory_ordered',
+                'case_management',
+                'task_management_directory_ordered'
+            ],
+            '/language/english/':[
+                'dashboard_directory_ordered',
+                'case_management',
+                'task_management_directory_ordered'
+            ],
+            '/language/german/':[
+                'dashboard_directory_ordered',
+                'case_management',
+                'task_management_directory_ordered'
+            ],
+            '/language/french/':[
+                'dashboard_directory_ordered',
+                'case_management',
+                'task_management_directory_ordered'
+            ]
+
+        }
+    }
+}
+
diff --git a/docs/README.md b/docs/README.md
@@ -0,0 +1,11 @@
+# Welcome
+
+This glossary contains the nomenclature and definitions of the SORMAS entities and attributes (data elements). It seeks to provide a common understanding and interpretation of the data collected in SORMAS among the different countries, organizations and users.
+
+This glossary is a living document insofar as SORMAS retains its versatility of adopting to changing demands of disease surveillance and outbreak management. It is worth noting that, this document was based on the generic design of SORMAS and may not reflect all the country-specific adoptions currently in use.
+
+For ease of reference, we used the same structure of the directories in the SORMAS application to organize this glossary. Each section of the glossary begin with a brief overview of the epidemiological principles pertained to the entity in question, then followed by the nomenclature of each of its attributes.
+
+
+
+
diff --git a/docs/Case_Management.md → docs/homepage/case_management.md b/docs/Case_Management.md → docs/homepage/case_management.md
@@ -1,4 +1,4 @@
-## Brief Notes    
+## Task Management Directory Ordered   
 
 A case of a disease, syndrome, or health condition is determined by a set of standard clinical, laboratory, and epidemiological criteria called case definitions. Case definitions are useful for making uniform decisions of whether or not; an individual has a disease or health event of interest. 
 

diff --git a/docs/homepage/dashboard_directory_ordered.md b/docs/homepage/dashboard_directory_ordered.md
@@ -0,0 +1,43 @@
+## Dashboard Directory Ordered
+
+Epidemiological dashboards are digital innovations for real-time visualisation of multiple streams of related data for purposes of surveillance and outbreak management. By these attributes, dashboards facilitate informed decision making using multiple combinations of indicators and figures obtained from data analyses. In this way, dashboards improve situational awareness - especially for ongoing outbreak responses. Aside from providing visuals for speedy situational assessment, epidemiological dashboards reduce information floods that may result from multiple sources of data, and minimise workflow interruptions – e.g. by having to manually perform periodic analyses of incoming data.
+
+## Overview of the SORMAS Dashboard
+
+The SORMAS dashboard has two sections viz. surveillance and contacts; each displayed at a time. These are represented by tabs on the upper right corner of the screen. There are multiple filters for selecting variables of interest e.g. disease, time, etc.
+
+**Surveillance Dashboard:** The Surveillance dashboard has two sections. The upper section displays summary information of case counts of each infectious disease for specified time interval of notification. This is accompanied by graphical display of the difference in number of cases between any two specified time intervals. The lower section displays an epidemiological curve, case status map and indicators for each disease; one at a time. The dashboard has filters for displaying information of specified diseases, times, and places.
+
+**Contact Dashboard:** The contact dashboard displays summary information of individuals reported to have come into contact with probable or confirmed cases of infectious diseases. For a selected disease of interest, the types of contact information displayed include: number of contacts, follow-up status chart and spatial distribution of contacts.
+
+## Dashboard Glossary
+
+### Surveillance Dashboard
+
+1.	**Case status (on epi curve):** This is used to group the cases by case classification (confirmed, probable, suspected, not yet classified).
+2.	**Case status map:** This is an interactive map that shows the spatial distribution of cases, contacts, events, and their related variables.
+3.	**Epidemiological curve (epi curve):** This a histogram of the number of cases of a specified disease by the date of illness onset. An epidemiological curve shows the progression and magnitude of the disease in the population.
+4.	**Fatalities:** The number of cases that died from the specified disease. 
+5.	**Grouping (on epi curve):** This is the unit of time used to scale the horizontal axis of the epi curve. The possible options are: days, weeks, and months. 
+6.	**Last report district:** The name of the district or local government area that reported the most recent case of a specified disease. 
+7.	**Map key:** A legend of the map. 
+8.	**Map layers:** This is an interactive function on the case status map that allows for the visualisation of cases, contacts, events, etc. by various characteristics of interest viz. case classification; reporting levels (facilities, regions, case counts, case incidence proportion), contacts, events, or any appropriate combinations of these variables.
+9.	**New cases:** The number of reported cases classified by case classification status (confirmed, probable, suspected, ...).
+10.	**New events:** The numbers of events classified by event status (signal, events, screening, cluster).
+11. **Outbreak notification:** Each epidemic prone disease has a predetermined number of case (outbreak threshold) beyond which an outbreak of the disease in question is said to occur. A red flag is automatically displayed on the tab of the disease in question when this outbreak threshold is exceeded. This outbreak notification is per disease, region and district.
+12.	**Test results:** The outcome of laboratory investigation of samples (positive, negative, pending, indeterminate).
+
+### Contacts Dashboard
+
+1.	**All contacts:** The number of contacts classified by contact classification status (unconfirmed, confirmed, not a contact (discarded)).
+2.	**Contact classification chart:** A histogram of number of contacts grouped by contact classification status (confirmed, unconfirmed).
+3.	**Contacts in quarantine:** The number of contacts in quarantine. 
+4.	Contacts per case: The minimum, maximum, and average number of contacts per case. 
+5.	**Data:** The type of contact data depicted by the contact chart namely: follow-up status, contact classification, and date of end of follow-up (follow-up until).
+6.	**Follow-up status chart:** A histogram of number of contacts grouped by follow-up status (under follow-up, lost to follow-up, completed follow-up, cancelled follow-up).
+7.	**Follow-up until chart:** A histogram of number of contacts grouped by their last date of follow up.
+8.	**Grouping (on chart):** This is the unit of time used to scale the horizontal axis of the contact chart.
+The possible options are: days, epi-weeks, and months. 
+9.	**Stopped follow-up:** The number of contacts which are no longer under follow-up for any of the following reasons: completed follow-up, cancelled follow-up, lost to follow-up, or converted to case.
+10.	**Under follow-up:** The number of contacts that are under monitoring (contact follow-up) by a contact tracing team. They are classified by their last visit remark (cooperative, uncooperative, unavailable).
+11.	**Visits:** The number of follow-up visits performed classified by visit remark (unavailable, uncooperative, cooperative).
diff --git a/docs/index.md → docs/homepage/index.md b/docs/index.md → docs/homepage/index.md
@@ -4,3 +4,6 @@ This glossary contains the nomenclature and definitions of the SORMAS entities a
 This glossary is a living document insofar as SORMAS retains its versatility of adopting to changing demands of disease surveillance and outbreak management. It is worth noting that, this document was based on the generic design of SORMAS and may not reflect all the country-specific adoptions currently in use.
 
 For ease of reference, we used the same structure of the directories in the SORMAS application to organize this glossary. Each section of the glossary begin with a brief overview of the epidemiological principles pertained to the entity in question, then followed by the nomenclature of each of its attributes.
+
+
+
diff --git a/docs/homepage/task_management_directory_ordered.md b/docs/homepage/task_management_directory_ordered.md
@@ -0,0 +1,37 @@
+## Task Management Directory Ordered
+
+Surveillance activities and outbreak responses often rely on the coordination of multidisciplinary teams. A broad classification of personas or user roles in an outbreak response include: hospital informants, surveillance officers, surveillance supervisors (state epidemiologist) contact officers, contact supervisors, case officers, laboratory officers, just to name a few. The task module allows realtime assignment and management of tasks among the different personas which then improves and enhances the overall efficiency of the outbreak response. The classification or context of a task can be general or associated to an entity (case, contact, event). 
+
+## Tasks Glossary
+
+### Task Management Directory
+
+1.	**Active tasks:** Tasks that the system loads by default each time a user opens the tasks directory. 
+2.	**All tasks:** All created tasks in SORMAS irrespective of the user role or persona that the task is assigned to. 
+3.	**Archived tasks:** Tasks that are removed from the default view. Archiving a task only prevent the task from being loaded by default in order to improve performance of the system. This similar logic applies to all directories in SORMAS.
+4.	**Basic export:** To download the task management directory with the associated variables as displayed on the default page. 
+5.	**By date or By epi week:** The time unit used to filter the task management directory. Possible options are: “by date” or “by epidemiological week”.
+6.	**Created by:** The name of the user who created the task.
+7.	**District:** The responsible district of the entity (case, contact, event) that the task is related to.
+8.	**Enter bulk edit mode:** Once activated, this function allows the selection of several tasks and execute a single action (deletion) on all of them at once.
+9.	**My task:** This filters the task directory for all tasks assigned to the logged in user.
+10.	**New task:** To create a new task.
+11.	**Officer tasks:** This filters the task directory for all tasks assigned to surveillance officers. 
+12. **Region:** The responsible region of the entity (case, contact, event,) that the task is related to.
+13.	**Task from epi week… and, Task to epi week… :** These two filters jointly select and display tasks by a desired period in epidemiological weeks. Activating the “By epi week” filter setting is a prerequisite for using these filters.
+14.	**Task reference date:** The date type used to filter the task directory. It
+can be either the suggested start date, or the suggested due date.
+
+### Task Entity
+
+1.	**Assigned to:** The name of the user responsible for executing the given task.
+2.	**Associated case/contact/event:** The name of the entity (case, contact, event) that the task is related to.
+3.	**Associated link:** It directs the user to the cases, contacts, or events for which a task is assigned.
+4.	**Comments on execution:** Any users’ comments on the execution of the task, e.g. updates, challenges encountered, request for clarification etc.
+5.	**Comments on tasks:** Any users’ general comments to the specific task.
+6.	**Due date:** The date by which an assigned task should be completed. 
+7.	**Suggested start:** The recommended date by which a newly assigned task should start.
+8.	**Task context:** This represents the entity (case, contact, event) or general aspects of response to which the task is associated.
+9. **Task priority:** An indication of the urgency with which a task should be executed (high, normal, low).
+10.	**Task status:** The state of the task. It could be any of the following:Pending – tasks awaiting execution; Done – completed tasks; Removed – tasks taken out of the system because they were discarded; Not executable – tasks that are not possible to carry out.
+11.	**Task type:** This represents the category of the task and includes: case investigation, case isolation, case management, contact investigation, contact follow-up, sample collection, sample transportation, sample testing, report generation, event investigation etc.
Original file line number	Diff line number	Diff line change
Expand Up		@@ -4,3 +4,6 @@ This glossary contains the nomenclature and definitions of the SORMAS entities a
		This glossary is a living document insofar as SORMAS retains its versatility of adopting to changing demands of disease surveillance and outbreak management. It is worth noting that, this document was based on the generic design of SORMAS and may not reflect all the country-specific adoptions currently in use.

		For ease of reference, we used the same structure of the directories in the SORMAS application to organize this glossary. Each section of the glossary begin with a brief overview of the epidemiological principles pertained to the entity in question, then followed by the nomenclature of each of its attributes.