IHRIS Ideas List

If you wish to work on any of these projects, you can contact us at our Project Communication page.

Use Cases Wiki

This would be a module for a wiki (whichever seems best) that will allow easier editing of use cases so this work can be shared. It will make it easier for people making customizations to modify use cases for their purposes.

OpenLayers Reporting

Incorporate openLayers into the reporting system: Reports which are tagged with geo-data (e.g. Lat and Long coordinates for a facility) will have numeric and aggregate data for the report plotted on a map.

Charting and Reporting Improvements

There are a few parts to this. We would like to remove the Flash charts and replace it with images. A second step would be to add the option for using Canvas for the charts as well. We'd like to add some additional features to the reporting to allow more complex charts to view the data. There are also some smaller additions like displaying all the limits chosen for a particular report so it's clear what is being displayed.

Self Service

This would be an expansion of the current role/task system that would allow person records in the system to login and have access to certain information about themselves or the people they supervise.

SDMX-HD

This would allow a direct export of reports in SDMX-HD format.

Mobile Updates / Roll-Call

Build an interface that can work on various levels of mobile phones to interface with iHRIS. Perhaps using OpenRosa. The Roll-Call module is to allow supervisors or workers (i.e. community health workers) to log their activity.

Convert Configuration Data (MagicData) to MongoDB (or others?)

Build a faster interface for MagicData to save using MongoDB instead of MySQL to try to improve speed to this information since it is access so frequently

Will still probably need to retain mysql as a write storage mechanism so that magic data form storage remains fast.

Add Memcached for Configuration Data (MagicData)

Adding an additional storage module for MagicData to cache using Memcached as an intermediary between APC and the database to see if this offers any speed improvements. With MongoDB (or something similar) it may not be necessary. done!

Form and Page Editors

Build an administrative interface to allow customization of forms through the application instead of using module configuration files. Building on that, create and interface to define display and edit pages based on the existing forms so more work can be done through the application instead of manually editing XML configuration files. More information: Custom Forms and Custom Pages.

Context Sensitive Help

Set up more help links within the application so users can get direct access to help instead of having to find the relevant section in the manual. Perhaps even rewrite how the manual is used in the application.

Web Services

Build a web services interface so other applications can access and update allowed data without having to export/import at regular intervals.

Write MagicData Objects as C

Rewrite the MagicData PHP classes in C to speed up usage.

Leave Tracking Module

Add a module to iHRIS Manage to track an employees leave. If done in concert with Self Service this could allow employees to request and view leave details directly.

PDF Printing for Certificates or Other Form Data

Build a separate view to all for the printing of certificates for iHRIS Qualify related to licensing. This can be extended into an alternate view of any form or combination of forms for printing or viewing. This could be a part of the Page Editor. Design Document