"paperSize": "A3", //The default paper size is A4. This is the recommended way to perform Reporting/Analytics at scale, so that Bahmni EMR doesn't suffer from any performance load due to adhoc & intensive Reporting queries, and you can use a BI/Reporting tool of your choice to easily create visualisations off this secondary database. For instance, it transforms every Form into its own table, with each form instance as one row, so that creating reports from the form data becomes easy. Bahmni-Mart with Metabase (Reports & Analytics)īahmni-Mart is a separate analytics database created by pulling data from Bahmni database (Spring Batch), and is optimised for Analytics purposes. Since this is one of the very old ways, it is not recommended to introduce to any site implementations.ĥ. In this mechanism, Bahmni gives a way to connect with Jasper Report module and an implementer will have to setup Jasper and design the form and SQL using that. Jasper Reports (Deprecated)įew of the earlier Bahmni implementations uses this feature. This type denotes that the SQL query is executed on BahmniMartįor reference, here are some of the custom reports at one of our implementations. This type denotes that the SQL query is executed on Odoo/OpenERP This type denotes that the SQL query is executed on OpenELIS This type denotes that the SQL query is executed on OpenMRS Custom SQL Reports seek to solve this problem. But an implementer has to understand the complete data model of the data source and this can be difficult and cumbersome. Custom SQLīahmni offers Custom SQL reports where an implementer can specify a SQL to extract the data from the system. There is minimal configuration available for these reports. These reports can be used to get specific or predefined information from Bahmni. Generic reports provides options to include related fields and to apply various filters. Generic reports allow an implementer to extract data from the system for each entity, hence Bahmni has a report for each. To solve this, Bahmni has introduced generic reports for various entities in OpenMRS, for example: Observations, Visits and Programs etc. This makes life difficult for the community. In response to customer requests, developers have to repeatedly create canned reports and duplicate the SQL from the similar report, thus increasing the maintenance. An implementer needs to know the OpenMRS data model and Custom SQL to extract the data for custom reports. Generic ReportsĬanned and Custom Reports have their limitations. Custom EXCEL (Excel with pre-defined macro).Standard Reports are useful to management level peopleĬustom Reports can extract data from the backend database to analyse various facts for different stakeholders.īahmni report module supports various output format.Reports can be used in multiple ways in Bahmni The configuration file is located at openmrs/apps/reports directory of the config module. ![]() ![]() An implementer has to configure the required reports properly so that the Reports app will show all the configured ones. The user can launch any of the reports sorted by Start and End date and output format.Įvery Bahmni implementation has its own config module. A list of configured reports appears on the Report app screen. Generally, the Admin user will have the privilege to access reports app. One can also leverage work being done by the OpenMRS community for Reporting/Analytics (see sidebar on this page for OpenMRS links).īahmni Reports app or module can be accessed from the Home dashboard. Reporting/Analytics on Bahmni can be achieved with a variety of ways.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |