[Jeff Manley]

A05 messages are getting the same error.  Here is a sample message from our Epic vendor.

MSH

EVN

PID

PD1

NTE

PV1

PV2

NTE

GT1

IN1

IN1

[msg :RecP:WARN/0:EPIC_ADT_xlate:10/23/2013 13:36:21] WARNING: Multiple segments with same address were found in message format ‘2.3 epic ADT_A05’ in file /cloverleaf/cis6.0/integrator/live/formats/hl7/2.3/epic/ADT_A05. This may lead to incorrect parse or translation.

[msg :RecP:WARN/0:EPIC_ADT_xlate:–/–/—- –:–:–] Detailed warning information:

[msg :RecP:WARN/0:EPIC_ADT_xlate:–/–/—- –:–:–]     Segment ‘NTE’ with address ‘0(0).NTE’ found at lines 13,17,20

So not much we can do here except have Epic change their messages(unlikely) or just deal with the warning messages?

[Jeff Manley]

We need to do the exact same thing.

Any help would be greatly appreciated.

Jeff

[Jeff Manley]

We get the same every now and then.

[tps :tps :ERR /0:   TO_ESI_ADT:09/17/2010 02:03:54] ‘KILL ‘ (returned by ‘check_ack ‘) does not match { }

I wonder if it the timing issue like was discussed here:

https://usspvlclovertch2.infor.com/viewtopic.php?t=3562

[Jeff Manley]

Again, thanks to everyone.

I checked this morning and the only thing in the log is “Engine idle”.

Very nice!

[Jeff Manley]

Works perfect.  No dashes and no errors.

Thanks everyone!

[Jeff Manley]

I went from:

if [llength $xlateInVals] {

set xlateOutVals [string map {- “”} $xlateInVals]

}

no dashes in the output

to this:

if [llength $xlateInVals] {

lassign xlateOutVals [string map {- “”} $xlateInVals]

}

dashes show back up in the output

[Jeff Manley]

Ok, I found an offending message.

There was a xlt, and in the Z1N segment, it was looking at Z1N-6(insurance holder number).  99% of the time it was the MRUN number which is ##-##-##.  A few messages now and then have a 8 digit number ########.

Someone had written a tcl proc and placed it in the copy action.  It looks like this:

lassign $xlateInVals mrun

if [llength $xlateInVals] {

  set first [csubstr $mrun 0 end]

  set new_first [split $first -]

  set second [csubstr $mrun 3 end]

  set new_second [split $second -]

  set new_third [csubstr $mrun 6 end]

  # set new_third [split $third -]

  lassign $new_first first

  lassign $new_second second

  lassign $new_third third

  set xlateOutVals

}

Seems like what they are trying to do is to take the dashes out of the MRUN.

Can I do something simple like the following?

lassign $xlateInVals mrun

if [llength $xlateInVals] {

set xlateOutVals [string map {- “”} $xlateInVals]

}

Testing of my code allows the dashes to be removed and the number without dashes no longer causes error messages.

[Jeff Manley]

I can test the xlt, but the error does not happen for every message.  It is just once in a blue moon.

[Jeff Manley]

More info from the site daemons – view logfile

[icl :tcpi:ERR /0:  hcimonitord:08/19/2009 16:09:56] write failed: WSAECONNRESET

[cmd :cmd :INFO/0:  hcimonitord:08/19/2009 16:09:56] Inrecoverable socket error.  Closing connection.

[aler:aler:INFO/0:  hcimonitord:08/19/2009 16:09:56] Removing alerts and wants for connection 0xeb7f30

[icl :tcpi:ERR /0:  hcimonitord:08/19/2009 16:09:58] write failed: WSAECONNRESET

[cmd :cmd :INFO/0:  hcimonitord:08/19/2009 16:09:58] Inrecoverable socket error.  Closing connection.

[aler:aler:INFO/0:  hcimonitord:08/19/2009 16:09:58] Removing alerts and wants for connection 0xc90f48

[cmd :cmd :INFO/0:  hcimonitord:08/19/2009 16:09:58] Received command: ‘iwant state pstate’

[cmd :cmd :INFO/0:  hcimonitord:08/19/2009 16:09:58] Doing ‘iwant’ command with args ‘state pstate’

[aler:aler:INFO/0:  hcimonitord:08/19/2009 16:09:58] New alert #6:

{VALUE status} {SOURCE all} {MODE delta} {WITH -1} {COMP diff} {FOR once} {ACTION status}

[aler:aler:INFO/0:  hcimonitord:08/19/2009 16:09:58] New alert #7:

{VALUE ps} {SOURCE all} {MODE delta} {WITH -1} {COMP diff} {FOR once} {ACTION status}

[cmd :cmd :INFO/0:  hcimonitord:08/19/2009 16:09:58] Received command: ‘iwant alerts’

[cmd :cmd :INFO/0:  hcimonitord:08/19/2009 16:09:58] Doing ‘iwant’ command with args ‘alerts’

[aler:aler:WARN/0:  hcimonitord:08/19/2009 16:09:58] Creating AlertAction: cascade

[aler:aler:INFO/0:  hcimonitord:08/19/2009 16:09:58] New alert #8:

{VALUE action} {SOURCE notify} {MODE actual} {WITH -1} {COMP none} {FOR once} {ACTION cascade}

[cmd :cmd :WARN/0:  hcimonitord:08/19/2009 16:09:58] alerts client 0xd15e70

[icl :tcpi:ERR /0:  hcimonitord:08/19/2009 16:09:58] write failed: WSAECONNABORTED

[cmd :cmd :INFO/0:  hcimonitord:08/19/2009 16:09:58] Inrecoverable socket error.  Closing connection.

[aler:aler:INFO/0:  hcimonitord:08/19/2009 16:09:58] Removing alerts and wants for connection 0xd15e70

[cmd :cmd :WARN/0:  hcimonitord:08/19/2009 16:09:59] Invalid connection, tcpip =  0x0

[pti :sign:WARN/0:  hcimonitord:08/19/2009 16:09:59] Thread 0 received signal

[Jeff Manley]

The only thing that scares me about the code above is that it might delete the directory, but for some unknown reason, not able to delete the site from the server file.  If that happens, problems could arise.

Would it be better to delete the site from the server file and if that went ok, then delete the directory?

[Author]

Replies