Backend
Location 1.X uses a custom API to retrieve Org Unit data from a DHIS2 instance with custom attributes. The information is retrieved from a replica server to minimised direct impact on the production database of DHIS2. For 2.0 we need to continue using a custom API, as DHIS2 standard API is not able to perform geo-search operation. We will also continue using custom DHIS2 attributes to store information for a location that it is not part of the standard DHIS2 Org Unit default properties.
Locator 2.0 will also allow FHIR as a data source. Hence, to the extend possible, custom attributes in DHIS2 will be aligned to FHIR concepts, and when appropiate, we will store information on a FHIR format.
Frontend
Locator 2.0 will be delivered as a generic javascript library, with can in principle be incorporated into any web development or even a mobile application (online only).
...