We have some data elements that have very specific data validation rules:
values can be either 0 or 5, but not any other number (including 1,2,3,4)
As a result, the Min-Max setting doesn’t work and I don’t see how one of the validation rules can be set up with two options for the same dataelement. If I create a rule “datavalue=0” then I can’t also create a rule “datavalue=5” what I need is an or “datavalue=0 or datavalue=5”.
since you seem to have only two possible values, this looks like what we call option sets, which we have had for patient level data for quite some time.
There was some hope to get this into aggregate also for 2.10, but not sure if it made it in?
Knut
···
On Wed, Nov 28, 2012 at 10:41 AM, Wilson,Randy rwilson@msh.org wrote:
We have some data elements that have very specific data validation rules:
values can be either 0 or 5, but not any other number (including 1,2,3,4)
As a result, the Min-Max setting doesn’t work and I don’t see how one of the validation rules can be set up with two options for the same dataelement. If I create a rule “datavalue=0” then I can’t also create a rule “datavalue=5” what I need is an or “datavalue=0 or datavalue=5”.
A but difficult to say form the brief information, but from the case you describe it sounds almost like this would be better captured through the case-based data entry in Tracker (called “single events without registration”), which can capture anonymous data (data elements with domain type “patient”) for cases/events/snapshots of data for a facility.
These data elements can be linked to option sets which are pre-defined textual or numeric values that appear as drop downs in data entry. Later this “case” data can be aggregated to “normal” data elements (with domain type “aggregated”), e.g. “Number of replies/values with 5’s”, “Number of replies/values with 0” etc. for a given facility+period through the patient aggregation feature, and automatically be inserted into the datavalue “store” for data elements with domain type “aggregate” through scheduled patient aggregation jobs, and from there be available in all normal reports, visualizer charts etc.
If you can share the form or some more information about the data Randy, I could comment further.
Ola
···
Ola Hodne Titlestad (Mr)
HISP
Department of Informatics
University of Oslo
Mobile: +47 48069736
Home address: Eftasåsen 68, 0687 Oslo, Norway. Googlemaps link
since you seem to have only two possible values, this looks like what we call option sets, which we have had for patient level data for quite some time.
There was some hope to get this into aggregate also for 2.10, but not sure if it made it in?
Knut
On Wed, Nov 28, 2012 at 10:41 AM, Wilson,Randy rwilson@msh.org wrote:
We have some data elements that have very specific data validation rules:
values can be either 0 or 5, but not any other number (including 1,2,3,4)
As a result, the Min-Max setting doesn’t work and I don’t see how one of the validation rules can be set up with two options for the same dataelement. If I create a rule “datavalue=0” then I can’t also create a rule “datavalue=5” what I need is an or “datavalue=0 or datavalue=5”.