[Dhis2-users] Program rule to hide Tracked entity attribute field show a warning in console

2017-10-11 Thread Rady
Dear DHIS2 team,

I have tried using Program rule to hide Tracked entity attribute field, it
works properly. But it shows a warning message "*ProgramRuleAction
C1pSVKWZ40F is of type HIDEFIELD, bot does not have a dataelement defined*"
in console (see attached files). However, if I tried the same program rule
to hide data element field, it does not show such warning message in
console. Does anyone have experience with this?

Regards,
Rady
___
Mailing list: https://launchpad.net/~dhis2-users
Post to : dhis2-users@lists.launchpad.net
Unsubscribe : https://launchpad.net/~dhis2-users
More help   : https://help.launchpad.net/ListHelp


Re: [Dhis2-users] dhis version 2.28 is out

2017-10-11 Thread Kamugunga Adolphe
Thanks Lars and Team

Adolphe

*Adolphe Kamugunga*
*MIS Technical Advisor*
Mobile: +250 788 740 578
Email:kaa...@gmail.com
Skype: ka.adolphe
 RWANDA


On 11 October 2017 at 18:56, Lars Helge Øverland  wrote:

> Hi all,
>
> DHIS version 2.28 is out. This version includes a range of improvements
> and stability enhancements.
>
> Log in with admin/district on the demo 
> system.
>
>
> ANALYTICS FEATURES
>
> ---
>
> Measure criteria support in pivot tables: Pivot table app now supports
> measure criteria, meaning criteria to apply to the data being returned,
> such as a min and max value. Can be enabled in the Options dialog.
>
> Demo  |
> Screenshot
> 
>
>
> Multiple regression types in charts: Data visualizer and event visualizer
> apps now supports a new option for linear, polynomial and loess regression
> types (trend lines). Can be enabled in the Options dialog.
>
> Demo 1 
> | 2  | 
> Screenshot
> 1
> 
> | 2
> 
>
>
> Remove gaps in bar/column charts: Data visualizer and event visualizer
> apps now support an option for displaying bar/column charts without gaps
> between the bars/columns. Can be enabled in the Options dialog.
>
> Demo  |
> Screenshot
> 
>
>
> Daily relative periods in event analytics: Various daily relative periods
> are now supported in event reports and event visualizer.
>
> Demo 
> | Screenshot
> 
>
>
> Share favorites with users: Analytics favorites can now be shared with
> individual users in addition to user groups. This is useful for more
> flexible sharing and removes the need for always creating a group. Click
> *Share* from the *Favorites* menu.
>
> Demo
> 
> | Screenshot
> 
>
>
> Favorite filter for “Created by me”: You can now easily filter your
> favorites with the new “Created by me”/”Created by others” filter,
> available in all the analytics apps.
>
> Demo  |
> Screenshot
> 
>
>
> Sort favorites by created and last updated: Analytics favorites can now
> be sorted by the date they were created and the date they were last updated.
>
> Demo
> 
> | Screenshot
> 
>
>
> Combine totals and details in pivots: Total values and details (operands)
> can now be combined in pivot tables and charts.
>
> Demo  |
> Screenshot
> 
>
>
> Indicator totals in pivots: The pivot table app now calculates total and
> subtotal values in a better way, dividing the sum of numerator values with
> the sum of denominator values multiplied by the average of indicator
> factors.
>
> Demo  |
> Screenshot
> 
>
>
>
> TRACKER FEATURES
>
> ---
>
> Compare to previous event during data entry: You can now choose to
> compare the current data entry for an event with previously completed
> events. This option is available when doing data entry for a new event in
> tracker capture.
>
> Demo 
> | Docs
> 
>
>
> Tracker and event capture with time, datetime and URL value types: Tracker
> and event capture apps now support the “Time”, “Datetime” and “URL” data
> element value types.
>
> Demo 
>
>
>
> GENERAL FEATURES
>
> 

Re: [Dhis2-users] [Dhis2-devs] dhis version 2.28 is out

2017-10-11 Thread Ocaya Stephen
Thanks Lars and Team.

Features looks  very much worked on.

Regards

On Wed, Oct 11, 2017 at 8:09 PM, Prosper BT  wrote:

> Congs Lars and team
>
> Looking forward implementations.
>
> Regards
>
>
> On Wed, Oct 11, 2017, 7:56 PM Lars Helge Øverland  wrote:
>
>> Hi all,
>>
>> DHIS version 2.28 is out. This version includes a range of improvements
>> and stability enhancements.
>>
>> Log in with admin/district on the demo 
>> system.
>>
>>
>> ANALYTICS FEATURES
>>
>> ---
>>
>> Measure criteria support in pivot tables: Pivot table app now supports
>> measure criteria, meaning criteria to apply to the data being returned,
>> such as a min and max value. Can be enabled in the Options dialog.
>>
>> Demo  |
>> Screenshot
>> 
>>
>>
>> Multiple regression types in charts: Data visualizer and event
>> visualizer apps now supports a new option for linear, polynomial and loess
>> regression types (trend lines). Can be enabled in the Options dialog.
>>
>> Demo 1 
>> | 2  | 
>> Screenshot
>> 1
>> 
>> | 2
>> 
>>
>>
>> Remove gaps in bar/column charts: Data visualizer and event visualizer
>> apps now support an option for displaying bar/column charts without gaps
>> between the bars/columns. Can be enabled in the Options dialog.
>>
>> Demo  |
>> Screenshot
>> 
>>
>>
>> Daily relative periods in event analytics: Various daily relative
>> periods are now supported in event reports and event visualizer.
>>
>> Demo 
>> | Screenshot
>> 
>>
>>
>> Share favorites with users: Analytics favorites can now be shared with
>> individual users in addition to user groups. This is useful for more
>> flexible sharing and removes the need for always creating a group. Click
>> *Share* from the *Favorites* menu.
>>
>> Demo
>> 
>> | Screenshot
>> 
>>
>>
>> Favorite filter for “Created by me”: You can now easily filter your
>> favorites with the new “Created by me”/”Created by others” filter,
>> available in all the analytics apps.
>>
>> Demo  |
>> Screenshot
>> 
>>
>>
>> Sort favorites by created and last updated: Analytics favorites can now
>> be sorted by the date they were created and the date they were last updated.
>>
>> Demo
>> 
>> | Screenshot
>> 
>>
>>
>> Combine totals and details in pivots: Total values and details
>> (operands) can now be combined in pivot tables and charts.
>>
>> Demo  |
>> Screenshot
>> 
>>
>>
>> Indicator totals in pivots: The pivot table app now calculates total and
>> subtotal values in a better way, dividing the sum of numerator values with
>> the sum of denominator values multiplied by the average of indicator
>> factors.
>>
>> Demo  |
>> Screenshot
>> 
>>
>>
>>
>> TRACKER FEATURES
>>
>> ---
>>
>> Compare to previous event during data entry: You can now choose to
>> compare the current data entry for an event with previously completed
>> events. This option is available when doing data entry for a new event in
>> tracker capture.
>>
>> Demo 
>> | Docs
>> 
>>
>>
>> Tracker and event capture with time, datetime and URL value types: Tracker
>> and event 

Re: [Dhis2-users] dhis version 2.28 is out

2017-10-11 Thread Nayeem Al Mifthah
Congratulations...

A number of new features :)

*Nayeem Al Mifthah*
*Consultant for HSS, Health MIS, M*
Email: n.mift...@gmail.com
Cell:+8801914030574
Skype: nayeem.a.m

On Wed, Oct 11, 2017 at 10:56 PM, Lars Helge Øverland 
wrote:

