[john benevento]

Hi Bryan

Please disregard the last post – it works!

The only other thing I need to modify is to include the value of PID-4 (patient medical record number) in the name of each file.  Do you know if it is possible to include specific message data in the filename?

John

[john benevento]

Thanks for your help, Bryan – I’ll give it a try.  Where would I create the Tcl Procedure?  I assume there’s an editor in Cloverleaf to accomplish this.  Can I just copy and paste the code from the post?

John

[john benevento]

Thanks, Bryan.  Unfortunately, I’m not too familiar with .tcl procs and am just starting to learn the basics.  I would really appreciate it if you can provide me with some of the code you’re using – perhaps I could figure out how to modify it for my own thread.

John

[john benevento]

The problem only occurs when the value of MSH-10 is the same in two transactions sent in the same batch.  When I send out a batch consisting only of the original transaction plus the newly-created one (with MSH-10 incremented by 1 in the xlate), it works fine.  However, if there are additional transactions in the batch, and if one of them duplicates the value of MSH-10 in the new transaction, everything stops flowing and inbound replies (of the new transaction) are generated and placed in pending (state 11) every 60 seconds (the timeout value).  I don’t know Cloverleaf well enough to understand what’s going on, but a TCL that increments MSH-10 for every transaction (and provides an accurate message count in BTS-1) would probably solve the problem.

[john benevento]

Thanks for your suggested code – I’ll give it a try.  The problem I think has to do with the Message Control ID in MSH:  it is not incremented when the new transaction message is created, so you get two messages with the same ID.  Incrementing it by one in the xlate doesn’t help if you have another message with the same (new) ID.  I am not familiar with TCL so I can’t write a proc to accomplish this.  Is there a simple way to increment the ID in the xlate for all the messages?

[john benevento]

Vince,

Based on your suggestion, I created an xlate consisting of a BULKCOPY, a SEND, an IF statement to catch the charge to duplicate (containing a COPY to move in the new charge code, and another SEND), and finally a SUPPRESS.  The problem I’m having is that the new charge transaction messages remain in pending and are not transmitted unless I stop and start the thread.  Is there something I’m missing?  Thanks.

[john benevento]

Yes it does – thanks for your help!

[Author]

Replies