Option, option set and dataelement

Dear all,

Sorry for this basic question but I prefer to ask for confirmation.

Can we use the same option in different option sets (for example positive/negative in different option Sets) and the same option sets in different dataelements (for example the option sets results for different tests)?

Thanks!

Lise.

Dear Lise

We don’t have uniqueness in options across different option sets. So it’s possible to use same options names in different options sets.

Regards

···

22, 2016, 6:51 PM GROUT, Lise groutl@who.int wrote:

Dear all,

Sorry for this basic question but I prefer to ask for confirmation.

Can we use the same option in different option sets (for example positive/negative in different option Sets) and the same option sets in different dataelements (for example the option sets results for different tests)?

Thanks!

Lise.


Mailing list: https://launchpad.net/~dhis2-users

Post to : dhis2-users@lists.launchpad.net

Unsubscribe : https://launchpad.net/~dhis2-users

More help : https://help.launchpad.net/ListHelp

Hi Lise!
You can use the same Option Set in multiple data elements. This will in turn mean that you use the same options for these data elements.

Using the same options in different option sets is not possible through the UI - do you have a use case for this?

Best regards,
Markus

···

22. mai 2016 kl. 17.31 skrev GROUT, Lise <groutl@who.int>:

Dear all,

Sorry for this basic question but I prefer to ask for confirmation.

Can we use the same option in different option sets (for example positive/negative in different option Sets) and the same option sets in different dataelements (for example the option sets results for different tests)?

Thanks!

Lise.

_______________________________________________
Mailing list: https://launchpad.net/~dhis2-users
Post to : dhis2-users@lists.launchpad.net <mailto:dhis2-users@lists.launchpad.net>
Unsubscribe : https://launchpad.net/~dhis2-users
More help : https://help.launchpad.net/ListHelp

Hi Markus,

Thank you very much for your quick help!

Very simple use case: the option “unknown” is used in most of my option sets. Can I use the same “unknown” or do I have to create one “unknown” per option sets. The option 1 would be more logical, but I don’t know how it will work in the analysis.

Thank you!

Lise.

···

From: Markus Bekken [mailto:markus.bekken@gmail.com]

Sent: 22 May 2016 18:11

To: GROUT, Lise

Cc: dhis2-users@lists.launchpad.net

Subject: Re: [Dhis2-users] Option, option set and dataelement

Hi Lise!

You can use the same Option Set in multiple data elements. This will in turn mean that you use the same options for these data elements.

Using the same options in different option sets is not possible through the UI - do you have a use case for this?

Best regards,

Markus

  1. mai 2016 kl. 17.31 skrev GROUT, Lise groutl@who.int:

Dear all,

Sorry for this basic question but I prefer to ask for confirmation.

Can we use the same option in different option sets (for example positive/negative in different option Sets) and the same option sets in different dataelements (for example the option sets results for different tests)?

Thanks!

Lise.


Mailing list: https://launchpad.net/~dhis2-users

Post to : dhis2-users@lists.launchpad.net

Unsubscribe : https://launchpad.net/~dhis2-users

More help : https://help.launchpad.net/ListHelp

I think your instinct of reusing options is sound. However, in the database we are connecting each option to exactly one option set - and you will have to duplicate your common options for now.

Best regards,
Markus

···

22. mai 2016 kl. 18.25 skrev GROUT, Lise <groutl@who.int>:

Hi Markus,

Thank you very much for your quick help!

Very simple use case: the option “unknown” is used in most of my option sets. Can I use the same “unknown” or do I have to create one “unknown” per option sets. The option 1 would be more logical, but I don’t know how it will work in the analysis.

Thank you!

Lise.

From: Markus Bekken [mailto:markus.bekken@gmail.com <mailto:markus.bekken@gmail.com>]
Sent: 22 May 2016 18:11
To: GROUT, Lise
Cc: dhis2-users@lists.launchpad.net <mailto:dhis2-users@lists.launchpad.net>
Subject: Re: [Dhis2-users] Option, option set and dataelement

