Regarding Code for Options in Option Sets

Implementation - Implémentation
1

Hello,

What should be the best practice to for configuring the option sets. Can we keep the same set of code in options for two different option sets.

For an example:
Option Set 1: Provinces
Options:
Name: ABC Code: 1
Name: XYZ Code: 2

Option Set 2: Districts
Options:
Name: AAA Code: 1
Name: XXX Code: 2

Keeping the same code in two different option sets will cause any issue in future? Any data migration issues in import or export?

Any input will be highly appreciated.

Thanks,
Hiral

1 Like
2

Normally it’s not problematic. We have plenty of numeric codes (similar/common) but different questions/dataelements with different optionsets. The options will have different ids.

3

HI @ramavat

Yes, you can use the same option codes across different option sets in DHIS2, and it will not cause issues as long as the option sets themselves are distinct and properly referenced in data elements or attributes.

DHIS2 manages option sets and options as separate entities, meaning the same option code (e.g., 1, 2) can be reused in another option set without conflict. Each option is uniquely identified by the combination of its UID and the option set it belongs to, not just by the code.

2 Likes