Possibility to make tracker data element unique

Dear All CBS members

Specimen ID in Lab require unique value in organisation unit.

As draft document of CBS in DHIS2 suggested to design Lab result in a
separate stage, it is important to have the functionality to make data
element unique. It will help to prevent wrong data entry in some values
like specimen ID from Lab.

I have put in jira but still open:
https://jira.dhis2.org/browse/DHIS2-2458

Another way to address this issue is allowing assignment of attribute to
program stages. So Specimen ID from lab can made it unique as attribute.

Any other idea?

*Nayeem Al Mifthah*
*Consultant for HSS, Health MIS, M&E*
Email: n.mifthah@gmail.com
Cell:+8801914030574
Skype: nayeem.a.m

Dear Nayeem,

We had the same issue and fixed with custom form. We had to generate the
unique identifier.

I support the addition of the feature.

Alex

···

On Thu, Nov 9, 2017 at 10:02 AM, Nayeem Al Mifthah <n.mifthah@gmail.com> wrote:

Dear All CBS members

Specimen ID in Lab require unique value in organisation unit.

As draft document of CBS in DHIS2 suggested to design Lab result in a
separate stage, it is important to have the functionality to make data
element unique. It will help to prevent wrong data entry in some values
like specimen ID from Lab.

I have put in jira but still open:
[DHIS2-2458] - Jira

Another way to address this issue is allowing assignment of attribute to
program stages. So Specimen ID from lab can made it unique as attribute.

Any other idea?

*Nayeem Al Mifthah*
*Consultant for HSS, Health MIS, M&E*
Email: n.mifthah@gmail.com
Cell:+8801914030574 <+880%201914-030574>
Skype: nayeem.a.m

You are receiving this message because you are a member of the community DHIS2
Case-Based Surveillance Community
<https://knowledge-gateway.org/dhis2-cbs-community&gt;\.

View this contribution on the web site
<Knowledge Gateway - Login;

A reply to this message will be sent to all members of DHIS2 Case-Based
Surveillance Community.

Reply to sender <n.mifthah@gmail.com> | Unsubscribe
<leave.dhis2-cbs-community@knowledge-gateway.org>

--
Alex Tumwesigye

Technical Advisor - DHIS2 (Consultant),
Ministry of Health/AFENET | HISP Uganda
Kampala
Uganda
+256 774149 775, + 256 759 800161
Skype ID: talexie

IT Consultant (Servers, Networks and Security, Health Information Systems -
DHIS2, Disease Outbreak & Surveillance Systems) & Solar Consultant

"I don't want to be anything other than what I have been - one tree hill "

Hi,

I had same issue,

My solution was:

1. Use custom form
2. Use api to get unique number for that field

It need a little bit coding. :slight_smile: hope it helps.

<img src=‘/uploads/default/original/1X/99a3b2a80e5fa9077a60db4681d9a743011ea407.png’ width=‘690’ height=‘165’>

*Truong Nguyen, *HIS Specialist, Global Health Security Partnership
PATH

Hi Alex - then you should vote for it in JIRA :wink:

Cheers,
Knut

···

On Thu, Nov 9, 2017 at 11:05 AM, atumwesigye@gmail.com < atumwesigye@gmail.com> wrote:

Dear Nayeem,

We had the same issue and fixed with custom form. We had to generate the
unique identifier.

I support the addition of the feature.

Alex

On Thu, Nov 9, 2017 at 10:02 AM, Nayeem Al Mifthah <n.mifthah@gmail.com> > wrote:

Dear All CBS members

Specimen ID in Lab require unique value in organisation unit.

As draft document of CBS in DHIS2 suggested to design Lab result in a
separate stage, it is important to have the functionality to make data
element unique. It will help to prevent wrong data entry in some values
like specimen ID from Lab.

I have put in jira but still open:
[DHIS2-2458] - Jira

Another way to address this issue is allowing assignment of attribute to
program stages. So Specimen ID from lab can made it unique as attribute.

Any other idea?

*Nayeem Al Mifthah*
*Consultant for HSS, Health MIS, M&E*
Email: n.mifthah@gmail.com
Cell:+8801914030574 <+880%201914-030574>
Skype: nayeem.a.m

