Tcl failure in Trxid determination(103) – reruns fine

[Lawrence Nelson]

Over the course of a last couple weeks – We’ve had messages fail for this:

msgState          : Tcl failure in Trxid determination (103)

When the message is located and reprocessed from SMAT starting at

Inbound pre-TPS – the message processes without incident each time.

We route messages by UPOC – the TCL in question hasn’t been changed in several months.

Thoughts on why this hiccup occurs?

Lawrence Nelson
System Architect - MaineHealth IT

Topic

[Jim Kosloskey]

What is the Tcl error shown iin the log?

email: jim.kosloskey@jim-kosloskey.com 30+ years Cloverleaf, 60 years IT – old fart.

[Lawrence Nelson]

[tcl :out :INFO/0:  p_nap_xlate:05/13/2016 09:30:09] position 3 pipe fieldSep = |

[tcl :out :INFO/0:  p_nap_xlate:05/13/2016 09:30:09] position 4 compSep = ^

[tcl :out :INFO/0:  p_nap_xlate:05/13/2016 09:30:09] position 7 subSep = &

[tcl :out :INFO/0:  p_nap_xlate:05/13/2016 09:30:09] PV1 is in position 2 ? 2

[tcl :out :INFO/0:  p_nap_xlate:05/13/2016 09:30:09] pv1Flds = PV1 1 O BFHC2^^^BFHC2 {} {} {} 1306801444^D^R{} {} {} {} {} {} {} {} {} {} {} {} {} {} {} {} {} {} {} {} {} {} {} {} {} {} {} {} {} {} {} {} {} {} {} {} 201605111059 {} {} {} {} {} 2944560

[tcl :out :INFO/0:  p_nap_xlate:05/13/2016 09:30:09] ward_idSeg = BFHC2 {} {} BFHC2

[tcl :out :INFO/0:  p_nap_xlate:05/13/2016 09:30:09] PV13 ward_idamp0 = BFHC2

[tcl :out :INFO/0:  p_nap_xlate:05/13/2016 09:30:09] PV13 ward_idamp1 =

[tcl :out :INFO/0:  p_nap_xlate:05/13/2016 09:30:09] PV13 ward_idamp2 =

[tcl :out :INFO/0:  p_nap_xlate:05/13/2016 09:30:09] PV13 ward_idamp3 =

[tcl :out :INFO/0:  p_nap_xlate:05/13/2016 09:30:09] PV13 ward_idamp4 =

[tcl :out :INFO/0:  p_nap_xlate:05/13/2016 09:30:09] compsep = ^

[tcl :out :INFO/0:  p_nap_xlate:05/13/2016 09:30:09] maplist =  ^ “” & “”

[tcl :out :INFO/0:  p_nap_xlate:05/13/2016 09:30:09] sendingFac = HEALTHREACH^0001

[tcl :out :INFO/0:  p_nap_xlate:05/13/2016 09:30:09] rcvFac = Billing System

[tcl :out :INFO/0:  p_nap_xlate:05/13/2016 09:30:09] ward_id = BFHC2BFHC2

[tcl :out :INFO/0:  p_nap_xlate:05/13/2016 09:30:09] msgType = ORM

[tcl :out :INFO/0:  p_nap_xlate:05/13/2016 09:30:09]

[tcl :out :INFO/0:  p_nap_xlate:05/13/2016 09:30:09]

[tcl :out :INFO/0:  p_nap_xlate:05/13/2016 09:30:09]

[tcl :out :INFO/0:  p_nap_xlate:05/13/2016 09:30:09]

[xlt :rout:ERR /0:  p_nap_xlate:05/13/2016 09:30:10] TrxId determination via Tcl failed: No recipients specified

[xlt :rout:ERR /0:  p_nap_xlate:–/–/—- –:–:–] “/home/hci/dead.letter” File exists , args()

[tcl :out :INFO/0:       fr_nap:05/13/2016 09:30:12]

[tcl :out :INFO/0:       fr_nap:–/–/—- –:–:–] fr_nap/tps_hl7_raw_ack – msg rcvd at 2016-05-13 09:30:12

Lawrence Nelson
System Architect - MaineHealth IT

[Keith McLeod]

What are you using for a TrxId? Are you pulling multiple fields to determine a TrxId and then routing accordingly?   Has the data changed?

[Lawrence Nelson]

Pretty straight forward –

– based on this

#Bring in the message and break it by carriage return

    set msg [msgget $mh]                                     ;# get the current message data

    set maplist { n “” }

    set msg [string map $maplist $msg]

    set fieldSep [string index $msg 3]                    ;# determine field separator

    set compSep [string index $msg 4]                  ;# determine component separator

    set subSep [string index $msg 7]                    ;# determine component ampersand  

    set segList [split $msg r]                               ;# create list of segments

#MSH segment work

    set mshSeg [lindex $segList 0]                          ;# pull MSH segment from list

    set mshFlds [split $mshSeg $fieldSep]                ;# split MSH segment into list of fields

    set sndApp [lindex $mshFlds 2]                          ;# get Seding App (Lab or Mic)

    set sendingFac [lindex $mshFlds 3]                     ;# get Sendind Facility

    set rcvFac [lindex $mshFlds 5]                            ;# get Receving Facility

    set msh9 [split [lindex $mshFlds 8] $compSep]   ;# get Message Type list of subfields

    set msgType [lindex $msh9 0]                           ;# get Type

    set msgTypeNum [lindex $msh9 1]                     ;# get Type num

 if {“HEALTHREACH^0001” == $sendingFac} {set trxID “HEALTHREACH_${msgType}”}[/b]

Lawrence Nelson
System Architect - MaineHealth IT

[Keith McLeod]

Looks like your trxId should have been HEALTHREACH_ORM based on the previous posts.  Who is the recipient of the email?  Is this code contained in the upoc tcl?  I think the error is at this point causing the tcl to fail.  What version of Cloverleaf are you on?  Can you show error details on the message with msg state 103?

or use ‘hcidbdump -e -m -c | more’ without the 0.0. preceding the msg ID.  This may give you more insight as to exactly where in the code it failed.  Key word is ‘may’.

[Lawrence Nelson]

We are on 6.0

I will have to wait until this occurs again.

Again, it’s very infrequent and just started recently – with a TRXID tcl that hasn’t been changed in months.

Also to repeat – when the message is reprocessed or run through the testing tool – it processes fine – and also doesn’t fail in the tool.

Lawrence Nelson
System Architect - MaineHealth IT

[Author]

Replies