[Jorge Medina]

Hey everybody  –  finally got this moved to production, so I am posting the configuration used. Attached are the steps used to set up the thread, the tcl used to create the soap envelope and the tcl to remove the soap envelope.  As you read thru the attached, feel free to point out set up which could be improved upon.   🙂

Thanks!

Attachments:

You must be logged in to view attached files.

[Jorge Medina]

Hi Jim –

There is a way to set up the WS to put the HL7 message in a soapwrapper. Unfortunately, I was not able to solve that puzzle. 🙁

What I ended up doing is creating a tcl and used it as a post proc at the route detail. The tcl sets headers and footers, then sets new message. Here is a snippet:

set msg [msgget $mh]

set soapheader1 {<soap:Body>}
set soapheader2 {<urn:submitSingleMessage>}
set soapfooter2 {</urn:submitSingleMessage>}
set soapfooter1 {</soap:Body>}

set newMessage $soapheader1$soapheader2$msg$soapfooter2$soapfooter1

Hope this helps

Jorge

 

 

[Jorge Medina]

Paul – yes we do have CAA. I set up a java/ws-client and am generating error:

msgState : Bad data (419)

BADDATA caught exception trying to processMessageFromCloverleaf: Caught bad data exception trying to process message from Cloverleaf

 

I am definitely open to a screen share as I am getting nowhere.

Thank you for your help! Jorge

[Jorge Medina]

I’m trying to set up a vaccination query to our state agency, Immtrac.
I set up a ws-rawclient:

Bus: only checked “Message Logging Enabled”
Conduit: added proxy and enabled TLSv1.2
Raw Consumer: filled in address; Default Method is GET; Trx ID Determination set to “VALUE”; Trx ID Value set to ‘ ‘ and only Cloverleaf Copy Driver Control is checked.

DISCLAIMER: The configuration for the thread was derived from the Cloverleaf example RawClient thread. It’s not like I suddenly got smart and figure all this out over the weekend 🙂

Even though the response code was a 200, the actual response message was more of a java script for building a web page, see attached. I am waiting to here from Immtrac why this type of response was generated.

Maybe the message structure is incorrect?

Thanks!

Attachments:

You must be logged in to view attached files.

[Jorge Medina]

Jim,

Thank you for your response. Not the answer for which I was looking , but now I can direct my efforts elsewhere to resolve this concern.

Thanks again,

Jorge

[Jorge Medina]

Jim,

We receive NTEs with the strings MAYO & *MAYO  The request is to remove NTEs with the string *MAYO  Then add a message if remaining NTEs do not contain the string MAYO  The plan was to copy @null to outbound if *MAYO is found then iterate thru outbound looking for string MAYO.

If I iterate thru inbound looking for MAYO, the string will always be found regardless if it was nulled out on the outbound and no message will be added. However, I think I may have found a work around based on setting flags if an asterisk and MAYO are found in the same NTE.  It would still be good to know if you can or cannot iterate through the outbound.

Thank you for your response, Jorge

[Jorge Medina]

Rentian thank you for your prompt response. I have tested and the desired results are not acheived. Some detail as to what is the goal:  the inbound variant is the form:

{

[ OBX ]

[{ NTE } ]

}

In the NTEs we receive messages stating “Testing performed at Mayo lab….”

Of these messages, some contain an asterisk. The goal is to remove the NTEs which contain an asterisk. Then go back thru the outbound variant and if no NTEs contain “Mayo” add a message. If an NTE does contain “Mayo” no further action required. I have attached a screen shot of the translate for further details. Thank you in advance for your assistance. Jorge

[Author]

Replies