You are receiving this message because you are a member of the community DHIS2
Case-Based Surveillance Community
<https://knowledge-gateway.org/dhis2-cbs-community&gt;\.

View this contribution on the web site
<Knowledge Gateway - Login;

A reply to this message will be sent to all members of DHIS2 Case-Based
Surveillance Community.

Reply to sender <n.mifthah@gmail.com> | Unsubscribe
<leave.dhis2-cbs-community@knowledge-gateway.org>

--
Alex Tumwesigye

Technical Advisor - DHIS2 (Consultant),
Ministry of Health/AFENET | HISP Uganda
Kampala
Uganda
+256 774149 775, + 256 759 800161
Skype ID: talexie

IT Consultant (Servers, Networks and Security, Health Information Systems
- DHIS2, Disease Outbreak & Surveillance Systems) & Solar Consultant

"I don't want to be anything other than what I have been - one tree hill "

You are receiving this message because you are a member of the community DHIS2
Case-Based Surveillance Community
<https://knowledge-gateway.org/dhis2-cbs-community&gt;\.

View this contribution on the web site
<Knowledge Gateway - Login;

A reply to this message will be sent to all members of DHIS2 Case-Based
Surveillance Community.

Reply to sender <atumwesigye@gmail.com> | Unsubscribe
<leave.dhis2-cbs-community@knowledge-gateway.org>

--
Knut Staring
Dept. of Informatics, University of Oslo
Norway: +4791880522
Skype: knutstar

Dear Nayeem,
could this issue be more or less the feature that you needed?
DHIS2-434 <[DHIS2-434] - Jira;

Is it possible to add your specific requirements if there is anything else we should think of working on this issue?

Markus

···

9. nov. 2017 kl. 11.05 skrev atumwesigye@gmail.com:

Dear Nayeem,

We had the same issue and fixed with custom form. We had to generate the unique identifier.

I support the addition of the feature.

Alex

On Thu, Nov 9, 2017 at 10:02 AM, Nayeem Al Mifthah <n.mifthah@gmail.com <mailto:n.mifthah@gmail.com>> wrote:
Dear All CBS members

Specimen ID in Lab require unique value in organisation unit.

As draft document of CBS in DHIS2 suggested to design Lab result in a separate stage, it is important to have the functionality to make data element unique. It will help to prevent wrong data entry in some values like specimen ID from Lab.

I have put in jira but still open:
[DHIS2-2458] - Jira

Another way to address this issue is allowing assignment of attribute to program stages. So Specimen ID from lab can made it unique as attribute.

Any other idea?

Nayeem Al Mifthah
Consultant for HSS, Health MIS, M&E
Email: n.mifthah@gmail.com <mailto:n.mifthah@gmail.com>
Cell:+8801914030574 <tel:+880%201914-030574>
Skype: nayeem.a.m
You are receiving this message because you are a member of the community DHIS2 Case-Based Surveillance Community <https://knowledge-gateway.org/dhis2-cbs-community&gt;\.

View this contribution on the web site <Knowledge Gateway - Login;
A reply to this message will be sent to all members of DHIS2 Case-Based Surveillance Community.

Reply to sender <mailto:n.mifthah@gmail.com> | Unsubscribe <mailto:leave.dhis2-cbs-community@knowledge-gateway.org>

--
Alex Tumwesigye

Technical Advisor - DHIS2 (Consultant),
Ministry of Health/AFENET | HISP Uganda
Kampala
Uganda
+256 774149 775 <>, + 256 759 800161 <>
Skype ID: talexie

IT Consultant (Servers, Networks and Security, Health Information Systems - DHIS2, Disease Outbreak & Surveillance Systems) & Solar Consultant

"I don't want to be anything other than what I have been - one tree hill "
You are receiving this message because you are a member of the community DHIS2 Case-Based Surveillance Community <https://knowledge-gateway.org/dhis2-cbs-community&gt;\.

View this contribution on the web site <Knowledge Gateway - Login;
A reply to this message will be sent to all members of DHIS2 Case-Based Surveillance Community.

