Note: this SOP applies to both, new designs, as well as changes to configurations that are active.

The process of design and building a DHIS2 configuration (aggregated or tracker) is iterative, blah

Before you start

Requirments document: detailing the actors, purpose and data points envisioned for the required solution

D2A: Data for Action framework, which clearly delineates the expected outcomes in terms of charts/ tables, and in different dimensions that are expected to be available for data disaggregation and filtering.

Design and Build

As in most system, this is an iterative process on which varios prototypes are build, discussed and iterated, until a configuration contains sufficient details

Environments

The process of design and development must be done in a development server. You should never do design of a new system, or changes to system that it is in production.

See also

Deploying configurations to production

Versions