HL7 Setup

126 views
Skip to first unread message

rlb

unread,
Oct 2, 2009, 12:22:58 PM10/2/09
to Hardhats
I am in the process of setting up my Hl7 interface using VistA as a
client only. My intention is to send HL7 messages over TCP to a Mural
Master Patient Index (MPI). My MPI and Vista server are on two
different machines. I have been following the VA refernce manuals for
setup and configuration. I have created a TCP link with the IP
address, started Taskman, Link Manager etc. I have included my system
outputs below:

I am having a problem starting HLO Process Manager via System
Monitor. I get this error:

PROCESS^HLOPROC, HL7 - PROCESS MANAGER. No device.


**************************************************************************************
SYSTEM LINK MONITOR for VOE OFFICE INSTITUTION OLD (T
System)
MESSAGES MESSAGES MESSAGES MESSAGES
DEVICE
NODE RECEIVED PROCESSED TO SEND SENT
TYPE STATE

NPTF
3
PSOTPBAAC
50 NC Open
PXRM7-RECO
28

Incoming filers running => 1 TaskMan running
Outgoing filers running => 2 Link Manager running

Monitor current [next job 0.9 hr]

*************************************************************************************
HLO SYSTEM MONITOR Oct 02, 2009@16:14:22 Page:
1 of 1

Brief Operational
Overview
SYSTEM STATUS:
RUNNING
PROCESS MANAGER:
STOPPED
STANDARD LISTENER: NOT
OPERATIONAL
TASKMAN:
RUNNING
DOWN
LINKS:
CLIENT LINK PROCESSES:
0
IN-FILER PROCESSES:
0
MESSAGES PENDING ON OUT QUEUES: 0 ON SEQUENCE
QUEUES: 0
STOPPED OUTGOING
QUEUES:
MESSAGES PENDING ON APPLICATIONS:
0
STOPPED INCOMING
QUEUES:
FILE 777 RECORD COUNT: --> as
of
FILE 778 RECORD COUNT: --> as
of
MESSAGES SENT TODAY:
0
MESSAGES RECEIVED TODAY:
0
MESSAGE ERRORS TODAY: 0

***************************************************************************************

HL7 LOGICAL LINK
--------------------------------------------------------------------------------
NODE: TEST
DESCRIPTION:
INSTITUTION: VOE OFFICE INSTITUTION
MAILMAN DOMAIN:
AUTOSTART:
QUEUE SIZE: 10
LLP TYPE: TCP
DNS DOMAIN:
------------------------------------------------------------------------------
TCP LOWER LEVEL PARAMETERS
TEST
TCP/IP SERVICE TYPE: CLIENT (SENDER)
TCP/IP ADDRESS: 10.248.91.194
TCP/IP PORT: 6661
TCP/IP PORT (OPTIMIZED):
ACK TIMEOUT:
RE-TRANSMISION ATTEMPTS:
READ TIMEOUT:
EXCEED RE-TRANSMIT ACTION:
BLOCK SIZE:
SAY HELO:
DIRECT CONNECT OPEN TIMEOUT:
STARTUP NODE:
PERSISTENT:
RETENTION:
UNI-DIRECTIONAL WAIT:

DanB

unread,
Oct 2, 2009, 12:45:13 PM10/2/09
to Hardhats
What OS are you running? I'm not sure if HLO fully supports GTM yet.

Are these custom HL7 interfaces or existing VistA interfaces? I'm not
sure how many packages are using HLO right now so it may not even be
needed to get you operational.

This is the doc you need for HLO setup:
http://www.va.gov/vdl/documents/Infrastructure/Health_Level_7_(HL7)/hl_1_6_126_ig.pdf

rlb

unread,
Oct 2, 2009, 12:46:26 PM10/2/09
to Hardhats
GTM

On Oct 2, 12:45 pm, DanB <b351...@yahoo.com> wrote:
> What OS are you running?  I'm not sure if HLO fully supports GTM yet.
>
> Are these custom HL7 interfaces or existing VistA interfaces?  I'm not
> sure how many packages are using HLO right now so it may not even be
> needed to get you operational.
>
> This is the doc you need for HLO setup:http://www.va.gov/vdl/documents/Infrastructure/Health_Level_7_(HL7)/h...

