What strategies have others used to ensure that tracked entities have unique IDs in the absence of an existing unique identifier?
For people, we’re considering a combination of name, date of birth (or estimated date of birth), parent’s names, place of birth, etc.
We’re also considering a soundex like search feature to find people (since names and places could be misspelled).
The thing I’m not sure of is what is the best strategy to have the system auto-generate this ID in the absence of a national ID number? i.e. The system requires minimum information and generates the ID based on the entered data.
Does this have to be implemented using a custom form for data entry with API interface for POST/GET?
What strategies have others used to ensure that tracked entities have unique IDs in the absence of an existing unique identifier?
For people, we’re considering a combination of name, date of birth (or estimated date of birth), parent’s names, place of birth, etc.
We’re also considering a soundex like search feature to find people (since names and places could be misspelled).
The thing I’m not sure of is what is the best strategy to have the system auto-generate this ID in the absence of a national ID number? i.e. The system requires minimum information and generates the ID based on the entered data.
Does this have to be implemented using a custom form for data entry with API interface for POST/GET?
Currently we have attribute Unique Identifiers with just simply random generated number that could be set to be unique within Orgunits or entire system. This is being expanded to address your need to customize to the use cases pattern; check jira issue (DHIS2-434) in progress for 2.29.
Please review the suggestions and add your comments.
Again you can use program rules (Assign) to construct the ID you are describing; combination of names, age, place birth … if they are corrected as attributes. The only challenge now will be that the generated code will not be enforced for uniqueness.
Regards
···
On Thu, Nov 16, 2017 at 1:04 PM, Stanley Kalyati skalyati@gmail.com wrote:
What strategies have others used to ensure that tracked entities have unique IDs in the absence of an existing unique identifier?
For people, we’re considering a combination of name, date of birth (or estimated date of birth), parent’s names, place of birth, etc.
We’re also considering a soundex like search feature to find people (since names and places could be misspelled).
The thing I’m not sure of is what is the best strategy to have the system auto-generate this ID in the absence of a national ID number? i.e. The system requires minimum information and generates the ID based on the entered data.
Does this have to be implemented using a custom form for data entry with API interface for POST/GET?
Currently we have attribute Unique Identifiers with just simply random generated number that could be set to be unique within Orgunits or entire system. This is being expanded to address your need to customize to the use cases pattern; check jira issue (DHIS2-434) in progress for 2.29.
Please review the suggestions and add your comments.
Again you can use program rules (Assign) to construct the ID you are describing; combination of names, age, place birth … if they are corrected as attributes. The only challenge now will be that the generated code will not be enforced for uniqueness.
What strategies have others used to ensure that tracked entities have unique IDs in the absence of an existing unique identifier?
For people, we’re considering a combination of name, date of birth (or estimated date of birth), parent’s names, place of birth, etc.
We’re also considering a soundex like search feature to find people (since names and places could be misspelled).
The thing I’m not sure of is what is the best strategy to have the system auto-generate this ID in the absence of a national ID number? i.e. The system requires minimum information and generates the ID based on the entered data.
Does this have to be implemented using a custom form for data entry with API interface for POST/GET?
Currently we have attribute Unique Identifiers with just simply random generated number that could be set to be unique within Orgunits or entire system. This is being expanded to address your need to customize to the use cases pattern; check jira issue (DHIS2-434) in progress for 2.29.
Please review the suggestions and add your comments.
Again you can use program rules (Assign) to construct the ID you are describing; combination of names, age, place birth … if they are corrected as attributes. The only challenge now will be that the generated code will not be enforced for uniqueness.
What strategies have others used to ensure that tracked entities have unique IDs in the absence of an existing unique identifier?
For people, we’re considering a combination of name, date of birth (or estimated date of birth), parent’s names, place of birth, etc.
We’re also considering a soundex like search feature to find people (since names and places could be misspelled).
The thing I’m not sure of is what is the best strategy to have the system auto-generate this ID in the absence of a national ID number? i.e. The system requires minimum information and generates the ID based on the entered data.
Does this have to be implemented using a custom form for data entry with API interface for POST/GET?