Thothathri --
Thanks for all the work you've been doing on this project.
We can't assume network connectivity or even that the HL7 will be sent over
a network. We might be piping the output to another app running on the same
server. We might be making a file to put onto a thumb drive to be sent to the
regional office. We might be waiting to be polled by an external system. We
might be sending data via a broker, so the destination of the message is not
the same as the (final) destination in the message. We might be packaging the
HL7 in a PHIN message.
So I agree with Ben that we need to review the circumstances under which a
message is dequeued. It may be that we need to raise an event when a new
message is available, and have any process that wants to work in real time
listen for that event. We may also need to have APIs to examine the queue for
messages for a particular destination or produce a file of all messages for a
particular destination; a scheduled process or a poll response process or a
manual process would be able to use this API. Although it would be nice to
have some standard communications methods available, I think the creation of
the HL7 message is the heart of what we're looking for. The triggering of
message generation (we should be able to pass in an individual patient or a
cohort or have a logic rule) and the dequeueing of generated messages pretty
much depend on the needs of the surrounding application.
Saludos, Roger
From: [email protected] [mailto:[email protected]] On Behalf Of Ben Wolfe
Sent: Thursday, December 01, 2011 5:46 AM
To: [email protected]
Subject: Re: [OPENMRS-DEV] About the progress in the HL7 Output Messages Module
The messages can just go out as the text hl7 message. Thats all you want to
send, don't send our objects or xml to other systems.
Can you link to the most up-to-date code review so we can see your
code/tables/etc? (Or link to wiki docs that you have created)
Ben
On Thu, Dec 1, 2011 at 10:24 AM, Thothathri Srinivasan
<[email protected]<mailto:[email protected]>> wrote:
So I've used HAPI to convert into HL7 Message formats (ADT and ORU), and stored
these details into a table called HL7OutQueue in the database.
I have also created a HL7OutQueueDestination that has the destination details.
I thought that we could serialize the objects in the HL7OutQueue table (which
would have transient data members too), and then send it over the network to
the destination from the HL7OutQueueDestination table.
Isn't this what we have to do to send the HL7 messages to a destination?
Please let me know.
Thanks,
Thothathri
On Thu, Dec 1, 2011 at 2:08 AM, Ben Wolfe
<[email protected]<mailto:[email protected]>> wrote:
Serializing and sending to a destination? What do you mean by that? Can you
give you the steps in your processing?
Ben
On Thu, Dec 1, 2011 at 6:57 AM, Thothathri Srinivasan
<[email protected]<mailto:[email protected]>> wrote:
Hello Ben,
We had talked to you a few days back about what we intended to do about the HL7
Output Messages module.
We tried using Mirth like you had mentioned, but then decided to implement the
conversion of details into HL7 ADTA28 and ORUR01 messages using HAPI, and then
serializing and sending it over to a destination.
Please let us know if that's fine.
Thanks,
Thothathri
--
Thothathri Srinivasan
Graduate Student in Computer Science,
NC STATE UNIVERSITY
--
Thothathri Srinivasan
Graduate Student in Computer Science,
NC STATE UNIVERSITY
________________________________
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]
