# Auto-Generated Client UICs in Tracker v2.25 **URL:** \ **Category:** Support - Assistance technique\ **Created:** [25 April 2017 10:48 UTC](https://community.dhis2.org/t/auto-generated-client-uics-in-tracker-v2-25/4267 "2017-04-25T10:48:41Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![brian](https://dhis2.b-cdn.net/user_avatar/community.dhis2.org/brian/32/48251_2.png) [@brian](https://community.dhis2.org/u/brian)\ **Post date:** [25 April 2017 10:48 UTC](https://community.dhis2.org/t/auto-generated-client-uics-in-tracker-v2-25/4267/1 "2017-04-25T10:48:41Z")
Hi all, 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](https://dhis2.b-cdn.net/images/transparent.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: [https://play.google.com/store/apps/details?id=org.eyeseetea.uicapp&hl=en](https://play.google.com/store/apps/details?id=org.eyeseetea.uicapp&hl=en) I am not the only one who has requested this ([https://lists.launchpad.net/dhis2-devs/msg47211.html](https://lists.launchpad.net/dhis2-devs/msg47211.html)) but I cannot find a manual or correspondence online. Happy to provide more details on use case on request. Brian > **···** > > [![Akros](https://dhis2.b-cdn.net/uploads/default/original/3X/1/3/13d0b74258125257121e6dc59fed78a0bc44830d.png)](http://www.akros.com/) > Brian O’Donnell, MPAff > Informatics Project Manager > [bodonnell@akros.com](mailto:bodonnell@akros.com) ---
**Author:** ![em.hispvietnam](https://dhis2.b-cdn.net/user_avatar/community.dhis2.org/em.hispvietnam/32/191_2.png) [@em.hispvietnam](https://community.dhis2.org/u/em.hispvietnam)\ **Post date:** [25 April 2017 15:49 UTC](https://community.dhis2.org/t/auto-generated-client-uics-in-tracker-v2-25/4267/2 "2017-04-25T15:49:34Z")
You can use script on custom form. Until now, there’s no way for default form to generate based on tracked entity attributes. ![image](https://dhis2.b-cdn.net/images/transparent.png) > **···** > > On Tue, Apr 25, 2017 at 5:48 PM, Brian O’Donnell [bodonnell@akros.com](mailto:bodonnell@akros.com) wrote: > > > Hi all, > > > 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: > > > [https://play.google.com/store/apps/details?id=org.eyeseetea.uicapp&hl=en](https://play.google.com/store/apps/details?id=org.eyeseetea.uicapp&hl=en) > > > > > > I am not the only one who has requested this ([https://lists.launchpad.net/dhis2-devs/msg47211.html](https://lists.launchpad.net/dhis2-devs/msg47211.html)) but I cannot find a manual or correspondence online. Happy to provide more details on use case on request. > > > > > > Brian > > > [![Akros](https://dhis2.b-cdn.net/uploads/default/original/3X/9/4/94b9e0d9fe06f7aac51d52017dbd5a06d136c2a5.png)](http://www.akros.com/) > > Brian O’Donnell, MPAff > > Informatics Project Manager > > [bodonnell@akros.com](mailto:bodonnell@akros.com) > > > – > > > * * * > > > > Mailing list: [https://launchpad.net/~dhis2-users](https://launchpad.net/~dhis2-users) > > > > Post to : [dhis2-users@lists.launchpad.net](mailto:dhis2-users@lists.launchpad.net) > > > > Unsubscribe : [https://launchpad.net/~dhis2-users](https://launchpad.net/~dhis2-users) > > > > More help : [https://help.launchpad.net/ListHelp](https://help.launchpad.net/ListHelp) > > – > > **Em Le Hong** > DHIS2 Implementation| \*\*HISP Vietnam \*\* > > [em.hispvietnam@gmail.com](mailto:em.hispvietnam@gmail.com) | **Skype:** [em.hispvietnam@gmail.com](mailto:em.hispvietnam@gmail.com) > > ![](https://drive.google.com/uc?id=0B-tlJrv190f5dmR1Y0t2NERvcVU&export=download) ---
**Author:** ![Markus](https://dhis2.b-cdn.net/letter_avatar_proxy/v4/letter/m/b782af/32.png) [@Markus](https://community.dhis2.org/u/Markus)\ **Post date:** [26 April 2017 08:24 UTC](https://community.dhis2.org/t/auto-generated-client-uics-in-tracker-v2-25/4267/3 "2017-04-26T08:24:42Z")
Also, you can vote for this issue, and add your specific requirements in the comments: [https://jira.dhis2.org/browse/DHIS2-434](https://jira.dhis2.org/browse/DHIS2-434) > **···** > > On Tue, Apr 25, 2017 at 5:48 PM, Brian O’Donnell [bodonnell@akros.com](mailto:bodonnell@akros.com) wrote: > > > Hi all, > > > 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: > > > [https://play.google.com/store/apps/details?id=org.eyeseetea.uicapp&hl=en](https://play.google.com/store/apps/details?id=org.eyeseetea.uicapp&hl=en) > > > > > > I am not the only one who has requested this ([https://lists.launchpad.net/dhis2-devs/msg47211.html](https://lists.launchpad.net/dhis2-devs/msg47211.html)) but I cannot find a manual or correspondence online. Happy to provide more details on use case on request. > > > > > > Brian > > > [![Akros](https://dhis2.b-cdn.net/uploads/default/original/3X/9/4/94b9e0d9fe06f7aac51d52017dbd5a06d136c2a5.png)](http://www.akros.com/) > > Brian O’Donnell, MPAff > > Informatics Project Manager > > [bodonnell@akros.com](mailto:bodonnell@akros.com) > > > – > > > * * * > > > > Mailing list: [https://launchpad.net/~dhis2-users](https://launchpad.net/~dhis2-users) > > > > Post to : [dhis2-users@lists.launchpad.net](mailto:dhis2-users@lists.launchpad.net) > > > > Unsubscribe : [https://launchpad.net/~dhis2-users](https://launchpad.net/~dhis2-users) > > > > More help : [https://help.launchpad.net/ListHelp](https://help.launchpad.net/ListHelp) > > – > > **Em Le Hong** > DHIS2 Implementation| \*\*HISP Vietnam \*\* > > [em.hispvietnam@gmail.com](mailto:em.hispvietnam@gmail.com) | **Skype:** [em.hispvietnam@gmail.com](mailto:em.hispvietnam@gmail.com) > > ![](https://drive.google.com/uc?id=0B-tlJrv190f5dmR1Y0t2NERvcVU&export=download)