Hi James, You can do this with a logic indicator. (I forget the exact terminology offhand, so this might not be exactly right.)
You can set up an indicator with: * cohort definition = all patients with a clinic visit * logic query = (I think you'd need to write a custom groovy logic query to get the number of clinic visits per patient) * aggregation = SUM -Darius On Fri, Dec 16, 2011 at 2:06 PM, James Arbaugh <[email protected]>wrote: > Is it possible to use the Reporting Module to aggregate a number of > widgets rather than the number of patients with a widget. For example, we > want to know how many clinic visits there were. We don’t want to know how > many patients had at least one clinic visit. In other words, if one > patient went to the clinic 5 times and another patient went to the clinic 3 > times, I want the number of clinic visits to be 8. I’m not interested in > knowing that 2 patients went to the clinic. I thought I could do this with > an SQL Cohort Query, but it’s returning the results as if was “SELECT * > DISTINCT* patient_id WHERE bla bla bla”. By definition of what a cohort > is (a group of people) this behavior does make sense. It’s almost like we > need a WIDGET Queries section in the module.**** > > ** ** > > Thanks,**** > > James Arbaugh**** > ------------------------------ > Click here to > unsubscribe<[email protected]?body=SIGNOFF%20openmrs-implement-l>from > OpenMRS Implementers' mailing list _________________________________________ To unsubscribe from OpenMRS Implementers' mailing list, send an e-mail to [email protected] with "SIGNOFF openmrs-implement-l" in the body (not the subject) of your e-mail. [mailto:[email protected]?body=SIGNOFF%20openmrs-implement-l]