Reply to sender <mailto:atumwesigye@gmail.com> | Unsubscribe <mailto:leave.dhis2-cbs-community@knowledge-gateway.org>

Dear Markus
The issue you have shared is talking about custom attribute generation.

My proposal is to make data element unique.

The draft document for CBS demo design uploaded in knowledge gateway
proposed repeatable stage for specimen tracking and lab result. We can't
use attribute in program stage. But lab require unique ID. As a result
either we need to add feature to make data element unique or allow
attribute to be added in program stage to design the specimen ID as unique
and include it in repeatable stage.

*Nayeem Al Mifthah*
*Consultant for HSS, Health MIS, M&E*
Email: n.mifthah@gmail.com
Cell:+8801914030574
Skype: nayeem.a.m

···

On Thu, Nov 9, 2017 at 5:52 PM, markus@dhis2.org <markus@dhis2.org> wrote:

Dear Nayeem,
could this issue be more or less the feature that you needed?
DHIS2-434 <[DHIS2-434] - Jira;

Is it possible to add your specific requirements if there is anything else
we should think of working on this issue?

Markus

9. nov. 2017 kl. 11.05 skrev atumwesigye@gmail.com:

Dear Nayeem,

We had the same issue and fixed with custom form. We had to generate the
unique identifier.

I support the addition of the feature.

Alex

On Thu, Nov 9, 2017 at 10:02 AM, Nayeem Al Mifthah <n.mifthah@gmail.com> > wrote:

Dear All CBS members

Specimen ID in Lab require unique value in organisation unit.

As draft document of CBS in DHIS2 suggested to design Lab result in a
separate stage, it is important to have the functionality to make data
element unique. It will help to prevent wrong data entry in some values
like specimen ID from Lab.

I have put in jira but still open:
[DHIS2-2458] - Jira

Another way to address this issue is allowing assignment of attribute to
program stages. So Specimen ID from lab can made it unique as attribute.

Any other idea?

*Nayeem Al Mifthah*
*Consultant for HSS, Health MIS, M&E*
Email: n.mifthah@gmail.com
Cell:+8801914030574 <+880%201914-030574>
Skype: nayeem.a.m

You are receiving this message because you are a member of the community DHIS2
Case-Based Surveillance Community
<https://knowledge-gateway.org/dhis2-cbs-community&gt;\.

View this contribution on the web site
<Knowledge Gateway - Login;

A reply to this message will be sent to all members of DHIS2 Case-Based
Surveillance Community.

Reply to sender <n.mifthah@gmail.com> | Unsubscribe
<leave.dhis2-cbs-community@knowledge-gateway.org>

--
Alex Tumwesigye

Technical Advisor - DHIS2 (Consultant),
Ministry of Health/AFENET | HISP Uganda
Kampala
Uganda
+256 774149 775, + 256 759 800161
Skype ID: talexie

IT Consultant (Servers, Networks and Security, Health Information Systems
- DHIS2, Disease Outbreak & Surveillance Systems) & Solar Consultant

"I don't want to be anything other than what I have been - one tree hill "

You are receiving this message because you are a member of the community DHIS2
Case-Based Surveillance Community
<https://knowledge-gateway.org/dhis2-cbs-community&gt;\.

View this contribution on the web site
<Knowledge Gateway - Login;

A reply to this message will be sent to all members of DHIS2 Case-Based
Surveillance Community.

Reply to sender <atumwesigye@gmail.com> | Unsubscribe
<leave.dhis2-cbs-community@knowledge-gateway.org>

You are receiving this message because you are a member of the community DHIS2
Case-Based Surveillance Community
<https://knowledge-gateway.org/dhis2-cbs-community&gt;\.

View this contribution on the web site
<Knowledge Gateway - Login;

A reply to this message will be sent to all members of DHIS2 Case-Based
Surveillance Community.

Reply to sender <markus@dhis2.org> | Unsubscribe
<leave.dhis2-cbs-community@knowledge-gateway.org>

Thank you Nayeem,
Sorry for shooting off the email before reading properly.

