Unsupported Transaction IDs

May not be much help, but have you looked at the process log?  Unsupported TrxID doesn’t always mean what it says.  If there’s more to the problem, the process log should give you a little more insight.

Steve

I don’t know if this is your problem or not, but when we set up our wild card routes we use a pipe “|” between the values like this…

Not sure how it would interpret the comma?

I can’t remember the specific cases.  However, the errorDB will report an unsupported TrxID, but the process log will show the error as something else.  ‘Unable to load xlate’ comes to mind, but I don’t think that’s right.

I’m not sure what you’re problem may be.  I’ve used wildcard routing in a similar fashion without any issues.

Sorry I couldn’t help.

Steve

I see now the square brackets with the commas so that probably works.  I’ve always used the parens and pipes so that caught my eye.

If some messages are going, some are not, then I might look more closely at the translations?  What are you doing in the xlates?  I see the 17s and 34s are raw… is there a TCL proc there?

Can you show us the metadata for one of these messages in the error database?

Are these going to a real destination or are they routed back into the engine?

You shouls *ALWAYS* verify your regexp whne using wildcards!

You state a regexp like:  

ADT_A(01|02|03|04|05|06|07|08|11|13|17|35|36)

which I would code like:

ADT_(A((0[1-9])|(1[137])|(3[56])))

In tcl or hcitcl I would then do something like:

set regexp {ADT_(A((0[1-9])|(1[137])|(3[56])))}

for {set i 1} {$i < 40} {incr i} {    set ADT ADT_A[format %02d $i]    if {![regexp — $regexp $ADT]} {echo $ADT FAILED} } All of the ones I want should pass and all of the others should fail

Can I suggest you do as Charlie suggest.s

Pull your transaction out into a tcl prompt and test them.

I think the results you get will surprise you a lot.

I’m pretty sure those are not the results you were expecting.

But even at that I’m not sure why the ADT_A34 would have failed one of the above expersions should have covered it.

So first get them tested and working as desired the come back to the Invalid transaction.

Great idea Charlie…

It may not be the only problem, but it’s definitely a problem.   😀

You might want to check the A17/A34 route and see if wildcard is actually checked. If it is, did you bounce the process after making the change?

Please post the output from the message in the error database:

Curious to see if the message is data or ack message.

hcidbdump -e -m -L -c

To get the message ID you can list what is in the error database by typing hcidbdump -e

This output will give us more info to go on..

Darren:

I do not believe you were taught to configure a Wildcard route as you ststed above, at least not at a Quovadx class.  Perhaps you mis-remembered what was taught?

We *ALWAYS* teach that Wildacrd uses the smae regular expression engine as Tcl.  What you have defined is not a valid regular expression

Get Brent’s latest Tcl book and read the chapter on regular expressions.

Does the wild card expression have to match the whole transaction id?


tcl>set regexp {ADT_A(10|12)}

tcl>for {set i 1} {$i < 40} {incr i} {
[code]
tcl>set regexp {ADT_A(10|12)}

tcl>for {set i 1} {$i < 40} {incr i} {

i think i am more lost now than before.

Darren,

Is this the actual data in the message(‘MSH|***i’ took out the patient data on purpose***x0d’), because this would bomb for an invalid TRXID, as there isn’t an event type (i.e. ADT^A01, etc) in MSH:9.  If this is not the actual data message( assuming you had edited it for posting), then the ‘xlate error’ message would indicate that there is something happening in the Xlate.  I would dump the message to a file, and run it through the testing tool using the appropriate Xlate; you should see the error occur in the tester.

Jim Cobane

Henry Ford Health

Here is a good, single page, cheat sheet I found for regular expressions:

http://www.night-ray.com/regex.pdf” class=”bbcode_url”>http://www.night-ray.com/regex.pdf

Darren,

You need to post only the MSH segment which does not have any patient identifiable data in it.  Specifically, what is in MSH-9 on the inbound message? You should see something like |ADT^A08|.

Nobody has asked, but what do you have set up for “Trx id determination Format” on the Inbound tab of your inbound thread? It is the value that is returned from here that the regular expression in the Route Detail must match. When it doesn’t match any of the routes, you get “Unsupported Trxid”.  This is also where the ADT^AXX gets converted to ADT_AXX. Whether you have an xlate really has nothing to do with it.

You might want to check the format of your regular expression.  Unless I am reading the documentation wrong, stuff inside a square brack represents all the things that match a single character.  So

ADT_A[10,12] will match ADT_A1 ADT_A0 ADT_A, ADT_A1 (again) or ADT_A2.  It does’t matter what comes after these (so all the ADT_A10 – A19 and A20 – A29 work).

If you just want ADT_A10 or ADT_A12, try something like ADT_A1[02]

Can you check and see if the Xlate has been configured with the right variant.

Open the Xlate and go to file -> reconfigure and see if the format you picked for inbound or outbout is ok.

I know it sounds simple but sometimes that might work. Good Luck  😉

Can you check and see if the Xlate has been configured with the right variant.

Open the Xlate and go to file -> reconfigure and see if the format you picked for inbound or outbout is ok.

I know it sounds simple but sometimes that might work. Good Luck  😉