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]>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] with "SIGNOFF openmrs-devel-l" in the body > (not the subject) of your e-mail. > > [mailto:[email protected]?body=SIGNOFF%20openmrs-devel-l] > _________________________________________ 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]
