medic
User friendly CHT Contacts Management System
Is your feature request related to a problem? Please describe.
csv-to-docs, move-contacts and upload-docs commands in medic-conf are currently the command available for contact(persons and places) management in CHT. While the command work, there is an unmet gap in CHT contact management. Specifically, for a large deployment, we are not addressing the following requirements effectively:-
- Bulk creation of contacts. In particular, the creation of a new hierarchy and addition of contacts to an existing hierarchy.
- Hierarchy updates in bulk. This is mostly moving contacts from a hierarchy level to another. It includes situations such as a CHA who exists at a level above a CHW being demoted to a CHW and vice versa.
- Bulk editing of contacts. Some details associated with contacts require updating at some point, for example, phone number.
- Bulk deletion / deactivation. Ability to delete contacts that are no longer active in the system for a reason or another. A thing to keep in mind here is the nuanced requirement to still be able to access data associated with these contacts even after they are deleted.
Describe the solution you'd like
- A mechanism to synchronize a new list with what is in the target instance. For example, say a new community health worker(CHW) is being added under a community health assistant(CHA). It should be possible to query the instance for an existing CHA with the CHA details associated with the new CHW and use that when creating the CHW record. The unique identifier visible to the user for the mapping exercise for the linkage would need to be human readable as well.
- It should be possible to tell, in a snapshot, where a user exists within the hierarchy.
- User lists, especially in MOH settings are not managed by one single person and are mostly a concerted effort with a lot of responsibility devolution at play. It should then be possible to accommodate this. For a practical perspective, let us use a typical hierarchy, bottom-up: CHW, CHA, County Health Management Team(CHMT). Every CHA is responsible for collating CHW details then passing them along to CHMT who are then put together the complete list. The solution needs to factor in the whole process of contact lists management.
- Effectively handle deletions and deactivations. When a CHA is deactivated, data under them should be available for analysis. If CHWs under them are assigned to another CHA, data associated with the new CHA should reflect from the point in time when the new allocation took effect.
Describe alternatives you've considered Write a custom script specific to the project.
Additional context A more detailed write up with one project's study case.
To add the non-technical voice to this issue;
-
As the CHA I want to assign all my CHVs to their new CHV areas via the App during the App’s training so that the CHVs have access to the right app for training and during deployment for quality health service delivery and data collection
-
As the CHA I want to assign new CHVs to new CHV areas, remove non-existing ones and transfer CHWs as needed via the App so that I have an updated system of CHVs for quality health service delivery and data collection
-
As a programs officer/manager I want to delete all the CHVs from the project’s instance after training so that the CHVs have access to the right app during deployment for quality health service delivery and data collection See also the document detailing this. cc @michaelkohn , @JenniferMuli, @leah-ngaari , @billwambua, @korirm
