dhis2-devs team mailing list archive

[Ola Hodne Titlestad <olati@xxxxxxxxxx>]

Hi,

Thanks to Abyot and Thuy for sharing this interesting discussion on the
list.

As Thuy pointed out there is a need for an admin or design manual (or
implementer's guide if you like) which explains how to customise and set up
this module to a production system.

I know that there are now quite a few people that have experience with
setting up the patient/community/nbits module (we have so many names for
it!) and if you can join forces I think we can come up with such a manual
relatively quickly. A lot of people are asking about this module and
requesting help to customise it.

We have tried to gather some bits and pieces from the mailing list about the
module here, which together with the user manual is a good start when
preparing the admin manual:
http://www.hisp.uio.no/projects/dhiscommunity/documentation.html

I hope that people like John L., Bharath, Tran, Abyot, Zeferino, who all
know this module can contribute to make it more accessible to others.
Abyot, would you be willing to coordinate such a manual writing effort?

Thanks,

----------------------------------
Ola Hodne Titlestad (Mr)
HISP
Department of Informatics
University of Oslo

Mobile: +47 48069736
Home address: Vetlandsvn. 95B, 0685 Oslo, Norway. Googlemaps
link<http://maps.google.com/maps?f=q&source=s_q&hl=en&geocode=&q=Vetlandsvn.+95B,+0685+Oslo,+Norway>


On 2 November 2010 11:08, Abyot Gizaw <abyota@xxxxxxxxx> wrote:

> Hi Thuy,
>
> Below are my answers on the questions you asked. Viet and Bharath can also
> explain you more.
>
> On Mon, Nov 1, 2010 at 8:06 AM, Thuy Nguyen <thuy.hispvietnam@xxxxxxxxx>wrote:
>
>> Hi Abyot,
>> I read the document you sent (
>> http://www.hisp.uio.no/projects/dhiscommunity/NBITS%20Operational%20Manual.doc).
>> That document is very useful for me to have some pictures about the module.
>> I forward that to other Sri Lankan students and one of them decided to
>> select DHIS for her project at Mother And Child Health Care field. The
>> project document was approved last week, and the board of study ask us to
>> use DHIS for it.
>>
>
> That is good. Hope you guys will come-up with something good that can go
> back to the module.
>
>
>> But seem that document is more about user manual when the program already
>> developed, it didn't explain how to use the module to develop.
>>
> So there are some confuse in the Beneficiaries and Program module I have
>> met. When you get time please explain to me.
>>
>> 1. In Beneficiary Attribute. When create new attribute, there is a thing
>> called Inheritable. Could you explain its meaning? and when we set yes/no
>>
>
> That is to ask you whether a particular attribute is inheritable (among
> relatives) or not. For example you can register a mother with all the
> necessary attributes (housenumber, phone number, village, ..........) then
> when the mother gives birth to a baby, you need to have all the necessary
> details about the baby so that you provide for example immunization service.
> And obviously, a baby will not have phone number, address,..... and the like
> but can inherit all these from the mother - this is just to give you an idea
> where and how to use the inheritable feature of attributes. For the baby to
> inherit attributes, first you need to define relationships (for example
> parent/child).
>
> In general, there will be lots of use-cases for inheritable attributes in
> different relationships.
>
>
>
>> 2. In Beneficiary Identifier Type function, there
>>
>>    -  I don't understand the meaning of State format. When I created a
>>    Beneficiary Identifier Type, and check that State format, then I couldn't
>>    add new Beneficiary because it generated this message *"Please set
>>    valid 9 digit organisation unit code to add new Beneficiary"*. When
>>    the State format is unchecked, then I can add new beneficiary. Where the
>>    State format is set?
>>    - The second one is the Related. In which case this Related is Yes or
>>    No?
>>
>> I am not sure of this? This is something very specific from India I guess.
>
> The idea is you can define any identifier type, and then assign identifiers
> based on defined types for beneficiaries.
>
>
>
>> 3. In the Program
>>
>>    - In each program there is Validation Data Element Associations
>>    function. I couldn't know how to work on this. I tried to create 2 data
>>    elements with Domain type is Patient. But none of them show in this list.
>>
>>
> We have programs and programstages. And the idea is in the course of a
> program we are going to meet beneficiaries and provide a service following
> specific programstages and the type of dataelements defined in the stage.
> While collecting data during each programstage, we might want to have some
> sort of validation. I can't think of specific example, may be those from the
> domain can help. But in the broader sense, for example the value you are
> entering for a dataelement of a specific program stage is going to be
> checked against some sort of criteria. For example in the normal dataentry,
> you can define min/max values and next time when you try to store some
> value, the value you are entering is going to be checked against the min/max
> validation criteria. The program stage validation dataelement association
> similar to this..... but then it is kind of linked with the other stages of
> the program........ I don't know may be that is also some sort of validation
> rule.
>
>>
>>    -
>>
>> 4. Benificiary Aggregation Query Builder function : I'm very confuse about
>> this function. I don't understand what it is used for. I select data element
>> group, program state, case properties, left expression, right expression,
>> then click Test button, it show a expression in the Expression text area. I
>> click Save button but don't know where it is saved. And The button Generate
>> doesn't show anything.
>>
>
>
> But the idea is in the community-module, we are going to record individual
> data using Beneficiary and Program. But in DHIS we want to do reporting,
> graphs, charts and maps using aggregate figures. For this to happen, we need
> to aggregate individual records (from the community module) and feed
> aggregate figures to DHIS2 so that we can do further reporting and the like
>
> For example in DHIS2 you might have a dataelement called "ANC 1st Visit"
> and you can put 20 for the month of Nov 2010 to imply 20 individuals have
> been visited for their 1st stage of ANC in the month of Nov. This figure can
> be generate automatically by the community system - but for this to happen
> you need to query through the beneficiary record and count the number of
> pregnant women who are enrolled in mother care program and have completed
> their 1st ANC in Nov.
>
>
> {Get all individuals enrolled in *mother care program* and
> completed *ANC 1st Stage*and                                               =       {ANC 1st
> visit}                         =  20
> only the *month of Nov 2010*}                                                        from the dhis2 side
> from the community side
>
> If you have such a system in place, then you can be relieved from entering
> the figure 20 manually. The system will automatically generate the aggregate
> figure and assign a value of 20 for "ANC 1st visit". But for this to happen
> you need to build the expression.
>
> In other words, you are going to have the source and destination. The
> source is the community, and the destination is the dhis2. If you are
> thinking a more generic feature then the expression will be quite complex
> involving
>
>             {left side expression} *operator* {right side expression}
>
> You define such an expression of your choice under maintenance and run the
> expression from the services side.... then it will populate the dataentry
> screen.
>
>
> Hope this answers some of your questions.
>
> Abyot.
>
>
>>
>> Those are confusions I have until now. I wonder if there is any document
>> which explain detail about this module. I am looking for helping from you or
>> any one used to work on this module.
>>
>> Thank you very much.
>>
>> --
>> Thuy
>>
>> _______________________________________________
>> Mailing list: https://launchpad.net/~dhis2-devs<https://launchpad.net/%7Edhis2-devs>
>> Post to     : dhis2-devs@xxxxxxxxxxxxxxxxxxx
>> Unsubscribe : https://launchpad.net/~dhis2-devs<https://launchpad.net/%7Edhis2-devs>
>> More help   : https://help.launchpad.net/ListHelp
>>
>>
>
> _______________________________________________
> Mailing list: https://launchpad.net/~dhis2-devs
> Post to     : dhis2-devs@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~dhis2-devs
> More help   : https://help.launchpad.net/ListHelp
>
>