TCP listener in HL7

[BikerDude]

hey Y'all,

I have a couple of questions

1) What is the best way to test if the TCP listener in Vista is
started. I have been using telnet xxx.xxx.xxx yyyy to test it, Is
there any tool within vista to test its own interface. I have read the
manuals and they only say vista can be used to test another vista's
interface. Also, do I need to define the M routine that will parse the
message coming in to be able to successfully start the listener?

2) What are the minimalistic steps needed to start a TCP interface in
HL7 menu. The manuals are little confusing. These are the options I
have used but the TCP listener does not seem to be running


1)

Created an application under

Systems Manager Menu Option >> HL7 Main Menu Option >> Interface
Developer Options Option >> HL7 APPLICATION PARAMETER NAME

with the following parameters

Name : xxxxx
facility Name : yyyyyy
Active/ Inactive : Active
HL7 Field seperator : |
Country Code : USA
HL7 encoding characters : ~^\&




2)

Created a protocol under
Systems Manager Menu Option >> HL7 Main Menu Option >> Interface
Developer Options Option >> PROTOCOL EDIT >> PROTOCOL NAME

with the following parameters
Name : HL7 INP
Type : subscriber


3)

Created a under
Systems Manager Menu Option >> HL7 Main Menu Option >> Interface
Developer Options Option >> PROTOCOL NAME>> HL LOGICAL LINK NODE >>
LINK EDIT
Node : Biker
Autostart : Enabled
Queue Size : 10
LLP Type : TCP

TCP lower level parameters are

Facility Name : yyyyy
TCP/IP SERVICE TYPE : MULTI LISTENER
TCP/ IP ADDRESS : 1xxx. 1xxx. xx.xxx
TCP/IP PORT OPTIMIZED : 5000 <----------- this is
the one recommended
SAY HELo : NO
PERSISTENT : YES


After I set these and restart all thelinks, my link does not showup in
the monitor list. My taksman is running and Link manger is running.

Probably missing a key step and any light on this is appreciated.

Thanks!
BD

[Nancy Anthracite]

What are you using - Linux/GTM or Cache/Windows?

--
Nancy Anthracite

[John McCormack]

The default view in the monitor listing is to only show links that have activity, i.e. a positive message count in one of the four columns.
Unless you switch to view all (A) or setup a "view" and define the links you want on that "view" and then select that "view"  under "V".

[Gregory Woodhouse]

The reason I've suggested testing with telnet (ugly as that is) is to
determine what happens when the connection is ACCEPTED. You can use
netstat to check to see if a process is LISTENING on the port. But if
the listener is configured improperly, an error will occur when the
connection accepted, closing the remote end and causing telnet to
disconnect immediately.

[Elanchezhiyan]

Hi,

As per my knowledge on VistA there are two HL7 packages
General HL7 package and HLO package(OPTIMIZED).

TCP/IP PORT OPTIMIZED : 5000 field is used for HLO package
TCP/IP PORT: field is used for General
HL7 package.

Make sure which package are you using? if are using general HL7
package leave the "TCP/IP PORT OPTIMIZED :" field blank or other
one HLO leave "TCP/IP PORT:" field blank.
And as per my understanding of your details i think you have to check
link status at system monitor view (ML MONITOR LINK) of HLO MAIN MENU
not the system monitor view of HL7 Main Menu.

main thing don't forget to start the link.

> Gregory Woodhouse >>You can use netstat to check to see if a process is LISTENING on the port.

Regards,
elanchezhiyan K

[Elanchezhiyan]

Hi,

>I have read the manuals and they only say vista can be used to test another vista's
interface.

what manuals are you refering to ? can you please tell specifically
that told you "vista can be used to test another vista's interface."

>. Also, do I need to define the M routine that will parse the
message coming in to be able to successfully start the listener?

Yes we have to write the one processing routine to parse the incoming
HL7 message and one for generating HL7 messaeg. But we should make
sure that whether we are not re-inventing the existing programs in
VistA.

>2) What are the minimalistic steps needed to start a TCP interface in
HL7 menu.

For General HL7 package, as per my understanding to start TCP
interface ( HL logical link in VistA HL7 package terminology)
necessary details required are
NODE: VISTA-TCP
LLP TYPE: TCP
TCP/IP ADDRESS: xxx.yyy.www.zzz
TCP/IP PORT: 5001
TCP/IP SERVICE TYPE: SINGLE LISTENER
PERSISTENT: YES <- can be no also

and start the link VISTA-TCP

but for Full fledged HL7 message generation and receiving using
General HL7 we have to define

1. Two Application ( sending and receiving)
2. Minimum Two Protocol ( Event driver and Subscriber)
3. Two HL logical link ( Client sender and Listener)

Regards,
elanchezhiyan K.

[BikerDude]

GTM

[BikerDude]

Elanchezhiyan,

this did the trick. Using the regular port instead of optimized.

Thanks Y'all