1.              Background Background

The Surveillance Outbreak Response Management and Analysis Systems (SORMAS) is an open-source digital platform for epidemic and pandemic preparedness and response. The system allows routine disease surveillance, early detection, and management of disease outbreaks.

...

Do not hesitate to get in touch with us if you have any issues filling in the form. Questions that you are not able to answer on the document can be discussed during a virtual or in-person meeting.

2.              Current  Current situation

2.1         Stakeholders 1 Stakeholders mapping

A list of stakeholders is important before starting a SORMAS project because it helps us to plan a strong communication strategy. It also helps streamlining the approval process, helping to ensure that project resources are available and remain focused, and keeping information flowing.

...

·        Are there other relevant stakeholders in disease surveillance and outbreak management?

2.2         Health 2 Health system infrastructure and organization

...

2.3         Current 3 Current digital tools and systems

...

·        What are the challenges that you are facing with your current system?

2.4         IT 4 IT infrastructure

·        Does your IT infrastructure run in a private cloud or do you have a 3rd party service like AWS, Microsoft Azure, etc?

...

·        Do they have the skills or knowledge in Linux, Zulu OpenJDK (Java 11 JDK), docker containers, GitHub, PostgreSQL, Java, domain names, networking, Java, IT security, backups, and disaster recovery plans?

2.5         Policy 5 Policy documents

·        Are there any digital strategy documents/policy documents in your country/region? (e.g., digital health strategy, data protection guidelines)

·        Are there any additional specific rules that need to be considered for implementation in your country?

3.              SORMAS  SORMAS configuration

3.1         Location1 Location

·        Where would you like to deploy SORMAS (according to the table on section 1.2)?

...

·        What is the population in this area? (Number) 

·        How many health facilities would you like to cover with SORMAS? (Number) 

·        How many users are expected to use the SORMAS system daily? (Number) 

·        How many users will be using SORMAS in an offline mode with an android phone or tablet? (Number)

·        In which language(Number)s) will you be using SORMAS?

3.2         Diseases2 Diseases

SORMAS has a default configuration with disease modules already included in it (see full list of diseases currently available in SORMAS: Disease Configuration Options · SORMAS-Foundation/SORMAS-Project Wiki · GitHub)

...

·        Could you provide the list of notifiable diseases in your country? 

·        Which diseases would you like to add to SORMAS system?

3.3         Identification 3 Identification of key SORMAS staff

Identification of key SORMAS staff is important before implementing SORMAS because it helps to maximise the value of SORMAS and its sustainability. Proper training of staff is key to reaping the full benefits of SORMAS. It is important to properly prepare for the implementation process with your team and the SORMAS end users.

...