PLEASE EDIT THIS PAGE TO MAKE IT MORE UP TO DATE WITH WHAT WE ARE TRYING TO ACHIEVE IN THE FALL OF 2005. THE INFORMATION SO FAR PERTAINS ONLY TO THE PROTOTYPE DEVELOPED IN THE SPRING OF 2005

Comparison

Participants:
HISP:Vietnam
The Oslo Team

Progress Reports

Weekly Reports

General Description

This module shall support daily data-entry of patient consultations in wards or clinics. It shall be flexible with regards to what kind of data that are entered and stored.

Furthermore, this module shall also include functionality to support reports and graphical presentations of patient data in the wards or clinics. The first step is to support the standard weight/height graph for babies.

This module introduces additional needs for security as it stores patient-data and not only aggregated data. Good back-up routines are also very important in this module, as this is a daily data-entry system with little or no "backup" on paper.

This module will firstly be developed to support the daily work in wards in Ho Chi Minh City, Vietnam, but is must be flexible enough to cater for more general needs of a daily patient-based data entry module.

Documentation

• File and folder structure
• Document of dhis-wpm-core (see the attached dhis-wpm-core document)
• Document of dhis-wpm-MVC
• Dhis-wpm framework (see the attached WPM framework image file)

Test the application

Instructions on how to set up the application

Environment

The module shall be web-based, and the web-based data-entry functionality shall be re-used in other data-entry modules. However, this module must be tested also as a local module, as it is likely to be used in offices without network access. This means that the module must be able to run satisfactory on NOT-the-state-of-the-art computers with a web server and a servlet container (e.g Jetty that covers both) running.

Compatibility with other DHIS modules

This module will typically be used together with the main (routine & semi-permanent & survey data - all anonymised and aggregated) module of the DHIS (any version). The daily patient data stored in this module must therefore be "mapped" to the routine aggregated data handled in the main module through a flexible aggregation mechanism.

The aggregated data will be temporarily stored in a "routine data" table, and then exported to the standard XML-based export/import format used by the DHIS version 1.4 and 2.0

The DHIS version 1.3.xx is using comma-delimited TEXT files (either ASCII or Unicode) for export/import, but that format will gradually be phased out.

As a first step this mapping sequence can be hard coded. However, in future releases the mapping should be done through a GUI, and be flexible so that this module can be used globally, supporting different working routines for patient registering.

Requirements list

• Web-based module
• Data-entry of all kinds of data
• Generic and user-defined data capture, -users can define additional data
• Patient history required
• One-click export to routine aggregated data
• The mapping from patient to aggregated data must be flexible and user-defined
• Patient history reports
• Graphical presentations of data e.g. height/weight graph
• Secure patient database with restricted access
• User-friendly back-up routines
• Satisfactory performance on older computers(~ 1.0 GHz CPU + 128 Mb RAM)
• Easy install and setup on local computers
• Possible to run locally (no network) with e.g. jetty

Report

WPM-Beta-1-Report

Technology

Javascript
Hibernate
jfreechart
For more information, see the attached Requirements Analysis document.

Further development (Next version)

Now we have just finished some (could be most) of functions in our requierment list. We did a presentation to Knut Staring and Kristian Nordal, they gave us a lot commnents and we do appriciate for that.Here is the list of our further developments

Developer information

• 3 students + 1 instructors at Nong Lam Univiversity, HCMC, Vietnam