+1 for "proper event notification mechanism", we have pushed AOP to limits with event notification in Chica, it doesn't scale up.
Vibha From: [email protected] [mailto:[email protected]] On Behalf Of Darius Jazayeri Sent: Thursday, October 20, 2011 12:00 PM To: [email protected] Subject: Re: [OPENMRS-DEV] Regarding HL7 Output This could be an opportunity to introduce a proper event notification mechanism (not AOP), e.g. we'd actually introduce a "patient created" event, and tie the creation of the ADT_A01 to that. Though this would end up making the project more complex, and harder to do in a module. So it's probably not worth it at this stage. I would also prefer for OpenMRS to be able to generate these without needing mirth. (Presumably mirth could be used to transform them.) -Darius On Thu, Oct 20, 2011 at 3:33 AM, Ben Wolfe <[email protected]<mailto:[email protected]>> wrote: This is probably best done in an hl7output module. We can then iterate on it faster and add other features for different kinds of connections. I actually would prefer option #1 where we generate a small number of messages based on some AOP around the savePatient and saveEncounter methods. A new patient would create an ADT_A01 message. is A02 a modified patient? A new encounter with obs is ORU_R01. Any thoughts from other devs? How is this usually done? And/or what types of outgoing messages would be useful? Ben On Thu, Oct 20, 2011 at 8:38 AM, Thothathri Srinivasan <[email protected]<mailto:[email protected]>> wrote: Hi, I just started working on OpenMRS, and am working on the HL7 Output (Design Page). I had sent out a mail to Ben earlier, and he told me that the HL7 Output project has two options : 1. Generate a few simple messages ourselves using the HAPI library and put those into the output queue 2.Put xml objects into the output queue and have mirth sit externally and read those to generate the actual hl7 messages. Which option would be better for it, so that I can start off with it? Thanks a lot, Thothathri _________________________________________ To unsubscribe from OpenMRS Developers' mailing list, send an e-mail to [email protected]<mailto:[email protected]> with "SIGNOFF openmrs-devel-l" in the body (not the subject) of your e-mail. [mailto:[email protected]<mailto:[email protected]>?body=SIGNOFF%20openmrs-devel-l] ________________________________ Click here to unsubscribe<mailto:[email protected]?body=SIGNOFF%20openmrs-devel-l> from OpenMRS Developers' mailing list ________________________________ Click here to unsubscribe<mailto:[email protected]?body=SIGNOFF%20openmrs-devel-l> from OpenMRS Developers' mailing list _________________________________________ 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]
