dhis2-devs-core team mailing list archive

[Ola Hodne Titlestad <olati@xxxxxxxxxx>]

I support this change. We just need to be sure old databases get upgraded
without too many issues.

I think we need a new predefined attribute type called phone number. The we
will know where to look for phone numbers.

When it comes to encryption, do we then encrypt all attribute values? Will
be hard to know which of the dynamic attributes that are privacy-related,
e.g. name, address etc.

Or do we include another property on the attribute to define whether it
should be encrypted or not?

While at it, should we combine dynamic attributes and identifiers as one
object, or we continue to keep them separate?  The identifier is strictly
speaking just a special attribute type or? What are the pros and cons here?
>From the users' point of view this would certainly be a simplification.

Ola
------
On 18 Nov 2013 08:03, "Tran Chau" <tran.hispvietnam@xxxxxxxxx> wrote:

> Hi Lars,
>
> Before removing all fixed attributes of persons, we should create a new
> attribute type called for phone number, we need it for sending sms message.
> How do you think about it ?
>
> Besides, we need to find out a way to display dynamic attribute params
> when defining template messages in Add program...
>
> Best regards,
> ------------------------------------------------
> Châu Thu Trân
> HISP Viet Nam
> Email: tran.hispvietnam@xxxxxxxxx
>
>
> On Mon, Nov 18, 2013 at 5:18 AM, Lars Helge Øverland <larshelge@xxxxxxxxx>wrote:
>
>> Hi,
>>
>> I suggest we remove all fixed attributes from the Patient object
>> (representing "person") and rely on "dynamic" attributes only.
>>
>> The reason is first that we have lots of scenarios where people want to
>> capture persons without attributes like name, gender, birth date, for
>> practical or confidential reasons. Currently we create custom forms where
>> we hide these fixed attributes for person registration, but this does not
>> work well on devices which does not support HTML and is a rather back-ward
>> approach anyway.
>>
>> Second, by having only dynamic attributes we greatly extend the usability
>> of tracker into new domains. One example is logistics tracking and
>> management, where a commodity could be registered as a "person", then
>> tracked through a multi-stage program with stages for "sent from national
>> store", "received at district store", "received at service point",
>> "administered to client", or similar. This model could work as a basis for
>> a more or less "fully-fledged" logistics system.
>>
>> Any objects or concerns? If not I suggest we start making this change
>> right away since 2.14 is nearing and it is a rather intrusive change.
>>
>> Lars
>>
>>
>> --
>> Mailing list: https://launchpad.net/~dhis2-devs-core
>> Post to     : dhis2-devs-core@xxxxxxxxxxxxxxxxxxx
>> Unsubscribe : https://launchpad.net/~dhis2-devs-core
>> More help   : https://help.launchpad.net/ListHelp
>>
>>
>
> --
> Mailing list: https://launchpad.net/~dhis2-devs-core
> Post to     : dhis2-devs-core@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~dhis2-devs-core
> More help   : https://help.launchpad.net/ListHelp
>
>