dhis2-documenters team mailing list archive

[Jason Pickering <jason.p.pickering@xxxxxxxxx>]

Hi Jens,

I think you make some good points regarding the need for a a better workflow
oriented UI. However this is a much bigger discussion I think which goes
beyond the scope of the documentation.

In terms of documentation, I think the a good way forward would be local
additions to the user manual (for instance, a Tanzania version) which would
provide users examples of how to accomplish specific tasks in their
workflow, using the functionality oriented UI of DHIS. This will likely be
highly specific to each country and would need to be adapted for each
implementation.

I believe the current documentation is modular enough to probably accomplish
much of this this with a separate scaffolding document which could rearrange
the documentation text, but in the form of specific workflow elements or use
cases which could describe how to accomplish specific tasks, rather than
describing the functionality in a general way.

Would be good to see the attachments, whatever they might be!

Regards,
Jason


2011/6/10 Jens Johan Kaasbøll <jensj@xxxxxxxxxx>

> Hi
> 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 and for a document which is closer to a
> textbook than a manual. 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
>
> _______________________________________________
> Mailing list: https://launchpad.net/~dhis2-documenters
> Post to     : dhis2-documenters@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~dhis2-documenters
> More help   : https://help.launchpad.net/ListHelp
>
>