Hi Lise!
You can use the same Option Set in multiple data elements. This will in turn mean that you use the same options for these data elements.

Using the same options in different option sets is not possible through the UI - do you have a use case for this?

Best regards,
Markus

22. mai 2016 kl. 17.31 skrev GROUT, Lise <groutl@who.int <mailto:groutl@who.int>>:

Dear all,

Sorry for this basic question but I prefer to ask for confirmation.

Can we use the same option in different option sets (for example positive/negative in different option Sets) and the same option sets in different dataelements (for example the option sets results for different tests)?

Thanks!

Lise.

_______________________________________________
Mailing list: https://launchpad.net/~dhis2-users
Post to : dhis2-users@lists.launchpad.net <mailto:dhis2-users@lists.launchpad.net>
Unsubscribe : https://launchpad.net/~dhis2-users
More help : https://help.launchpad.net/ListHelp

Dear Markus and Prosper,

Thank you for your help!

So if I understand correctly, I have to create different options (with different UID and codes) but I can reuse the same option name?

Thank you!

Lise.

···

We don’t have uniqueness in options across different option sets. So it’s possible to use same options names in different options sets.

Regards

22, 2016, 6:51 PM GROUT, Lise groutl@who.int wrote:

Dear all,

Sorry for this basic question but I prefer to ask for confirmation.

Can we use the same option in different option sets (for example positive/negative in different option Sets) and the same option sets in different dataelements (for example the option sets results for different tests)?

Thanks!

Lise.


Mailing list: https://launchpad.net/~dhis2-users

Post to : dhis2-users@lists.launchpad.net

Unsubscribe : https://launchpad.net/~dhis2-users

More help : https://help.launchpad.net/ListHelp

Hi Lise,

It is possible to re-use the same option set for several data elements, for example you can have option-set called “Test Result” with these options: “positive,Negative, Not applicable”…this can be applied to different data elements like "“Pregnancy test”,“HIV Test” so that they both pick the same option-set.

Kind Regards

···

Seth Okeyo | Data Management Officer

Drugs for Neglected Diseases initiative – Africa

c/o Centre for Clinical Research | Kenya Medical Research Institute| Nairobi | Kenya

T: +254 20 2077767 | +254 20 2403336 | +254 20 2733031 | M: +254 727389149 | sokeyo@dndi.org
| skype: dndi_seth.okeyo |@sethokeyo

*Best Science for the Most Neglected * | www.dndi.org

cid:image001.gif@01D049FD.1DA795A0cid:image002.gif@01D049FD.1DA795A0cid:image003.gif@01D049FD.1DA795A0cid:image004.gif@01D049FD.1DA795A0cid:image005.gif@01D049FD.1DA795A0


From: Dhis2-users dhis2-users-bounces+sokeyo=dndi.org@lists.launchpad.net on behalf of GROUT, Lise groutl@who.int

Sent: Sunday, May 22, 2016 7:50:28 PM

To: Prosper BT; dhis2-users@lists.launchpad.net

Subject: Re: [Dhis2-users] Option, option set and dataelement

Dear Markus and Prosper,

Thank you for your help!

So if I understand correctly, I have to create different options (with different UID and codes) but I can reuse the same option name?

Thank you!

Lise.

From: Prosper BT [mailto:ptb3000@gmail.com]

Sent: 22 May 2016 18:11

To: GROUT, Lise; dhis2-users@lists.launchpad.net

Subject: Re: [Dhis2-users] Option, option set and dataelement

Dear Lise

We don’t have uniqueness in options across different option sets. So it’s possible to use same options names in different options sets.

Regards

22, 2016, 6:51 PM GROUT, Lise groutl@who.int wrote:

Dear all,

Sorry for this basic question but I prefer to ask for confirmation.

Can we use the same option in different option sets (for example positive/negative in different option Sets) and the same option sets in different dataelements (for example the option sets results for different tests)?

Thanks!

Lise.


Mailing list: https://launchpad.net/~dhis2-users

Post to : dhis2-users@lists.launchpad.net

Unsubscribe : https://launchpad.net/~dhis2-users

