SESP data centralization is being implemented with the goal to centralize all SESP data at the provincial level to identify duplicate clients, reduce costs and facilitate data ownership. All the HFs with SESP, synchronize their data directly to a central provincial database. For the HFs with direct internet connectivity the synchronization occurs in real time. For the HFs without reliable internet connectivity, the synchronization occurs every 30 minutes or when internet connection is available. Data is synchronized or pushed from a health facility to the central provincial server (one-way communication). Client data from the centralized server can be used for the Shared Health Records (SHR), for reporting, and as inputs into the Master Client Index (MCI), among others. Since the actual implementation of SESP requires a database at each HF, the same user can be registered in different databases (HFs), with the same username and/or system ID but with a different UUID.When the client data is pushed from the HF to the central provincial server, it goes with respective users from each HF who created or updated the client record causing duplications of users at central level. The duplicate usernames are preventing the Remote Client Search module from importing clients from central DBs to remote DBs. This document describes the requirements for a User Harmonization module that allows deduplication of users, export from the central server and import on remote HFs.
● To develop a feature to harmonize users at the central database
● To develop a feature to allow the Export of harmonized users from central database to remote databases.
● To develop a feature to allow the Import of harmonized users in to remote databases.