> Hi all,
>
> DHIS version 2.28 is out. This version includes a range of improvements
> and stability enhancements.
>
> Log in with admin/district on the demo 
> system.
>
>
> ANALYTICS FEATURES
>
> ---
>
> Measure criteria support in pivot tables: Pivot table app now supports
> measure criteria, meaning criteria to apply to the data being returned,
> such as a min and max value. Can be enabled in the Options dialog.
>
> Demo  |
> Screenshot
> 
>
>
> Multiple regression types in charts: Data visualizer and event visualizer
> apps now supports a new option for linear, polynomial and loess regression
> types (trend lines). Can be enabled in the Options dialog.
>
> Demo 1 
> | 2  | 
> Screenshot
> 1
> 
> | 2
> 
>
>
> Remove gaps in bar/column charts: Data visualizer and event visualizer
> apps now support an option for displaying bar/column charts without gaps
> between the bars/columns. Can be enabled in the Options dialog.
>
> Demo  |
> Screenshot
> 
>
>
> Daily relative periods in event analytics: Various daily relative periods
> are now supported in event reports and event visualizer.
>
> Demo 
> | Screenshot
> 
>
>
> Share favorites with users: Analytics favorites can now be shared with
> individual users in addition to user groups. This is useful for more
> flexible sharing and removes the need for always creating a group. Click
> *Share* from the *Favorites* menu.
>
> Demo
> 
> | Screenshot
> 
>
>
> Favorite filter for “Created by me”: You can now easily filter your
> favorites with the new “Created by me”/”Created by others” filter,
> available in all the analytics apps.
>
> Demo  |
> Screenshot
> 
>
>
> Sort favorites by created and last updated: Analytics favorites can now
> be sorted by the date they were created and the date they were last updated.
>
> Demo
> 
> | Screenshot
> 
>
>
> Combine totals and details in pivots: Total values and details (operands)
> can now be combined in pivot tables and charts.
>
> Demo  |
> Screenshot
> 
>
>
> Indicator totals in pivots: The pivot table app now calculates total and
> subtotal values in a better way, dividing the sum of numerator values with
> the sum of denominator values multiplied by the average of indicator
> factors.
>
> Demo  |
> Screenshot
> 
>
>
>
> TRACKER FEATURES
>
> ---
>
> Compare to previous event during data entry: You can now choose to
> compare the current data entry for an event with previously completed
> events. This option is available when doing data entry for a new event in
> tracker capture.
>
> Demo 
> | Docs
> 
>
>
> Tracker and event capture with time, datetime and URL value types: Tracker
> and event capture apps now support the “Time”, “Datetime” and “URL” data
> element value types.
>
> Demo 
>
>

Re: [Dhis2-users] dhis version 2.28 is out

2017-10-11 Thread Prosper BT
Congs Lars and team

Looking forward implementations.

Regards

On Wed, Oct 11, 2017, 7:56 PM Lars Helge Øverland  wrote:

> Hi all,
>
> DHIS version 2.28 is out. This version includes a range of improvements
> and stability enhancements.
>
> Log in with admin/district on the demo 
> system.
>
>
> ANALYTICS FEATURES
>
> ---
>
> Measure criteria support in pivot tables: Pivot table app now supports
> measure criteria, meaning criteria to apply to the data being returned,
> such as a min and max value. Can be enabled in the Options dialog.
>
> Demo  |
> Screenshot
> 
>
>
> Multiple regression types in charts: Data visualizer and event visualizer
> apps now supports a new option for linear, polynomial and loess regression
> types (trend lines). Can be enabled in the Options dialog.
>
> Demo 1 
> | 2  | 
> Screenshot
> 1
> 
> | 2
> 
>
>
> Remove gaps in bar/column charts: Data visualizer and event visualizer
> apps now support an option for displaying bar/column charts without gaps
> between the bars/columns. Can be enabled in the Options dialog.
>
> Demo  |
> Screenshot
> 
>
>
> Daily relative periods in event analytics: Various daily relative periods
> are now supported in event reports and event visualizer.
>
> Demo 
> | Screenshot
> 
>
>
> Share favorites with users: Analytics favorites can now be shared with
> individual users in addition to user groups. This is useful for more
> flexible sharing and removes the need for always creating a group. Click
> *Share* from the *Favorites* menu.
>
> Demo
> 
> | Screenshot
> 
>
>
> Favorite filter for “Created by me”: You can now easily filter your
> favorites with the new “Created by me”/”Created by others” filter,
> available in all the analytics apps.
>
> Demo  |
> Screenshot
> 
>
>
> Sort favorites by created and last updated: Analytics favorites can now
> be sorted by the date they were created and the date they were last updated.
>
> Demo
> 
> | Screenshot
> 
>
>
> Combine totals and details in pivots: Total values and details (operands)
> can now be combined in pivot tables and charts.
>
> Demo  |
> Screenshot
> 
>
>
> Indicator totals in pivots: The pivot table app now calculates total and
> subtotal values in a better way, dividing the sum of numerator values with
> the sum of denominator values multiplied by the average of indicator
> factors.
>
> Demo  |
> Screenshot
> 
>
>
>
> TRACKER FEATURES
>
> ---
>
> Compare to previous event during data entry: You can now choose to
> compare the current data entry for an event with previously completed
> events. This option is available when doing data entry for a new event in
> tracker capture.
>
> Demo 
> | Docs
> 
>
>
> Tracker and event capture with time, datetime and URL value types: Tracker
> and event capture apps now support the “Time”, “Datetime” and “URL” data
> element value types.
>
> Demo 
>
>
>
> GENERAL FEATURES
>
> ---
>
> Persist validation results: Validation results (violations) can now be
> 

Re: [Dhis2-users] dhis version 2.28 is out

2017-10-11 Thread jhansirk
Thank you and many congratulations to the team for the 2.28 release!!!

> On 11-Oct-2017, at 10:26 PM, Lars Helge Øverland  wrote:
> 
> Hi all,
> 
> DHIS version 2.28 is out. This version includes a range of improvements and 
> stability enhancements.
> 
> Log in with admin/district on the demo  system.
> 
> 
> ANALYTICS FEATURES
> ---
> 
> Measure criteria support in pivot tables: Pivot table app now supports 
> measure criteria, meaning criteria to apply to the data being returned, such 
> as a min and max value. Can be enabled in the Options dialog.
> 
> Demo  | 
> Screenshot 
> 
> 
> Multiple regression types in charts: Data visualizer and event visualizer 
> apps now supports a new option for linear, polynomial and loess regression 
> types (trend lines). Can be enabled in the Options dialog.
> 
> Demo 1  | 2 
>  | 
> Screenshot 1 
> 
>  | 2 
> 
> 
> Remove gaps in bar/column charts: Data visualizer and event visualizer apps 
> now support an option for displaying bar/column charts without gaps between 
> the bars/columns. Can be enabled in the Options dialog.
> 
> Demo  | 
> Screenshot 
> 
> 
> Daily relative periods in event analytics: Various daily relative periods are 
> now supported in event reports and event visualizer.
> 
> Demo  | 
> Screenshot 
> 
> 
> Share favorites with users: Analytics favorites can now be shared with 
> individual users in addition to user groups. This is useful for more flexible 
> sharing and removes the need for always creating a group. Click Share from 
> the Favorites menu.
> 
> Demo 
>  | 
> Screenshot 
> 
> 
> Favorite filter for “Created by me”: You can now easily filter your favorites 
> with the new “Created by me”/”Created by others” filter, available in all the 
> analytics apps.
> 
> Demo  | 
> Screenshot 
> 
> 
> Sort favorites by created and last updated: Analytics favorites can now be 
> sorted by the date they were created and the date they were last updated.
> 
> Demo 
>  | 
> Screenshot 
> 
> 
> Combine totals and details in pivots: Total values and details (operands) can 
> now be combined in pivot tables and charts.
> 
> Demo  | 
> Screenshot 
> 
> 
> Indicator totals in pivots: The pivot table app now calculates total and 
> subtotal values in a better way, dividing the sum of numerator values with 
> the sum of denominator values multiplied by the average of indicator factors.
> 
> Demo  | 
> Screenshot 
> 
> 
> 
> 
> TRACKER FEATURES
> ---
> 
> Compare to previous event during data entry: You can now choose to compare 
> the current data entry for an event with previously completed events. This 
> option is available when doing data entry for a new event in tracker capture.
> 
> Demo  | 
> Docs 
> 
> 
> Tracker and event capture with time, datetime and URL value types: Tracker 
> and event capture apps now support the “Time”, “Datetime” and “URL” data 
> element value types.
> 
> Demo 
> 
> 
> GENERAL FEATURES
> ---
> 
> Persist validation results: 

[Dhis2-users] dhis version 2.28 is out

2017-10-11 Thread Lars Helge Øverland
Hi all,

DHIS version 2.28 is out. This version includes a range of improvements and
stability enhancements.

Log in with admin/district on the demo  system.


ANALYTICS FEATURES

---

Measure criteria support in pivot tables: Pivot table app now supports
measure criteria, meaning criteria to apply to the data being returned,
such as a min and max value. Can be enabled in the Options dialog.

Demo  |
Screenshot



Multiple regression types in charts: Data visualizer and event visualizer
apps now supports a new option for linear, polynomial and loess regression
types (trend lines). Can be enabled in the Options dialog.

Demo 1  | 2
 | Screenshot
1

| 2



Remove gaps in bar/column charts: Data visualizer and event visualizer apps
now support an option for displaying bar/column charts without gaps between
the bars/columns. Can be enabled in the Options dialog.

Demo  |
Screenshot



Daily relative periods in event analytics: Various daily relative periods
are now supported in event reports and event visualizer.

Demo  |
Screenshot



Share favorites with users: Analytics favorites can now be shared with
individual users in addition to user groups. This is useful for more
flexible sharing and removes the need for always creating a group. Click
*Share* from the *Favorites* menu.

Demo

| Screenshot



Favorite filter for “Created by me”: You can now easily filter your
favorites with the new “Created by me”/”Created by others” filter,
available in all the analytics apps.

Demo  |
Screenshot



Sort favorites by created and last updated: Analytics favorites can now be
sorted by the date they were created and the date they were last updated.

Demo

| Screenshot



Combine totals and details in pivots: Total values and details (operands)
can now be combined in pivot tables and charts.

Demo  |
Screenshot



Indicator totals in pivots: The pivot table app now calculates total and
subtotal values in a better way, dividing the sum of numerator values with
the sum of denominator values multiplied by the average of indicator
factors.

Demo  |
Screenshot




TRACKER FEATURES

---

Compare to previous event during data entry: You can now choose to compare
the current data entry for an event with previously completed events. This
option is available when doing data entry for a new event in tracker
capture.

Demo  |
Docs



Tracker and event capture with time, datetime and URL value types: Tracker
and event capture apps now support the “Time”, “Datetime” and “URL” data
element value types.

Demo 



GENERAL FEATURES

---

Persist validation results: Validation results (violations) can now be
persisted. You can also access validation results in the analytics API,
meaning counts of validation violations.

Screenshot

| Docs



Skip form validation for validation 

Re: [Dhis2-users] postgresql 10 released

2017-10-11 Thread Lars Helge Øverland
Hi,

postgres 10 is out:

https://www.postgresql.org/about/news/1786/

Hint: we plan to leverage some of the new postgres 10 features in DHIS 2
and so planning to upgrade may be a good idea.

regards,

Lars



-- 
Lars Helge Øverland
Lead developer, DHIS 2
University of Oslo
Skype: larshelgeoverland
l...@dhis2.org
http://www.dhis2.org 
___
Mailing list: https://launchpad.net/~dhis2-users
Post to : dhis2-users@lists.launchpad.net
Unsubscribe : https://launchpad.net/~dhis2-users
More help   : https://help.launchpad.net/ListHelp


[Dhis2-users] postgresql 10 released

2017-10-11 Thread Lars Helge Øverland
Hi,

postgres

https://www.postgresql.org/about/news/1786/




-- 
Lars Helge Øverland
Lead developer, DHIS 2
University of Oslo
Skype: larshelgeoverland
l...@dhis2.org
http://www.dhis2.org 
___
Mailing list: https://launchpad.net/~dhis2-users
Post to : dhis2-users@lists.launchpad.net
Unsubscribe : https://launchpad.net/~dhis2-users
More help   : https://help.launchpad.net/ListHelp


Re: [Dhis2-users] postgresql 10 released

2017-10-11 Thread Bob Jolliffe
Some interesting looking new features.  Per database and per table
level replication could be particularly useful.

On 11 October 2017 at 17:42, Lars Helge Øverland  wrote:
> Hi,
>
> postgres
>
> https://www.postgresql.org/about/news/1786/
>
>
>
>
> --
> Lars Helge Øverland
> Lead developer, DHIS 2
> University of Oslo
> Skype: larshelgeoverland
> l...@dhis2.org
> http://www.dhis2.org
>
>
> ___
> Mailing list: https://launchpad.net/~dhis2-users
> Post to : dhis2-users@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~dhis2-users
> More help   : https://help.launchpad.net/ListHelp
>

___
Mailing list: https://launchpad.net/~dhis2-users
Post to : dhis2-users@lists.launchpad.net
Unsubscribe : https://launchpad.net/~dhis2-users
More help   : https://help.launchpad.net/ListHelp


Re: [Dhis2-users] DHIS 2 to support PostgreSQL only?

2017-10-11 Thread Lars Helge Øverland
Thanks all for the feedback on this issue!

regards,

Lars


On Fri, Sep 8, 2017 at 1:19 PM, Hannan Khan  wrote:

> Hi Lars
>
> Fully agreed. To concentrate one one DB platforms will not only saves time
> and effort, also being efficiency to the system and can make more use of
> advance functionality of the PostgreSQL & PostGIS.
>
> You will have our full support.
>
> Hannan
>
> On Fri, Sep 8, 2017 at 2:26 PM, Lars Helge Øverland 
> wrote:
>
>> Hi all,
>>
>> I want to bring up the idea of solely support PostgreSQL for DHIS 2 for
>> production use to get feedback from the community.
>>
>> The DHIS 2 team is seeing clear benefits of moving to PostgreSQL-only.
>> The main ones are:
>>
>> 1. Supporting and testing for more than one database platform is
>> time-consuming. The majority of DHIS 2 implementations is using PostgreSQL
>> already.
>>
>> 2. PostgreSQL supports advanced geospatial features through PostGIS. We
>> are already depending on these for the GIS module to work optimally (i.e.
>> for event clustering in GIS). There are no direct equivalent in e.g. MySQL.
>> We are also considering using PostGIS data types in main data model.
>>
>> 3. PostgreSQL will provide some impressive features which will become
>> very useful for us in version 10
>>  and 11. E.g.
>> native partitioning, parallel queries, logical replication, foreign tables
>> and improved query performance will be useful and allow us to develop the
>> next DHIS 2 analytics solution.
>>
>>
>> We are aware this will be inconvenient for users of other databases such
>> as MySQL, but there is the option of migrating your database through the
>> DHIS 2 metadata and data value import-export feature.
>>
>> On a technical note, we will keep the Hibernate development framework and
>> keep supporting the H2 database for unit testing purposes.
>>
>> Please let us know your thoughts on this.
>>
>> regards,
>>
>> Lars
>>
>>
>>
>>
>> --
>> Lars Helge Øverland
>> Lead developer, DHIS 2
>> University of Oslo
>> Skype: larshelgeoverland
>> l...@dhis2.org
>> http://www.dhis2.org 
>>
>>
>> ___
>> Mailing list: https://launchpad.net/~dhis2-users
>> Post to : dhis2-users@lists.launchpad.net
>> Unsubscribe : https://launchpad.net/~dhis2-users
>> More help   : https://help.launchpad.net/ListHelp
>>
>>
>
>
> --
> Muhammad Abdul Hannan Khan
> Team Leader
> Support to the National HMIS
> MIS, Director General of Health Service
> Ministry of Health and Family Welfare
>
> T +880-2- 58816459 <+880%202-58816459>, 58816412 ext 118
> <58%2081%2064%2012>
> F +88 02 58813 875
> M+88 01819 239 241
> M+88 01534 312 066
> E hann...@gmail.com
> S hannan.khan.dhaka
> B hannan-tech.blogspot.com
> L https://bd.linkedin.com/in/hannankhan
>
>
>
>


-- 
Lars Helge Øverland
Lead developer, DHIS 2
University of Oslo
Skype: larshelgeoverland
l...@dhis2.org
http://www.dhis2.org 
___
Mailing list: https://launchpad.net/~dhis2-users
Post to : dhis2-users@lists.launchpad.net
Unsubscribe : https://launchpad.net/~dhis2-users
More help   : https://help.launchpad.net/ListHelp


Re: [Dhis2-users] Standard approach for recording age at the time of diagnosis when date of birth is unknown

2017-10-11 Thread Abyot Asalefew Gizaw
Hi,

To avoid confusion, probably better we rename AGE value type to DOB - this,
I believe, should always be calculated against today.

And for your usecases, what you need is not really DOB or AGE as we know is
conventionally ... rather just a number that you can store with "age"
value.

--
Abyot A. Gizaw.
Senior Engineer, DHIS2
University of Oslo
http://www.dhis2.org

On Wed, Oct 11, 2017 at 5:14 PM, TIMIMI, Hazim Bakir 
wrote:

> Thanks very much Lise, you described my concerns very well (although I had
> to stop to work out what DE and PI meant!).
>
> Cheers,
>
> Hazim
>
>
>
> *From:* GROUT, Lise
> *Sent:* 11 October 2017 17:09
> *To:* Abyot Asalefew Gizaw; TIMIMI, Hazim Bakir
> *Cc:* dhis2-users@lists.launchpad.net
>
> *Subject:* RE: [Dhis2-users] Standard approach for recording age at the
> time of diagnosis when date of birth is unknown
>
>
>
> Dear all,
>
>
>
> I tested the Age-type date element which is good to capture the
> approximate age of the patient. But this is a dynamic variable, in the
> sense that every day, the patient will be older of one day. Obviously, this
> is a very good attribute for the registration for example in tracker, in
> order to be able to look for a patient with the age variable, even if s/he
> shows up months or years later.
>
>
>
> But it is also important for us to capture the age at the moment of
> clinical examination/admission/presentation (whatever the name you give
> it) and that this variable is static (it won’t change over time). And for
> this, the age-type DE is therefore not helpful.
>
>
>
> We currently have “Date of birth” which is date-type and “Age in years”
> which is number-type DE, and we would actually like to have a PI “Age at
> clinical examination” which is calculated with “DOB” if available or “Age
> in years” if not available (not configured properly yet). Probably,
> ideally, the PI “Age at clinical examination” should be calculated either
> on the “DOB” DE or in the approximative DOB provided through the Age-type
> DE, but I don’t know if this is possible. (Don’t know if I make sense).
>
>
>
> Best
>
> Lise.
>
>
>
> *From:* Dhis2-users [mailto:dhis2-users-bounces+groutl=who.int@lists.
> launchpad.net ] *On
> Behalf Of *Abyot Asalefew Gizaw
> *Sent:* 11 October 2017 16:46
> *To:* TIMIMI, Hazim Bakir
> *Cc:* dhis2-users@lists.launchpad.net
> *Subject:* Re: [Dhis2-users] Standard approach for recording age at the
> time of diagnosis when date of birth is unknown
>
>
>
> Hi,
>
>
>
> We will try to update the documentation :)
>
>
>
> As to the issue you refereed, it is a new one and most of us here haven't
> looked into it before... Nonetheless, looking into the requirement
> mentioned there - I think introducing the concept of age there will
> probably over complicate things. What is required seems to capture a static
> figure - and defining a simple data element of type number will handle that.
>
>
> --
>
> Abyot A. Gizaw.
>
> Senior Engineer, DHIS2
>
> University of Oslo
>
> http://www.dhis2.org
>
>
>
> On Wed, Oct 11, 2017 at 4:23 PM, TIMIMI, Hazim Bakir 
> wrote:
>
> Hi Abyot,
>
>
>
> Interesting, thanks. I wasn’t aware of the value type called AGE within
> DHIS2. I tried to find some documentation for this at
> https://www.dhis2.org/documentation  but couldn't see anything. I only
> found references to it on Github and also on the 2.26 release notes (
> https://www.dhis2.org/226). It doesn't explain what to do if you only
> know approximate age in years, not whether the reference date is the data
> entry date or the report/event/diagnosis date (if data entry is post hoc).
> I see this is already reported as a request in JIRA (
> https://jira.dhis2.org/browse/DHIS2-2345).
>
>
>
> Cheers,
>
> Hazim
>
>
>
>
>
>
>
> *From:* Abyot Asalefew Gizaw [mailto:ab...@dhis2.org]
> *Sent:* 11 October 2017 15:02
> *To:* TIMIMI, Hazim Bakir
> *Cc:* Edward Robinson; dhis2-users@lists.launchpad.net
> *Subject:* Re: [Dhis2-users] Standard approach for recording age at the
> time of diagnosis when date of birth is unknown
>
>
>
> Hi,
>
>
>
> We don't capture the additional data if DOB is approximated or not...
>
>
>
> Otherwise, we have a value type called AGE, then during data entry a
> special input field is rendered, see below
>
>
>
> [image: Inline image 1]
>
>
> Users are free to fill any or combination of these and behind the scene
> the system calculates/updates each field and in the end DOB is saved.
>
>
>
> --
>
> Abyot A. Gizaw.
>
> Senior Engineer, DHIS2
>
> University of Oslo
>
> http://www.dhis2.org
>
>
>
> On Wed, Oct 11, 2017 at 2:21 PM, TIMIMI, Hazim Bakir 
> wrote:
>
> Hi Ed,
>
> Thanks very much, that makes sense. I also came across this yesterday
> which seems similar to what you have done in the past (see under
> "Collection and usage attributes"): http://meteor.aihw.gov.au/
> content/index.phtml/itemId/287007
>
> Cheers,
> Hazim
>
>
> 

Re: [Dhis2-users] Standard approach for recording age at the time of diagnosis when date of birth is unknown

2017-10-11 Thread TIMIMI , Hazim Bakir
Thanks very much Lise, you described my concerns very well (although I had to 
stop to work out what DE and PI meant!).
Cheers,
Hazim
 
From: GROUT, Lise 
Sent: 11 October 2017 17:09
To: Abyot Asalefew Gizaw; TIMIMI, Hazim Bakir
Cc: dhis2-users@lists.launchpad.net
Subject: RE: [Dhis2-users] Standard approach for recording age at the time of 
diagnosis when date of birth is unknown

 
Dear all, 
 
I tested the Age-type date element which is good to capture the approximate age 
of the patient. But this is a dynamic variable, in the sense that every day, 
the patient will be older of one day. Obviously, this is a very good attribute 
for the registration for example in tracker, in order to be able to look for a 
patient with the age variable, even if s/he shows up months or years later.
 
But it is also important for us to capture the age at the moment of clinical 
examination/admission/presentation (whatever the name you give it) and that 
this variable is static (it won’t change over time). And for this, the age-type 
DE is therefore not helpful. 
 
We currently have “Date of birth” which is date-type and “Age in years” which 
is number-type DE, and we would actually like to have a PI “Age at clinical 
examination” which is calculated with “DOB” if available or “Age in years” if 
not available (not configured properly yet). Probably, ideally, the PI “Age at 
clinical examination” should be calculated either on the “DOB” DE or in the 
approximative DOB provided through the Age-type DE, but I don’t know if this is 
possible. (Don’t know if I make sense). 
 
Best
Lise.
 
From: Dhis2-users 
[mailto:dhis2-users-bounces+groutl=who@lists.launchpad.net] On Behalf Of 
Abyot Asalefew Gizaw
Sent: 11 October 2017 16:46
To: TIMIMI, Hazim Bakir
Cc: dhis2-users@lists.launchpad.net
Subject: Re: [Dhis2-users] Standard approach for recording age at the time of 
diagnosis when date of birth is unknown
 
Hi,
 

We will try to update the documentation :)

 

As to the issue you refereed, it is a new one and most of us here haven't 
looked into it before... Nonetheless, looking into the requirement mentioned 
there - I think introducing the concept of age there will probably over 
complicate things. What is required seems to capture a static figure - and 
defining a simple data element of type number will handle that.



--

Abyot A. Gizaw.

Senior Engineer, DHIS2

University of Oslo

http://www.dhis2.org

 
On Wed, Oct 11, 2017 at 4:23 PM, TIMIMI, Hazim Bakir  wrote:
Hi Abyot,
 
Interesting, thanks. I wasn’t aware of the value type called AGE within DHIS2. 
I tried to find some documentation for this at 
https://www.dhis2.org/documentation  but couldn't see anything. I only found 
references to it on Github and also on the 2.26 release notes 
(https://www.dhis2.org/226). It doesn't explain what to do if you only know 
approximate age in years, not whether the reference date is the data entry date 
or the report/event/diagnosis date (if data entry is post hoc). I see this is 
already reported as a request in JIRA 
(https://jira.dhis2.org/browse/DHIS2-2345). 
 
Cheers,
Hazim  
 
 
 
From: Abyot Asalefew Gizaw [mailto:ab...@dhis2.org] 
Sent: 11 October 2017 15:02
To: TIMIMI, Hazim Bakir
Cc: Edward Robinson; dhis2-users@lists.launchpad.net
Subject: Re: [Dhis2-users] Standard approach for recording age at the time of 
diagnosis when date of birth is unknown
 
Hi,
 

We don't capture the additional data if DOB is approximated or not...

 

Otherwise, we have a value type called AGE, then during data entry a special 
input field is rendered, see below

 

 [Inline image 1] 



Users are free to fill any or combination of these and behind the scene the 
system calculates/updates each field and in the end DOB is saved.

 

--

Abyot A. Gizaw.

Senior Engineer, DHIS2

University of Oslo

http://www.dhis2.org

 
On Wed, Oct 11, 2017 at 2:21 PM, TIMIMI, Hazim Bakir  wrote:
Hi Ed,

Thanks very much, that makes sense. I also came across this yesterday which 
seems similar to what you have done in the past (see under "Collection and 
usage attributes"): http://meteor.aihw.gov.au/content/index.phtml/itemId/287007

Cheers,
Hazim

-Original Message-
From: Edward Robinson [mailto:erobin...@projectbalance.com]
Sent: 11 October 2017 13:40
To: TIMIMI, Hazim Bakir; dhis2-users@lists.launchpad.net
Subject: RE: [Dhis2-users] Standard approach for recording age at the time of 
diagnosis when date of birth is unknown

What we've done in the past with other systems is have a field for estimated 
age at time of registration - only completed if the DOB is not known.  DOB is 
then auto-populated based on the entered age, and an additional YES/NO field is 
updated to note that the DOB is estimated and not exact.
Ed

-Original Message-
From: Dhis2-users 
[mailto:dhis2-users-bounces+erobinson=projectbalance@lists.launchpad.net] 
On Behalf Of TIMIMI, Hazim Bakir
Sent: Tuesday, 10 October 2017 5:01 PM
To: 

Re: [Dhis2-users] Standard approach for recording age at the time of diagnosis when date of birth is unknown

2017-10-11 Thread GROUT , Lise
Dear all, 
 
I tested the Age-type date element which is good to capture the approximate age 
of the patient. But this is a dynamic variable, in the sense that every day, 
the patient will be older of one day. Obviously, this is a very good attribute 
for the registration for example in tracker, in order to be able to look for a 
patient with the age variable, even if s/he shows up months or years later.
 
But it is also important for us to capture the age at the moment of clinical 
examination/admission/presentation (whatever the name you give it) and that 
this variable is static (it won’t change over time). And for this, the age-type 
DE is therefore not helpful. 
 
We currently have “Date of birth” which is date-type and “Age in years” which 
is number-type DE, and we would actually like to have a PI “Age at clinical 
examination” which is calculated with “DOB” if available or “Age in years” if 
not available (not configured properly yet). Probably, ideally, the PI “Age at 
clinical examination” should be calculated either on the “DOB” DE or in the 
approximative DOB provided through the Age-type DE, but I don’t know if this is 
possible. (Don’t know if I make sense). 
 
Best
Lise.
 
From: Dhis2-users 
[mailto:dhis2-users-bounces+groutl=who@lists.launchpad.net] On Behalf Of 
Abyot Asalefew Gizaw
Sent: 11 October 2017 16:46
To: TIMIMI, Hazim Bakir
Cc: dhis2-users@lists.launchpad.net
Subject: Re: [Dhis2-users] Standard approach for recording age at the time of 
diagnosis when date of birth is unknown
 
Hi,
 

We will try to update the documentation :)

 

As to the issue you refereed, it is a new one and most of us here haven't 
looked into it before... Nonetheless, looking into the requirement mentioned 
there - I think introducing the concept of age there will probably over 
complicate things. What is required seems to capture a static figure - and 
defining a simple data element of type number will handle that.



--

Abyot A. Gizaw.

Senior Engineer, DHIS2

University of Oslo

http://www.dhis2.org

 
On Wed, Oct 11, 2017 at 4:23 PM, TIMIMI, Hazim Bakir  wrote:
Hi Abyot,
 
Interesting, thanks. I wasn’t aware of the value type called AGE within DHIS2. 
I tried to find some documentation for this at 
https://www.dhis2.org/documentation  but couldn't see anything. I only found 
references to it on Github and also on the 2.26 release notes 
(https://www.dhis2.org/226). It doesn't explain what to do if you only know 
approximate age in years, not whether the reference date is the data entry date 
or the report/event/diagnosis date (if data entry is post hoc). I see this is 
already reported as a request in JIRA 
(https://jira.dhis2.org/browse/DHIS2-2345). 
 
Cheers,
Hazim  
 
 
 
From: Abyot Asalefew Gizaw [mailto:ab...@dhis2.org] 
Sent: 11 October 2017 15:02
To: TIMIMI, Hazim Bakir
Cc: Edward Robinson; dhis2-users@lists.launchpad.net
Subject: Re: [Dhis2-users] Standard approach for recording age at the time of 
diagnosis when date of birth is unknown
 
Hi,
 

We don't capture the additional data if DOB is approximated or not...

 

Otherwise, we have a value type called AGE, then during data entry a special 
input field is rendered, see below

 

 [Inline image 1] 



Users are free to fill any or combination of these and behind the scene the 
system calculates/updates each field and in the end DOB is saved.

 

--

Abyot A. Gizaw.

Senior Engineer, DHIS2

University of Oslo

http://www.dhis2.org

 
On Wed, Oct 11, 2017 at 2:21 PM, TIMIMI, Hazim Bakir  wrote:
Hi Ed,

Thanks very much, that makes sense. I also came across this yesterday which 
seems similar to what you have done in the past (see under "Collection and 
usage attributes"): http://meteor.aihw.gov.au/content/index.phtml/itemId/287007

Cheers,
Hazim

-Original Message-
From: Edward Robinson [mailto:erobin...@projectbalance.com]
Sent: 11 October 2017 13:40
To: TIMIMI, Hazim Bakir; dhis2-users@lists.launchpad.net
Subject: RE: [Dhis2-users] Standard approach for recording age at the time of 
diagnosis when date of birth is unknown

What we've done in the past with other systems is have a field for estimated 
age at time of registration - only completed if the DOB is not known.  DOB is 
then auto-populated based on the entered age, and an additional YES/NO field is 
updated to note that the DOB is estimated and not exact.
Ed

-Original Message-
From: Dhis2-users 
[mailto:dhis2-users-bounces+erobinson=projectbalance@lists.launchpad.net] 
On Behalf Of TIMIMI, Hazim Bakir
Sent: Tuesday, 10 October 2017 5:01 PM
To: dhis2-users@lists.launchpad.net
Subject: [Dhis2-users] Standard approach for recording age at the time of 
diagnosis when date of birth is unknown

Is there a standard approach commonly in use to handle ages when the exact date 
of birth of a patient is unknown? I can think of two ways -- either using a 
surrogate (approximate) date of birth that tallies with a person's reported 

Re: [Dhis2-users] Standard approach for recording age at the time of diagnosis when date of birth is unknown

2017-10-11 Thread Abyot Asalefew Gizaw
Hi,

We will try to update the documentation :)

As to the issue you refereed, it is a new one and most of us here haven't
looked into it before... Nonetheless, looking into the requirement
mentioned there - I think introducing the concept of age there will
probably over complicate things. What is required seems to capture a static
figure - and defining a simple data element of type number will handle that.

--
Abyot A. Gizaw.
Senior Engineer, DHIS2
University of Oslo
http://www.dhis2.org

On Wed, Oct 11, 2017 at 4:23 PM, TIMIMI, Hazim Bakir 
wrote:

> Hi Abyot,
>
>
>
> Interesting, thanks. I wasn’t aware of the value type called AGE within
> DHIS2. I tried to find some documentation for this at
> https://www.dhis2.org/documentation  but couldn't see anything. I only
> found references to it on Github and also on the 2.26 release notes (
> https://www.dhis2.org/226). It doesn't explain what to do if you only
> know approximate age in years, not whether the reference date is the data
> entry date or the report/event/diagnosis date (if data entry is post hoc).
> I see this is already reported as a request in JIRA (
> https://jira.dhis2.org/browse/DHIS2-2345).
>
>
>
> Cheers,
>
> Hazim
>
>
>
>
>
>
>
> *From:* Abyot Asalefew Gizaw [mailto:ab...@dhis2.org]
> *Sent:* 11 October 2017 15:02
> *To:* TIMIMI, Hazim Bakir
> *Cc:* Edward Robinson; dhis2-users@lists.launchpad.net
> *Subject:* Re: [Dhis2-users] Standard approach for recording age at the
> time of diagnosis when date of birth is unknown
>
>
>
> Hi,
>
>
>
> We don't capture the additional data if DOB is approximated or not...
>
>
>
> Otherwise, we have a value type called AGE, then during data entry a
> special input field is rendered, see below
>
>
>
> [image: Inline image 1]
>
>
> Users are free to fill any or combination of these and behind the scene
> the system calculates/updates each field and in the end DOB is saved.
>
>
>
> --
>
> Abyot A. Gizaw.
>
> Senior Engineer, DHIS2
>
> University of Oslo
>
> http://www.dhis2.org
>
>
>
> On Wed, Oct 11, 2017 at 2:21 PM, TIMIMI, Hazim Bakir 
> wrote:
>
> Hi Ed,
>
> Thanks very much, that makes sense. I also came across this yesterday
> which seems similar to what you have done in the past (see under
> "Collection and usage attributes"): http://meteor.aihw.gov.au/
> content/index.phtml/itemId/287007
>
> Cheers,
> Hazim
>
>
> -Original Message-
> From: Edward Robinson [mailto:erobin...@projectbalance.com]
> Sent: 11 October 2017 13:40
> To: TIMIMI, Hazim Bakir; dhis2-users@lists.launchpad.net
> Subject: RE: [Dhis2-users] Standard approach for recording age at the time
> of diagnosis when date of birth is unknown
>
> What we've done in the past with other systems is have a field for
> estimated age at time of registration - only completed if the DOB is not
> known.  DOB is then auto-populated based on the entered age, and an
> additional YES/NO field is updated to note that the DOB is estimated and
> not exact.
> Ed
>
> -Original Message-
> From: Dhis2-users [mailto:dhis2-users-bounces+erobinson=
> projectbalance@lists.launchpad.net] On Behalf Of TIMIMI, Hazim Bakir
> Sent: Tuesday, 10 October 2017 5:01 PM
> To: dhis2-users@lists.launchpad.net
> Subject: [Dhis2-users] Standard approach for recording age at the time of
> diagnosis when date of birth is unknown
>
> Is there a standard approach commonly in use to handle ages when the exact
> date of birth of a patient is unknown? I can think of two ways -- either
> using a surrogate (approximate) date of birth that tallies with a person's
> reported age, or have an extra data element for age at time of diagnosis to
> be used only if date of birth is unknown. Obviously, if date of birth is
> known then age is calculated automatically.
>
> I would like to know what people have been using and have seen to be
> working in practice (and not necessarily just in DHIS2).
>
> Thanks!
>
> Hazim
> …..
> Hazim Timimi
> Data Manager, Tuberculosis Monitoring and Evaluation, World Health
> Organization, Geneva, Switzerland Tel : +41 22 791 3468
>
>
>
> ___
> Mailing list: https://launchpad.net/~dhis2-users
> Post to : dhis2-users@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~dhis2-users
> More help   : https://help.launchpad.net/ListHelp
> ___
> Mailing list: https://launchpad.net/~dhis2-users
> Post to : dhis2-users@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~dhis2-users
> More help   : https://help.launchpad.net/ListHelp
>
>
>
___
Mailing list: https://launchpad.net/~dhis2-users
Post to : dhis2-users@lists.launchpad.net
Unsubscribe : https://launchpad.net/~dhis2-users
More help   : https://help.launchpad.net/ListHelp


Re: [Dhis2-users] Standard approach for recording age at the time of diagnosis when date of birth is unknown

2017-10-11 Thread TIMIMI , Hazim Bakir
Hi Abyot,
 
Interesting, thanks. I wasn’t aware of the value type called AGE within DHIS2. 
I tried to find some documentation for this at 
https://www.dhis2.org/documentation  but couldn't see anything. I only found 
references to it on Github and also on the 2.26 release notes 
(https://www.dhis2.org/226). It doesn't explain what to do if you only know 
approximate age in years, not whether the reference date is the data entry date 
or the report/event/diagnosis date (if data entry is post hoc). I see this is 
already reported as a request in JIRA 
(https://jira.dhis2.org/browse/DHIS2-2345). 
 
Cheers,
Hazim  
 
 
 
From: Abyot Asalefew Gizaw [mailto:ab...@dhis2.org] 
Sent: 11 October 2017 15:02
To: TIMIMI, Hazim Bakir
Cc: Edward Robinson; dhis2-users@lists.launchpad.net
Subject: Re: [Dhis2-users] Standard approach for recording age at the time of 
diagnosis when date of birth is unknown
 
Hi,
 

We don't capture the additional data if DOB is approximated or not...

 

Otherwise, we have a value type called AGE, then during data entry a special 
input field is rendered, see below

 

 [Inline image 1] 



Users are free to fill any or combination of these and behind the scene the 
system calculates/updates each field and in the end DOB is saved.

 

--

Abyot A. Gizaw.

Senior Engineer, DHIS2

University of Oslo

http://www.dhis2.org

 
On Wed, Oct 11, 2017 at 2:21 PM, TIMIMI, Hazim Bakir  wrote:
Hi Ed,

Thanks very much, that makes sense. I also came across this yesterday which 
seems similar to what you have done in the past (see under "Collection and 
usage attributes"): http://meteor.aihw.gov.au/content/index.phtml/itemId/287007

Cheers,
Hazim

-Original Message-
From: Edward Robinson [mailto:erobin...@projectbalance.com]
Sent: 11 October 2017 13:40
To: TIMIMI, Hazim Bakir; dhis2-users@lists.launchpad.net
Subject: RE: [Dhis2-users] Standard approach for recording age at the time of 
diagnosis when date of birth is unknown

What we've done in the past with other systems is have a field for estimated 
age at time of registration - only completed if the DOB is not known.  DOB is 
then auto-populated based on the entered age, and an additional YES/NO field is 
updated to note that the DOB is estimated and not exact.
Ed

-Original Message-
From: Dhis2-users 
[mailto:dhis2-users-bounces+erobinson=projectbalance@lists.launchpad.net] 
On Behalf Of TIMIMI, Hazim Bakir
Sent: Tuesday, 10 October 2017 5:01 PM
To: dhis2-users@lists.launchpad.net
Subject: [Dhis2-users] Standard approach for recording age at the time of 
diagnosis when date of birth is unknown

Is there a standard approach commonly in use to handle ages when the exact date 
of birth of a patient is unknown? I can think of two ways -- either using a 
surrogate (approximate) date of birth that tallies with a person's reported 
age, or have an extra data element for age at time of diagnosis to be used only 
if date of birth is unknown. Obviously, if date of birth is known then age is 
calculated automatically.

I would like to know what people have been using and have seen to be working in 
practice (and not necessarily just in DHIS2).

Thanks!

Hazim
…..
Hazim Timimi
Data Manager, Tuberculosis Monitoring and Evaluation, World Health 
Organization, Geneva, Switzerland Tel : +41 22 791 3468



___
Mailing list: https://launchpad.net/~dhis2-users
Post to : dhis2-users@lists.launchpad.net
Unsubscribe : https://launchpad.net/~dhis2-users
More help   : https://help.launchpad.net/ListHelp
___
Mailing list: https://launchpad.net/~dhis2-users
Post to : dhis2-users@lists.launchpad.net
Unsubscribe : https://launchpad.net/~dhis2-users
More help   : https://help.launchpad.net/ListHelp

 


___
Mailing list: https://launchpad.net/~dhis2-users
Post to : dhis2-users@lists.launchpad.net
Unsubscribe : https://launchpad.net/~dhis2-users
More help   : https://help.launchpad.net/ListHelp


Re: [Dhis2-users] Restrict data access on the mobile application

2017-10-11 Thread abhishek addepally
Thank you, Marta for the reply and detailed description of the DHIS2
behavior in this regard.

-Siva

On Sun, Oct 8, 2017 at 5:15 AM, Marta Vila  wrote:

> Hi Siva,
>
> the Android App has the same access that restrictions than the web. It is
> based in org. unit assignment, program assignment ( via user role ) and
> sharing settings, so... there is no direct way to allow access of one user
> only the information that s/he has entered. It has to be done through
> configuration.
>
> However, in Android , downloading data (Tracked entities, and their
> program data) is not automatic, it has to be done explicitly by the user
> through the "Download Entities" functionality. As a result, if your users
> do not download Tracked Entities, they will only have access to the data
> that they have entered in their device. It is not exactly what you were
> asking for, but is the closest behavior I can find for your request.
>
> Best,
> Marta
>
>
>
> On 8 October 2017 at 03:29, abhishek addepally <
> abhishekaddepa...@gmail.com> wrote:
>
>> Hi,
>>
>> When a user is capturing the data using tracker capture application is
>> there any way to restrict access only to retrieve the information the user
>> has entered.
>> Please let me know.
>>
>> -Siva
>>
>>
>> ___
>> Mailing list: https://launchpad.net/~dhis2-users
>> Post to : dhis2-users@lists.launchpad.net
>> Unsubscribe : https://launchpad.net/~dhis2-users
>> More help   : https://help.launchpad.net/ListHelp
>>
>>
>
___
Mailing list: https://launchpad.net/~dhis2-users
Post to : dhis2-users@lists.launchpad.net
Unsubscribe : https://launchpad.net/~dhis2-users
More help   : https://help.launchpad.net/ListHelp


Re: [Dhis2-users] Standard approach for recording age at the time of diagnosis when date of birth is unknown

2017-10-11 Thread Abyot Asalefew Gizaw
Hi,

We don't capture the additional data if DOB is approximated or not...

Otherwise, we have a value type called AGE, then during data entry a
special input field is rendered, see below

[image: Inline image 1]

Users are free to fill any or combination of these and behind the scene the
system calculates/updates each field and in the end DOB is saved.

--
Abyot A. Gizaw.
Senior Engineer, DHIS2
University of Oslo
http://www.dhis2.org

On Wed, Oct 11, 2017 at 2:21 PM, TIMIMI, Hazim Bakir 
wrote:

> Hi Ed,
>
> Thanks very much, that makes sense. I also came across this yesterday
> which seems similar to what you have done in the past (see under
> "Collection and usage attributes"): http://meteor.aihw.gov.au/
> content/index.phtml/itemId/287007
>
> Cheers,
> Hazim
>
> -Original Message-
> From: Edward Robinson [mailto:erobin...@projectbalance.com]
> Sent: 11 October 2017 13:40
> To: TIMIMI, Hazim Bakir; dhis2-users@lists.launchpad.net
> Subject: RE: [Dhis2-users] Standard approach for recording age at the time
> of diagnosis when date of birth is unknown
>
> What we've done in the past with other systems is have a field for
> estimated age at time of registration - only completed if the DOB is not
> known.  DOB is then auto-populated based on the entered age, and an
> additional YES/NO field is updated to note that the DOB is estimated and
> not exact.
> Ed
>
> -Original Message-
> From: Dhis2-users [mailto:dhis2-users-bounces+erobinson=
> projectbalance@lists.launchpad.net] On Behalf Of TIMIMI, Hazim Bakir
> Sent: Tuesday, 10 October 2017 5:01 PM
> To: dhis2-users@lists.launchpad.net
> Subject: [Dhis2-users] Standard approach for recording age at the time of
> diagnosis when date of birth is unknown
>
> Is there a standard approach commonly in use to handle ages when the exact
> date of birth of a patient is unknown? I can think of two ways -- either
> using a surrogate (approximate) date of birth that tallies with a person's
> reported age, or have an extra data element for age at time of diagnosis to
> be used only if date of birth is unknown. Obviously, if date of birth is
> known then age is calculated automatically.
>
> I would like to know what people have been using and have seen to be
> working in practice (and not necessarily just in DHIS2).
>
> Thanks!
>
> Hazim
> …..
> Hazim Timimi
> Data Manager, Tuberculosis Monitoring and Evaluation, World Health
> Organization, Geneva, Switzerland Tel : +41 22 791 3468
>
>
>
> ___
> Mailing list: https://launchpad.net/~dhis2-users
> Post to : dhis2-users@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~dhis2-users
> More help   : https://help.launchpad.net/ListHelp
> ___
> Mailing list: https://launchpad.net/~dhis2-users
> Post to : dhis2-users@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~dhis2-users
> More help   : https://help.launchpad.net/ListHelp
>
___
Mailing list: https://launchpad.net/~dhis2-users
Post to : dhis2-users@lists.launchpad.net
Unsubscribe : https://launchpad.net/~dhis2-users
More help   : https://help.launchpad.net/ListHelp


Re: [Dhis2-users] Standard approach for recording age at the time of diagnosis when date of birth is unknown

2017-10-11 Thread TIMIMI , Hazim Bakir
Hi Ed,

Thanks very much, that makes sense. I also came across this yesterday which 
seems similar to what you have done in the past (see under "Collection and 
usage attributes"): http://meteor.aihw.gov.au/content/index.phtml/itemId/287007 

Cheers,
Hazim

-Original Message-
From: Edward Robinson [mailto:erobin...@projectbalance.com] 
Sent: 11 October 2017 13:40
To: TIMIMI, Hazim Bakir; dhis2-users@lists.launchpad.net
Subject: RE: [Dhis2-users] Standard approach for recording age at the time of 
diagnosis when date of birth is unknown

What we've done in the past with other systems is have a field for estimated 
age at time of registration - only completed if the DOB is not known.  DOB is 
then auto-populated based on the entered age, and an additional YES/NO field is 
updated to note that the DOB is estimated and not exact.
Ed

-Original Message-
From: Dhis2-users 
[mailto:dhis2-users-bounces+erobinson=projectbalance@lists.launchpad.net] 
On Behalf Of TIMIMI, Hazim Bakir
Sent: Tuesday, 10 October 2017 5:01 PM
To: dhis2-users@lists.launchpad.net
Subject: [Dhis2-users] Standard approach for recording age at the time of 
diagnosis when date of birth is unknown

Is there a standard approach commonly in use to handle ages when the exact date 
of birth of a patient is unknown? I can think of two ways -- either using a 
surrogate (approximate) date of birth that tallies with a person's reported 
age, or have an extra data element for age at time of diagnosis to be used only 
if date of birth is unknown. Obviously, if date of birth is known then age is 
calculated automatically.

I would like to know what people have been using and have seen to be working in 
practice (and not necessarily just in DHIS2).

Thanks!

Hazim
…..
Hazim Timimi
Data Manager, Tuberculosis Monitoring and Evaluation, World Health 
Organization, Geneva, Switzerland Tel : +41 22 791 3468



___
Mailing list: https://launchpad.net/~dhis2-users
Post to : dhis2-users@lists.launchpad.net
Unsubscribe : https://launchpad.net/~dhis2-users
More help   : https://help.launchpad.net/ListHelp
___
Mailing list: https://launchpad.net/~dhis2-users
Post to : dhis2-users@lists.launchpad.net
Unsubscribe : https://launchpad.net/~dhis2-users
More help   : https://help.launchpad.net/ListHelp


Re: [Dhis2-users] Standard approach for recording age at the time of diagnosis when date of birth is unknown

2017-10-11 Thread Edward Robinson
What we've done in the past with other systems is have a field for estimated 
age at time of registration - only completed if the DOB is not known.  DOB is 
then auto-populated based on the entered age, and an additional YES/NO field is 
updated to note that the DOB is estimated and not exact.
Ed

-Original Message-
From: Dhis2-users 
[mailto:dhis2-users-bounces+erobinson=projectbalance@lists.launchpad.net] 
On Behalf Of TIMIMI, Hazim Bakir
Sent: Tuesday, 10 October 2017 5:01 PM
To: dhis2-users@lists.launchpad.net
Subject: [Dhis2-users] Standard approach for recording age at the time of 
diagnosis when date of birth is unknown

Is there a standard approach commonly in use to handle ages when the exact date 
of birth of a patient is unknown? I can think of two ways -- either using a 
surrogate (approximate) date of birth that tallies with a person's reported 
age, or have an extra data element for age at time of diagnosis to be used only 
if date of birth is unknown. Obviously, if date of birth is known then age is 
calculated automatically.

I would like to know what people have been using and have seen to be working in 
practice (and not necessarily just in DHIS2).

Thanks!

Hazim
…..
Hazim Timimi
Data Manager, Tuberculosis Monitoring and Evaluation, World Health 
Organization, Geneva, Switzerland Tel : +41 22 791 3468



___
Mailing list: https://launchpad.net/~dhis2-users
Post to : dhis2-users@lists.launchpad.net
Unsubscribe : https://launchpad.net/~dhis2-users
More help   : https://help.launchpad.net/ListHelp
___
Mailing list: https://launchpad.net/~dhis2-users
Post to : dhis2-users@lists.launchpad.net
Unsubscribe : https://launchpad.net/~dhis2-users
More help   : https://help.launchpad.net/ListHelp


Re: [Dhis2-users] Import of a new event (not from another instance)

2017-10-11 Thread Morten Olav Hansen
Hi there

Sending in event IDs is not required, but its definitely recommended if you
want do repeated imports (good to have a unique id connected to your event
so that you don't end up with duplicates)

We offer a few options to generate UIDs:

1) Using the web-api /api/system/id (you can add limit=X to adjust how many
you need)
2) Install the dhis2 cli (npm -g install dhis2-cli) and then just do "dhis2
uid", or "dhis2 uid -h" to get more help
3) if you are nodejs directly you can also use the dhis2-uid lib for
generating uids (npm --save install dhis2-uid)

https://www.npmjs.com/package/dhis2-cli
https://www.npmjs.com/package/dhis2-uid

-- 
Morten Olav Hansen
Senior Engineer, DHIS 2
University of Oslo
http://www.dhis2.org

On Wed, Oct 11, 2017 at 1:21 PM, Terence Scott <
terence.sc...@rabiesalliance.org> wrote:

> Dear All
>
> We have collected animal vaccination data (including GPS coordinates,
> time, date, species etc.) in a custom developed program and have a CSV
> output for this program. We are looking to try to import the data from the
> custom-built programme into our DHIS2 instance via Event import. I have
> gotten the import to work on Event export files that I have edited with new
> animal data (e.g. by changing the species) and this works, as it simply
> updates the old event (based on the event ID). However, we would like to
> import these data as new events as opposed to simply replacing existing
> events currently on the system.
>
> Therefore, I would like to please find out as to whether it is possible to
> do one of the following:
>
> 1) Do an event import without an Event ID (i.e. register a new event on
> the DHIS2 instance via Event import)
> - I have looked through the documentation but am unable to find out
> whetherthis is possible
> - In the Developer Docs, it seems to mention that import using XML
> does notrequire an Event ID, but I have not managed to
> determine whether I am  misinterpreting this or whether I
> simply do not know how to do it.
>
> 2) Generate our own Event IDs in our custom-built programme that will be
> recognised by the DHIS2 instance.
> - Is there some way by which the Event IDs could be automatically
> generated  outside of the DHIS2 instance (in our programme) so that
> new events can be  imported into the instance?
>
> Please let me know if you need any further clarification. I would really
> appreciate any help that you could provide!
>
> Kind regards,
> Terence
>
>
> Terence Scott
>
> Global Alliance for Rabies Control (GARC)
> Pan-African Rabies Control Network (PARACON) Steering Committee
> terence.sc...@rabiesalliance.org
> https://paracon.rabiesalliance.org
> Skype: tpscott1987
>
>
>
>
> ___
> Mailing list: https://launchpad.net/~dhis2-users
> Post to : dhis2-users@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~dhis2-users
> More help   : https://help.launchpad.net/ListHelp
>
>
___
Mailing list: https://launchpad.net/~dhis2-users
Post to : dhis2-users@lists.launchpad.net
Unsubscribe : https://launchpad.net/~dhis2-users
More help   : https://help.launchpad.net/ListHelp


[Dhis2-users] Import of a new event (not from another instance)

2017-10-11 Thread Terence Scott
Dear All

We have collected animal vaccination data (including GPS coordinates, time,
date, species etc.) in a custom developed program and have a CSV output for
this program. We are looking to try to import the data from the
custom-built programme into our DHIS2 instance via Event import. I have
gotten the import to work on Event export files that I have edited with new
animal data (e.g. by changing the species) and this works, as it simply
updates the old event (based on the event ID). However, we would like to
import these data as new events as opposed to simply replacing existing
events currently on the system.

Therefore, I would like to please find out as to whether it is possible to
do one of the following:

1) Do an event import without an Event ID (i.e. register a new event on the
DHIS2 instance via Event import)
- I have looked through the documentation but am unable to find out
whetherthis is possible
- In the Developer Docs, it seems to mention that import using XML does
notrequire an Event ID, but I have not managed to determine
whether I am  misinterpreting this or whether I simply do
not know how to do it.

2) Generate our own Event IDs in our custom-built programme that will be
recognised by the DHIS2 instance.
- Is there some way by which the Event IDs could be automatically
generated  outside of the DHIS2 instance (in our programme) so that
new events can be  imported into the instance?

Please let me know if you need any further clarification. I would really
appreciate any help that you could provide!

Kind regards,
Terence


Terence Scott

Global Alliance for Rabies Control (GARC)
Pan-African Rabies Control Network (PARACON) Steering Committee
terence.sc...@rabiesalliance.org
https://paracon.rabiesalliance.org
Skype: tpscott1987
___
Mailing list: https://launchpad.net/~dhis2-users
Post to : dhis2-users@lists.launchpad.net
Unsubscribe : https://launchpad.net/~dhis2-users
More help   : https://help.launchpad.net/ListHelp


Re: [Dhis2-users] DHIS2- Data Types of Data elements

2017-10-11 Thread Lars Helge Øverland
Hi Omer,

did you look at the "Positive or Zero integer" data element value type?

regards,

Lars


On Wed, Oct 11, 2017 at 12:08 PM, Omer Butt  wrote:

> Hi,
>
> Can you please tell me the data type that accept 0 as a first value while
> taking values from user in data entry section.  (other than text data
> type). Because  i want to store integer values that may be start with a 0;
>
> e.g 001001343
>
> Thanks
>
>
>
> ___
> Mailing list: https://launchpad.net/~dhis2-users
> Post to : dhis2-users@lists.launchpad.net
> 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
l...@dhis2.org
http://www.dhis2.org 
___
Mailing list: https://launchpad.net/~dhis2-users
Post to : dhis2-users@lists.launchpad.net
Unsubscribe : https://launchpad.net/~dhis2-users
More help   : https://help.launchpad.net/ListHelp


Re: [Dhis2-users] Email notifications

2017-10-11 Thread Lars Helge Øverland
Hi Anna,

okay. Could it be that you have not enabled email notifications? This can
be configured as a system setting, and also be overridden by user specific
settings.

Go Settings app > Messaging and enable email notifications.

Also make sure that your users have not disabled this under Profile > User
settings > email notifications.

regards,

Lars


On Wed, Oct 11, 2017 at 11:57 AM, Anna Mennella 
wrote:

> Hi there,
>
> I have been trying to send notification emails to some users within my
> team by using the message app; however, I have noticed that any message can
> be read only by logging in into DHIS2 and therefore these emails don't
> reach the email inbox.
> I'm a bit surprised about it as I guess that in some cases the purpose of
> sending notifications/reminders from there is to remind the users to upload
> information and therefore to log in into the system.
>
> Any help?
>
> Thanks
> Anna
>
>
>
> ___
> Mailing list: https://launchpad.net/~dhis2-users
> Post to : dhis2-users@lists.launchpad.net
> 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
l...@dhis2.org
http://www.dhis2.org 
___
Mailing list: https://launchpad.net/~dhis2-users
Post to : dhis2-users@lists.launchpad.net
Unsubscribe : https://launchpad.net/~dhis2-users
More help   : https://help.launchpad.net/ListHelp


[Dhis2-users] DHIS2- Data Types of Data elements

2017-10-11 Thread Omer Butt
Hi,

Can you please tell me the data type that accept 0 as a first value while
taking values from user in data entry section.  (other than text data
type). Because  i want to store integer values that may be start with a 0;

e.g 001001343

Thanks
___
Mailing list: https://launchpad.net/~dhis2-users
Post to : dhis2-users@lists.launchpad.net
Unsubscribe : https://launchpad.net/~dhis2-users
More help   : https://help.launchpad.net/ListHelp


[Dhis2-users] Email notifications

2017-10-11 Thread Anna Mennella
Hi there,

I have been trying to send notification emails to some users within my team
by using the message app; however, I have noticed that any message can be
read only by logging in into DHIS2 and therefore these emails don't reach
the email inbox.
I'm a bit surprised about it as I guess that in some cases the purpose of
sending notifications/reminders from there is to remind the users to upload
information and therefore to log in into the system.

Any help?

Thanks
Anna
___
Mailing list: https://launchpad.net/~dhis2-users
Post to : dhis2-users@lists.launchpad.net
Unsubscribe : https://launchpad.net/~dhis2-users
More help   : https://help.launchpad.net/ListHelp


Re: [Dhis2-users] Calendar Issue in DHIS2

2017-10-11 Thread Seleman Ally
Thanks All, 

I am facing the similar problem even for the latest War file which I downloaded 
yesterday. 

Thanks for your collaboration

Regards
Sele
 

On Wednesday, October 11, 2017 7:23 AM, gourav sachdeva 
 wrote:
 

 Hi, 

I did Create an issue on JIRA. Kindly follow the given link.
https://jira.dhis2.org/browse/DHIS2-2357 

Thanks
On Wed, Oct 11, 2017 at 9:02 AM, Hannan Khan  wrote:

Thanks Gourav. 
We just experience a similar Case. In that form we have 3 date field and 2 
appears in place and one is lost; wait I found at the bottom after scrolling 
down.
We are using version 26. Please let me know the Jira issue tracker, so that I 
can followup. 
Regards
Hannan 
On Tue, Oct 10, 2017 at 12:04 PM, gourav sachdeva  
wrote:

Hello Team,
Greetings of the Day,
We are facing the issue in calendar whenever we select the date, the calendar 
doesn't pop up on it's specified location rather it comes in the end of the 
page and the screen also get splits into two parts.
We have also attached the screenshot from the demo version of dhis2 
(https://play.dhis2.org/demo).  
Kindly look into the issue. We hope for the positive response from your side.

Thanks & Regards,HISP India
__ _
Mailing list: https://launchpad.net/~dhis2-u sers
Post to     : dhis2-us...@lists.launchpad.ne t
Unsubscribe : https://launchpad.net/~dhis2-u sers
More help   : https://help.launchpad.net/Lis tHelp





-- 
Muhammad Abdul Hannan KhanTeam LeaderSupport to theNational HMISMIS, 
DirectorGeneral of Health ServiceMinistry of Health and Family Welfare
T +880-2- 58816459, 58816412 ext 118F +88 02 58813 875M+88 01819 239 241M+88 
01534 312 066E hann...@gmail.coms hannan.khan.dhaka
B hannan-tech.blogspot.comL https://bd.linkedin.com/in/ hannankhan 
 






Thanks & Regards,Gourav Sachdeva___
Mailing list: https://launchpad.net/~dhis2-users
Post to    : dhis2-users@lists.launchpad.net
Unsubscribe : https://launchpad.net/~dhis2-users
More help  : https://help.launchpad.net/ListHelp


   

|  | Virus-free. www.avast.com  |

___
Mailing list: https://launchpad.net/~dhis2-users
Post to : dhis2-users@lists.launchpad.net
Unsubscribe : https://launchpad.net/~dhis2-users
More help   : https://help.launchpad.net/ListHelp