More help : https://help.launchpad.net/ListHelp

Dear Seth,

Thank you for your message. Why did you choose not to re-use the same option set in your tracker then? (microscopy, pregnancy, HIV…).

Best,

Lise.

image

···

From: Seth Okeyo [mailto:sokeyo@dndi.org]

Sent: 22 May 2016 21:39

To: GROUT, Lise; Prosper BT; dhis2-users@lists.launchpad.net

Subject: Re: [Dhis2-users] Option, option set and dataelement

Hi Lise,

It is possible to re-use the same option set for several data elements, for example you can have option-set called “Test Result” with these options: “positive,Negative, Not applicable”…this can be applied to different data elements like "“Pregnancy test”,“HIV Test” so that they both pick the same option-set.

Kind Regards

Seth Okeyo | Data Management Officer

Drugs for Neglected Diseases initiative – Africa

c/o Centre for Clinical Research | Kenya Medical Research Institute| Nairobi | Kenya

T: +254 20 2077767 | +254 20 2403336 | +254 20 2733031 | M: +254 727389149 | sokeyo@dndi.org
| skype: dndi_seth.okeyo |@sethokeyo

*Best Science for the Most Neglected * | www.dndi.org


From: Dhis2-users dhis2-users-bounces+sokeyo=dndi.org@lists.launchpad.net on behalf of GROUT, Lise groutl@who.int

Sent: Sunday, May 22, 2016 7:50:28 PM

To: Prosper BT; dhis2-users@lists.launchpad.net

Subject: Re: [Dhis2-users] Option, option set and dataelement

Dear Markus and Prosper,

Thank you for your help!

So if I understand correctly, I have to create different options (with different UID and codes) but I can reuse the same option name?

Thank you!

Lise.

From: Prosper BT [mailto:ptb3000@gmail.com]

Sent: 22 May 2016 18:11

To: GROUT, Lise; dhis2-users@lists.launchpad.net

Subject: Re: [Dhis2-users] Option, option set and dataelement

Dear Lise

We don’t have uniqueness in options across different option sets. So it’s possible to use same options names in different options sets.

Regards

22, 2016, 6:51 PM GROUT, Lise groutl@who.int wrote:

Dear all,

Sorry for this basic question but I prefer to ask for confirmation.

Can we use the same option in different option sets (for example positive/negative in different option Sets) and the same option sets in different dataelements (for example the option sets results for different tests)?

Thanks!

Lise.


Mailing list: https://launchpad.net/~dhis2-users

Post to : dhis2-users@lists.launchpad.net

Unsubscribe : https://launchpad.net/~dhis2-users

More help : https://help.launchpad.net/ListHelp

Hi Lise,

at the moment you must create a new “Unknown” option. You can give it the same name and code though as the other Unknowns. The uid will be different.

It is debatable whether this is the right way. We are considering whether to change the design to allow for re-use of options.

regards,

Lars

···

On Sun, May 22, 2016 at 6:50 PM, GROUT, Lise groutl@who.int wrote:

Dear Markus and Prosper,

Thank you for your help!

So if I understand correctly, I have to create different options (with different UID and codes) but I can reuse the same option name?

Thank you!

Lise.

From: Prosper BT [mailto:ptb3000@gmail.com]

Sent: 22 May 2016 18:11

To: GROUT, Lise; dhis2-users@lists.launchpad.net

Subject: Re: [Dhis2-users] Option, option set and dataelement

Dear Lise

We don’t have uniqueness in options across different option sets. So it’s possible to use same options names in different options sets.

Regards

22, 2016, 6:51 PM GROUT, Lise groutl@who.int wrote:

Dear all,

Sorry for this basic question but I prefer to ask for confirmation.

Can we use the same option in different option sets (for example positive/negative in different option Sets) and the same option sets in different dataelements (for example the option sets results for different tests)?

Thanks!

Lise.


Mailing list: https://launchpad.net/~dhis2-users

Post to : dhis2-users@lists.launchpad.net

Unsubscribe : https://launchpad.net/~dhis2-users

More help : https://help.launchpad.net/ListHelp


