Great to hear you want to continue! I think a good follow-on project would be to set up the destination.
1) You need to make these optional. We don't want outbound messages created if the user isn't going to do anything with them. 1a) Create a table hl7_out_queue_destination. hoqd_id, name, description, destination (e.g. ip addr, hostname), creator_*, changed_by*, retired_* 1b) Create table hl7_out_queue_destination_message_type: hoqd_id, message_type (or should this be object type?) 1b) Create outbound queue entries for each destination listed that has that type defined 2) Create admin interface in webapp to manage the destinations and which types go to which destination 3) Create api methods to be able to get outbound messages for a certain destination. For speed, this means adding a column to the hoq table for the destination id. Is the destination stored somewhere in the hl7 message? I think Burke mentioned that earlier. Does that need to be inserted into the hl7 message while its being written? Ben On Mon, Nov 14, 2011 at 12:10 PM, Thothathri Srinivasan <[email protected]>wrote: > Hello, > > We worked on the HL7 output design. We are very interested in continuing > work on the OpenMRS project. It'd be great if you could provide us the > further specifications of the project and new specifications for any new > features that you want us to include. > We had talked to Ben and the Dev group before, and he has asked us to > split up the project into two parts : > 1. Create the HL7 Messages, which we have done, and > 2. Send the HL7 Messages to a destination specified. > We have done the first part, and wanted to know if we could continue and > do the second part. > The changes had been made in a patch file, at > https://source.openmrs.org/cru/CR-TRUNK-569 and we have included the > latest copy of the patch, > *openmrs_v3.patch<https://source.openmrs.org/cru/CR-TRUNK-569/downloadpatch/498/openmrs_v3.patch> > * > Please let us know about any changes that need to be made to the first > part of the HL7 Output Design Project, and if we could continue on to do > the second part of the project. > Also, should I upload the new patch file in a separate review request? > Please let me know. > > Thank you for giving us the opportunity to work on this project. > > Thanks, > Thothathri > > -- > Thothathri Srinivasan > Graduate Student in Computer Science, > *NC STATE* UNIVERSITY > > ------------------------------ > 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]
