As some sites in India scale, I’ve been thinking more about how best
to create usernames that have meaning to both the CommCare user and
the different web users. I’ve learned that user information needs to
be displayed differently for different people looking at the CCHQ
reports online. We’re thinking carefully about the information we
convey in usernames and how we take advantage of the Groups feature.
I’m seeking tips from other CommCare implementers. Perhaps you can
share your use cases. Below I share what we’ve tried out at two sites
For the small 10 CHW pilots we ran, we create usernames containing
only the first name of the CHW. (i.e. suman) But now as these sites
scale, we learn that this is no longer feasible. The obvious reason is
because there are so many CHWs with the same name.
Avoiding duplication among users
Alternatively, we tried firstname.lastname. But not surprisingly,
there were several CHWs with the same first and last name. For those,
we distinguished by adding initials of the village name at the end. So
evidently, the usernames became firstname.lastname.villageinitials.
(The IDs are quite long and fall off the login screen).For this site,
we also used the Groups feature to divide the 70 CHWs by Primary
Health Center for top level insight.
I’m still not convinced this is the best option and sure there are
many more alternatives.
Meaningful information for Web users
One of the first questions I ask before implementation is about who
will be looking at the data on CCHQ. Each web users may be interested
in seeing information differently. The field-based project coordinator
most often knows their health workers well and can identify users on
CCHQ by the firstname.lastname. But perhaps a government official or
manager more removed from the field who also wants to monitor the data
doesn’t find it meaningful to see performance data on a name-wise
basis and perhaps would prefer less detail?
An option could be to take advantage of the groups feature and create
’x’ many groups as required by the different web user types.
More than 1 health worker type and multiple stakeholders
For a project that involves three different frontline health workers,
we created usernames with the following format:
firstname.position.communitycode. We need the ability to sort the CCHQ
reports by position (either ASHA, AWW or ANM) because they work under
different government departments. Right now, this would be possible
using the search box at the top of the CCHQ reports. Similarly, field
based supervisors will need to be able to sort data based on
communities, and they can also do this by using the search box.
Another web user needs to be able to organize data by subcenter. For
this use case, we decided to take advantage of the Groups feature.
Dealing with health worker turnover
What happens when a health worker gets replaced? (Though this rarely
happens). I guess its up to the NGO or government, and it becomes more
of a question of whether they want to track the cases or track CHW-
specific performance. If they want to track only the cases, then
perhaps a simple username like asha_05 could be used. Then the new
ASHA could pick up the work from that phone, using that ID. Does
anyone have thoughts on this?
Eager to hear if anyone has inputs.