[Dennis Pfeifer]

Very nice of you to create this version.

Will one be available for 6.2 ?

[Dennis Pfeifer]

5.7 on Windows 7 ..

run the install in XP SP3 compatibility mode (not VM, but run in compatibility mode).

for the Patch, I had to modify the batch file ..

runs fine, haven’t had any problems…

Dennis

[Dennis Pfeifer]

Just for completeness ..

This is what we have ours set at ..

kernel.sem=250 128000 100 512

# .. and we change the default keep alive.

# Decrease the time default value for tcp_keepalive_time connection

net.ipv4.tcp_keepalive_time = 1800

[Dennis Pfeifer]

hcicmd -p processname -c “”

you will see the list of available commands .. one of which is ..

hcicmd -p processname -c “. purgex”

which will puge translation cache.

Dennis

[Dennis Pfeifer]

We don’t keep our systems up that long, because I try to replace them every couple of years.

[Dennis Pfeifer]

Oh, Ya, after reading another ‘thread’ .. I realized that we also do this for database connections…

If the connection exisits, we use the global… which is shared amoungst all Xlates in the same process.

Dennis

[Dennis Pfeifer]

An instance where I have used a global in the Xlate thread, was in using a global across multiple interfaces, but all in the same process. My specific example was tracking patients’ room and bed.  I could have used a file on disk, or database, but instead, I used memory. Updates were written to disk (to support startup), but ‘reads’ came from the global which was shared across multiple ‘Xlates’ …. saved some disk I/O.

Dennis

[Dennis Pfeifer]

I’m a simple guy.

I use the date in the MSH segment, taking the eight left most characters and store into a variable (MSH has current date). I then take the eight left most characters from the IN1 segment, and store in a variable. Next, an IF statement is used to compare the two ‘integers’

[Dennis Pfeifer]

;##how about text util .. .

package require textutil

;## assume ‘text’ is in $text

set textList [split [textutil::adjust $text -length 75] “n”]

;## textList now contains a list

;## with each element containing one line of text.

;## Dennis..

[Dennis Pfeifer]

That’s an option…

You could use one table instead of three (sounds like you intend to use three) ..

Input would be Dr. number. output would be destination interface ‘id’ ..

then put the ID as a parameter to the tcl proc.

If the ID returned by the table look up does not match the ID in the parameter, then kill the message..

You would use a different ID on each route…

Dennis

[Dennis Pfeifer]

Even though you are routing raw, you can still put in a proc in the route.

Send the message to all three destinations, then kill it on two of them.

You could use the same proc on all three, and have a parameter on each route indicating the ID to keep …

Dennis

[Dennis Pfeifer]

go with the latest that your version of Cloverleaf supports…

[Dennis Pfeifer]

Thanks Jim .. yes a second iteration using the input would be possible, just not as clean ..

It’s interesting that the GUI allows you to select a basis from the output.

Dennis

[Dennis Pfeifer]

any chance you can get your lab to use a separator ..

e.g.

Trnx #1:

OBX5:  |2+  – BACILLUS ANTHRACIS|

Trnx #2:

OBX5 |PRESUMPTIVE – BACILLUS ANTHRACIS|

Trnx #3:

OBX5  |>100,000 C/F – BACILLUS ANTHRACIS|

or perhaps a tilde

Trnx #1:

OBX5:  |2+ ~BACILLUS ANTHRACIS|

Trnx #2:

OBX5 |PRESUMPTIVE ~BACILLUS ANTHRACIS|

Trnx #3:

OBX5  |>100,000 C/F ~BACILLUS ANTHRACIS|

you could then split and go from there ….

Dennis

[Dennis Pfeifer]

I’ve worked with EPIC for over 7 years now, and have found them to very competent and always willing to try and help find a solution. My experience is that they have been solution focused, and NOT territorial, such that things ‘must’ be done in Cloverleaf, or that they ‘must’ be done in EPIC. They are agreeable to coming up with solutions that work best.  Our general preference has been to do what we can in Cloverleaf, and that which we can’t is done in EPIC .. i.e. generally state or historical dependencies are handled in EPIC.. e.g. if the current insurance is X, don’t replace with Y .. this can’t be easily done in CL, so it’s done in EPIC .. (I prefer not to create databases in CL .. )

and .. yes they do produce lots of messages on their ADT interfaces.

I refer to EPIC as the BMW of information systems .. they are very good in quality, but generally, very expensive… so .. you get what you pay for ..

.. if you can only afford a Chevy .. you’re not purchasing a BMW.

Dennis

[Author]

Replies