Mailing list: https://launchpad.net/~dhis2-users

Post to : dhis2-users@lists.launchpad.net

Unsubscribe : https://launchpad.net/~dhis2-users

More help : https://help.launchpad.net/ListHelp

Lars Helge Øverland

Lead developer, DHIS 2

University of Oslo

Skype: larshelgeoverland

lars@dhis2.org

http://www.dhis2.org

Thank you Lars.

Lise.

···

Hi Lise,

at the moment you must create a new “Unknown” option. You can give it the same name and code though as the other Unknowns. The uid will be different.

It is debatable whether this is the right way. We are considering whether to change the design to allow for re-use of options.

regards,

Lars

On Sun, May 22, 2016 at 6:50 PM, GROUT, Lise groutl@who.int wrote:

Dear Markus and Prosper,

Thank you for your help!

So if I understand correctly, I have to create different options (with different UID and codes) but I can reuse the same option name?

Thank you!

Lise.

From: Prosper BT [mailto:ptb3000@gmail.com]

Sent: 22 May 2016 18:11

To: GROUT, Lise;
dhis2-users@lists.launchpad.net

Subject: Re: [Dhis2-users] Option, option set and dataelement

Dear Lise

We don’t have uniqueness in options across different option sets. So it’s possible to use same options names in different options sets.

Regards

22, 2016, 6:51 PM GROUT, Lise groutl@who.int wrote:

Dear all,

Sorry for this basic question but I prefer to ask for confirmation.

Can we use the same option in different option sets (for example positive/negative in different option Sets) and the same option sets in different dataelements (for example the option sets results for different tests)?

Thanks!

Lise.


Mailing list: https://launchpad.net/~dhis2-users

Post to : dhis2-users@lists.launchpad.net

Unsubscribe : https://launchpad.net/~dhis2-users

More help : https://help.launchpad.net/ListHelp


Mailing list: https://launchpad.net/~dhis2-users

Post to : dhis2-users@lists.launchpad.net

Unsubscribe : https://launchpad.net/~dhis2-users

More help : https://help.launchpad.net/ListHelp

Lars Helge Øverland

Lead developer, DHIS 2

University of Oslo

Skype: larshelgeoverland

lars@dhis2.org

http://www.dhis2.org

I think (semantically) the correct way is to create a new "Unknown"
option, though it should have a different code and uid from other
unknowns. The displayed label just happens to be the same but the
underlying concept is different. That is, they actually represent the
likes of "Unknown age", "Unknown test result", "Unknown sex" etc.
Despite sharing the same text label, they are really quite different
options.

There is a similar issue we have grappled with
categories/categoryOptions which is resolved in a different (also
slightly unsatisfactory) way.

My longer term view is that options should be able to be reused in
different optionsets, but not in a completely free manner.

There is some experience of the problem outside of dhis2 and I believe
the established consensus is that
(i) codes/options in a controlled vocabulary are contained in a code
list. Every item in that list should be uniquely identifiable.
(ii) these items should relate to a specific concept (age, disease,
test result etc)
(ii) value sets (such as categories and optionsets in dhis2) should
be selected from one and only one codelist. There can be any number
of valuesets for any one codelist. This allows for reuse of items but
disallows a valueset with mixed concepts (ie you couldn't construct an
optionset containing 'Malaria','Male','under5','Unknown')

If we do get to re-examine our model in this area, this is the
approach I would advocate.

···

On 23 May 2016 at 12:35, Lars Helge Øverland <lars@dhis2.org> wrote:

Hi Lise,

at the moment you must create a new "Unknown" option. You can give it the
same name and code though as the other Unknowns. The uid will be different.

It is debatable whether this is the right way. We are considering whether to
change the design to allow for re-use of options.

regards,

Lars

On Sun, May 22, 2016 at 6:50 PM, GROUT, Lise <groutl@who.int> wrote:

Dear Markus and Prosper,

Thank you for your help!

So if I understand correctly, I have to create different options (with
different UID and codes) but I can reuse the same option name?

Thank you!

Lise.