In the case of tracked entity attributes, one of the main advantages for the uniqueness scope is that it is a very reliable data point for avoiding duplication of data. If you try and register a person and the national ID entered already exists in the system - you would open her existing record instead of creating a new one. In your case you want to enter a specimen ID from lab as a data element in a program stage. I assume the specimen ID would be printed on a piece of paper, and entered into the system when registering the lab sample? Two questions to help understand the usecase better:
- What would you suspect being the the main reason for duplication of values of the "Specimen ID" of a lab program stage? And where would the duplication generally be?
- What would the clinican do if trying to enter a specimen ID, and the system prevents her from doing so because it would cause a duplication?

The issue from Alex seems to be that a data element should be or is not only unique, but generated by the tracker program itself?

Best regards,
Markus

···

9. nov. 2017 kl. 15.23 skrev Nayeem Al Mifthah <n.mifthah@gmail.com>:

Dear Markus
The issue you have shared is talking about custom attribute generation.

My proposal is to make data element unique.

The draft document for CBS demo design uploaded in knowledge gateway proposed repeatable stage for specimen tracking and lab result. We can't use attribute in program stage. But lab require unique ID. As a result either we need to add feature to make data element unique or allow attribute to be added in program stage to design the specimen ID as unique and include it in repeatable stage.

Nayeem Al Mifthah
Consultant for HSS, Health MIS, M&E
Email: n.mifthah@gmail.com <mailto:n.mifthah@gmail.com>
Cell:+8801914030574
Skype: nayeem.a.m

On Thu, Nov 9, 2017 at 5:52 PM, markus@dhis2.org <mailto:markus@dhis2.org> <markus@dhis2.org <mailto:markus@dhis2.org>> wrote:
Dear Nayeem,
could this issue be more or less the feature that you needed?
DHIS2-434 <[DHIS2-434] - Jira;

Is it possible to add your specific requirements if there is anything else we should think of working on this issue?

Markus

9. nov. 2017 kl. 11.05 skrev atumwesigye@gmail.com <mailto:atumwesigye@gmail.com>:

Dear Nayeem,

We had the same issue and fixed with custom form. We had to generate the unique identifier.

I support the addition of the feature.

Alex

On Thu, Nov 9, 2017 at 10:02 AM, Nayeem Al Mifthah <n.mifthah@gmail.com <mailto:n.mifthah@gmail.com>> wrote:
Dear All CBS members

Specimen ID in Lab require unique value in organisation unit.

As draft document of CBS in DHIS2 suggested to design Lab result in a separate stage, it is important to have the functionality to make data element unique. It will help to prevent wrong data entry in some values like specimen ID from Lab.

I have put in jira but still open:
[DHIS2-2458] - Jira

Another way to address this issue is allowing assignment of attribute to program stages. So Specimen ID from lab can made it unique as attribute.

Any other idea?

Nayeem Al Mifthah
Consultant for HSS, Health MIS, M&E
Email: n.mifthah@gmail.com <mailto:n.mifthah@gmail.com>
Cell:+8801914030574 <tel:+880%201914-030574>
Skype: nayeem.a.m
You are receiving this message because you are a member of the community DHIS2 Case-Based Surveillance Community <https://knowledge-gateway.org/dhis2-cbs-community&gt;\.

View this contribution on the web site <Knowledge Gateway - Login;
A reply to this message will be sent to all members of DHIS2 Case-Based Surveillance Community.

Reply to sender <mailto:n.mifthah@gmail.com> | Unsubscribe <mailto:leave.dhis2-cbs-community@knowledge-gateway.org>

--
Alex Tumwesigye

Technical Advisor - DHIS2 (Consultant),
Ministry of Health/AFENET | HISP Uganda
Kampala
Uganda
+256 774149 775 <>, + 256 759 800161 <>
Skype ID: talexie

IT Consultant (Servers, Networks and Security, Health Information Systems - DHIS2, Disease Outbreak & Surveillance Systems) & Solar Consultant

"I don't want to be anything other than what I have been - one tree hill "
You are receiving this message because you are a member of the community DHIS2 Case-Based Surveillance Community <https://knowledge-gateway.org/dhis2-cbs-community&gt;\.

