[Jared Miller]

Thanks guys! I had gotten to the point of Kevin’s suggestion (so clearly I’m no tcl expert either) prior to coming for help. I am getting the result I’m looking for now after reviewing Charlie and Mark’s posts.

Before I was only getting “Cysto-Grafin,” so the 25 ml was getting cut off. Now I’m getting all the data needed, “Cysto-Grafin, 25 ml”

[Jared Miller]

Charile, thanks for the link to the XML tutorial. That’s some good reading material.

As for my issue, yes I was able to compile but am still not to the point of going from XML to HL7. I have created the Xlate but I receive the error below when trying to send a message through. Thoughts anyone?

[xlt :xlat:ERR /0:     um_xlate:06/24/2014 15:20:22] [0.0.67910] Xlate ‘X_ALLSCRIPTS_XML.xlt’ failed: Input validation errors: Error generated during parsing. – Unknown element ‘OutboundDataFeed’ – Line 2, Col 396

[Jared Miller]

Keith, did you ever get this figured out? I’m working on my first XML inbound interface right now and was curious about your question.

Thanks

[Jared Miller]

Yes I am using 5.8 and progress has been made. I’ve downloaded Oxygen and that has helped. From looking the XSD files and the test message from the vendor it seems that ‘OutboundDataFeed’ is the name of the base schema. I was able to compile ‘OutboundDataFeed.xsd’ and ‘OutboundDataFeed_V3.0.xsd’ so I’m not exactly sure which one to use in Xlate.

I’ve attached a test message and a screen shot of my successful compile.

Thanks!

[Jared Miller]

Well since I won’t know how many DG1 segments there will be in a given message or in which DG1 segment will have a ‘VI’ in DG1-6 (which indicates a reason for visit diagnosis) I think I have to use the ITERATE function, don’t I?

[Jared Miller]

Yes, : the field separator for Star. I will have to clarify with the vendor, but according to their specs the ZRV will accept 3 codes. The segment needs to repeat if there are both ICD-9 and ICD-10 codes.

Here’s the vendor spec for the ZRV:

ZRV

[Jared Miller]

Jim,

The ZRV segment is defined at optional/repeating, but the fields of the ZRV are just optional currently.

[Jared Miller]

Thanks Levy. That makes sense and this code is working for me. I appreciate the assistance!

[Jared Miller]

I received the exact same PANIC errors last night, which resulted in all the interfaces being shutdown temporarily.  I just had to restart everything and they interface threads have been operating as normal since but I have no explanation as to why the PANIC errors occurred.

Have you been able find reason for why it happened to you??

[Jared Miller]

Thanks, I have it working now.

[Jared Miller]

Thanks for the input…I have been trying to implement the code provided by Scott, but keep getting this error below.  I have tried several different things, but can’t get past this error:

Code:

[sms :sms :ERR /0:    neobrowse] Tcl error:
msgId = message0
proc = ‘kill_pao’
args = ”
result = ‘extra characters after close-brace’
errorInfo: ‘
extra characters after close-brace
   while compiling
“if { $pv1_18_1 == “PAO” && $pid_3_4 == “W” ”
   (”run” arm line 40)
   invoked from within
“switch -exact — $mode {
       start {
           # Perform special init functions
   # N.B.: there may or may not be a MSGID key in args
      …”
   (procedure “kill_pao” line 6)
   invoked from within
“kill_pao {MSGID message0} {CONTEXT sms_ob_data} {ARGS {}} {MODE run} {VERSION 3.0}”‘

[Jared Miller]

Here are the steps I follow for the 3.8.1 reboot:

1. Shutdown all processes in production.

2. Shutdown Netmonitor and Lock Manager.

3. Open shell window and login.

4. Stop the HOSTSERVER

a. Type hciss

[Jared Miller]

Well the real world problem is that we are working on implementing a number that the nurses can give to a patients family to refernce when calling to check on the patient’s status.  The number is setup as 11 digits in our registration system and is being sent thru the ADT feed to our clinical system.  We were just told yesterday that 11 digits is too long of a number for the nurse to write down and they wanted the middle zeros removed to make the number shorter.

Robert, I was able to get your suggestion to work for me.  Thanks!

[Jared Miller]

Thanks for suggesting the search…I had done a search a few weeks ago and didn’t find anything I was able to get to work for me, however, today I find something I was able to adapt into a working solution.

   # Here we retrieve the data from our original message

   set msg [msgget $mh]

   

   #Variable to set what is sent in the body of the email

   set EmailMsg “$msg”

   #Variable to set what is sent as the email subject

   set EmailSub “Invalid Registration – NO MRN”

   #Variable to set what email addresses to send to

   set Emails “sample@tmcmed.org”

   # Now we need to determine our field and subcomponent seperatoprs

   set field_sep [csubstr $msg 3 1] ;# HL7 field separator    

   set sub_sep [csubstr $msg 4 1] ;# HL7 subfield separator    

   # Here we spilt the original message into a list of the segments contained within

   set segmentList [split $msg r]

   # Now we iterate over each segment in our list.

   foreach segment $segmentList {

if {[cequal [crange $segment 0 2] PID]} {

set fieldList [split $segment $field_sep]

set pid_3 [lindex $fieldList 3]

                   # split PID-3 on the sub-seperator

                        set pid_3_list [split $pid_3 $sub_sep]

                   #  get the first element in PID-3

                      set pid_3_1 [lindex $pid_3_list 0]

         

   if {[cequal $pid_3_1 “”]} {

catch [exec << $EmailMsg mailx -s $EmailSub $Emails]

lappend dispList “KILL $mh”

return $dispList

} else {

lappend dispList “CONTINUE $mh”

return $dispList

}

   }

}

   }

[Jared Miller]

Ariba,

Thanks for your response.  When an update is done do you get another BAR message or do you receive at ADT^A08?  Prior to learning of the medical records trigger, the only place we were seeing diagnosis & procedure codes were in A08s so I am curious to see if this is what you are referring to.

Jim,

Thanks for your response as well.  That was good input to have.

[Author]

Replies