Dear all,
I am trying to create event without registration and i am trying to capture a data element where i need to select more than one Value. For eg: Service offered by Facility which might be more than one. How do we address these types of cases in DHIS2?
This is not supported with a single data element. You will need to create multiple data elements of type Yes Only or Yes/No for this for each of the services which might be offered.
Dear all,
I am trying to create event without registration and i am trying to capture a data element where i need to select more than one Value. For eg: Service offered by Facility which might be more than one. How do we address these types of cases in DHIS2?
Hi Jason,Thanks for your quick response. As I have already mention i have got nearly 20 services to select from and creating data element for each and every single services as yes only or yes/no will over populate the data element list. I have got another scenario where i have to register my provider. In that program i have to chose either the provider is certified, trained or interested. And the we have nearly 15 services in the list. So that means we need to create 45 data elements to capture the details. I am afraid to implement this idea. Can you or anyone suggest me any possible solution?
Regards,Utsav
Hi Asiz,
The problem is option sets allow for a single choice, not multiple ones. I realize it is not particularly convenient, but I cannot think of another way to do it in this case. If there are other ideas however, it would be good to know!
Hi Jason,
Thanks for your quick response. As I have already mention i have got nearly 20 services to select from and creating data element for each and every single services as yes only or yes/no will over populate the data element list. I have got another scenario where i have to register my provider. In that program i have to chose either the provider is certified, trained or interested. And the we have nearly 15 services in the list. So that means we need to create 45 data elements to capture the details. I am afraid to implement this idea. Can you or anyone suggest me any possible solution?
This is not supported with a single data element. You will need to create multiple data elements of type Yes Only or Yes/No for this for each of the services which might be offered.
Dear all,
I am trying to create event without registration and i am trying to capture a data element where i need to select more than one Value. For eg: Service offered by Facility which might be more than one. How do we address these types of cases in DHIS2?
Hi Asiz,
The problem is option sets allow for a single choice, not multiple ones. I realize it is not particularly convenient, but I cannot think of another way to do it in this case. If there are other ideas however, it would be good to know!
Hi Jason,
Thanks for your quick response. As I have already mention i have got nearly 20 services to select from and creating data element for each and every single services as yes only or yes/no will over populate the data element list. I have got another scenario where i have to register my provider. In that program i have to chose either the provider is certified, trained or interested. And the we have nearly 15 services in the list. So that means we need to create 45 data elements to capture the details. I am afraid to implement this idea. Can you or anyone suggest me any possible solution?
This is not supported with a single data element. You will need to create multiple data elements of type Yes Only or Yes/No for this for each of the services which might be offered.
Dear all,
I am trying to create event without registration and i am trying to capture a data element where i need to select more than one Value. For eg: Service offered by Facility which might be more than one. How do we address these types of cases in DHIS2?
I am facing the same issue as you Asiz, and was planning to do a custom solution for the Palestine project: Use 10-ish “Yes only” dataelements, and group them together in a multiple select dropdown/popover/adaptation of select2 - all while using the underlying yes only dataelements.
Perhaps the solution can be improved upon so we could implement a generic version in the /\w* capture/g clients.
Hi Asiz,
The problem is option sets allow for a single choice, not multiple ones. I realize it is not particularly convenient, but I cannot think of another way to do it in this case. If there are other ideas however, it would be good to know!
Hi Jason,
Thanks for your quick response. As I have already mention i have got nearly 20 services to select from and creating data element for each and every single services as yes only or yes/no will over populate the data element list. I have got another scenario where i have to register my provider. In that program i have to chose either the provider is certified, trained or interested. And the we have nearly 15 services in the list. So that means we need to create 45 data elements to capture the details. I am afraid to implement this idea. Can you or anyone suggest me any possible solution?
This is not supported with a single data element. You will need to create multiple data elements of type Yes Only or Yes/No for this for each of the services which might be offered.
Dear all,
I am trying to create event without registration and i am trying to capture a data element where i need to select more than one Value. For eg: **Service offered by Facility **which might be more than one. How do we address these types of cases in DHIS2?
Yes custom solutions are possible - I also remember doing a similar thing for the first version of Palestine tracker. What I did back then was appended all the values under a single dataeleemnt.
In general, the issue is not from the input side, rather from the output side. If we are interested in counting or aggregating each distinct value then we have to create as many dataelements as values.
Hi guys,
I am facing the same issue as you Asiz, and was planning to do a custom solution for the Palestine project: Use 10-ish “Yes only” dataelements, and group them together in a multiple select dropdown/popover/adaptation of select2 - all while using the underlying yes only dataelements.
Perhaps the solution can be improved upon so we could implement a generic version in the /\w* capture/g clients.
Hi Asiz,
The problem is option sets allow for a single choice, not multiple ones. I realize it is not particularly convenient, but I cannot think of another way to do it in this case. If there are other ideas however, it would be good to know!
Hi Jason,
Thanks for your quick response. As I have already mention i have got nearly 20 services to select from and creating data element for each and every single services as yes only or yes/no will over populate the data element list. I have got another scenario where i have to register my provider. In that program i have to chose either the provider is certified, trained or interested. And the we have nearly 15 services in the list. So that means we need to create 45 data elements to capture the details. I am afraid to implement this idea. Can you or anyone suggest me any possible solution?
This is not supported with a single data element. You will need to create multiple data elements of type Yes Only or Yes/No for this for each of the services which might be offered.
Dear all,
I am trying to create event without registration and i am trying to capture a data element where i need to select more than one Value. For eg: **Service offered by Facility **which might be more than one. How do we address these types of cases in DHIS2?
Yes, for the previous pregnancies table? However, if the solution shall work end to end we need to store the values across several dataelements. Given this, the problem and solution can be in the client side - the problem is a unruly long list of “yes only” fields, and the solution could be a smarter/more compact input mecanism for a group of such dataelements.
Will post here once I have something in the Palestine tree.
Hi guys,
I am facing the same issue as you Asiz, and was planning to do a custom solution for the Palestine project: Use 10-ish “Yes only” dataelements, and group them together in a multiple select dropdown/popover/adaptation of select2 - all while using the underlying yes only dataelements.
Perhaps the solution can be improved upon so we could implement a generic version in the /\w* capture/g clients.
Hi Asiz,
The problem is option sets allow for a single choice, not multiple ones. I realize it is not particularly convenient, but I cannot think of another way to do it in this case. If there are other ideas however, it would be good to know!
Hi Jason,
Thanks for your quick response. As I have already mention i have got nearly 20 services to select from and creating data element for each and every single services as yes only or yes/no will over populate the data element list. I have got another scenario where i have to register my provider. In that program i have to chose either the provider is certified, trained or interested. And the we have nearly 15 services in the list. So that means we need to create 45 data elements to capture the details. I am afraid to implement this idea. Can you or anyone suggest me any possible solution?
This is not supported with a single data element. You will need to create multiple data elements of type Yes Only or Yes/No for this for each of the services which might be offered.
Dear all,
I am trying to create event without registration and i am trying to capture a data element where i need to select more than one Value. For eg: **Service offered by Facility **which might be more than one. How do we address these types of cases in DHIS2?
Hi all,Your replies are making things quite interesting. Reading all the replies i think we can summarize the solution we have as below1. As JASON suggested, we can have Yes only/Yes/No (preferable Yes only) for check-box. But the drawback over here is we need to create as many DE as the options in our checkbox. 2. As Markus suggested, We can have as many DE as our options alike to JASON but we can trick over in UI. We can make it look like group of checkbox merge together to show them as multi select drop down. Am i right?3. As Abyot suggested, he has got something different. He has created one DE; presented option as checkbox and stored value in that DE as json or something else. The problem with this approach is, its harder for us to analyze the details if we ever need to do so.
Checkboxes has always been headache and I am still confused which one should i prefer while addressing this problem in my program. Please suggest me.