dhis2-users team mailing list archive

[Martin Van Aken <martin@xxxxxxxxxxxxxxxx>]

Hi everyone,
I'm wondering about the best way to manage a use case of ours in DHIS2. We
have a specific element of data (prices for services in an RBF system)
which is normally the same for every org unit for a given period (and in
most case stable for several periods). As an example, we could have
something like:

Consultation Price:
- Jan-December 2016: 2.5$
- Jan-June 2016: 2$
- July-December 2016: 3$

I'm not sure what to use to represent this kind of data in DHIS2:

- Constant is not good as it can evolve
- Standard Data Element means that when we make a change, we need to
"apply" it to every entity for the given period (thus generating hundreds
or thousand of copies of that values)

Added question: if we go for a Data Element, how could we "fill it" at
regular basis (like for the next period each time) - we don't want people
to fill as a data entry for individual entities (it does not make any
sense, and it's not something they "report" anyway).

Any opinion is welcome!

Martin
-- 
*Martin Van Aken - **Freelance Enthusiast Developer*

Mobile : +32 486 899 652

Follow me on Twitter : @martinvanaken <http://twitter.com/martinvanaken>
Call me on Skype : vanakenm
Hang out with me : martin@xxxxxxxxxxxxxxxx
Contact me on LinkedIn : http://www.linkedin.com/in/martinvanaken
Company website : www.joyouscoding.com