SORMAS stands for “Surveillance, Outbreak Response Management and Analysis System“, developed during the West African Ebola pandemic 2014/15. SORMAS is an early warning and management system based on flexible mobile telephone apps in combination with modern cloud technology, enabling even countries equipped with only limited information and comm…
Clone or download
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
sormas-api
sormas-app
sormas-backend
sormas-base
sormas-ear [GITFLOW]Updating develop poms back to pre merge state Jan 10, 2019
sormas-rest
sormas-ui #900 Added generated property constants for i18n strings and validations Jan 14, 2019
sormas-widgetset
.gitattributes
.gitignore
.travis.yml
ADDING_LICENSE.md
DEMO_APP.md
DEVELOPMENT_ENVIRONMENT.md Unix line endings #800 Sep 24, 2018
LICENSE
README.md
RELEASE.md Unix line endings #800 Sep 24, 2018
SERVER_SETUP.md
SERVER_UPDATE.md
logo.png Prepare SORMAS for Contributors #722 Aug 6, 2018

README.md

SORMAS - Surveillance, Outbreak Response Management and Analysis System

Table of Contents

Project Structure

The project consists of the following modules:

  • sormas-api: general business logic and definitions for data exchange between app and server
  • sormas-app: the android app
  • sormas-backend: server entity services, facades, etc.
  • sormas-base: base project that also contains build scripts
  • sormas-ear: the ear needed to build the application
  • sormas-rest: the rest interface
  • sormas-ui: the web application

Releases and Server Setup

Contributing

Developers

  1. Use the Eclipse code formatter (Ctrl+Shift+F).
    Use the Android Studio code formatter for the sormas-app project
  2. Each commit should be related to a single issue on Github and have a reference to this issue. Separate subject from body with a blank line.

    Automatic case classification for existing SORMAS diseases #61

    build model to define classification
    apply automatic case classification whenever a field value changes

  3. Each pull request should be related to a single issue as-well (if possible).