(these don't include the reports from OpenERP and OpenELIS)
Remaining canned reports
(used in JSS) Number of Patient Registrations (Number of registrations by age group, gender, address). https://github.com/Bhamni/possible-config/blob/master/openmrs/reports/number_of_clients.sql
Number (used in JSS) Number of Patient Visits (Number of visits by age group, gender, address)
Developed canned reports
...
https://github.com/Bhamni/possible-config/blob/master/openmrs/reports/hmis/childhood_illness_lessthan_2months.sql
https://github.com/Bhamni/possible-config/blob/master/openmrs/reports/hmis/childhood_illness_greaterthan_2months.sql
childhood_illness_death.sql
Registration
- Patient Registration Report (granularity=patient)
- Patient Visit Report
- Program Enrolment
Potential Canned Reports
In Patient
- Admission/Discharge/Transfer report
- Bed Occupancy
Clinical
- Diagnosis (granularity=patient)
- Observation (granularity=visit)
- Disposition (granularity=visit)
- Lab Result (granularity=visit)
Dimensions
when granularity=patient then age, gender
when granularity=visit then dimensions-from-patient-granularity, visit type, visit attribute
Notes
- Age groups table should be provided by Bahmni. The implementers can fill the information in it. The canned reports can depend on this table.
- As we add more tables we would require user interface to manage the data in them. Is grails the best tool for it?
- Disposition concept should be categorized between in-patient, out-patient and common. For an in-patient only in-patient dispositions should be shown. We need a database view for disposition.
- Disposition seems to be really important for reporting. Lot more than for communicating about the patient status during his/her visit. Should we allow multiple dispositions in an encounter? Or should our disposition tab support visit attributes too.
- We should perhaps standardise in-patient and out-patient visit types via visit attributes.
- each query can run in individual or aggregation mode