I’m curious if anyone has experience in auto-generating Unique Identifier Codes (UICs) in tracker capture module (v2.25 or below), or if there is a best practices document out there.
We are capturing sensitive information about clients through android tracker. The service provider would like to capture name and phone number data, but restrict viewing of these data to higher-level users. Data entry roles should only be able to search based on a system-generated UIC. You should be able to construct and re-construct UICs based on client data, as in the diagram from PSI below.
So we do not need a randomly generated ID for the tracked entity, but a script which constructs a custom string attribute based on other tracked entity attributes, similar to this app, but built directly into DHIS2 form:
I’m curious if anyone has experience in auto-generating Unique Identifier Codes (UICs) in tracker capture module (v2.25 or below), or if there is a best practices document out there.
We are capturing sensitive information about clients through android tracker. The service provider would like to capture name and phone number data, but restrict viewing of these data to higher-level users. Data entry roles should only be able to search based on a system-generated UIC. You should be able to construct and re-construct UICs based on client data, as in the diagram from PSI below.
So we do not need a randomly generated ID for the tracked entity, but a script which constructs a custom string attribute based on other tracked entity attributes, similar to this app, but built directly into DHIS2 form:
I’m curious if anyone has experience in auto-generating Unique Identifier Codes (UICs) in tracker capture module (v2.25 or below), or if there is a best practices document out there.
We are capturing sensitive information about clients through android tracker. The service provider would like to capture name and phone number data, but restrict viewing of these data to higher-level users. Data entry roles should only be able to search based on a system-generated UIC. You should be able to construct and re-construct UICs based on client data, as in the diagram from PSI below.
<image.png>
So we do not need a randomly generated ID for the tracked entity, but a script which constructs a custom string attribute based on other tracked entity attributes, similar to this app, but built directly into DHIS2 form:
