dhis2-users team mailing list archive

[Marta Vila <martavila@xxxxxxxxx>]

Thanks Ola,

they want to keep the patient data, so your second option would be best.
I understand, then, that every new event will create a new instance of the
program.

Could you please confirm it is ok not to see the options *Tracking->Visit
Schedule* &* Tracking-> Program Tracking* that appear in the
documentation?? Have they been removed?

thanks again.

Marta

On 15 October 2012 10:54, Ola Hodne Titlestad <olati@xxxxxxxxxx> wrote:

> Hi,
>
> So this is a disease surveillance/notification system? If the goal is to
> track outbreaks etc. and to collect details about each case, BUT not really
> to keep a history of all events for each patient, then I would suggest
> using single event without registration. This will be the easiest way to
> collect and import data about these events and to generate statistics about
> these. You can still include information about the patient such as name,
> relatives, location etc. as data elements, but without involving the
> patient object in DHIS 2 and skipping the whole registration process.
>
> If keeping track of a patients history of multiple similar events (same
> data collection form) then you need to have registration. You can have a
> program with one repeatable stage and schedule and re-schedule new events
> at any time, and there is no need to schedule a new one immediately after
> data entry of the previous event.
>
> Ola
> ---------
>
>
>
> ----------------------------------
> Ola Hodne Titlestad (Mr)
> HISP
> Department of Informatics
> University of Oslo
>
> Mobile: +47 48069736
> Home address: Eftasåsen 68, 0687 Oslo, Norway. Googlemaps link<https://maps.google.com/maps?q=Eftas%C3%A5sen+68,+0687+Oslo,+Norge&hl=en&ie=UTF8&sll=59.893855,10.785116&sspn=0.222842,0.585709&oq=eftas%C3%A5sen+68,+0687+Oslo,+&t=h&hnear=Eftas%C3%A5sen+68,+%C3%98stensj%C3%B8,+0687+Oslo,+Norway&z=16>
>
>
> On 15 October 2012 10:43, Marta Vila <martavila@xxxxxxxxx> wrote:
>
>> Hi Ola,
>>
>> it is an event notification system in which the event information is
>> gathered in a single stage and a patient can notify more than one event.
>>
>> thanks.
>>
>> Marta
>>
>>
>> On 15 October 2012 10:33, Ola Hodne Titlestad <olati@xxxxxxxxxx> wrote:
>>
>>> HI Marta,
>>>
>>> Can you tell us briefly about your use case (what kind of data,
>>> programs, "encounters")?
>>> Then it will be easier to explain how to set up the programs/stages etc.
>>>
>>> Ola
>>> -----
>>>
>>> ----------------------------------
>>> Ola Hodne Titlestad (Mr)
>>> HISP
>>> Department of Informatics
>>> University of Oslo
>>>
>>> Mobile: +47 48069736
>>> Home address: Eftasåsen 68, 0687 Oslo, Norway. Googlemaps link<https://maps.google.com/maps?q=Eftas%C3%A5sen+68,+0687+Oslo,+Norge&hl=en&ie=UTF8&sll=59.893855,10.785116&sspn=0.222842,0.585709&oq=eftas%C3%A5sen+68,+0687+Oslo,+&t=h&hnear=Eftas%C3%A5sen+68,+%C3%98stensj%C3%B8,+0687+Oslo,+Norway&z=16>
>>>
>>>
>>> On 15 October 2012 10:21, Marta Vila <martavila@xxxxxxxxx> wrote:
>>>
>>>> Dear all,
>>>>
>>>> I´m importing some patient legacy data for Colombia pilot project. To
>>>> do that, I´ve trying to understang how the patient module works in the db
>>>> and I have some doubts on the use of Single Event with registration program
>>>> with repeatable stage.
>>>>
>>>> I create the program and introduce data for one patient. Complete the
>>>> data entry form ... and it appears a pop-up to schedule the next
>>>> encounter... then:
>>>>
>>>> 1) Is it possible not to schedule the next encounter there, but when it
>>>> happens? (Like a spontaneous clinic visit)
>>>> 2) Is it posible to re-schedule an encounter?
>>>> 3) How can I "retrieve" an encounter to introduce data on it? I don´t
>>>> find the way, even if i´m on the date the ecounter was scheduled for.
>>>>
>>>> - I don´t see the options Tracking->Visit Schedule & Tracking-> Program
>>>> Tracking that I´ve read in the documentation, in case it has smth to do
>>>> with the limitations I found.
>>>> (Version 2.9 Build Revision 7897)  I´m using admin acccount.
>>>>
>>>> Following this functionality, The way I can do it now is creating a new
>>>> instance of the program everytime a patient comes (even if he/she has come
>>>> before) So in the end, for a single patient, I have as many instances of
>>>> the program as visits he/she made, with one encounter per instance with
>>>> data... and one preogrammed but never accesed..
>>>>
>>>> Any help on understanding this will be much appreciated.
>>>> thanks!
>>>>
>>>> Marta
>>>>
>>>> _______________________________________________
>>>> Mailing list: https://launchpad.net/~dhis2-users
>>>> Post to     : dhis2-users@xxxxxxxxxxxxxxxxxxx
>>>> Unsubscribe : https://launchpad.net/~dhis2-users
>>>> More help   : https://help.launchpad.net/ListHelp
>>>>
>>>>
>>>
>>
>