Hi Oliver,
(replying on the dev list)
The reporting module is designed to do exactly what you are asking.
Each time you run a report, both the report results (eg. the raw data)
and the rendered output (eg. an html or excel file) are stored on the
filesystem. The most recent of these are also kept in an in-memory
cache for quicker access. Once you have run a report, you should see
the history of previous runs, and if you click on one of these, it
should give you the option of either viewing the previously-saved
results, or running the report again.
If you are not seeing this behavior, can you please open up a ticket
with screenshots and/or any stacktraces you might find in the logs that
demonstrate that this is not working?
Thanks very much,
Mike
On 12/20/2011 01:45 AM, Oliver Mwalo wrote:
Hi Mike,
My name is Oliver, an AMPATH Eldoret programmer. I have been working
on a module to generate reports for the ministry of health, Kenya.
The module is called amrsReports(also in the openMRS svn repository).
The module rides on the reporting module and its dependancies. It can
generate reports. The only concern is that every time a report is
needed in row per patient format, it has to be regenerated and given
the volume of data that we have here, it makes it very slow to get a
report. Is there a way that we can save a generated report so that on
querying it can give an instance of a report generated in the past
instead of regenerating it each time it is viewed?
Thanks
--
/*Oliver Mwalo*/
/*Java Programmer/System Engineer*/
/*USAID/AMPATH - Eldoret, Kenya*/
_________________________________________
To unsubscribe from OpenMRS Developers' mailing list, send an e-mail to
[email protected] with "SIGNOFF openmrs-devel-l" in the body (not
the subject) of your e-mail.
[mailto:[email protected]?body=SIGNOFF%20openmrs-devel-l]
