SORMAS is a comprehensive system for managing and tracking events related to outbreaks.

Keypoints

    Events in SORMAS can be signals, medical tests, outbreaks, or other happenings related to an outbreak
    People involved in events can be created and documents can be saved
    Templates for documents can be kept for downloaded
    Events can be organized and structured in a hierarchy
    People linked to the outbreak can be listed as event participants
    Events can be searched, filtered, and sorted in the event list
    New events can be added with details and assigned a special number
    Duplicate detection is important in SORMAS to avoid creating the same thing twice.
    The system checks the similarity of names for duplicate detection.
    People are considered duplicates if they have similar names, the same gender, and the same birthday.
    The system recognizes when first and last names are switched and considers letters like UE/Ü as the same.
    A person needs to be connected to at least one case, contact, or event participant.
    Event participants can be connected to cases and contacts for further monitoring.
    Documents can be stored and organized using the ’Store document’ button
    Events in SORMAS can be grouped as main events and smaller events to organize outbreaks

Summary SORMAS: A Comprehensive System for Managing Outbreak Events

SORMAS is a system that allows for the creation and management of events related to outbreaks. These events can include medical tests, outbreaks with multiple cases, and other relevant happenings. Participants and documents can be added to events, and templates for documents can be saved. The system allows for organizing events in a hierarchy and provides details about the location and organization of events. People linked to the outbreak can be listed as event participants, even if they didn’t have close contact with the infected person. The event list can be filtered and sorted, and specific events can be searched for using various criteria. The system also allows for the creation of new events, with details such as event type, description, and source of information. Different event statuses can be chosen, including event, screening, and cluster. The system also provides options for marking events as dropped or for tracking progress. It is important to choose a specific name for events to easily find them later. Event participants can be added manually or imported from lists, and their details are displayed in a table. Events and event participants can be deleted or closed, with deletion times set if needed. Overall, SORMAS provides a comprehensive and organized approach to managing and tracking events related to outbreaks.


Managing Duplicate Entries and Linking People in SORMAS System

The SORMAS manual explains how the system detects and handles duplicate entries for cases, contacts, and event participants. It uses various criteria to determine if two entries are similar, such as name similarity, gender, and date of birth. The system also recognizes when first and last names are switched and considers certain variations in names. If duplicates are found, users with special permission can merge them into one entry. The system also allows for linking people to cases, contacts, or events, and checks for existing connections to prevent duplicate entries. When creating a new case for someone who attended an event, the system checks if the person is already part of the event and prompts the user accordingly. The manual also explains how to view and manage event participants, create contacts for close contacts, and connect documents and tasks to events.


Managing Documents and Events in SORMAS: A Comprehensive Guide

Events in SORMAS can be grouped as main events and smaller events, allowing for better organization of outbreaks based on topic, location, or chronological order. We will explain how to link events and search for specific events using their ID, title, or description. New events can be created and connected to existing events. Event groups can be created, changed, and connected by different users, with administrators having the ability to remove or close event groups. The manual also mentions a special editing mode for administrators to edit multiple events at once. 

Glossary - Events Directory

 
 
 
  1. Actions: To display the default view of the action directory.
  2. Active events: To display the list of active events.
  3. All: To display all reported events.
  4. Apply filters: To execute filter selections.
  5. By date: To filter events by their calendar date of report.
  6. By epi week: To filter events by their epidemiological week of report.
  7. Cases: The number of cases resulting from the event.
  8. Cluster: To filter events with event status equal to “clusters”.
  9. Community: To filter events by the communities in a district where the events occurred.
  10. Contact count method: To specify how event contacts should be counted namely, all contacts, only contacts with source case in event, or by both methods.
  11. Contacts: The number of contacts resulting from the event.
  12. Date of event from … to …: A composite filter for filtering events by by calendar date range.
  13. Date of event from epi week … to …: A composite filter for filtering events by epidemiological week range.
  14. Date of last evolution from epi week … epi week …: A composite filter for filtering events by event evolution week range.
  15. Disease: To filter events by the disease of the event e.g., Anthrax, COVID-19, Cholera, etc.
  16. District: To filter events by the districts in a region where the events occurred.
  17. Done: To display the list of investigated and closed events.
  18. Dropped: To filter events with event status equal to “dropped”.
  19. Enter bulk edit mode: A feature used to execute the same action (e.g., edit, delete, archive, etc.) to many events in one process or step.
  20. Event Management: To filter events by the management status of the event namely, pending, ongoing, done, and closed.
  21. Event reference date: To filter events by the report date.
  22. Event: To filter events with event status equal to “event”.
  23. Events: To display the default view of the event directory.
  24. Export: A feature used to export event data in .csv format.
  25. Fatalities: The number deaths resulting from the cases linked to the event.
  26. Groups: To display the default view of the group directory.
  27. Import: A feature used to import event data in .csv format.
  28. In progress: To display the list of events that are still under investigation.
  29. Investigation status: To filter events by their investigation status namely, pending/ongoing/done/discarded.
  30. New event: A feature used to register a new event.
  31. Pending: To display the list of events with pending investigation status.
  32. Region: To filter events by the regions in a country where the events occurred.
  33. Reported by: To filter events by the role of the users who created them.
  34. Reset filters: To return filters to the default setting.
  35. Responsible user: To filter events by the users responsible for them.
  36. Risk level: To filter events by the risk of acquiring an infection from the events namely, low, moderate, high, or unknown.
  37. Screening: To filter events with event status equal to “screening”.
  38. Search specific event: A feature used to search for a specific event. The search text can be case ID, person ID, etc.
  39. Show more filters/Show less filters: A feature that allows a switch between the filters displayed by default and all the possible filters.
  40. Signal: To filter events with event status equal to “signal”.
  41. Source type: To filter events by their source of information type, e.g., media/news, hotline/person, institutional partner, etc.
  42. Type of place: To filter events by the type of place where they occurred e.g., facility, festivities, etc.
 

