dhis2-users team mailing list archive

[Lars Helge Øverland <lars@xxxxxxxxx>]

Hi Martin,

good question. There is no perfect solution at this point. I assume you
need these values for analytics. This means that the best solution is
likely:

1. Find and use the lowest common period type (frequency) for which data
will change (I assume Quarterly)

2. Store the RBF specific data in an external data source, e.g. using data
store
<http://dhis2.github.io/dhis2-docs/master/en/developer/html/webapi_data_store.html>,
where you can store the Quarter, data element (Consultation Price) and
value. You can write a front end app that provides a user-friendly
interface to this data.

3. Generate values for all org units. You can write code in your component
to keep this data in check, e.g. every time someone changes a value in your
RBF data source/app, then automatically generate/populate data values
accordingly in DHIS 2.

This is admittedly a bit painful, but its not too bad, and it gives you the
benefit that all analytics features of DHIS 2 will just work (indicators,
dashboards and so on).


best,

Lars





On Fri, Aug 19, 2016 at 8:46 AM, Martin Van Aken <martin@xxxxxxxxxxxxxxxx>
wrote:

> 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
>
> _______________________________________________
> Mailing list: https://launchpad.net/~dhis2-users
> Post to     : dhis2-users@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~dhis2-users
> More help   : https://help.launchpad.net/ListHelp
>
>


-- 
Lars Helge Øverland
Lead developer, DHIS 2
University of Oslo
Skype: larshelgeoverland
lars@xxxxxxxxx
http://www.dhis2.org <https://www.dhis2.org/>