[Mike Wilson]

Larry,

Thank you very much.  This is the first XML dealings I have had so I was a bit lost.  I appreciate your help.  I am going to try and get it working today.  What I had done was write a proc to get the HL7 ack out of the message to not worry about the XML.  But I want to get it working fully.  Thank you again.

MIke

[Mike Wilson]

Levy Lazarre wrote:

Mike,

Did you get this problem resolved? I see a couple of issues with the XSD. Perhaps you already have a fix.

No I have not gotten it fixed.  If you have some insight I would appreciate it.

[Mike Wilson]

James Cobane wrote:

Mike,

Take a look at the ‘intersect’ or ‘intersect3’ commands.

Thanks,

Jim Cobane

Henry Ford Health

Ok, here is what I came up with. As long as something in the lists matches I pass the message.  Is there a more efficient way to do this?

set LISTA { 1 2 3}

set LISTB { 3 4 5}

set MATCHES [intersect $LISTA $LISTB]

if {([llength $MATCHES]) > 0}

    continue

else

    kill

Thanks for all the help.

[Mike Wilson]

Max Drown wrote:

Here’s another example of using NetConfig args.

# NetConfig Args Example 1: {PATTERN {trigger}}
# NetConfig Args Example 2: {PATTERN {^PEPPP[VHNW][HN]$}}

proc tps_fileset_dirparse_regex { args } {
[code]# NetConfig Args Example 1: {PATTERN {trigger}}
# NetConfig Args Example 2: {PATTERN {^PEPPP[VHNW][HN]$}}

proc tps_fileset_dirparse_regex { args } {

[Mike Wilson]

Here it is:

I haven’t tested this with every operator.  But the usuals work so far, >,<,==, etc.

I can pass the 4 arguments and do whatever filtering is needed.  

Code:

if {[expr {$seg_fld_length} $oper {$crit}]} {
               echo “meets the IF $crit: Remove it”
           lappend dispList “KILL $mh”
           } else {
echo ” Does not meet IF: Keep it”
               lappend dispList “CONTINUE $mh”
           }

[Mike Wilson]

just needed the curly braces around the 2 variables.  {}.  I thought I had tried that with no success.  This works great now.  Thanks.

[Mike Wilson]

Not sure why the & was working to store the original replaced character but I fixed it by adding \ in front of the &.  like so “\"”  not sure of the reasoning.

[Mike Wilson]

David Barr wrote:

I’d try setting the inbound encoding to windows-1252, then using the regsub with u2019. Setting the encoding to 1252 should allow Cloverleaf to properly convert the characters to Unicode, then you can use the Unicode character code to replace with the plain ASCII equivalent.

That did the trick!  What a pain.  Thank you David!

[Mike Wilson]

the Vendor is Meditech C/S 5.66.  I have the encoding set to bypass right now.  I have been changing it to see if I can get any change with no luck.

[Mike Wilson]

David Barr wrote:

From the debug window it looks like your bad character has a hex value of hex 92, so you could use the same regsub but replace the u2019 with x92.

David, I have tried that as well.  It simply wont recognize that character with my TCLproc.  Im stumped.

[Mike Wilson]

unfortunately that didn’t work either.  The sections in bold are where the issue is.

Here is what the actual text from the EMR looks like:

Comparison is made to the patient

[Mike Wilson]

Whats the “u2019” ?

Is that the code for that specific character?

[Mike Wilson]

I was able to resolve the issue.  The vendor did not actually want the credentials in an HTTP header.  They wanted every message to start with them…  Not documented of course.

[Mike Wilson]

Im in the same boat.  I can not authenticate to them.  Ive tried every authentication option in the GUI.  I added the Authentication header with no luck.  I see nobody replied to your post.  Did you ever figure it out?

[Mike Wilson]

I just requested and received our OID last month.  What questions do you have?

[Author]

Replies