View this contribution on the web site <Knowledge Gateway - Login;
A reply to this message will be sent to all members of DHIS2 Case-Based Surveillance Community.

Reply to sender <mailto:atumwesigye@gmail.com> | Unsubscribe <mailto:leave.dhis2-cbs-community@knowledge-gateway.org>

You are receiving this message because you are a member of the community DHIS2 Case-Based Surveillance Community <https://knowledge-gateway.org/dhis2-cbs-community&gt;\.

View this contribution on the web site <Knowledge Gateway - Login;
A reply to this message will be sent to all members of DHIS2 Case-Based Surveillance Community.

Reply to sender <mailto:markus@dhis2.org> | Unsubscribe <mailto:leave.dhis2-cbs-community@knowledge-gateway.org>

Dear Markus,

The experience we have seen is that specimen, lab request ids are not
usually unique across the entire country. They may be unique for a facility
only ( in most cases not because they are generated by the human and there
is a high probability of repeatability of the same ids). In some cases, the
system may be used as a small lab module for the case of idsr, it can be
used for result confirmation.

It is therefore required that we have a unique generator on a data element
in a program stage so that at least lab requests and specimens are uniquely
identified in DHIS2 using a human readable identifier. It would be good if
the pattern can include orgunit code, etc ( this can still be achieved
using program rules - assign action).

Hope this explains it a bit. May be I can share some screenshots of my
implementation for lab requests and lab resulting where a lab request has
multiple lab results uniquely identified.

Alex

···

On Thursday, November 9, 2017, markus@dhis2.org <markus@dhis2.org> wrote:

Thank you Nayeem,
Sorry for shooting off the email before reading properly.

In the case of tracked entity attributes, one of the main advantages for
the uniqueness scope is that it is a very reliable data point for avoiding
duplication of data. If you try and register a person and the national ID
entered already exists in the system - you would open her existing record
instead of creating a new one. In your case you want to enter a specimen ID
from lab as a data element in a program stage. I assume the specimen ID
would be printed on a piece of paper, and entered into the system when
registering the lab sample? Two questions to help understand the usecase
better:
- What would you suspect being the the main reason for duplication of
values of the "Specimen ID" of a lab program stage? And where would the
duplication generally be?
- What would the clinican do if trying to enter a specimen ID, and the
system prevents her from doing so because it would cause a duplication?

The issue from Alex seems to be that a data element should be or is not
only unique, but generated by the tracker program itself?

Best regards,
Markus

9. nov. 2017 kl. 15.23 skrev Nayeem Al Mifthah <n.mifthah@gmail.com
<javascript:_e(%7B%7D,'cvml','n.mifthah@gmail.com');>>:

Dear Markus
The issue you have shared is talking about custom attribute generation.

My proposal is to make data element unique.

The draft document for CBS demo design uploaded in knowledge gateway
proposed repeatable stage for specimen tracking and lab result. We can't
use attribute in program stage. But lab require unique ID. As a result
either we need to add feature to make data element unique or allow
attribute to be added in program stage to design the specimen ID as
unique and include it in repeatable stage.

*Nayeem Al Mifthah*
*Consultant for HSS, Health MIS, M&E*
Email: n.mifthah@gmail.com
<javascript:_e(%7B%7D,'cvml','n.mifthah@gmail.com');>
Cell:+8801914030574
Skype: nayeem.a.m

On Thu, Nov 9, 2017 at 5:52 PM, markus@dhis2.org > <javascript:_e(%7B%7D,'cvml','markus@dhis2.org');> <markus@dhis2.org > <javascript:_e(%7B%7D,'cvml','markus@dhis2.org');>> wrote:

Dear Nayeem,
could this issue be more or less the feature that you needed?
DHIS2-434 <[DHIS2-434] - Jira;

Is it possible to add your specific requirements if there is anything
else we should think of working on this issue?

Markus

9. nov. 2017 kl. 11.05 skrev atumwesigye@gmail.com
<javascript:_e(%7B%7D,'cvml','atumwesigye@gmail.com');>:

Dear Nayeem,

We had the same issue and fixed with custom form. We had to generate the
unique identifier.

I support the addition of the feature.

