dhis2-devs team mailing list archive

[Ola Hodne Titlestad <olatitle@xxxxxxxxx>]

Hi,

Just a few quick thoughts on this.

We have talked about putting a restriction on data sets to limit to only one
categorycombo among its data elements.
Typical paper forms have multiple categorycombos (e.g. many smaller tables
with different column headings) and to mimic this in an electronic form
these is a need for multiple catcombos, or given the proposed constraint
mulitple data sets.
Forms should be able to be designed without the 1-1 link to data sets as
long as it is somehow validated that data elements are only captured using
one period type (which is set in the data set).

So, before doing to much here I would thing that it makes sense to look at
the bigger picture first.

Ola Hodne Titlestad |Technical Officer|
Health Metrics Network (HMN) | World Health Organization
Avenue Appia 20 |1211 Geneva 27, Switzerland | Email: titlestado@xxxxxxx|Tel:
+41 788216897
Website: www.healthmetricsnetwork.org

Better Information. Better Decisions. Better Health.


2009/11/29 Lars Helge Øverland <larshelge@xxxxxxxxx>

> ** Changed in: dhis2
>     Assignee: (unassigned) => Abyot Asalefew (abyot)
>
> --
> Custom data entry screens are not restricted to data elements in the data
> set
> https://bugs.launchpad.net/bugs/439473
> You received this bug notification because you are a member of DHIS 2
> coordinators, which is the registrant for DHIS.
>
> Status in DHIS 2 - District Health Information Software: Confirmed
>
> Bug description:
> Custom data entry screens is not restricted to data elements in the data
> set it is based on. This breaks with the whole data set concept.
>
>
>

-- 
Custom data entry screens are not restricted to data elements in the data set
https://bugs.launchpad.net/bugs/439473
You received this bug notification because you are a member of DHIS 2
developers, which is subscribed to DHIS.

Status in DHIS 2 - District Health Information Software: Confirmed

Bug description:
Custom data entry screens is not restricted to data elements in the data set it is based on. This breaks with the whole data set concept.