dhis2-documenters team mailing list archive

[Jens Johan Kaasbøll <jensj@xxxxxxxxxx>]

Obviously no success. Use the web links below instead

On Fri, 10 Jun 2011 14:38:23 +0200, Jens Johan Kaasbøll 
<jensj@xxxxxxxxxx> wrote:
> Seems like the attachments did not come through, even if they are in
> my Sent box. Strange. Try again.

During discussions on user learning in Tanzania, two issues came up. 
First, users struggle with finding out how to generate reports for their 
health management tasks. Second, many are confused as to aspects of the 
overall structure of the HMIS, including both health information and 
DHIS.
Problems of coupling the DHIS functionality to health tasks may be 
eased through changes in the user interface and documentation. Pushing 
the Reports choice under Services takes you to a page void of health 
tasks. For instance, the explanation of Chart is
“View and add charts. Charts are based on indicators and either 
organisation units or periods.”
If we rather start with health tasks, we could for example write:
“To get an overview of the facilities in your area for a health 
service, choose Charts.”
Likewise, manuals and slides could also be designed based on health 
tasks, see attached drafts. These drafts also includes examples of how 
the structures, components, concepts and principles of DHIS and HMIS 
could be presented. The drafts are for slides
http://www.uio.no/studier/emner/matnat/ifi/INF3280/v11/ChartReportTestSlides.ppt

and for a document which is closer to a textbook than a manual.
http://www.uio.no/studier/emner/matnat/ifi/INF3280/v11/ChartReportTestTextbook.doc
http://www.uio.no/studier/emner/matnat/ifi/INF3280/v11/ChartReportTestTextbookAnnotated.pdf

Shorter versions could also appear as instructions on the right part of 
the screen as context-sensitive help when running the DHIS, possibly as 
videos.
Are there any opinions on these matters?
Is it worthwhile trying to design documentaiton in this way?
Managing documentation of the same thing for different media begs for a 
more systematic way of storing and generating it than the Office files I 
produced. This is another, but related topic for discussion.
Regards,
Jens Kaasbøll