Re: Port for real time HL7 transactions -- MIDRANGE-L

Ryan - Your example of ports matches what I am seeing.

Jerry - We have two setups. In the first scenario, we are acting as a
server and receiving operative notes from another hospital. In the second
scenario, we are the client and will return the signed operative notes back
to the other hospital. Our network folks opened up two ports between the
two hospitals. One for our socket server and one for their socket server.
Right now, I am working on our server piece and have not touched our client
piece that will connect to their server. That being said, I start our
server job and the other hospital connects w/o any trouble. Our server job
then reads data until it gets an x'1c'. At that point in time, the server
builds and returns an acknowledgment record using send() and using the same
connection that received the HL7 message. I have tried sending it both
translated and untranslated. The receiving side says they do not see it.
However, netstat and the com trace I did show that it went.

We have a conference call tomorrow to try to work this out. I'll post the
results tomorrow.

Thanks for the replies!

Joe

Joe Wells
University of Alabama Health Services Foundation
500 22nd Street South, Suite 308
Birmingham, AL 35233
205-731-5610

CONFIDENTIALITY NOTICE
This e-mail is intended for the sole use of the individual(s) to whom it is
addressed, and may contain information that is privileged, confidential and
exempt from disclosure under applicable law. You are hereby notified that
any dissemination, duplication or distribution of this transmission by
someone other than the intended addressee or its designated agent is
strictly prohibited. If you receive this e-mail in error, please notify me
immediately by replying to this e-mail.

On 8/27/2009 at 2:46 PM, in message

<OF05FD81BA.AA14FFE5-ON8525761F.006B2FB4-8525761F.006C9AB4@xxxxxxxxxxxxxxxx>

<GKern@xxxxxxxxxxxxxxxx> wrote:

Joe,

"Question - when the tunnel was created between "us" and "them", a
specific
port was designated for traffic coming to us (i.e., to our listener) and
another for return traffic (to their listener). I noticed on netstat
that
the local port is correct, but the remote port varies (and is not one
that
was specified). Since the socket connects, and we receive data, and I
am
returning data through this same socket connection......do the remote
port
need to be open for them to receive?"

I'm not sure why the tunnel was created to use two ports (one for
sending
and one for receiving). Unless there are underlying reasons for doing
this, this is (to me) more complex than need be.

To my understanding a socket connection is a one to one connection that
has to be able to send and receive data and acknowledge when it does
both
activities at both ends of the connection. Otherwise you can't guarantee

the integrity of the transmission.

When you connect (in listen mode) to the server, (it sounds like) all
your
reads and writes are going though the port you are listening on. (That's

the way my programs work.) But with two ports (one to send and one to
receive), you would need to program your listener to detect receipt of
an
ack on the other port, and coordinate the send/receive between your
sender
and receiver programs.

(If I am way off base here someone please chime in and enlighten me!)

Regards, Jerry

Gerald Kern - MIS Project Leader
Lotus Notes/Domino Administrator
IBM Certified RPG IV Developer
The Toledo Clinic, Inc.
4235 Secor Road
Toledo, OH 43623-4299
Phone 419-479-5535
gkern@xxxxxxxxxxxxxxxx

This e-mail message, including any attachments, is for the sole use of
the
intended recipient(s) and may contain confidential and privileged
information. Any unauthorized use, disclosure or distribution is
prohibited. If you are not the intended recipient, please inform the
sender by reply e-mail and destroy this and all copies of this message.