Thanks Abyot,
I didn't know the dashboard was that flexible. The pin down feature worked
great for me but am forced to move the indicator widget to the right
because it seem like you can only Pin down the right side widget at the
moment.
Is it possible to pin down the left column as you recommended
Hi Lars,
Looks great.Please include, two
NGO Implementations in Kenya,
1. International Center For AIDS Programs. (ICAP-Kenya Office), Nairobi
have adopted DHIS2 branded as IRIS.
2. Association of Public Health Laboratories in collaboration with the MOHs
National Public Health Laboratories are usin
In that case you can put the indicator widget at left top and pin down the
left column. This will make the left top always visible.
-
Thank you,
Abyot.
(sent from mobile)
On Nov 24, 2015 8:43 PM, "Ese Egerega" wrote:
> Thanks Lars,
>
> We are actually using the indicator widget at the momen
Thanks Lars,
We are actually using the indicator widget at the moment. It works
perfectly for small data entry forms because you can see the indicator
value while entering data.
However, it's little complex when the data entry form is large and you are
entering data at the bottom part of the for
Hi Ese,
I am sure you are aware of it but you can also use the "Indicators" widget
and place it above the data entry widget:
[image: Inline image 1]
On Tue, Nov 24, 2015 at 9:02 AM, Ese Egerega wrote:
> Thanks so much for responding Prosper. You are right; tracker does not
> support it at the
Hi Hari,
you are absolutely correct. It is based on the start date of the week (or
period in general).
If you want to visualize exactly how the periods and period types relate
you can generate analytics and have a look in the _periodstructure database
table.
regards,
Lars
On Tue, Nov 24, 201
Hi Jason,
This is VERY helpful. It’s clear you’ve thought a lot about these issues.
Thanks for sharing these ideas, including the link to your validation example.
Our exchange has very quickly helped me to get a sense of how to get started
and where the trouble spots might be. Thanks for all o
Hello,
I want to create an Aggregation query builder details as sum of data element
value I put everything but it comes to Data element for sum/average/min/max
* and try to select I can't find anything and this field is
mandatory and the data aggregator data element and tracker data elemen
Dear Hannan,
Unique ID is quite tricky. In an ideal situation, it is better unique ID is
generated outside DHIS2 and feed to it.
The thing is we don't have a mechanism to tell DHIS2 how the ID should be
generated. Yes, we used to have a something that worked before - but it was
not-scalable.
Cur
Dear Hannan,
This is related to DHIS2 being able to generate unique codes with
customized parameters e.g FacilityCodeOrgunitNumberX.
A good use case of this is the outbreak code (for tracking outbreaks - it
depends on facility/district /disease/ period (weekNo)).
I support the idea. May be t
Dear Abyot
Yes that is a small one. The major problem creator is in the attachment.
Regards
Hannan
HISP Bangladesh
On Tue, Nov 24, 2015 at 2:58 PM, Abyot Gizaw wrote:
> Hi Hannan,
>
> Sorry that I haven't responded. can you please remind us what was reported
> - I can see this bug https://b
Dear Prosper
In tracker we have large amount of data, as we are using tracker from
introduction of the tracker in DHIS2. And the data conversion is a major
problem for us.
Major significant change in tracker is in 'Patient Attribute' and system
generated 'Patient Identifier' and is the major prob
Hi Hannan,
Sorry that I haven't responded. can you please remind us what was reported
- I can see this bug https://bugs.launchpad.net/dhis2/+bug/1492967
Do you have more?
---
Thank you,
Abyot.
On Tue, Nov 24, 2015 at 9:10 AM, Hannan Khan wrote:
> Dear Prosper
>
> Yes you are right; new versi
Dear Hannan,
I can understand the pain of upgrading and change management. Obviously
between 2.13 and 2.20 there have been major changes in the tracker.
Since its a small tracker program with few data elements, would you rather
take the option of rebuilding everything from scratch on 2.20, then p
Hi Eric,
Indicators in DHIS2 are constructed by metadata, so there is no standard
way. If you are going to aggregate these yourself, then yes, you would need
to pull out all of the component data elements, reconstruct the indicator
in R, and then perform the aggregation. You can see an example of
Dear Prosper
Yes you are right; new versions have some very good feature (Thanks to Lars
and the Team) which meet majority of the requirements and some are done
through discussion and alternative reporting.
But converting from 13 to 21 is a big headache; we already done some
conversion from 13 to
Thanks so much for responding Prosper. You are right; tracker does not
support it at the moment. It's a feature the dev team should consider
adding though.
-Ese
On Nov 22, 2015 5:39 AM, "Prosper BT" wrote:
> Hi Ese,
>
> This would only be achieved through a custom entry screen, but the custom
>
17 matches
Mail list logo
