[Chris Williams]

I forgot to mention in my suggestion for changing the Reflection settings that you will also need to tell your AIX session what screen width you are using. Running in Linux we have a script that contains:

Code:

export COLUMNS=196
export LINES=72

[Chris Williams]

We’re not on 6.0 yet, but it looks a lot like you have the EO turned up, or you have some Tcl code generating all of those lines.

I have a couple of band-aids for you:

1. Change your Reflection settings. In the version we use: Setup > Display > Screen > Columns. Set the number of columns that works for you. You may need to adjust the font to improve readability. (I happen to use 196 columns).

2. Use “colrm [startcol [endcol]]”  in conjunction with “less” to remove the columns you don’t want to see. “colrm” reads from stdin and writes to stdout so you can use it like a filter.

Code:

cat logFileName | colrm 1 59 | less

Cheers.

[Chris Williams]

Has anyone switched to Google for their corporate email? The disappearance of the digests happened when we moved from Exchange/Outlook. Our email guy says he was told by Google that the digests are being “dropped” because they violate some yet to be explained Google policy.

[Chris Williams]

If memory serves, when you use PATHCOPY it copies individual fields according to their HL7 item numbers. If the number in the inbound variant doesn’t match the item number in the outbound, it won’t copy the field across.

[Chris Williams]

Still no digests since the one on 1/22, however I am receiving the Topic Reply Notifications.

[Chris Williams]

Thanks, guys.

[Chris Williams]

We used to get this unending stream of errors when a connection was dropped without being closed properly. In our case it was a network switch whose time-out was shorter than the shortest keep-alive setting. Of course, your mileage may vary.

[Chris Williams]

A common mistake when setting the time window is that the asterisks mean “ALL”. If you set the hours at 8-21 and “*” for minutes and seconds, it works out to “ALL seconds of ALL minutes within those hours”. If you want it to end at 9 PM change the hours to “8-20” so it will be active up to 8:59 PM. You might also want to trim the window down a bit by picking a specific value for Seconds like “00” so it won’t fire more than once a minute.

In the Unix world, you rearm the Alerts by touching the default.alrt file. In our system we have cron touch the default.alrt file once an hour.That way you get hourly reminders if the alert condition has not been resolved. I seem to recall Russ Ross posting something not long ago about the way MDACC handles this 🙂

[Chris Williams]

Basically, the OID represents the unique assigning authority/ID type for the data you own but on a world-wide basis. You apply for an OID (from HL7 or the CDC) that will represent your institution.

It is up to you to assign the numbers beyond your institution ID that will be used to identify your internal values you send. The OIDs that you send not only represent the institution with a unique value globally, it represents what type of value it is within your institution.

Not everything you send will have your OID. For example, if you are sending a LOINC code, you would use LOINC’s OID.

For Epic users, Epic already provides most OID values for you.

Both HL7 and the CDC have more detailed information:

<a href="http://www.hl7.org/oid/index.cfm?ref=common&#8221; class=”bbcode_url”>http://www.hl7.org/oid/index.cfm?ref=common

<a href="http://www.cdc.gov/phin/library/archive_2005/CFC_RSv1.0.pdf&#8221; class=”bbcode_url”>http://www.cdc.gov/phin/library/archive_2005/CFC_RSv1.0.pdf

[Chris Williams]

Here at McFarland Clinic, two of us handle Cloverleaf and Epic Bridges with production traffic in the 700K/day range. With Epic you can wind up with many environments, but we only interface to four of them (PRD, TST, REL, BLD). For Epic version upgrades we create additional environments with interfaces.  We each have 10+ years experience.

Bill – we look at thread count, but if you’re talking traffic volume we use outgoing message counts.

[Chris Williams]

We’re running sh on Linux. We start our Tcl scripts with these three lines:

Code:

#! /bin/sh
#
exec tcl “$0” “$@”

Unlike Windows, the routine doesn’t require an extension, but it can be anything you want. Just make sure the file is executable. The major point to remember is that cron does not create the environment. It will run as the user who submitted the job, but it doesn’t use the normal setup process that creates all of the profile variables. You are responsible for doing that. This has been discussed a number of times. Try searching for “cron”.

[Chris Williams]

Both ways are valid. My personal preference is the first because it emphasizes the list structure.

[Chris Williams]

I seem to recall having a similar experience a long time ago. It resulted from doing things out of sequence. Did you delete some_thread while you still had messages in the Recovery Database with some_thread as their destination? If so, a couple options you could try:

(1) Manually delete the messages from the recovery db.

(2) Rebuild the route and destination thread and let them flush out.

[Chris Williams]

In UNIX/Linux, monitorShmemFile is not a file in the traditional sense. It is a FIFO (First In First Out), also known as a “Named Pipe”.

[Chris Williams]

It sounds like you may be running up against the licensed thread count unless you have an unlimited license. Check the beginning of your process logs for more information.

[Author]

Replies