A quick question on whether the standard out-of-the-box capability of DHIS2 allows one to filter a drop-down based on a previous selection (I would assume something like this would normally be implemented via a rule - ideally the skip-logic rule area).
For larger lists (e.g. diagnosis codes) I’m sure this must have been considered previously, but can’t find any mentions in the mail list, and can’t see how this can be implemented (using standard capability currently offered).
We are looking at the scenario of implementing a simplistic version of ICPC for field encounters … and there are 2 quick potential ‘pre-selectors’ that reduce final selection from hundreds to less than 30 items, greatly speeding up the data capture process for the end-user.
(Note we are looking at using the latest v2.21 Android Tracker App as the basis for serving this encounter form)
This is not yet supported, you may have to write a script with custom forms. We had a similar challenge during the eIDSR implementation in Rwanda for selecting Laboratories by drilling down from region to district.
A quick question on whether the standard out-of-the-box capability of DHIS2 allows one to filter a drop-down based on a previous selection (I would assume something like this would normally be implemented via a rule - ideally the skip-logic rule area).
For larger lists (e.g. diagnosis codes) I’m sure this must have been considered previously, but can’t find any mentions in the mail list, and can’t see how this can be implemented (using standard capability currently offered).
We are looking at the scenario of implementing a simplistic version of ICPC for field encounters … and there are 2 quick potential ‘pre-selectors’ that reduce final selection from hundreds to less than 30 items, greatly speeding up the data capture process for the end-user.
(Note we are looking at using the latest v2.21 Android Tracker App as the basis for serving this encounter form)
This is not yet supported, you may have to write a script with custom forms. We had a similar challenge during the eIDSR implementation in Rwanda for selecting Laboratories by drilling down from region to district.
A quick question on whether the standard out-of-the-box capability of DHIS2 allows one to filter a drop-down based on a previous selection (I would assume something like this would normally be implemented via a rule - ideally the skip-logic rule area).
For larger lists (e.g. diagnosis codes) I’m sure this must have been considered previously, but can’t find any mentions in the mail list, and can’t see how this can be implemented (using standard capability currently offered).
We are looking at the scenario of implementing a simplistic version of ICPC for field encounters … and there are 2 quick potential ‘pre-selectors’ that reduce final selection from hundreds to less than 30 items, greatly speeding up the data capture process for the end-user.
(Note we are looking at using the latest v2.21 Android Tracker App as the basis for serving this encounter form)
It has come up a lot of times, but think I never got around to writing it up…
···
On Fri, Dec 4, 2015 at 12:21 PM, Prosper BT ptb3000@gmail.com wrote:
Hi David,
This is not yet supported, you may have to write a script with custom forms. We had a similar challenge during the eIDSR implementation in Rwanda for selecting Laboratories by drilling down from region to district.
A quick question on whether the standard out-of-the-box capability of DHIS2 allows one to filter a drop-down based on a previous selection (I would assume something like this would normally be implemented via a rule - ideally the skip-logic rule area).
For larger lists (e.g. diagnosis codes) I’m sure this must have been considered previously, but can’t find any mentions in the mail list, and can’t see how this can be implemented (using standard capability currently offered).
We are looking at the scenario of implementing a simplistic version of ICPC for field encounters … and there are 2 quick potential ‘pre-selectors’ that reduce final selection from hundreds to less than 30 items, greatly speeding up the data capture process for the end-user.
(Note we are looking at using the latest v2.21 Android Tracker App as the basis for serving this encounter form)
This is not yet supported, you may have to write a script with custom forms. We had a similar challenge during the eIDSR implementation in Rwanda for selecting Laboratories by drilling down from region to district.
A quick question on whether the standard out-of-the-box capability of DHIS2 allows one to filter a drop-down based on a previous selection (I would assume something like this would normally be implemented via a rule - ideally the skip-logic rule area).
For larger lists (e.g. diagnosis codes) I’m sure this must have been considered previously, but can’t find any mentions in the mail list, and can’t see how this can be implemented (using standard capability currently offered).
We are looking at the scenario of implementing a simplistic version of ICPC for field encounters … and there are 2 quick potential ‘pre-selectors’ that reduce final selection from hundreds to less than 30 items, greatly speeding up the data capture process for the end-user.
(Note we are looking at using the latest v2.21 Android Tracker App as the basis for serving this encounter form)
Dear David,
program rules for filtering/hiding option set values is not yet supported. That said we have seen a few use cases for this, now including yours. We plan to include support in the program rules for hiding options in an option set, pushing for 2.22 here.
In 2.21 you would have to make separate dataelements with separate option sets to acheive something similar. If you make separate data elements you can hide the ones that is not relevant based on pre-selectors, provided that each data element has an option set that includes only the option values that is relevant for the values in the pre-selectors.
Best regards,
Markus
···
On Mon, Dec 7, 2015 at 2:37 PM, Lars Helge Øverland larshelge@gmail.com wrote:
Halla kunne du svart på denne? Noen planer om linking av option sets for program rules…?
A quick question on whether the standard out-of-the-box capability of DHIS2 allows one to filter a drop-down based on a previous selection (I would assume something like this would normally be implemented via a rule - ideally the skip-logic rule area).
For larger lists (e.g. diagnosis codes) I’m sure this must have been considered previously, but can’t find any mentions in the mail list, and can’t see how this can be implemented (using standard capability currently offered).
We are looking at the scenario of implementing a simplistic version of ICPC for field encounters … and there are 2 quick potential ‘pre-selectors’ that reduce final selection from hundreds to less than 30 items, greatly speeding up the data capture process for the end-user.
(Note we are looking at using the latest v2.21 Android Tracker App as the basis for serving this encounter form)
That will indeed be useful if you can get it into 2.22
The challenge with your alternative (which I had considered) is that (in this ‘use case’ of attempting to model a lite version of ICPC - which includes one or more symptoms, diagnosis codes and intervention codes) is that the final ‘episode’ of care is spread across potentially hundreds of data elements (most of them empty), just to ‘fake’ this filter ability on the front end.
A quick related comment … it would be great if one of the Action(s) in a Program Rule were to populate a ‘label’ element that could be used in a later section (as a reminder of what was previously filled in) - particularly for the Android Tracker App, where each ‘section’ is on a separate ‘screen’.
Dear David,
program rules for filtering/hiding option set values is not yet supported. That said we have seen a few use cases for this, now including yours. We plan to include support in the program rules for hiding options in an option set, pushing for 2.22 here.
In 2.21 you would have to make separate dataelements with separate option sets to acheive something similar. If you make separate data elements you can hide the ones that is not relevant based on pre-selectors, provided that each data element has an option set that includes only the option values that is relevant for the values in the pre-selectors.
Best regards,
Markus
On Mon, Dec 7, 2015 at 2:37 PM, Lars Helge Øverland larshelge@gmail.com wrote:
Halla kunne du svart på denne? Noen planer om linking av option sets for program rules…?
A quick question on whether the standard out-of-the-box capability of DHIS2 allows one to filter a drop-down based on a previous selection (I would assume something like this would normally be implemented via a rule - ideally the skip-logic rule area).
For larger lists (e.g. diagnosis codes) I’m sure this must have been considered previously, but can’t find any mentions in the mail list, and can’t see how this can be implemented (using standard capability currently offered).
We are looking at the scenario of implementing a simplistic version of ICPC for field encounters … and there are 2 quick potential ‘pre-selectors’ that reduce final selection from hundreds to less than 30 items, greatly speeding up the data capture process for the end-user.
(Note we are looking at using the latest v2.21 Android Tracker App as the basis for serving this encounter form)