From: Prosper BT [mailto:ptb3000@gmail.com]
Sent: 22 May 2016 18:11
To: GROUT, Lise; dhis2-users@lists.launchpad.net
Subject: Re: [Dhis2-users] Option, option set and dataelement

Dear Lise

We don't have uniqueness in options across different option sets. So it's
possible to use same options names in different options sets.

Regards

22, 2016, 6:51 PM GROUT, Lise <groutl@who.int> wrote:

Dear all,

Sorry for this basic question but I prefer to ask for confirmation.

Can we use the same option in different option sets (for example
positive/negative in different option Sets) and the same option sets in
different dataelements (for example the option sets results for different
tests)?

Thanks!

Lise.

_______________________________________________
Mailing list: https://launchpad.net/~dhis2-users
Post to : dhis2-users@lists.launchpad.net
Unsubscribe : https://launchpad.net/~dhis2-users
More help : https://help.launchpad.net/ListHelp

_______________________________________________
Mailing list: https://launchpad.net/~dhis2-users
Post to : dhis2-users@lists.launchpad.net
Unsubscribe : https://launchpad.net/~dhis2-users
More help : https://help.launchpad.net/ListHelp

--
Lars Helge Øverland
Lead developer, DHIS 2
University of Oslo
Skype: larshelgeoverland
lars@dhis2.org
http://www.dhis2.org

_______________________________________________
Mailing list: https://launchpad.net/~dhis2-users
Post to : dhis2-users@lists.launchpad.net
Unsubscribe : https://launchpad.net/~dhis2-users
More help : https://help.launchpad.net/ListHelp

Hi Lars,

can you kindly verify your explanation about uniqueness of option codes?

It would be great if they hadn't to be unique system-wide, but I just tested it
on snapshot, and it seems to me that option codes codes must still be unique.
Which is in fact not really interesting: this way you cannot use simple F and M
for female/male as F might stand for False in another category. This is
especially difficult when you are dependent on the codes that are coming from a
source system.

My temporary solution is to prefix each code with a code for the category e.g.
GEN.F/GEN.M for gender female/male and HPY.T/HPY.F for happy or not happy. But
that's not really nice for the outputs and exports. Imagine having a simple
number code (like Month) that is presented as MON.10, Mon.11 etc. in charts and
pivots ...

Thanks and regards,

Uwe

···

Bob Jolliffe <bobjolliffe@gmail.com> hat am 23. Mai 2016 um 15:09 geschrieben:

I think (semantically) the correct way is to create a new "Unknown"
option, though it should have a different code and uid from other
unknowns. The displayed label just happens to be the same but the
underlying concept is different. That is, they actually represent the
likes of "Unknown age", "Unknown test result", "Unknown sex" etc.
Despite sharing the same text label, they are really quite different
options.

There is a similar issue we have grappled with
categories/categoryOptions which is resolved in a different (also
slightly unsatisfactory) way.

My longer term view is that options should be able to be reused in
different optionsets, but not in a completely free manner.

There is some experience of the problem outside of dhis2 and I believe
the established consensus is that
(i) codes/options in a controlled vocabulary are contained in a code
list. Every item in that list should be uniquely identifiable.
(ii) these items should relate to a specific concept (age, disease,
test result etc)
(ii) value sets (such as categories and optionsets in dhis2) should
be selected from one and only one codelist. There can be any number
of valuesets for any one codelist. This allows for reuse of items but
disallows a valueset with mixed concepts (ie you couldn't construct an
optionset containing 'Malaria','Male','under5','Unknown')

If we do get to re-examine our model in this area, this is the
approach I would advocate.

