The different system that we use at PSI are accessible via URL across the different domains that PSI’s DHM manages. The intention of this page is to document the use of those URLs, and the naming conventions for the related sub-domains.

We use subdomains to organise and categorise the difference services and the type of environment for the different systems that we develop and maintain. The management of these subdomains is done in AWS R53.

On this page

1 Domains
2 Subdomains naming policy
- 2.1 psidigital.org
- 2.2 psi-mis.org
- 2.3 psi-connect.org
- 2.4 kassai.org

Domains

Domain	Usage

Domain	Usage
psidigital.org	used for ALL digital interventions, except DHIS2 instances
psi-mis.org	Only used for DHIS2 instances
psi-connect.org	Legacy - to be discontinue
kassai.org	use for e-Learning implementations.

Subdomains naming policy

psidigital.org

This the the default domain for all our systems, except DHIS2 (see next). Acquired in early 2023, we plan by the end of 2024 to transition ALL systems to the new URL.

Each system is represented by its name as the sub-domain, and an suffix when appropriate.

sub-domain	Type (see environments)	Examples

sub-domain	Type (see environments)	Examples
system name	When only the system name is shown, it represents the production environment	RapidPro wfa nifi rocketchat openhim hapifhir keycloak superset
system_name.dev	the use of the suffix “-dev” denotes that the URL ifor the development environment of the related system. ALL systems that involve data capture (support create/update operations) are expected to have a development environment.	RapidPro.dev wfa.dev nifi.dev rocketchat.dev openhim.dev hapifhir.dev keycloak.dev superset.dev
system_name.qa	the use of the suffix “-qa” denotes that the URL if for the Quality Assurance (testing) environment of the related system. MOST systems that involve data capture are expected to have a QA environment. QA environments are not required for superset or keycloak.	RapidPro.qa wfa.qa nifi.qa rocketchat.qa openhim.qa hapifhir.qa keycloak.qa superset.qa
system_name.stage	the use of the suffix “-stage” denotes that the URL if for the staging environment of the related system. MOST systems are expected to have a staging environment Staging environments are not required for superset or keycloak	RapidPro.stage wfa.stage nifi.stage rocketchat.stage openhim.stage hapifhir.stage keycloak.stage superset.stage

psi-mis.org

Only used for DHIS2 instances

sub-domain	Description	Use

sub-domain	Description	Use
data	PSI’s main production server
dev	PSI’s main development server	used for prototyping future dataset and program implementation
clone	A clone of data, automatically build every 24hrs	used for debugging
staging	A copy of production, manually updated every 2-3 months.	testing of apps, changes to metadata, data imports
240	Denotes the version of DHIS2	testing of future versions
myanmar	Production server for Myanmar

psi-connect.org

This URL is treated as legacy. We expect to migrate all systems to psidigital.org by the end of 2024.

kassai.org

Use for PSI’s Moodle platform

sub-domain	Description	Example

sub-domain	Description	Example
www	PSI’s main production server	www.kassai.org
qas	development/testing server	qas.kassai.org
country	Country specific implementation, production	eswatini.kassai.org
country-qas	Country specific development/testing server	eswatini-qas.kassai.org

Platform 2.0

URLs for PSI platform - guidelines