djazayeri	bholagabbar: 1. Randomizer: I think low priority due to real-world usage patterns of OpenMRS
	bholagabbar	djazayeri: Hmm I see. But it sure is a great component to add to a cohort module.
	robbyoconnor	djazayeri, how goes that PR on your scrumbot, one of the issues fixed is that moment.js has an open CVE
	bholagabbar	djazayeri: Because several studies on cohorts are conducted as intervention trials..and I think randomized trials are the most common, wouldn't you say
	djazayeri	bholagabbar: 2. Cohort Builder: generally there is great value in having cohort builder
	djazayeri	bholagabbar: but my understanding is that the cohort module is primarily about defining fixed groups of patients, and then recording pieces of data against them.
	djazayeri	bholagabbar: so I'm not sure that cohort builder would go _in_ the cohort module vs a different module.
	robbyoconnor	Why not within?
	robbyoconnor	or maybe dependent on?
	bholagabbar	djazayeri: I see. I was looking to incorporate a system wherein the cohorts can be built faster.
	djazayeri	bholagabbar: 3. Integration of HFE: being able to capture obs against cohorts with implementation-defined forms is super valuable. I would put this highest priority. I'm not actually sure if it's feasible to _use_ HFE for this, versus needing to take another approach.
	bholagabbar	djazayeri: The cohort builder is a great way to do that. Like say get patients from DB between x and y and add them all to the cohort
	bholagabbar	djazayeri: Other alternatives *could* be?
	djazayeri	bholagabbar: I think the main use case is saying that, for example a family of 5 that lives together is a "household" type cohort. And then you want to record data points against that cohort (type of roof on house, etc).
	djazayeri	bholagabbar: so for this use case, defining dynamic queries doesn't help, you need to just pick a specific small number of patients.
	djazayeri	bholagabbar: at least, that's my understanding of the primary use case. If there's another big use case about building _large_ cohorts for a study or something, then the builder might help
	djazayeri	bholagabbar: again, though, I think that form-driven data capture is the most valuable thing
	|<--	djazayeri has left freenode (Read error: Connection reset by peer)
	eykrevooh	Hey everyone, I have been having a problem testing modules that I have made changes to. I am using OpenMRS-standalone-2.3.1 and am working in the reference application module. My problem is when I try and update the module using the GUI it crashes the application. Am I going about this wrong? If anyone has any advise I would greatly appreciate it.
	-->|	djazayeri (~Adium@154.70.36.62) has joined #openmrs
	=-=	Mode #openmrs +v djazayeri by ChanServ
	djazayeri	bholagabbar: 4. Redoing the UI: yes, I agree
	djazayeri	bholagabbar: (sorry, I was disconnected between my last 2 msgs, if you said anything)
	bholagabbar	djazayeri: Would you prefer I rearrange these priorities
	bholagabbar	djazayeri: Nope I read that you disconnected
	bholagabbar	djazayeri: Go on
	|<--	SandeepRaparthi has left freenode (Quit: Connection closed for inactivity)
	|<--	robbyoconnor has left freenode (Ping timeout: 252 seconds)
	djazayeri	bholagabbar: 5. display: agree that there's probably something to be done here. doing a mockup of some example would be good for a project application. (This probably goes with 4.)
	bholagabbar	djazayeri: IMO *some* sort of cohort builder would be necessary. Maimoona said we need 'Extensive searched mechanism available over an extensive range of parameters'
	bholagabbar	djazayeri: The first thing that came to my mind was the cohort builder
	djazayeri	6. Integrate reporting. Yes. There's probably a small integration that would provide a good amount of value.
	djazayeri	7. official module. Probably not.
	bholagabbar	djazayeri: Why not?
	djazayeri	bholagabbar: what is an "official" module?
	bholagabbar	djazayeri: Held my openmrs in the github account I meant
	bholagabbar	djazayeri: Currently it's on sharon's github
	OpenMRSbotSR	[Michael Downey] djazayeri: hey that's my question to ask
	djazayeri	bholagabbar: ah, well, maybe
	djazayeri	bholagabbar: anyway, that's not part of the proposal.
	bholagabbar	djazayeri: Yeah alright makes sense
	bholagabbar	djazayeri: Also, the cohort builder. what would you suggest for Maimoona's requirement?
	bholagabbar	djazayeri: 'Extensive searched mechanism available over an extensive range of parameters'
	bholagabbar	djazayeri: Is what she mentioned
	djazayeri	bholagabbar: so, if maimoona says this is valuable I believe her.
	bholagabbar	djazayeri: Wouldn't cohort builder be the closest to what we have?
	djazayeri	bholagabbar: yes
	|<--	eykrevooh has left freenode (Quit: Page closed)
	|<--	ssmusoke has left freenode (Quit: ssmusoke)
	djazayeri	bholagabbar: but also the ability to use a cohortdefinition defined in the reporting module (which does not have a nice UI, but is more powerful
	bholagabbar	djazayeri: I see. I'm not quite aware of that..but I'll look into it
	bholagabbar	djazayeri: I was speaking to Ada the other day. She too mentioned the need to incorporate cohort-definitions
	[INFO]	There is nothing to tab-complete. Use F6 to cycle through the user list, input box and the chat output.
	djazayeri	r0bby: sorry; I've been very busy going between continents. the main reason I haven't merged the PR is that it will change the way I have to deploy the code, and I already had a readme set up that I copy and paste from. So merging will make my life harder.
	bholagabbar	djazayeri: If we add details like cohort-active, cohort-inactive then It becomes very useful for mUzima, their module app to download only relevant (active) cohort data.
	bholagabbar	djazayeri: Basically, add more cohort metadata. Would that make sense?
	bholagabbar	djazayeri: Something like 'cohort definition would be the inclusive and exclusive criteria.  For example a) age within 18 and 30 years old b) diagnosis of CHF, c) no previous history of taking beta blockers, f) visited location ABC'
	djazayeri	bholagabbar: yes, in fact I would rank adding more cohort metadata as top priority
	djazayeri	bholagabbar: note that openmrs-core already has a Cohort class, and I actually thought that Ada's proposal was to extend the one in openmrs-core.
	bholagabbar	djazayeri: Great. So Cohort Forms > Cohort Metadata > Builder > UI
	bholagabbar	djazayeri: All of these with *must do* tho
	djazayeri	bholagabbar: personally I would put builder last, in the context of this module
	bholagabbar	djazayeri: Haha ok!
	djazayeri	bholagabbar: I would think that Cohort Builder is very high priority in general (maybe higher than the rest of this), but in the context of "enancements to cohort module" it feels lower. (just my opinoin)
	bholagabbar	djazayeri: Maimoona mentioned that half of the work regarding HTML forms has alrady been done. I'm not sure where/how/what tho
	djazayeri	bholagabbar: okay, off to bed
	djazayeri	bholagabbar: good luck
	bholagabbar	djazayeri: Thanks so much Darius
	bholagabbar	djazayeri: Much appreciated