However I would like to use the project to show best practices for setting up and organizing reporting in a custom module. Is this https://github.com/mseaton/openmrs-module-reportingdemo the recommended way to setup reporting in a module:
How are reports setup and configured
How to setup and use definition libraries
Renderers CSV, Excel
Row Per Patient and Indicator Report
Calculations - when to use these over data set definitions
How do I build re-usable reports? In our case (UgandaEMR) we have two different age disegregations that need to be applied
Is the legacy UI reporting setup the way into the future? How can I expose the definitions in a consistent manner
More will come along … I have colleagues who are building a brand new reporting functionality hence any answers will form part of the experiment and outcome documentation.
@ssmusoke, I do think that module provides a reasonable set of best practices, as they currently exist. It demonstrates how to add custom definitions, how to add your own libraries, how to set up reports automatically.
Longer term, I personally would like to see us shift our focus to enabling more to be defined outside of java code, and in more configuration files. We have taken some tentative steps in this direction but it is by no means complete.
Nothing that exists in the legacy UI can really be considered the way into the future. What aspects are you referring to specifically?
@darius did the initial implementation of config-file based definition libraries. Have a look at this ticket for some context. Clearly we need to improve reporting documentation.
No ready-made tool for this yet. I’d love to have this in the refapp. The closest thing to being able to do this with definition libraries for Row Per Patient reports is in the Ad Hoc Analysis tool that comes with the reportingui module. Again, @darius did most of the initial work on this.
Also no ready-made tool for this yet. I’d love to have this as well.