On 23 May 2016 at 12:35, Lars Helge Øverland <lars@dhis2.org> wrote:
> Hi Lise,
>
> at the moment you must create a new "Unknown" option. You can give it the
> same name and code though as the other Unknowns. The uid will be different.
>
> It is debatable whether this is the right way. We are considering whether to
> change the design to allow for re-use of options.
>
> regards,
>
> Lars
>
>
> On Sun, May 22, 2016 at 6:50 PM, GROUT, Lise <groutl@who.int> wrote:
>>
>> Dear Markus and Prosper,
>>
>>
>>
>> Thank you for your help!
>>
>>
>>
>> So if I understand correctly, I have to create different options (with
>> different UID and codes) but I can reuse the same option name?
>>
>>
>>
>> Thank you!
>>
>>
>>
>> Lise.
>>
>>
>>
>> From: Prosper BT [mailto:ptb3000@gmail.com]
>> Sent: 22 May 2016 18:11
>> To: GROUT, Lise; dhis2-users@lists.launchpad.net
>> Subject: Re: [Dhis2-users] Option, option set and dataelement
>>
>>
>>
>> Dear Lise
>>
>>
>>
>> We don't have uniqueness in options across different option sets. So it's
>> possible to use same options names in different options sets.
>>
>>
>>
>> Regards
>>
>> 22, 2016, 6:51 PM GROUT, Lise <groutl@who.int> wrote:
>>
>> Dear all,
>>
>>
>>
>> Sorry for this basic question but I prefer to ask for confirmation.
>>
>>
>>
>> Can we use the same option in different option sets (for example
>> positive/negative in different option Sets) and the same option sets in
>> different dataelements (for example the option sets results for different
>> tests)?
>>
>>
>>
>> Thanks!
>>
>>
>>
>> Lise.
>>
>>
>>
>> _______________________________________________
>> Mailing list: https://launchpad.net/~dhis2-users
>> Post to : dhis2-users@lists.launchpad.net
>> Unsubscribe : https://launchpad.net/~dhis2-users
>> More help : https://help.launchpad.net/ListHelp
>>
>>
>> _______________________________________________
>> Mailing list: https://launchpad.net/~dhis2-users
>> Post to : dhis2-users@lists.launchpad.net
>> Unsubscribe : https://launchpad.net/~dhis2-users
>> More help : https://help.launchpad.net/ListHelp
>>
>
>
>
> --
> Lars Helge Øverland
> Lead developer, DHIS 2
> University of Oslo
> Skype: larshelgeoverland
> lars@dhis2.org
> http://www.dhis2.org
>
>
> _______________________________________________
> Mailing list: https://launchpad.net/~dhis2-users
> Post to : dhis2-users@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~dhis2-users
> More help : https://help.launchpad.net/ListHelp
>

_______________________________________________
Mailing list: https://launchpad.net/~dhis2-users
Post to : dhis2-users@lists.launchpad.net
Unsubscribe : https://launchpad.net/~dhis2-users
More help : https://help.launchpad.net/ListHelp

Hi Uwe

Hi Lars,

can you kindly verify your explanation about uniqueness of option codes?

It would be great if they hadn't to be unique system-wide, but I just tested it
on snapshot, and it seems to me that option codes codes must still be unique.
Which is in fact not really interesting: this way you cannot use simple F and M
for female/male as F might stand for False in another category. This is
especially difficult when you are dependent on the codes that are coming from a
source system.

Agree. That is in fact what address in my proposal. codes (and
labels) should be unique within the scope of a codelist. Many
categories can draw off a codelist. There can be many codelists.
Codelists represent a list of possible codes for a given concept (
age_group, gender, disease, stock status etc).

Codelists should be importable/exportable to other systems. Hence
there are no uniqueness requirements across codelists.

Your temporary solution is probably best you can do at present.

···

On 27 May 2016 at 12:45, Uwe Wahser <uwe@wahser.de> wrote:

My temporary solution is to prefix each code with a code for the category e.g.
GEN.F/GEN.M for gender female/male and HPY.T/HPY.F for happy or not happy. But
that's not really nice for the outputs and exports. Imagine having a simple
number code (like Month) that is presented as MON.10, Mon.11 etc. in charts and
pivots ...

Thanks and regards,

Uwe

Bob Jolliffe <bobjolliffe@gmail.com> hat am 23. Mai 2016 um 15:09 geschrieben:

I think (semantically) the correct way is to create a new "Unknown"
option, though it should have a different code and uid from other
unknowns. The displayed label just happens to be the same but the
underlying concept is different. That is, they actually represent the
likes of "Unknown age", "Unknown test result", "Unknown sex" etc.
Despite sharing the same text label, they are really quite different
options.

There is a similar issue we have grappled with
categories/categoryOptions which is resolved in a different (also
slightly unsatisfactory) way.

My longer term view is that options should be able to be reused in
different optionsets, but not in a completely free manner.

There is some experience of the problem outside of dhis2 and I believe
the established consensus is that
(i) codes/options in a controlled vocabulary are contained in a code
list. Every item in that list should be uniquely identifiable.
(ii) these items should relate to a specific concept (age, disease,
test result etc)
(ii) value sets (such as categories and optionsets in dhis2) should
be selected from one and only one codelist. There can be any number
of valuesets for any one codelist. This allows for reuse of items but
disallows a valueset with mixed concepts (ie you couldn't construct an
optionset containing 'Malaria','Male','under5','Unknown')

If we do get to re-examine our model in this area, this is the
approach I would advocate.

On 23 May 2016 at 12:35, Lars Helge Øverland <lars@dhis2.org> wrote:
> Hi Lise,
>
> at the moment you must create a new "Unknown" option. You can give it the
> same name and code though as the other Unknowns. The uid will be different.
>
> It is debatable whether this is the right way. We are considering whether to
> change the design to allow for re-use of options.
>
> regards,
>
> Lars
>
>
> On Sun, May 22, 2016 at 6:50 PM, GROUT, Lise <groutl@who.int> wrote:
>>
>> Dear Markus and Prosper,
>>
>>
>>
>> Thank you for your help!
>>
>>
>>
>> So if I understand correctly, I have to create different options (with
>> different UID and codes) but I can reuse the same option name?
>>
>>
>>
>> Thank you!
>>
>>
>>
>> Lise.
>>
>>
>>
>> From: Prosper BT [mailto:ptb3000@gmail.com]
>> Sent: 22 May 2016 18:11
>> To: GROUT, Lise; dhis2-users@lists.launchpad.net
>> Subject: Re: [Dhis2-users] Option, option set and dataelement
>>
>>
>>
>> Dear Lise
>>
>>
>>
>> We don't have uniqueness in options across different option sets. So it's
>> possible to use same options names in different options sets.
>>
>>
>>
>> Regards
>>
>> 22, 2016, 6:51 PM GROUT, Lise <groutl@who.int> wrote:
>>
>> Dear all,
>>
>>
>>
>> Sorry for this basic question but I prefer to ask for confirmation.
>>
>>
>>
>> Can we use the same option in different option sets (for example
>> positive/negative in different option Sets) and the same option sets in
>> different dataelements (for example the option sets results for different
>> tests)?
>>
>>
>>
>> Thanks!
>>
>>
>>
>> Lise.
>>
>>
>>
>> _______________________________________________
>> Mailing list: https://launchpad.net/~dhis2-users
>> Post to : dhis2-users@lists.launchpad.net
>> Unsubscribe : https://launchpad.net/~dhis2-users
>> More help : https://help.launchpad.net/ListHelp
>>
>>
>> _______________________________________________
>> Mailing list: https://launchpad.net/~dhis2-users
>> Post to : dhis2-users@lists.launchpad.net
>> Unsubscribe : https://launchpad.net/~dhis2-users
>> More help : https://help.launchpad.net/ListHelp
>>
>
>
>
> --
> Lars Helge Øverland
> Lead developer, DHIS 2
> University of Oslo
> Skype: larshelgeoverland
> lars@dhis2.org
> http://www.dhis2.org
>
>
> _______________________________________________
> Mailing list: https://launchpad.net/~dhis2-users
> Post to : dhis2-users@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~dhis2-users
> More help : https://help.launchpad.net/ListHelp
>

_______________________________________________
Mailing list: https://launchpad.net/~dhis2-users
Post to : dhis2-users@lists.launchpad.net
Unsubscribe : https://launchpad.net/~dhis2-users
More help : https://help.launchpad.net/ListHelp