dhis2-devs-core team mailing list archive

[Rodolfo Melia <rmelia@xxxxxxxxxxxx>]

Thanks Lars for the update - we do like the approach that DHIS is taking,
where the core developers are using the API to develop the coreUI - no
better way to ensure that the API is functional. At PSI we are in the
process of writing our own app for Multiple Events w/ Reg. James Chang is
writing against the code on 2.14, using the API that Morten has been
developing. We will be doing testing of our App next week, and plan to take
it live on late March - a screenshot of the working prototype below. We
think that our app is generic enough for others to use - we refer to it as
Tabular Data Entry, as it presents in a single screen multiple patients and
the different program stages with the Data Elements in columns, on a given
timeframe. This is important for us, as we source most of our info from
Medical Log for a given month/ week.

[image: Inline image 1]

*Rodolfo Meliá*
*Principal  |  *rmelia@xxxxxxxxxxxx
Skype: rod.melia  |  +44 777 576 4090  |  +1 708 872 7636
www.knowming.com


On Tue, Feb 11, 2014 at 7:38 AM, Lars Helge Øverland <larshelge@xxxxxxxxx>wrote:

> Hi there,
>
> a quick update on the plans for tracker. We plan to split tracker out in
> multiple apps and rewrite most of it to work against the web api. There
> will be 4 apps:
>
> 1. Tracker Capture. Today's find/add person and person dashboard. We will
> rewrite as a separate app. Tran and Abyot will work on it.
>
> 2. Tracker Reports. Today's visit schedule, program summary, program
> statistics, completeness. We will leave this as Struts code for now.
>
> 3. Event Capture. Today's single event without registration. We will
> rewrite as a separate app against the web api. Abyot is working on it.
>
> 4. Event Reports. Today's tabular report. We will rewrite as a separate
> app, rename to event reports and provide pivot style functionality for the
> aggregate part. Jan is working on it.
>
>
> This implies a change in terminology:
>
> Multiple events with registration => Tracker
> Single events without registration => Event
> Single event with registration will be out as a separate option and now
> simply be part of tracker, as a multiple events with registration program
> with only one stage. This gets simpler and reduces it to two basic concepts.
>
>
> regards,
>
> Lars
>
>