2010/3/4 Viet Nguyen
>
>
> Hi Abyot,
>
>
> Any change you are making is fine with me as long as it makes sense to
> broader use cases. The ID for example is better if we could keep it as it
> was before. I remember the ID was made of organization unit code or short
> name plus a 5 (or 6??) digit
Hi Abyot,
Any change you are making is fine with me as long as it makes sense to
broader use cases. The ID for example is better if we could keep it as it
was before. I remember the ID was made of organization unit code or short
name plus a 5 (or 6??) digit number. It was made like this on the ass
2010/3/4 Bob Jolliffe
> 2010/3/4 Lars Helge Øverland :
> >
> >
> > 2010/3/4 Bob Jolliffe
> >>
> >> I agree depending on the uniqueness of names is not a good idea. I
> >> saw John said that facilities in India do have codes - the 16 digit
> >> ones which are built hierarchicly (is that a word?)
2010/3/4 Lars Helge Øverland :
>
>
> 2010/3/4 Bob Jolliffe
>>
>> I agree depending on the uniqueness of names is not a good idea. I
>> saw John said that facilities in India do have codes - the 16 digit
>> ones which are built hierarchicly (is that a word?).
>
> OK I wasn't aware of this code.. C
2010/3/4 Bob Jolliffe
> I agree depending on the uniqueness of names is not a good idea. I
> saw John said that facilities in India do have codes - the 16 digit
> ones which are built hierarchicly (is that a word?).
>
OK I wasn't aware of this code.. Certainly if we could generate a string
base
I agree depending on the uniqueness of names is not a good idea. I
saw John said that facilities in India do have codes - the 16 digit
ones which are built hierarchicly (is that a word?).
Is it possible to for a patient id to continue this hierarchy so that
a patient might have say a 6-8 digit lo
I've said my take on the solution before... But here again:
We generate a list of 6-digit Base30 ids(2 million or so ... ) (..or
8-digit). randomly allocate and make them used. During sync when the ids
collide we use the internal uuid to create separate rows and internally we
always use a combinat
Been chatting a bit with John and he expressed concern about the
orgunit-randomnumber apprach. In India there are multiple installations and
one cannot know for sure that an orgunit name will be unique. How do we deal
with this?
Using a globally unique identifier could be a solution, but the stand
Hi Thanh
On 3 March 2010 19:59, Ngoc Thanh Nguyen wrote:
>
>
> On Thu, Mar 4, 2010 at 12:11 AM, Bob Jolliffe wrote:
>>
>> Hi John
>>
>> On 3 March 2010 15:20, John lewis wrote:
>> > Hi bob,
>> > the system generated ID is to one way to identify the case or person.
>> > using
>> > orgunit you me
On Thu, Mar 4, 2010 at 12:11 AM, Bob Jolliffe wrote:
> Hi John
>
> On 3 March 2010 15:20, John lewis wrote:
> > Hi bob,
> > the system generated ID is to one way to identify the case or person.
> using
> > orgunit you mean the code for that organization unit. In india they have
> > generated a 1
Hi Viet,
Thanks for the update. But a little afraid that you are making it very much
hard coded to the requirements of India.
Any change you are making is fine with me as long as it makes sense to
broader use cases. The ID for example is better if we could keep it as it
was before. I remember the
On 3 March 2010 17:23, John lewis wrote:
> Ok bob, point taken. when you say facility+ unique string what do you mean.
> facility code or name of the facility and unique string is random number
> right?
yup. and facility code is infinitely better than facility name.
Though its obviously useful f
Ok bob, point taken. when you say facility+ unique string what do you mean.
facility code or name of the facility and unique string is random number
right?
On Wed, Mar 3, 2010 at 6:11 PM, Bob Jolliffe wrote:
> Hi John
>
> On 3 March 2010 15:20, John lewis wrote:
> > Hi bob,
> > the system gener
Hi John
On 3 March 2010 15:20, John lewis wrote:
> Hi bob,
> the system generated ID is to one way to identify the case or person. using
> orgunit you mean the code for that organization unit. In india they have
> generated a 16 digit ID based on Country, Province,District,Sub-district and
> faci
Hi bob,
the system generated ID is to one way to identify the case or person. using
orgunit you mean the code for that organization unit. In india they have
generated a 16 digit ID based on Country, Province,District,Sub-district and
facility. but the problem with this is what happen if new distric
Hi
On 3 March 2010 12:20, Viet Nguyen wrote:
>
> Hi,
>
> Just a quick update about Patient registration form functionality :
>
> * Check duplicate :
>
> This function allow user to check for existing patient base on : name ,
> birthdate, age, gender
>
> If there is duplicate patient, a pop up wil
Hi,
Just a quick update about Patient registration form functionality :
** Check duplicate : *
This function allow user to check for existing patient base on : name ,
birthdate, age, gender
If there is duplicate patient, a pop up will be showed, with the list of all
the duplicated patients.
>F
Hi there. Well, nothing has been done yet, but we have been discussing
the need for field-level validation with the use of regular
expressions. I am not sure this impacts the blue print so much
actually, however it would seem there would possibly need to be
another field added to the regex to recor
On Mon, Mar 1, 2010 at 4:02 PM, Bob Jolliffe wrote:
> Hi Viet
>
> On 1 March 2010 08:22, Viet Nguyen wrote:
>
>> Hi,
>>
>>
>> On Mon, Mar 1, 2010 at 11:13 AM, Chau Thu Tran <
>> tran.hispviet...@gmail.com> wrote:
>>
>>> Hi Abyot and Others,
>>>
>>> I tested the* UpdatePatientAttributeValues *fun
Hi Viet
On 1 March 2010 08:22, Viet Nguyen wrote:
> Hi,
>
>
> On Mon, Mar 1, 2010 at 11:13 AM, Chau Thu Tran > wrote:
>
>> Hi Abyot and Others,
>>
>> I tested the* UpdatePatientAttributeValues *function. It doesn't show
>> anything. I think if we have *EditPatient*, we don't need *
>> PatientAt
Hi all,
Sorry. I sorted them. It's Ok.
Châu Thu Trân
HISP Viet Nam
Email: tran.hispviet...@gmail.com
Cell phone: +84 97 324 1542
On Mon, Mar 1, 2010 at 3:38 PM, Abyot Gizaw wrote:
>
>
> On Mon, Mar 1, 2010 at 9:22 AM, Viet Nguy
On Mon, Mar 1, 2010 at 9:22 AM, Viet Nguyen wrote:
> Hi,
>
>
> On Mon, Mar 1, 2010 at 11:13 AM, Chau Thu Tran > wrote:
>
>> Hi Abyot and Others,
>>
>> I tested the* UpdatePatientAttributeValues *function. It doesn't show
>> anything. I think if we have *EditPatient*, we don't need *
>> PatientAt
Hi,
On Mon, Mar 1, 2010 at 11:13 AM, Chau Thu Tran
wrote:
> Hi Abyot and Others,
>
> I tested the* UpdatePatientAttributeValues *function. It doesn't show
> anything. I think if we have *EditPatient*, we don't need *
> PatientAttributeValues*.
>
Yeah, this is a bug, we changed Attribute object
Hi Abyot and Others,
I tested the* UpdatePatientAttributeValues *function. It doesn't show
anything. I think if we have *EditPatient*, we don't need *
PatientAttributeValues*.
*About enter name for Patient and Patient attribute*
- The validate function ( *required_group {validate...*) does
I think the OpenMRS project has considered this question extensively (and
many others that are relevant for a patient system).
Knut
On Mon, Feb 1, 2010 at 7:31 AM, Jason Pickering wrote:
> > So we are thinking of an algorithm to generate the id for the whole
> country,
> > but not depend on the
> So we are thinking of an algorithm to generate the id for the whole country,
> but not depend on the organisation unit. It should only depend on patient
> information and the time of creating...
A UUID perhaps? Seems to be the only way to guarantee you will end up
with a unique ID, especially in
Hi,
The reason of not put the organisation unit in the System generated Patient
Id is :
An organisation unit can be changed the name. Or it can be splited into two
smaller organisation unit ( This is happening in India ) . Or even it can be
merge with another organisationUnit to make a bigger one
Hi,
In Vietnam, code of patient likes this:
- Set of characters dependent on the organisation unit
- Set of digits, include date and number of patients in the day.
Châu Thu Trân
HISP Viet Nam
Email: tran.hispviet...@gmail.com
Cell phone: +84 97 324 1542
==
Hi,
Here are things that I've changed for patient - branch
- Add Date of Enrollment Description , Date of Incident Description for
Program. This is because those description is differ from each program,
when user enroll to a program, we need to show them the descriptions.
- Move b
On Thu, Jan 28, 2010 at 8:45 AM, Chau Thu Tran
wrote:
> Hi Abyot,
>
> I modify the source.
>
> Please find enclosed the attached file to see the patch.diff file.
>
> Best regards,
>
>
Nice work Tran...
___
Mailing list: https://launchpad.net/~dhis2-devs
t; Email: tran.hispviet...@gmail.com
>>> Cell phone: +84 97 324 1542
>>>
>>>
>>>
>>> On Thu, Jan 21, 2010 at 8:58 PM, Cong Duong Dinh <
>>> duong_dinhc...@hotmail.com> wrote:
>>>
>>>>
to put on one
>>>>> of three places as below, but i am not sure.
>>>>> 1. Create groups property for patient and request users add it in new
>>>>> patient GUI
>>>>> 2. Create other function named Add Groups for each in list of patients.
>>>>> 3. Create combox to load al
o choose each group to enter attribute.
>>>>
>>>> What is your suggestion?
>>>>
>>>> ================
>>>> Châu Thu Trân
>>>> HISP Viet Nam
>>>> Email: tran.hispviet...@gmail.com
>>>> Cell phone: +84 97 324 1542
>>>> =
Dear Abyota*,*
I'm trying to follow your working on Patient module so that I've got some
questions wanna ask you like this:
*
Creating attribute group*
>
> For step 1 you can follow the approach we have in DataElements and
> DataElementGroups. At the same I would suggest for a restriction of putt
t;http://my.wisestamp.com/link?u=6zk6hnnyzjswmm3g&site=www.wisestamp.com/email-install>
>>
>>
>> Duong Dinh Cong CUF/UTC 520 Ng Tri Phuong QX HCM-City Vietnam Tel 84 8
>> 8631383 Fax 84 8 650025
>>
>>
>>
>> --
>> Date: Thu, 21 Jan 2010 17:41
il-install>
>
>
> Duong Dinh Cong CUF/UTC 520 Ng Tri Phuong QX HCM-City Vietnam Tel 84 8
> 8631383 Fax 84 8 650025
>
>
>
> --------------
> Date: Thu, 21 Jan 2010 17:41:39 +0700
> Subject: Re: [Dhis2-devs] Greetings + new DHIS patient module
>
2010/1/21 Chau Thu Tran
> Hi Abyot,
>
> The Mother Form system has two objects, mother and child. There are somes
> attributes belonging to mother that does not belong to child and vice versa.
> For example, the atributes of mother are housenumber, street and pre-prefnacy
> (***). And the attribu
Hi Tran,
Ok, now I got it :)
You want to see only those attributes that you intened to fill - for example
you don't want to see attributes like apgarXXX when dealing with Mother; and
also things related with pre-pregnancy when dealing with babies. Is that
your quesion?
If so then we can solve th
Dear Tran, Thuy, Kim and others,
Great that you have started looking into the patient module of DHIS2. The
advantage with this module is that it is part of DHIS2 - no installation of
other system and also easy sharing of dataelements and orgunits defined
under DHIS2.
Below is a little clarificati
39 matches
Mail list logo