DanB

unread,
Oct 2, 2009, 2:10:44 PM10/2/09
to Hardhats
Well, you should be able to use the HLO setup procedure for using a
Taskman Multi-threaded listener (section 5.4). It may not be as
robust as using an OS native service, but it will get you running.

rlb

unread,
Oct 2, 2009, 4:04:33 PM10/2/09
to Hardhats
I am not trying for a listener, just a client sender. I did noticed
many other TCP links were already created for my system.

DanB

unread,
Oct 2, 2009, 5:24:21 PM10/2/09
to Hardhats
Without the HLO listener running, how do you expect to get HLO
Application ACKs back?

Laso, I don't know if HLO will send stuff out if it thinks it isn't
configured correctly (such as not having a listener running).

As for sending HLO message out, there's really not much to do. But
again, dont know if HLO works 100% with GTM.

Read Chapter 6:
http://www.va.gov/vdl/documents/Infrastructure/Health_Level_7_(HL7)/hl_1_6_126_tm.pdf

rlb

unread,
Oct 2, 2009, 5:58:30 PM10/2/09
to Hardhats
Turns out I was confused about HLO (HL7 Optimized). Apparently, from
what I have heard, HLO is not what I need, but rather plain HL7.
So it turns out I wont need HLO, so that solves my issue with Process
Manager, but then how do i go about setting up my TCP Link.

I guess what I dont understand is how to your turn on HL7 messages for
everytime an event occurs.
Popular HL7 based EHR integrations include external Labs, Practice
Management systems, and Master Patient Indexes.

The Mural MPI would want messages related to patient registration, or
the creation of a patient record (such as an Exam).

I have a TCP link defined. Now where do i say monitor these events and
do these messages?

David Whitten

unread,
Oct 2, 2009, 6:12:16 PM10/2/09
to hard...@googlegroups.com
Questions about HL7 are best answered by someone like Greg Woodhouse,
since he was actually on the HL7 team at one time, but I will point out that
there are menus that are part of HL7 configuration at

GTM>D ^XUP

Setting up programmer environment
This is a TEST account.

Terminal Type set to: C-VT102

You have 2526 new messages.
Select OPTION NAME: HL7 MAIN MENU  HL MAIN MENU     HL7 Main Menu

Select HL7 Main Menu Option: ?

          Event monitoring menu ...
          Systems Link Monitor
          Filer and Link Management Options ...
          Message Management Options ...
          Interface Developer Options ...
          Site Parameter Edit
   HLO    HL7 (Optimized) MAIN MENU ...

Enter ?? for more options, ??? for brief descriptions, ?OPTION for help text.

Select HL7 Main Menu Option:

basically, you need to use these options to setup the different HL7 Link names that the messages you want to receive need.

Select HL7 Main Menu Option: Filer and Link Management Options

Select Filer and Link Management Options Option: ?

   SM     Systems Link Monitor
   FM     Monitor, Start, Stop Filers
   LM     TCP Link Manager Start/Stop
   SA     Stop All Messaging Background Processes
   RA     Restart/Start All Links and Filers
   DF     Default Filers Startup
   SL     Start/Stop Links
   PI     Ping (TCP Only)
   ED     Link Edit
   ER     Link Errors ...

Enter ?? for more options, ??? for brief descriptions, ?OPTION for help text.

Select Filer and Link Management Options Option: Link Edit

Select HL LOGICAL LINK NODE: ?
 Answer with HL LOGICAL LINK NODE, or INSTITUTION, or MAILMAN DOMAIN, or
     DNS DOMAIN, or TCP/IP ADDRESS, or TCP/IP SERVICE TYPE, or
     IEN772 OutQ-Non-TCP, or IEN772 InQ-Non-TCP
 Do you want the entire 223-Entry HL LOGICAL LINK List? Y  (Yes)
   Choose from:
   AMB-CARE
   BPS NCPDP
   DGMST-SEND
   DGRU ADT
   EPHARM IN
   EPHARM OUT
   EPI-LAB
   FBFEE-FPPS
   HUI PROV
   IFCAP_FPDS
   IIV EC
   LA7POC1
   LA7POC1A
   LA7POC2
   LA7POC2A
   LA7POC3
   LA7POC3A
   LA7POC4
   '^' TO STOP:

So part of the task involves deciding which type of connection you need, and then finding the links that provide it.

Best Regards,
David

rlb

unread,
Oct 2, 2009, 6:21:33 PM10/2/09
to Hardhats
Here some more results of my tinkering.
I have turned on the master job

-------- Master job status is ACTIVE
--------
Last master job run was 21 min 43 sec
ago...
Next run [task# 301] is 1 hr 38 min 17 sec in the
future...
-------- Event monitoring status is ACTIVE --------

and event monitoring

SEND EVENTS (#11)
Description: distributes events to remote locations
Status: ACTIVE
Requeue minutes: 30min
Notification mail group: ---
M startup: SENDALL~HLEMSND

----------------------- Parameter "Variable" Descriptors
-----------------------

Recent Checks of the Monitor by Master Job
--------------------------------------------------------------------------------
Check-time Results
--------------------------------------------------------------------------------
10/02@15:38 QUEUED
10/02@17:38 QUEUED
10/02@19:38 QUEUED
10/02@21:38 QUEUED
10/02@21:52 TOO EARLY

rlb

unread,
Oct 2, 2009, 6:30:02 PM10/2/09
to Hardhats


On Oct 2, 6:12 pm, David Whitten <whit...@worldvista.org> wrote:
>
> So part of the task involves deciding which type of connection you need, and
> then finding the links that provide it.
>

So are you saying that I should use another one like ambualtory care
and just change the ip address and start it?
I will try.

rlb

unread,
Oct 2, 2009, 9:33:14 PM10/2/09
to Hardhats
I did notice that my Test Link is running now:

SYSTEM LINK MONITOR for VOE OFFICE INSTITUTION OLD (T
System)


NODE STATE

TEST Enabled


but it has no messages to send or sent

Nancy Anthracite

unread,
Oct 2, 2009, 10:34:14 PM10/2/09
to hard...@googlegroups.com, rlb
Richard, if there are some HL7 site parameters, I think that the VOE OFFICE
INSTITUTION as opposed to VOE OFFICE INSTITUTION OLD may be correct.
--
Nancy Anthracite

rlb

unread,
Oct 2, 2009, 10:42:52 PM10/2/09
to Hardhats
Here are some relevent messages from taskman

274: STARTIN^HLCSIN, HL7 Incoming Filer. No device. EHR,EHR.
From Yesterday at 1:12, By you. Started running Yesterday at
15:38.
Job #: 14578 [38F2] Updated: Today at 2:39

275: STARTOUT^HLCSOUT, HL7 Outgoing Filer. No device. EHR,EHR.
From Yesterday at 1:12, By you. Started running Yesterday at
15:38.
Job #: 14584 [38F8] Updated: Today at 2:40
-------------------------------------------------------------------------------
276: ^HLCSMM1, SPN Low Level Protocol. No device. EHR,EHR.
From Yesterday at 1:12, By you. Started running Yesterday at
15:39.
Job #: 14591 [38FF]
-------------------------------------------------------------------------------
277: ^HLCSMM1, SDPM Low Level Protocol. No device. EHR,EHR.
From Yesterday at 1:12, By you. Started running Yesterday at
15:39.
Job #: 14598 [3906]
-------------------------------------------------------------------------------
278: STARTOUT^HLCSOUT, HL7 Outgoing Filer. No device. EHR,EHR.
From Yesterday at 1:12, By you. Started running Yesterday at
15:39.
Job #: 14604 [390C] Updated: Today at 2:40
-------------------------------------------------------------------------------
279: EN^HLCSLM, HL7 Link Manager. No device. EHR,EHR. From
Yesterday at 1:13,
By you. Started running Yesterday at 15:39. Job #: 14611 [3913]
Updated: Today at 2:40

289: ^HLCSLSM, PSOTPBAAC Low Level Protocol. No device. EHR,EHR.
From Yesterday at 15:39, By you. Started running Yesterday at
15:39.
Job #: 14634 [392A]

307: MASTER^HLEVMST, HL Master Job - Event Monitoring. No device.
EHR,EHR.
From Today at 1:52, By you. Scheduled for Today at 3:52

rlb

unread,
Oct 2, 2009, 10:51:09 PM10/2/09
to Hardhats
> Richard, if there are some HL7 site parameters, I think that the VOE OFFICE
> INSTITUTION as opposed to VOE OFFICE INSTITUTION OLD may be correct.

I am trying to just get any VistA Hl7 interface running by redirecting
the output to my Mirth listener so I am sure traffic is coming in.
When I know I have the right traffic I can reroute it to Mural.

I already verified my mirth is listening as I sent some test HL7
messages to itfrom a client I have that works.

I am experimenting with the "PSOTPBAAC", "AMB-CARE", and my" Test"
Interface Nodes and I have tried different settings
for institution and other parameters.

The needle still hasn't moved on my mirth server.

I chose PSOTPBAAC because it seems it has some message to send
(according to System Link Monitor

DanB

unread,
Oct 2, 2009, 11:52:43 PM10/2/09
to Hardhats
You cant always rely on Systems Monitor. Look at the global:
^HLMA("AC","O", <-- thats "O" not zero

It will tell you which logical links have outbound messages queued for
sending.
^HLMA("AC","O",#870 ien, #773 ien)=""

rlb

unread,
Oct 3, 2009, 10:35:19 AM10/3/09
to Hardhats
On Oct 2, 11:52 pm, DanB <b351...@yahoo.com> wrote:
> You cant always rely on Systems Monitor.  Look at the global:
>      ^HLMA("AC","O",    <-- thats "O" not zero
>
> It will tell you which logical links have outbound messages queued for
> sending.
>      ^HLMA("AC","O",#870 ien, #773 ien)=""

Dan, that command didn't work. Did I do it wrong. It wouldn;t let me
run without the quotes
GTM> W ^HLMA("AC","O","#870 ien","#773 ien")
%GTM-E-GVUNDEF, Global variable undefined: ^HLMA("AC","O","#870
ien","#773 ien")

Sam Habiel

unread,
Oct 3, 2009, 1:30:23 PM10/3/09
to hard...@googlegroups.com
Richard,

You are not yet a genius in mumps.

You are looking for 'ZWRITE ^HLMA("AC","O",*)'

You can also the global peeker 'D ^%G' and look at the same node using
the same syntax as above.

Sam

rlb

unread,
Oct 4, 2009, 8:20:51 PM10/4/09
to Hardhats
>
> You are not yet a genius in mumps.
>
> You are looking for 'ZWRITE ^HLMA("AC","O",*)'
>
Nope, not even a nubile yet in Mumps. At least I tried putting in
the W for Write as that wasn't in the original command posted by DanB.

rlb

unread,
Oct 5, 2009, 10:16:24 PM10/5/09
to Hardhats
Bump this one. We need someone in the community to help us with HL7
setup in VistA so we can connect to Mural MPI.

CJ

unread,
Oct 7, 2009, 1:39:53 PM10/7/09
to Hardhats
I have not been able to get the TCP link up either trying with MailMan
instead I want to see what kind HL7 output Vista produces. Also I
downloaded GUIMail2.3 that can get the MailMan messages from the PC.
Probably need mailman working properly first to get HL7 to queue
messages to mailman. Is the MailMAN link on HL7 working on the GTM
port i.e worlvista does any one know ?

HL7 LOGICAL LINK
--------------------------------------------------------------------------------


NODE: MailManHL7 DESCRIPTION:

INSTITUTION:

MAILMAN DOMAIN:

AUTOSTART: Enabled

QUEUE SIZE: 10

LLP TYPE: MAILMAN

DNS DOMAIN: BETA.VISTA-OFFICE.ORG
_______________________________________________________________________________





COMMAND: Press <PF1>H for
help Insert

DanB

unread,
Oct 7, 2009, 2:12:18 PM10/7/09
to Hardhats
Dont know if I'd go the MailMan HL7 route.

I do believe that HL7 v1.6 package works with GTM. A few months ago I
was asked to help with troubleshooting a non-responsive HL7/GTM
system. I found that some of the HL7 patches weren't installed
correctly (routines at wrong release level and/or missing code). Not
sure which VistA distribution it was.
Reply all
Reply to author
Forward
0 new messages