Alex

On Thu, Nov 9, 2017 at 10:02 AM, Nayeem Al Mifthah <n.mifthah@gmail.com >> <javascript:_e(%7B%7D,'cvml','n.mifthah@gmail.com');>> wrote:

Dear All CBS members

Specimen ID in Lab require unique value in organisation unit.

As draft document of CBS in DHIS2 suggested to design Lab result in a
separate stage, it is important to have the functionality to make data
element unique. It will help to prevent wrong data entry in some values
like specimen ID from Lab.

I have put in jira but still open:
[DHIS2-2458] - Jira

Another way to address this issue is allowing assignment of attribute to
program stages. So Specimen ID from lab can made it unique as attribute.

Any other idea?

*Nayeem Al Mifthah*
*Consultant for HSS, Health MIS, M&E*
Email: n.mifthah@gmail.com
<javascript:_e(%7B%7D,'cvml','n.mifthah@gmail.com');>
Cell:+8801914030574 <+880%201914-030574>
Skype: nayeem.a.m

You are receiving this message because you are a member of the community DHIS2
Case-Based Surveillance Community
<https://knowledge-gateway.org/dhis2-cbs-community&gt;\.

View this contribution on the web site
<Knowledge Gateway - Login;

A reply to this message will be sent to all members of DHIS2 Case-Based
Surveillance Community.

Reply to sender <javascript:_e(%7B%7D,'cvml','n.mifthah@gmail.com');> |
Unsubscribe
<javascript:_e(%7B%7D,'cvml','leave.dhis2-cbs-community@knowledge-gateway.org');>

--
Alex Tumwesigye

Technical Advisor - DHIS2 (Consultant),
Ministry of Health/AFENET | HISP Uganda
Kampala
Uganda
+256 774149 775, + 256 759 800161
Skype ID: talexie

IT Consultant (Servers, Networks and Security, Health Information Systems
- DHIS2, Disease Outbreak & Surveillance Systems) & Solar Consultant

"I don't want to be anything other than what I have been - one tree hill "

You are receiving this message because you are a member of the community DHIS2
Case-Based Surveillance Community
<https://knowledge-gateway.org/dhis2-cbs-community&gt;\.

View this contribution on the web site
<Knowledge Gateway - Login;

A reply to this message will be sent to all members of DHIS2 Case-Based
Surveillance Community.

Reply to sender <javascript:_e(%7B%7D,'cvml','atumwesigye@gmail.com');>
> Unsubscribe
<javascript:_e(%7B%7D,'cvml','leave.dhis2-cbs-community@knowledge-gateway.org');>

You are receiving this message because you are a member of the community DHIS2
Case-Based Surveillance Community
<https://knowledge-gateway.org/dhis2-cbs-community&gt;\.

View this contribution on the web site
<Knowledge Gateway - Login;

A reply to this message will be sent to all members of DHIS2 Case-Based
Surveillance Community.

Reply to sender <javascript:_e(%7B%7D,'cvml','markus@dhis2.org');> |
Unsubscribe
<javascript:_e(%7B%7D,'cvml','leave.dhis2-cbs-community@knowledge-gateway.org');>

You are receiving this message because you are a member of the community DHIS2
Case-Based Surveillance Community
<https://knowledge-gateway.org/dhis2-cbs-community&gt;\.

View this contribution on the web site
<Knowledge Gateway - Login;

A reply to this message will be sent to all members of DHIS2 Case-Based
Surveillance Community.

Reply to sender <javascript:_e(%7B%7D,'cvml','markus@dhis2.org');> |
Unsubscribe
<javascript:_e(%7B%7D,'cvml','leave.dhis2-cbs-community@knowledge-gateway.org');>

--
Alex Tumwesigye

Technical Advisor - DHIS2 (Consultant),
Ministry of Health/AFENET | HISP Uganda
Kampala
Uganda
+256 774149 775, + 256 759 800161
Skype ID: talexie

IT Consultant (Servers, Networks and Security, Health Information Systems -
DHIS2, Disease Outbreak & Surveillance Systems) & Solar Consultant

"I don't want to be anything other than what I have been - one tree hill "