Event Data

  1. Action status: To specify whether an event action is pending, in progress, or done.
  2. Additional information: Additional information on the event.
  3. Apply date filter: To execute a date selection.
  4. Area type: The administrative area type where an event occurred namely, urban or rural.
  5. Assigned to: The specify the officer or user responsible for executing the task.
  6. City: The city where the event occurred.
  7. Comments on task: Any comments relevant to the execution of the task.
  8. Community contact person: The name of a contact person in the community where the event occurred.
  9. Community: The community where the event occurred.
  10. Country: The country where the event occurred.
  11. Create new action: A feature for creating a new action for an event.
  12. Date of report: The calendar date that an event was made known to a public health authority, e.g., the local health department.
  13. Date: The calendar date on which an action for an event was taken.
  14. Description: A brief description of the event or event action.
  15. Disease: The disease that the event is likely to spread.
  16. District: The district where the event occurred.
  17. Document template: A feature to create document templates.
  18. Due date: The calendar date on which execution of the task should be completed.
  19. End date: The calendar date on which the event ended.
  20. Event evolution date: The date of the last progression, evolution, or change of state of the event, e.g., addition of more information like participants, resulting cases, etc. to the event.
  21. Event groups: A feature for linking events in a non-hierarchical manner to an existing event group or creating a new event group. Unlike superordinate and subordinate linkage, event groups allow for one event to be linked to multiple groups at a time.
  22. Event handout: An example of an event document template.
  23. Event ID: A system-generated non-editable unique identification number.
  24. Event management status: The management status of the event namely, pending, ongoing, done, or closed.
  25. Event status: To specify the status or type of the event namely, signal, Event, screening, cluster, or dropped.
  26. External token: A unique token of the event, used to link the event to an external system.
  27. GPS accuracy in M: The radius (measured in meters) of the place where the event occurred.
  28. GPS latitude: The GPS latitude of the place where the event occurred.
  29. GPS longitude: The GPS longitude of the place where the event occurred.
  30. House number: The house number where the event occurred.
  31. Investigation status: The investigation status of the event namely, pending, ongoing, done, or discarded.
  32. Link event: A feature used to link an event to an existing supraordinate or subordinate event.
  33. Measure: To specify the type of event action e.g., sample collection, closure of facility, etc.
  34. Multi-day event: To indicate whether the event occurred in more than one day.
  35. New document: A feature to import or attach documents to the event.
  36. New task: A feature for creating a new task associated to the event.
  37. Postal code: The postal code of the administrative area where the event occurred.
  38. Priority: To indicate the level of priority of the task or event action namely, high, normal, or low.
  39. Region: The region where the event occurred.
  40. Reporting user: The user account that registered the event in SORMAS.
  41. Reset date filter: To return the date filter to default setting.
  42. Responsible user: The name of the SORMAS user who has been assigned the responsibility of following-up on the event.
  43. Risk level: The risk of infection among the people involved in the event namely, low, moderate, high, or unknown.
  44. See event cases: To show cases resulting from the event.
  45. See event contacts: To show contacts resulting from the event.
  46. Source type: To specify the source of information type of the event e.g., media/news, hotline/person, etc.
  47. Start date: The calendar date on which the event started.
  48. Street: The street where the event occurred.
  49. Subordinate: The sub-events (child events) of a series of related events when linked in a hierarchical order.
  50. Suggested start: The suggested calendar date for the start of the task.
  51. Supraordinate: The parent event of a series of related events when linked in a hierarchical order.
  52. Task context: To specify the entity type that the task relates to namely, a case, contact, event, or general.
  53. Task type: To specify the type of task e.g., testing of animals, investigating the event, etc.
  54. Title: The title of the event or event action.
  55. Type of place: To specify the type of place where the event occurred e.g., facility, festivities etc.
 

