Nursing Geekitude

[madshutterbug]

Once again, following upgrade of Major Software Vendor's software at Hospital, we have a Test Environment. This is important as we learn what the upgrade will let us do, and how to implement little fixes to bugs... yes, bugs. Un-Documented Features. Uh Huh.

So, it's a good thing to have a Test Environment.

Having the flag that lets us know which environment we're logging into set to "Production"? Not so much.

However, we have two tests to help verify that we are actually in Test Environment. One is, open up the OR Scheduler; compare it to the same app for the same day in Production. Good clue. The second is, if it's Slow As Molasses in an Ice Age, you're in Test.

Yup.

Comments

[miz-hatbox.livejournal.com]

Hey, I sent you a message at the email address on your photo website. Not sure whether you saw it...

[madshutterbug.livejournal.com]

I did, and I owe you a response, but I've been mildly swamped getting some things done at work & at home while getting ready for a busy month of travelling to nursing conferences to present. There are times I am not so much fond of October these past few years... though at least 2/3's the travel is paid for by others.

[ihgreenman.livejournal.com]

Be nice if they had a flag to have a visual indicator as well. Like on the title bar: "Test Hospital" or somesuch.

I am personally a strong advocate of a test environment... especially when rolling back is difficult or impossible in the event of a stow stopper found 2 minutes after the rollout was finished.

[madshutterbug.livejournal.com]

There is such a flag. It's a field in a table which defines who the "owner" of the software is. However, in Major Software Vendor's infinite wisdom, only a Data Base Adminstrator who has priveleges to directly access the table (not through the Database Maintenance application) via a SQL statement can change the value in the field which indicates "Production", "Test", "Training" (some customers set up three environments, we only do two).