Burke, so you're proposing that this project should create: * hl7_out_queue table and domain object * hl7_destination table and domain object (for now just a plain OpenmrsMetadata, with name + description + audit info) * the method Hl7Service.getNextMessageFromOutQueueByDestination(Hl7Destination) -> Hl7OutQueue
But the actual work of calling that service method, and doing something with the message, will be done by someone else at some other time. Right? -Darius On Sat, Oct 29, 2011 at 1:57 PM, Burke Mamlin <[email protected]>wrote: > Most important would be an API method to get the next outbound message by > destination application/facility (ideally, the option to get the next > outbound message via Java API call or via web service call). It would be > nice to support some basic destinations (e.g., to file system or to TCP > port); however, I wouldn't put a lot of effort into an already-solved > problem. Any one looking for robust delivery of messages (robust queuing, > re-play, re-connect on lost connection, sophisticated ack-nack, etc.) would > do well to implement mirth > connect<http://www.mirthcorp.com/products/mirth-connect> or > a similar third-party interface engine. All we need to do is expose these > outbound messages to such an engine. > > -Burke > > On Sat, Oct 29, 2011 at 2:45 PM, Ben Wolfe <[email protected]> wrote: > >> I think for now we don't have to worry about the destination. >> >> We also would like to have just one hl7_out_queue instead of the 3 like >> the in queues. Give it a "status" column for a simplistic way of knowing >> if its been acted on. >> >> A second project after this is completed could be to add >> hl7_out_destination and hl7_out_destination_status tables. >> >> Ben >> >> >> On Sat, Oct 29, 2011 at 6:39 AM, Thothathri Srinivasan >> <[email protected]>wrote: >> >>> I'm presently working on the HL7 Output Messages Project, and had a few >>> questions: >>> How does the admin choose the destination where he sends the HL7 >>> messages? >>> My understanding is that we need to do something similar to HL7InQueue, >>> HL7InQueueProcessor, and have something like HL7OutQueue and >>> HL7OutQueueProcessor. We would also need HL7Destination that knows the >>> server to send the HL7 messages to, right? >>> So do we have to ask the admin about which destination to send it to, and >>> just give like a server address for that, or how should this design be >>> done? >>> >>> Any help will be greatly appreciated! >>> >>> Thanks! >>> 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] >>> >> >> ------------------------------ >> Click here to >> unsubscribe<[email protected]?body=SIGNOFF%20openmrs-devel-l>from >> OpenMRS Developers' mailing list > > > ------------------------------ > Click here to > unsubscribe<[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]
