Wiki Spaces


Get Help from Others

Q&A: Ask OpenMRS
Discussion: OpenMRS Talk
Real-Time: IRC Chat | Slack


Page tree
Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »

Intuitive User interfaces for Report Designer

Primary mentor

Mike Seaton

Backup mentor


Assigned to



The OpenMRS Reporting Module provides a powerful and flexible reporting framework for OpenMRS.  One element of this flexibility is that a single report may be output into a variety of different formats by configuring one or more Report Renderers.  Each of these types of Report Renderers has particular ways in which it can be configured - a simple CSV renderer, for example, may be configured with information as to whether the elements should be quoted, or whether a delimiter other than a comma should be used.  A renderer that delegates to a report engine like BIRT on the other hand, may require complex and detailed XML design files that control the exact layout and formatting of a report rendered to PDF.  Despite these differences, currently there is a single, generic user interface presented to users for configuring any renderer as a Report Design, which directly mirrors the object and data model.  The end user must either know how to configure a particular report renderer by looking at the code, or by looking at documentation on the wiki, which is frequently incomplete or outdated.  The objective of this project is to improve this, but adding custom pages for creating or editing each currently support Report Renderer, and by doing this in such a way that it is easy to create and plug in custom pages for new report renderer implementation that are created, either directly in the reporting module, or in dependent modules.

Project Champions



Mike can provide specific tickets here.

Extra Credit


  • No labels