Event Participants

  1. Add participant: To create a new event participant.
  2. Additional information: Additional information on the event participant person’s address.
  3. Additional information: To record additional information that is relevant for contacting the event participant person.
  4. Address type: The type of address of the event participant namely, home, place of work, place of isolation, or other.
  5. Age: The age of the event participant person in years, months, or days.
  6. Area type: The administrative area type of the event participant person’s address namely, urban or rural.
  7. ATC code: The code assigned to a vaccine by the Anatomical Therapeutic Chemical (ATC) classification system of the WHO.
  8. Batch Number: The numeric or alphanumeric designation of a vaccine for identifying and tracing the vaccine by manufacturer, date of production and other unique information.
  9. City: The city of the event participant person’s address.
  10. Community contact person: The name of a contact person in the event participant person’s community.
  11. Community: The community of the event participant person’s address.
  12. Contact information: The contact information of the event participant person.
  13. Country: The country of the event participant person’s address.
  14. Create: A feature for creating a new record, e.g., document templates, event actions, etc.
  15. Date of birth (year/month/day): The date of birth of the event participant person in years, months, or days.
  16. Date of first vaccination: The calendar date on which a event participant person received the first dose of a vaccine.
  17. Date of last vaccination: The Calendar date on which a event participant person received the last dose of a vaccine.
  18. District: The district of the event participant person’s address.
  19. Education: The educational level of the event participant person.
  20. Event handout: An example of an event document template.
  21. Facility category: The facility category of the event participant person’s address, e.g., accommodation, medical facility, care facility etc
  22. Facility type: The facility type of the event participant person’s address.
  23. Facility: The facility name of the event participant person’s address.
  24. Father’s name: The name of the event participant person’s father.
  25. First name: The given name of the event participant person.
  26. General comment: Any comment relevant to the location of the event participant person.
  27. GPS accuracy in m: The radius (measured in meters) of the location of the event participant person’s address.
  28. GPS latitude: The GPS latitude of the event participant person’s address.
  29. GPS longitude: The GPS longitude of the event participant person’s address.
  30. House number: The house number of the event participant person’s address.
  31. INN: The International Nonproprietary Name of a vaccine.
  32. Involvement description: A brief description of how the event participant person was involved in the event.
  33. Last name: The surname or family name of the event participant person.
  34. Manufacturer: The name of the pharmaceutical company that produces a given vaccine.
  35. Mother’s maiden name: The maiden name of the event participant person’s mother.
  36. Mother’s name: The name of the event participant person’s mother.
  37. National health ID: The national health identification number of the event participant person.
  38. New contact: A feature for creating a new contact.
  39. New sample: A feature for creating a new sample.
  40. Nickname: The nick name of the event participant person.
  41. Only count contacts whose source case is related to this event: To show only the list of contacts with a source case related to the selected event.
  42. Passport number: The valid national passport number of the event participant person.
  43. Phone number type: To specify whether a phone is a landline, mobile, for work, or other.
  44. Postal code: The postal code of the event participant person’s address.
  45. Present condition of person: To specify the condition of the event participant person at the time of reporting namely, alive, dead, buried, or unknown.
  46. Primary contact details: The primary contact details of the event participant person.
  47. Quarantine order: A feature for creating a quarantine order document
  48. Region: The region of the event participant person’s address.
  49. Responsible district: The district within a region that is responsible to manage or follow-up on the event participant person. (This can be the same or different from the district of the event as captured under “event data”).
  50. Responsible region: The region within a country that is responsible to manage or follow-up on the event participant person. (This can be the same or different from the region of the event as captured under “event data”).
  51. Source of vaccination information: The source of the vaccination information. This could be a vaccination card, oral communication, no evidence, or unknown.
  52. Street: The street name of the event participant person’s address.
  53. Third party name: The name of a third-party contact person.
  54. Third party role: The role of a third-party contact person.
  55. Type of contact details: The event participant person’s contact details type namely, email, phone, or other.
  56. Type of occupation: The main occupation of the event participant person.
  57. UNII code (Unique Ingredient Identifier code): An alphanumeric identifier linked to a vaccine’s molecular structure or descriptive information.
  58. Unit: The unit of the age of the event participant person namely, years, months, or days.
  59. Vaccination status for this Disease: The vaccination status of the event participant person namely, vaccinated, unvaccinated, or unknown.
  60. Vaccine dose: The number of doses of a vaccine that the event participant person has received.
  61. Vaccine name: The formally approved name of a vaccine.
Última modificación: domingo, 28 de abril de 2024, 11:08