[Weston Olmstead]

Yes, my thread was using the DB Protocol, and I completely forgot about using hcitpsmsgkill. I just added that to my route replies route as a raw route tps and that that resolved my issue, thank you.

[Weston Olmstead]

I’m using the built in connectors for Cloverleaf (database protocol-outbound). I figured out what I needed to do for my use case anyway (as I was trying to avoid using TCL if possible).

1. Create a new database driver & connection for MSSQL (Options –> Site Preferences –> Database Configurations)
2. Configure a database schema for a destination table (Configuration –> Database Schema Configurer)
3. Create an XLate file from HL7 to Database Schema and select the Schema from #2.
4. Map the HL7 fields to my schema fields & save the Xlate.
5. Create a new inbound TCP/IP thread and a Database outbound thread
6. Set up a route between the two threads with the Xlate from step #4.
7. Edit my outbound thread to use the approriate fields.

 

I was getting hung up on the last step, as I thought I needed to reference the specific fields from my xLate as values in the outbound, but the schema configurer takes care of that already. If I don’t use “whole message” as the input option, it will already know what I populated in the xLate and use that value.

 

Thanks so much for all the help!

[Weston Olmstead]

Thank you for the info. An additional question. If I attempt to use the built-in cloverleaf functions instead of writing a JDBC / TCL function how to extract a specific field out into a variable and pass it to the outbound thread. Does the Database connector understand variables?

[Weston Olmstead]

That fixed it. Thank you!

[Weston Olmstead]

No, this is on a Windows Server.

[Weston Olmstead]

Thanks for the replies so far.

1. Yes, I am using the same inbound & Outbound Variants. I’m just attempting to copy some data to additonal fields in the same message format.

2. I did reconfigure the xLate, and see the Z Segments included in the variant in the xLate.

[Weston Olmstead]

Bill,

“set xlateOutVals

[Weston Olmstead]

Thank you, that clarifies things! That what I get for trying to be creative  with easily readable variable names :). I didn’t know that was a inherient requirement.

Thanks again!

[Weston Olmstead]

Thanks for the feedback. %group1 are the actual name of my variables defined in the iterate instead of %g1 or %g2 (i changed them so they would be easier to see from the screenshot. I’ll re-check the values for each iterate are correct (to my knowledge) and take screenshots of  each iterate to post on here shortly.

REferring to that basis, I believe those are specific to the structure of the HL7 definition, so I don’t think the one provided in your screenshot will work for my scenario.

[Weston Olmstead]

Jim / Robert,

Thank you both for the great ideas. I did end up clearing these out in the manner that Jim suggested, because there are other nested NTE segments in these results.

Thanks again!

[Weston Olmstead]

That is what I had in mind, but I’m still a bit fuzzy on how the TCL calls within cloverleaf work so I wasn’t able to get it work properly (I’ll have to revisit it as a learning exercise).

I ended up doing it in an xLate, it turns out the issue was my structure / message format. If anyone viewing this thread later is looking for a solution, I’ve included it below.

---

I ended up creating a message format/structure as one big set, as follows:

{

[Weston Olmstead]

Thank you all for the assistance. Its amazing how another set of eyes can catch a simple mistake!

I also have a difficult time determining to use quotes or curley brackets, but that example was very helpful. Thank you also for the advice on string mapping, I’ll look into that!

---

Edit: Forgot to include the solution that worked for me in case others find this thread. The regsub is currently working, but I’m looking into character maps as that seems the proper way to do this now.

proc tpsConvertCRLFToLF { args } {

  set argList [keylget args ARGS]    

  keylget args MODE mode               ;# Fetch mode

  switch -exact — $mode {

      run {

          set msgID [keylget args MSGID]    

          set msgText [msgget $msgID]        

regsub -all  {rn} $msgText “r” msgText

          msgset $msgID $msgText

          return “{CONTINUE $msgID}”

           }  

      default {

      error “Unknown mode ‘$mode’ in tpsMessageFilter.”

      }

  }

}

[Weston Olmstead]

Thank you for the assistance, that worked.

If you don’t mind further elaborating so I can fully understand: How did Cloverleaf know where the start and stop of each list element was?

When I get my input value,”First M” ,  in the TCL I’m doing that by by setting a variable to  lindex of xlateInVals 0. I was under the impression lindex is grabbing the first entry in the list xlateInVals in its entirety and assigning it to my input value.

Why does the TCL/Cloverleaf then think they are different elements when I assign it back out to xlateOutVals since I grabbed the first element only for my input?

[Author]

Replies