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

Jerry & Ryan,

Thanks for the replies. I have tried translating to ASCII and not
translating. I have tried adding framing characters and not adding framing
characters. The receiving side says they cannot see anything I am sending.
I have asked our network people to get involved and do a trace. We will see
what that shows.

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?

Thanks,

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 8:27 AM, in message

<b384299a0908270627i63e7b815uc8ba527f4433c11e@xxxxxxxxxxxxxx>, Michael
Ryan<michaelrtr@xxxxxxxxx> wrote:

Are you converting the text to ASCII (if that's what the receiver wants).

On Thu, Aug 27, 2009 at 9:17 AM, Joe Wells
<jwells@xxxxxxxxx> wrote:

Yes, I saw the bytes sent using netstat and I also did a communications
trace (STRCMNTRC - saw Aaron Bartel's post on the command) and saw the
bytes
there too. However, one thing puzzled me about the trace. The data
received showed as clear text, but the data sent looked like EBCDIC. I
tried the various combinations of sending the data converted/unconverted
and
changing the CODE parm on the PRTCMNTRC command from EBCDIC to ASCII

(and

also *CALC). The resulting printout for the data sent was never in

clear

text.

Any thoughts?

Thanks,

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/26/2009 at 7:05 PM, in message

<b384299a0908261705u1e603e5o77200234c3cf218f-JsoAwUIsXosN+BqQ9rBEUg@public.

gmane.org>, Michael

Ryan<michaelrtr@xxxxxxxxx> wrote:

I believe the return code from the write would be the number of bytes
sent.

Try a netstat option 3 after you connect. You should be able to see
bytes
in/out. That may let you know if you're sending data.

On Wed, Aug 26, 2009 at 3:37 PM, Joe Wells
<jwells@xxxxxxxxx> wrote:

Well, I am finally able to start testing the socket

connections......and

it

works (thank you Scott Kelements!)!

Unfortunately, I am having trouble sending the ACK back to server. I

build

the ACK message and the send it using Scott's WrLine. WrLine is

returning

101 (an RC of 1 plus a message length of 100). So I assume this is

the

proper procedure to use and that it makes the trip since it returns

101.

However, the people on the other end do not see the ACK and cannot

provide

me with a log or a trace.

So, I assume my only next option is to get our network people to

trace

the

activity.

Does anyone have any thoughts?

Thanks,

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

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

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 6/26/2009 at 10:47 AM, in message

<

OF7C747810.5C2B5EFF-ON852575E1.00543CA9-852575E1.0056C872-EfGSZ7ftWEp35B+agQ

sMFw@xxxxxxxxxxxxxxxx

<GKern@xxxxxxxxxxxxxxxx> wrote:

Joe,

My first application was the socket client. Not knowing anything

about

sockets, it was a learning experience to say the least. The server

side

came a few years later.

So in my case my EMR vendor provided me with the ip address/port

they

would be listening on (7001). You can probably use any unassigned

port.

Use NETSTAT *CNN to see what's in use at the current time on your
iSeries.

I don't do any validation when I receive data. Basically I just

parse

out
the string between the x'0b' and x'1c0d', and then assign a name

using

a

format of, for example, MercyMemorial09062611254029193.dat, which
defines
the source and then I append a date/time stamp on it. I then write

this

file to the IFS (using Scott's IFS tools), into two folders in the

IFS

-

one is an archive where I retain the original (for historical
purposes/testing/resends etc) and the same file goes into an

'Input'

folder.

Then I have a preprocessor that reads from the 'Input' folder and

does

initial edits and any custom HL7 formatting requirements before it
attempts to send to the EMR application. If there are errors in

this

process (say the demographics don't match for a lab result because

a

name misspelling or birthdate difference) I then put the unmodified

HL7

into an 'Error' folder in the IFS. Otherwise if everything looks

good

the
custom formatted/modified HL7 goes into an 'Output' folder. I then

have

an
RPG program that trolls for the files in the Output folder and loads

data queue that is used as input to the socket client program.

The socket client programs sends the data and waits to receive an

the

HL7
ack that is also wrapped with x'0b' and x'1c0d'. Then the next HL7

sent
and the process repeats itself.

Hope that helps.

Also - a neat inexpensive tool I use to test socket connections is

called

7Scan. It's designed for HL7 data and allows you to view, edit,

send

and

receive HL7. It also lets you use it as a socket client or server

you

can test connections from your pc as either a client or server.

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

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.

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L)

mailing

list

To post a message email:

MIDRANGE-L@xxxxxxxxxxxx

To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing

list

To post a message email:

MIDRANGE-L@xxxxxxxxxxxx

To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.