← Back to team overview

dhis2-devs team mailing list archive

Re: "Atomic" data validation rules

 

Hi Jim
Yes, I think I agree with you, but a still a bit fuzzy how it could happen
with the current UI.  I think the user would have an option like "Apply
this rule to common category combo options", and they would then select a
left side, and the right side would only show data elements with the same
category combo. The user would not select individual data elements.  An
operator would need to be selected as well, obviously.

For the use case we are dealing with, it is always comparing two data
elements, one which is typically a subset of another, which is quite common
in HIV M&E. Number counselled <= Number tested <= Number positive <= Number
receiving results.

Regards,
Jason



On Fri, May 23, 2014 at 1:44 PM, Jim Grace <jimgrace@xxxxxxxxx> wrote:

> I like it. A couple of ideas:
>
> - I suggest that this be a new property of validation rules, rather than a
> third type in addition to "Validation" and "Surveillance". It could be
> potentially useful for either of these two rule types.
>
> - When selecting this option, the user could choose from a list of
> category combos that then appears on the add validation rule screen. (We
> could even present a list of category combos that are actually *used* by
> data elements.) This list could be used to filter the data elements
> available when creating the left and right sides, to make sure they all
> have the same combos.
>
> Cheers,
> Jim
>
>
>
> On Fri, May 23, 2014 at 3:55 AM, Jason Pickering <
> jason.p.pickering@xxxxxxxxx> wrote:
>
>> Hi Lars,
>> Finally got around to creating the blueprint here
>>
>> https://blueprints.launchpad.net/dhis2/+spec/atomic-validation-rules
>>
>> Regards,
>> Jason
>>
>>
>>
>> On Wed, Jan 15, 2014 at 6:36 PM, Lars Helge Øverland <larshelge@xxxxxxxxx
>> > wrote:
>>
>>> Hi Jason,
>>>
>>> yes I think this makes sense. One could make a special kind of
>>> validation rule, with a constraint that all data elements on the left and
>>> right side expressions share the same category combination, and then tell
>>> the system to validate each and every category option combination. Feel
>>> free to write a blueprint.
>>>
>>> regards,
>>>
>>> Lars
>>>
>>>
>>>
>>> On Tue, Jan 14, 2014 at 3:52 PM, Jason Pickering <
>>> jason.p.pickering@xxxxxxxxx> wrote:
>>>
>>>> Hi Devs,
>>>> I came up against an issue today when looking at implementing a legacy
>>>> database in DHIS2. In the old system, there are about 75 rules. The rules
>>>> in the past have been applied at the atomic level, meaning that each and
>>>> every data element category combination value is compared with a counter
>>>> part. As an example.
>>>>
>>>> Number of persons currently receiving ART (including pregnant women)
>>>> is greater than or equal to
>>>> Number of individuals NEWLY initiating ART (including pregnant women)
>>>>
>>>> Each of these data elements are disaggregated by Gender and three age
>>>> groups, and the validation rules need to be applied to each respective
>>>> category combination options (not the totals).
>>>>
>>>> Although I do not know exactly how many rules we would need to to this,
>>>> it is surely at least several hundred. I have not really come up against
>>>> this before, and need to see if anyone has expericience with how the system
>>>> behaves with "large" numbers of rules.
>>>>
>>>> I think it would be good to think about how to we could make the rules
>>>> be applied within category combo options , without having to explicitly
>>>> define each and every rule. Thoughts?
>>>>
>>>> Regards,
>>>> Jason
>>>>
>>>>
>>>> _______________________________________________
>>>> Mailing list: https://launchpad.net/~dhis2-devs
>>>> Post to     : dhis2-devs@xxxxxxxxxxxxxxxxxxx
>>>> Unsubscribe : https://launchpad.net/~dhis2-devs
>>>> More help   : https://help.launchpad.net/ListHelp
>>>>
>>>>
>>>
>>
>> _______________________________________________
>> Mailing list: https://launchpad.net/~dhis2-devs
>> Post to     : dhis2-devs@xxxxxxxxxxxxxxxxxxx
>> Unsubscribe : https://launchpad.net/~dhis2-devs
>> More help   : https://help.launchpad.net/ListHelp
>>
>>
>

Follow ups

References