Discussion Locked

Blogging IT One Word at a Time

0 helpful
65 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
blog root

65 replies

by bill elmore

Working in healthcare IT (HIT) means learning to quickly
adapt and implement new technologies at breakneck speeds.  Healthcare has so embraced technology that
businesses must continue developing new and better methods of providing patient
care or else lose the competitive edge that is essential to their
survival.  That competitive edge ensures the
best physicians are retained, patients get higher quality care which is safer
and less invasive, and the bottom line is maintained against ever decreasing
insurance reimbursements.

So where does the HIT professional fit in all of this?  He fits right smack in the middle, holding
hundreds of spider-like threads together which stretch from the data center
back to every aspect of healthcare operations. 
Technology is entrenched enough that a down server could mean a doctor performing
a heart procedure can?t pull up needed images, or it could mean a recently
vacated patient room goes uncleaned because the bed and patient tracking system
couldn?t send the notification page to the environmental services
employee.  Heck, I just completed a new hospital
dietary system installation to replace an old paper system.  So now every time the Citrix server crashes
(ahem, last night), I get a call from panicked dietary workers who don?t know
what the patient in room 2217 ordered for dinner.  Two months ago, they used an entirely paper
driven system, and now they are completely immobilized if their new electronic
system hiccups.

To make matters worse, many times vendors ship out buggy
software in an attempt to be first with a new idea.  I know, buggy software is not unlike software
being sold in every other market, but its impact in this case is to patient
care, which takes it to an altogether different level.  Installing a poorly written software package compounds
the problems facing HIT departments because subsequent ?patches? and
?enhancements? become less optional and more often translate into required
upgrades.  Features seen on a glossy
brochure and included in a slick sales presentation are nowhere to be seen after
the initial installation or they often work less than perfectly.  Let?s see a show of hands if you?ve ever
installed a dot release upgrade to a system which wasn?t yet live.  My last system installation included four separate
dot upgrades before it ever made it to production status.  Depending on the complexity of the system,
this could mean required updates and testing to database, application,
interface and terminal servers; not to mention updating workstations and
handheld devices or rebuilding automated software deployment packages.

In all fairness, often software vendors and HIT departments
are pitted against each other to solve implementation problems when the root
issue originates with a hospital director or president who purchases a system
without involving the people responsible for its installation.  ?We bought this, now make it work? is a
phrase I?ve heard before.  Seemingly out
of nowhere, a contract is signed, money changes hands and then it?s sent to IT for review and installation.  Problems inevitably arise when you?re
speaking with the vendor?s technical support, and they reluctantly inform you
that they?ve never assisted with a thin-client implementation of their product or
don?t know if their software will run on a virtual server.

However, vendors will work with you much of the time to
install their software according to the standards and technologies in your
environment even when their support documentation doesn?t officially list it as
an accepted platform.  But what happens
when they won?t?  Then IT is left holding
CDs for a purchased system which doesn?t adhere to internal processes.  A decision must be made at this point either to
refuse installation (this never happens) or engage in a bit of creative
engineering which involves magic behind a pulled curtain.  Voila! 
A new system is installed and no one quite knows how it?s working.  Just don?t breathe too hard on the server on
the left.

As computerized methods replace the last remaining manual
procedures in healthcare operations, IT departments find themselves playing a
direct role in the delivery of patient care. 
This means promptly responding to problems that arise while juggling the
constantly evolving solutions passed down from vendors and into our laps.  Now if only I could learn to recognize the
beta software builds from the ?final? releases?

by bill elmore

Working in healthcare IT (HIT) means learning to quickly
adapt and implement new technologies at breakneck speeds. Healthcare has so embraced technology that
businesses must continue developing new and better methods of providing patient
care or else lose the competitive edge that is essential to their
survival. That competitive edge ensures the
best physicians are retained, patients get higher quality care which is safer
and less invasive, and the bottom line is maintained against ever decreasing
insurance reimbursements.

So where does the HIT professional fit in all of this? He fits right smack in the middle, holding
hundreds of spider-like threads together which stretch from the data center
back to every aspect of healthcare operations.
Technology is entrenched enough that a down server could mean a doctor performing
a heart procedure can?t pull up needed images, or it could mean a recently
vacated patient room goes uncleaned because the bed and patient tracking system
couldn?t send the notification page to the environmental services
employee. Heck, I just completed a new hospital
dietary system installation to replace an old paper system. So now every time the Citrix server crashes
(ahem, last night), I get a call from panicked dietary workers who don?t know
what the patient in room 2217 ordered for dinner. Two months ago, they used an entirely paper
driven system, and now they are completely immobilized if their new electronic
system hiccups.

To make matters worse, many times vendors ship out buggy
software in an attempt to be first with a new idea. I know, buggy software is not unlike software
being sold in every other market, but its impact in this case is to patient
care, which takes it to an altogether different level. Installing a poorly written software package compounds
the problems facing HIT departments because subsequent ?patches? and
?enhancements? become less optional and more often translate into required
upgrades. Features seen on a glossy
brochure and included in a slick sales presentation are nowhere to be seen after
the initial installation or they often work less than perfectly. Let?s see a show of hands if you?ve ever
installed a dot release upgrade to a system which wasn?t yet live. My last system installation included four separate
dot upgrades before it ever made it to production status. Depending on the complexity of the system,
this could mean required updates and testing to database, application,
interface and terminal servers; not to mention updating workstations and
handheld devices or rebuilding automated software deployment packages.

In all fairness, often software vendors and HIT departments
are pitted against each other to solve implementation problems when the root
issue originates with a hospital director or president who purchases a system
without involving the people responsible for its installation. ?We bought this, now make it work? is a
phrase I?ve heard before. Seemingly out
of nowhere, a contract is signed, money changes hands and then it?s sent to IT for review and installation. Problems inevitably arise when you?re
speaking with the vendor?s technical support, and they reluctantly inform you
that they?ve never assisted with a thin-client implementation of their product or
don?t know if their software will run on a virtual server.

However, vendors will work with you much of the time to
install their software according to the standards and technologies in your
environment even when their support documentation doesn?t officially list it as
an accepted platform. But what happens
when they won?t? Then IT is left holding
CDs for a purchased system which doesn?t adhere to internal processes. A decision must be made at this point either to
refuse installation (this never happens) or engage in a bit of creative
engineering which involves magic behind a pulled curtain. Voila!
A new system is installed and no one quite knows how it?s working. Just don?t breathe too hard on the server on
the left.

As computerized methods replace the last remaining manual
procedures in healthcare operations, IT departments find themselves playing a
direct role in the delivery of patient care.
This means promptly responding to problems that arise while juggling the
constantly evolving solutions passed down from vendors and into our laps. Now if only I could learn to recognize the
beta software builds from the ?final? releases?

by mike_patburgess

I have had some experience in reviewing IT in the health care industry.  If patients only knew how at risk their information is from hackers, and loss, they would think twice about giving their information out.

Whereas the medical industry likes to implement "new improved technolgy", they forget to implement the security around it or, the security is sub standard.

Well, that's been my experience.

by bill elmore

Monday afternoon began peaceful enough. Being ?on-call? for my daytime IT job means occasionally
carrying a pager and cell phone for a week of 24/7 paranoia. It also means I stay as late as needed to
perform scheduled server reboots, which are typically preceded by applying the
latest Microsoft Security Updates and Hotfixes.
Sounds simple. But on this day, I
had a particular Windows 2000 Server that seemed inclined to remind me it was,
in fact, a Windows box. And, oh yeah, it
was after all a Monday.

Microsoft made it easy.
A quick connection to the Windows/Microsoft Update site revealed a
whopping 24 updates were needed and recommended for immediate
installation. To my credit, I was smart
enough to first install the updates on the designated ?test? server, which
revealed no evident issues. And then, at
approximately 6 PM, I casually clicked the Install
Updates
button, and waited for thirty minutes while the installation
completed. One reboot later revealed a
fully functioning system with no warning or error messages in the system event logs. I could go home and enjoy my evening?

?But, no. Let me
explain. Arriving home to find your
spouse speaking with your employer?s Help Desk is never a good sign. It seemed no one located at any of our five hospitals
could print their much needed patient labels and medication barcodes following
the reboot. This ONE Windows server functions
as the sole print server for all 1,400 printers at our remote sites. (Note: I only rebooted it, not designed
it.)

I hadn?t panicked at this point. So as my family ate dinner, I connected to
the server via pcAnywhere and thought a quick restart of the print spooler
would coerce the printers to fulfill their life?s purpose. A subsequent look at the printer queues
revealed no jobs were queued and nothing was being printed. The Windows System Log showed a series of
Informational Events; Event ID 9, ?Printer xxx was set?. In fact, there were only Event ID 9s in the System Log.
That was because the maximum size of the log was set to 1 MB which made
it appear useless. Further investigation revealed the system
partition had less than 500 MB of available space, and the HP Insight Manager
agents indicated two bad memory modules.

It should be mentioned that at this point of my Monday
evening, I began receiving follow-up calls from the Help Desk requesting system
status and to relay much end user angst.

I went with the obvious.
A call was placed to our hardware support group and the bad memory was
replaced by 12:30 AM. I drove to the
data center for this as well, and one more reboot later proved that print jobs still
were not spooling. Openly sobbing wasn?t
appropriate, so I again perused through the event logs. It was still filling with Event ID 9s. Googling on this Event showed it was informational
and could be ignored, although it did look suspicious.

Fast forward to 2:00 AM.
The system had been down for over six hours. Users were very unhappy to say the least, and
panic was beginning to set in. It also
came to light a new hospital system was beginning production in less than five
hours and it had a dependency of, you guessed it, the down system. A roll-back of the Windows updates was
unhelpful, and the functional support person for the application was beginning
to mumble words like Disaster Recovery.
I ran back to my desk and frantically searched for more clues.

It seems typing ?Windows printer problem? into a search
engine returns more than 45 million results.
The team lead I awoke at 4:00 AM actually used the phrase ?resume
generating event?. That?s never good to
hear. But it was about that time I found
Microsoft Knowledge Base Article 832219. This gem of an article describes a scenario
much like my own. Putting the pieces
together, I discovered that the ?Update Rollup 1 for Windows 2000
SP4
? updates the PCL Universal Print Driver dll (unidrvui.dll). This, in turn, causes a rebuild of all the
PCL based printer description files (i.e., nearly 1,400 printers in this instance). I realized by studying the System Log events
again that roughly every 9 minutes a printer driver completed updating (Event
ID 20). Multiplying this times 25 PCL
drivers meant the system should be functioning again by 6:00 AM ? just in time
for the new system ?go-live? one hour later.

The system was spooling print jobs again at 6:05 AM. I notified the Help Desk and performed a
celebration dance in my cubicle while no one was looking. I also emailed an explanation and warning
message to my fellow team members explaining my travails and what not to do in
the future. Sleep was finally an option
by 9:00 AM.

So what can be learned from all of this? Obviously, testing and researching an update
should be required before it is applied to a production system. The reality is many organizations don?t have
the IT staff, hardware or time resources to thoroughly test every released update. Often there exists a catch-22 where it poses a
security risk to not install a patch, but the consequences of installing
without adequate testing are too great.
In the case I described above, updates were applied to the test system
first. But because the test system was a
scaled-down version of production and had 100 printers versus 1,400, the
problem issues weren?t evident.

My guess is many of you reading this are in similar
situations regarding patching production systems. Sound off and let me know! And while you?re at it, check out a different
perspective on this topic from fellow TechRepublic blogger, Shannon Kalvar.

by gregry

There is no such thing as a test system.  You either have duplicate productions systems or you are relying on the power of positive self-delusion.  (Hint:  I don't have duplicate production systems either).  For the most part, we ARE damned if we do and damned if we don't.

by reconlabtech

I discovered a long time ago that update rollbacks rarely rollback everything - good backups are the only thing that have saved me from spending hours / days trying to fix a "patch" problem.  I now live by the 30 minute rule - if I can't solve the problem in 30 minutes, I resort to the most reliable restoration process for the problem, whether that be a reimage or backup restored.  These machines will steal your life if you let them!

 

by dkroger9

I always perform an image backup before applying patches. This way, if the patch goes haywire, I can restore the image in less than 1 hour. You have to be sure to use a partition that is for the OS only so that you do not have to worry about any data loss problems.

by cincy2hot4u9

I KNOW That Patch Work, is NOT RELIABLE, MSN Zone is Patch-Work overloaded, so I ask for a ALL - New Gaming Zone.  Club Shepherd yyyy, fixes EVERYTHING Zone related, However, I must, because I have 0 Authorization, when I have A Systems Analysis College Degree from Miami, OH. 

I am HIT BY A Railroad TRAIN!  I know, that this causes people, NOT Hurt, that THINK THEY Know it all are Superior Human Beings, than me.  BUT OBVIOUSLY NOT, Because, President Bush can't even SOLVE The ILLEGAL Immigration problem, where I Have the Solution!  cincy2hot4u@homail.com, will respond with the Answer to George Bush's BIGGEST Problem.  93% of the Illegals tht have Already Crossed the Border ILLEGALLY Can stay, but MUST Pass an English Entrance Exam (EEE), generated by a TEAM Of College professors in English.  7 month Waiting time Frame so they CAN Study English!  For re-takes to enter, Legally.  WE Only Want THEE BEST, Right?  So EEE Spanish Exam takers will Study, IF they TRULY Want to become USA Citizens!

You're Welcome, MR. George Bush!

Brian Shepherd,   513-367-6048,   MY Solution oriented Brain thinking, for THEE USA,  +++Bridge_SMASH,  Club Shepherd yyyy, I Solved 7000++ Hours worth of very creative thinking brings the Solution to CHEATERS At cards, too! 

by bill elmore

Data breaches. The
number of reported data breaches involving sensitive private information at
organizations and companies is growing at an alarming pace. I click the refresh button for my RSS news
feed if it doesn?t flash a data breach story at some point during the day. I haven?t had to manually ?refresh? much
lately though, have I? There is an
abundance of data security stories not just in the IT trade magazines and on IT
focused web sites, but also in mainstream media outlets. It?s front page news read by millions of
people, many of whom aren?t knowledgeable or concerned with much of the general
happenings of corporate IT. But I feel
compelled to chime in with my two cents anyway, even though there are plenty of stories and opinions already
posted on the topic.

My take is a little different though. I view the reports of data breaches at
government offices, schools, banks and corporations as a good sign. That?s right; I said it?s a good sign there are so many reported
data breaches. It tells me there is
finally a focus on protecting private data.
The truth is, not until Congress passed laws such as Sarbanes-Oxley
and the Health Insurance Portability and Accountability Act of 1996 (HIPAA), and states such as California
passed laws requiring full disclosure of data breaches, agencies and
corporations were largely self-governed and lax with data security
practices.

The key to my absurd statement focuses on the word ?reports.? You see, data breaches (i.e., the loss of
sensitive private information) have been occurring for many years. It wasn?t until recently that corporations
took the topic seriously and began being forced to disclose security lapses. Thanks to consumer advocacy and watchdog
groups such as the Privacy
Rights Clearinghouse
and regulatory laws like HIPAA, senior executives are
being held ultimately responsible for protecting private data and maintaining regulatory
compliance. It is the threat of severe
criminal and civil penalties that is persuading CEOs to dedicate valuable and
scarce resources to securing consumer data.
What else would cause executives to spend money and time on something
that doesn?t directly affect the bottom line?

The data breach reports are significant because companies previously
didn?t place much emphasis on data security.
Blocking hacking attempts and viruses got the most attention, with efforts
mainly focused around keeping hackers on the outside through perimeter defenses
such as hardware firewalls and wireless network encryption. But not much effort went into developing
sound data handling procedures. The
reports of data breaches are both embarrassing and damaging to the responsible
companies, and ensure that more resources will be dedicated to reducing future
incidents. And while some data breaches
are occurring because of hacking attempts and viruses, most reports describe
incidents involving employees losing laptops or portable media devices, or lapses
in judgment.

Change takes time though; especially change involving
business process flow. Many organizations
are still in the very early stages of evaluating and implementing solutions to
mitigate security risks. Common IT-based
solutions involve implementing federated identity-management systems, utilizing
encryption and using thin-client technology to access data stored centrally in
a secure data center. Procedural
solutions include creating access control lists and determining exactly who
needs access to which systems, performing routine self-audits and training
staff to properly dispose of and protect sensitive data (e.g., shredding confidential
documents and knowing not to post private data on insecure web sites).

For example, when I started in healthcare IT in the late ?90s,
a stroll down hospital hallways revealed computer screens with patient data
clearly visible, computers logged into the network with generic accounts, and
applications that required no authentication.
Fast-forward to 2006 and those same hallways now reveal screen filters
on all monitors, staff using unique login credentials and applications with
either integrated directory services based authentication or a separate application
layer login. Security committees even
exist now with members from various departments who focus on ensuring the
company maintains HIPAA compliancy. How
to secure data has become a focus when discussing upgrading or installing a new
system, not an afterthought.

So again I say the frequent reports of data breaches are a
welcome site. And while it indicates we
still have a long way to go to reduce security risks, it also proves there are
watchful eyes on the companies storing sensitive private information. This will take time, but a quick glance to
past security practices shows just how far we have already come.

As always, let me know your thoughts, and while you?re at it,
check out these recently added resources on TechRepublic.

Why data encryption is no substitute for comprehensive security

Protect
corporate data with these physical security precautions

Insider
Threat Report by Aberdeen Group: Strategies for Data Protection

by nasty jack

I agree that awareness is a great stride forward, but, unfortunately, my experience tells me that it is only because the feds and business have been forced into this mode, and it is primarily for the protection of the bureaucracy and the bottom line.  I am a former broker of mailing lists turned privacy activist, and can speak with authority on the junk mail industry, as well as some of its relationships with the government.  The problem isn?t just our names and private information dribbling all over the environment, it is the use of this same data, by the same two powers, to invade every aspect of our inner sanctum. 

 

I believe George Orwell predicted the data breaches of 2005, as well as the iron fist control that now exists over our private lives.  1984 is about a totalitarian state where every aspect of public and private behavior is regulated.  We certainly aren?t at that point, but the control over our names and personal data by business and government has set the stage for the next step.  As Erich Fromm wrote in the book?s ?Afterword,? Orwell warns us that, unless drastic changes are made, people will become ?soulless automatons.?  If you look closely at Orwell?s ?Party? in 1984, as the representation of the all-powerful force that controls every aspect of the people of the fictional country of Oceania, it is easy to draw a comparison with the situation today, where our private information is under the exclusive control of government agencies and business.

 

There is only one way to protect the use of consumers? names and personal data.  Pass federal legislation to give the individual control over this private information, and, while we?re at it, pay them for its use.  You can read about it in my blog, The Dunning Letter at: http://thedunningletter.blogspot.com/2006/07/independence-is-control-over-your-name.html

 

Jack E. Dunning

Cave Creek, AZ  

 

 

by bill elmore

I arrived at the office just in time for an unusually early
eight o?clock meeting.  As if that wasn?t
enough to erase the happy feelings I had when I first awoke, the meeting was to
discuss a project which hadn?t been approved for a system not yet purchased.  Besides the vendor, there were ?happy?
representatives from most of our IT departments ? Client/Server, Networking,
Database, Interface and local hospital IT staff.  The purpose of the meeting was to discuss the
feasibility of a new system before purchasing it.  The hang-up for most attendees, other than
the early start time, was they perceived the meeting as a waste of time.  Lost was the idea that we were called to
perform pre-analysis work, and not to fix something.  Performing project pre-analysis is a luxury
most IT pros don?t get to participate in, but should take full advantage of
when presented with the opportunity.

The process usually works something like this.  Sales and marketing people peddle an
application towards directors and department managers, not IT staff.  The managers get sold on the benefits such as
increased staff efficiency and cost savings, and, ultimately, the system is purchased.  It is then handed to IT to implement and make
work in the existing environment.

Back to project pre-analysis.  This represents the perfect time to request
more detailed information from the vendor, other than the one page data sheet
posted on their web site.  Many times the
sales person can give the contact information for one of their installation engineers
or technical support specialists.  A
single one-on-one phone conversation can often answer questions about the
architecture of the system, recommended hardware configurations, whether it is
supported and certified to run in a thin client environment, or if any
components are a good candidate for virtualization, etc.  An entire book could be written on what to
look for and what questions to ask during the pre-analysis phase.  But the important point to remember is to be
as thorough as possible.  Once
expectations are set with your customers (i.e., end users) and the system is
purchased, it?s nearly impossible to stop mid-implementation and proclaim that
it just won?t work.  Enough negative
indicators may be identified during pre-analysis to justify not purchasing the
system.

One additional strategy I find useful is calling the customer
technical support line.  This can reveal uncensored
candor about common customer complaints and issues.  For example, they might reveal that printing
is always a problem because printers are defined per user using .ini files where
form margins are manually set.  Or you
could discover the system requires quarterly updates, which translates into a
30 ? 60 minute time commitment per server and each fat client, and, oh yeah, it
needs to be completed after hours.  Okay,
I slid in a couple of real examples, but they well illustrate my point about
the kind of information which can be gleaned from calling tech support prior to
giving the green flag for a system acquisition. 
It also can be an indicator to how promptly you?re able to speak to a
live person when needed, or if the norm is to leave a message and wait for a
call back.

So, the eight o?clock meeting scheduled with the good
intention of identifying potential implementation pitfalls never got on
track.  The ninety minutes were largely
spent arguing over why we shouldn?t be discussing this project when another
major project is on the horizon.  It is a
shame more analysis and brainstorming didn?t get accomplished with so many IT
team representatives in one place.  It is
not often that all the pieces are together for collaboration and analysis from
different areas of expertise.  An
opportunity like that should not be squandered. 
A little research up-front today can pay huge dividends for future
projects tomorrow.

Feedback is welcome as always.  Let me know if you have developed a good
system for conducting project pre-analysis, or if you face similar resistance to
the process in your workplace.

by barryc9

Would you as an IT pro, as the article puts it, read and accept as useful a white paper from a vendor that identifed issues relating to implementing their product? Assume that it covers the obvious factors as mention in the article and perhaps points out some other factors, pro and con to consider?

How about it it was a comparison peice - talking about advantages of the vendor's product as compared to a competitor's? It you would tend to be adverse to a competitive piece, how about if the paper seemed reasonably fair and impartial. (Reasonable means that it says nice things about the competition but still presumes that the vendor's product is a better choice.)

Self interest is involved here - my company produces the kinds of papers I'm asking about. My goal in the question is to hear what the people who read them have to say and would want to learn.

by cdyer

I totally agree.  My boss has taught us the value of such pre-analysis and we now expect input from all attendees to arrive a our consensus.  It has saved us countless hours and headaches in implementation later, and it has earned us respect from our (in-house) customers that we have our stuff together whenever something new is considered.

by bill elmore

Things just continue to change. Actually, IT is always changing and always will.
That is part of the fascination and draw for me, and one of the main
reasons I chose this field. Right now,
you?re probably wishing I would pick a topic and run with it; and so I
will.

For the past several years, I?ve been watching varying
levels of user access to electronic data become further and further
scrutinized. The scrutiny comes from IT
managers and, ultimately, CIOs who are responsible for ensuring only those who
need access to sensitive private data have access to it. The direction and push to control who needs
access to what and why, comes from internal and external audits to maintain
compliance with regulatory laws such as Sarbanes-Oxley (SOX) and HIPAA.

Controlling user access to electronic data means a lot of different
things to IT staff working in the trenches every day. It means setting up the proper security
controls when installing new systems, and not leaving the default Windows
permissions to shared folders. Leaving
the Everyone group with full access to a folder does not constitute a good
security plan. Setting up an Active
Directory Security Group for a new system and then adding only those users who
need to use the application as part of their job is a good start. If they don?t need Modify rights to the
directory, only give them Read rights.
These are common sense rules, but it?s amazing how many IT pros get lazy
and leave the default permissions as-is or don?t set up separate AD security groups.

Of course, even those users who do have a justified reason
for accessing a system can abuse their access and violate privacy laws. For instance, a healthcare employee may have
a job that requires occasional access to electronic medical records. Since access is pretty much all or nothing,
they may be tempted to peruse the records looking for patients they recognize
(e.g., friends or family members).
Without justifiable cause for accessing the records, this is a
major infraction and presumably grounds for termination. It is ITs responsibility to put safeguards in
place and to provide checks and balances for this kind of user behavior.

One such mechanism is to utilize Windows Group Policy to
enable object and directory access auditing.
This method is okay and may be the only means available of keeping an
audit trail for certain applications.
But more than likely, an application written within the last few years and
which stores sensitive data will have built-in capabilities for logging/auditing. Many times, power users working as system
administrators will get the responsibility of periodically reviewing these system
audit logs. Knowing who accessed what
and why they accessed it is the goal.

One area of user access control proving to be an issue where
I work is vendor access. Not access to
specific files or servers per se, but VPN account access. Our policy is for each vendor support person
accessing our network to have an individual VPN user account. The reality is one or two support reps
assisting with the implementation get accounts created in their name, and then
the credentials are stored in the vendor?s customer database for use by any
future support person to use. So access
logs aren?t accurate and we really don?t have any way of knowing exactly which
rep connected to the network after all.

But would compliance auditors give good marks to our company
for being able to say we require individual accounts for all vendor support
reps? Yes, but it is more of an empty
fulfillment of the requirements. For
larger vendors with many support reps working various shifts, it?s just not
viable to keep track of another company?s active employee roster. In this case, the more rational approach is
to require the vendor to sign a Service Level Agreement (SLA) specifying they
are responsible for logging each rep that works on an individual support
ticket, and they must be able to provide the access logs at the customer?s
request. This approach, while not
perfect, actually comes closer to accomplishing the goal ? knowing who accessed
a system which stores sensitive data.

There are many other aspects and examples to controlling
access to electronic data. I?ve only
touched on a couple, but it all goes back to ensuring sensitive data is
accessible only by the people who need it to do their jobs. As always, let me know your comments and some
of the ways you control access to critical data.

by fultonwilcox

Your comment that access to sensitive data is permitted on an "all or nothing" highlights a fundamental problem, because "need to know" is inherently situational to the job functions and specific assignments of the inquirer. Therefore, establishing user accounts, effective authentication and, perhaps, role definitions are all necessary steps forward, but are not sufficient for the "new world" of comprehensive data. The recognized objective should be to compartmentalize dynamically and on a very granular basis, even though that objective is a bit out of reach using today's capabilities.

 

Fulton Wilcox

Colts Neck Solutions LLC

by bill elmore

Thanks for the comment.  What I meant by "all or nothing" was a user who has access to patient data within a clinical application typically has access to all of the patients.  This can mean a medical records employee or a nurse working in ER.  It's true, though, that many of the applications have granular security settings for restricting access to certain modules, such as Radiology images or lab test results.  So, in this way more distinctive application and data access can be restricted.

-Bill E.

by milal9


The medical records scenario you brought up is a situation that is very real in the medical world. I'm sure this happens often in financial, legal and other industries as well. Unfortunately, issues regarding controlling data access don't stop there. What about e-mail? How can a lawyer stop an intended recipient from forwarding private lawsuit information, or a doctor make sure that his patients' data stay in his nurse's inbox? Access rights issues are far and wide. Solutions are being developed, but obviously Microsoft's Private Folder didn't work. For e-mail, companies should at least be using encryption, and even better look into rights management - which specifically control e-mail and attachments after you hit "send". http://www.essentialsecurity.com/Documents/article9.htm

by bill elmore

It seems that IT staffs are annually given more work to do
than they were the previous year; more new and complex projects to implement
while continuing to support an ever expanding list of yesterday?s systems.  The increase in work appears to be disproportionate
to the increase in new help hired.  Speaking
with friends in IT at other companies I discover the exact same scenario.  This is odd because I also know people
looking for work in IT, but who can?t seem to land a job despite their
substantial efforts.  So what is the
answer to getting more work done with less? 
More systems management utilities and appliances?  Server virtualization?  Robocopying ourselves?  No, I say it?s one word ? empowerment.

Give power to the people, or users in this case.  No, I am not inebriated as I write this.  And yes, I?ve witnessed my fair share of dumb
user moments; even contributed on a couple of those occasions.  I?m not saying make your users local
administrators of their workstations and hand them the keys to the server room
so you can play golf.  Page me if I?m
needed, please. 

What I am saying is identify and enlist the help of one or
two power users as you are implementing a new system; preferably two in case
one leaves the company.  You?d be
surprised how helpful a user serving as the system champion and front-line
support person can be.  Many times the
empowered person will end up being the user who stands to benefit the most from
the new system.  It?s in their best
interest for the system to be successful and remain in proper working
condition, and it frees IT staff to concentrate on rolling out new applications
and troubleshooting infrastructure level issues.

What level of empowerment am I suggesting?  I am suggesting that a user serve as pseudo
system administrator for the day-to-day functions such as creating user
accounts within the application, resetting application level passwords, and
running applicable system maintenance tools as needed.  Basically, anything that can be done from
within the application and from the user?s PC should be fair game.  The key is to remove yourself from the daily
operation of the application, and empower a designated user to accomplish these
routine tasks.

Defining role based system access levels is extremely
beneficial.  Many times, applications
will have granular security which is capable of hiding groups of functions not
needed by all users.  This level of
granularity should be managed by someone intimately familiar with the system that
can fulfill user access requests.  Functions
needed for system administration should only be accessible by the power user.  All other access to the system should be
predicated on what they need available to perform their jobs.

Empowered users can serve as front-line support for other end
users, intercepting many requests before they reach your desk in the form of
support incidents.  In the days leading
up to a system go-live event or immediately after, go over documented steps to
resolve common issues and requests.  Is
the user unable to print because the printer is paused or out of paper?  Teach them to fix common problems and it not
only frees some of your time, but it also makes for happier users.  Their issues are resolved quicker because
they won?t need to wait for your schedule to become light enough to help
them. 

Empowered users can prove extremely beneficial in
communication.  For instance, I have
found them to be very helpful with relaying system downtime intervals due to
server reboots, patch installations, etc. 
It is much easier to provide pertinent system information to one user
and have them disseminate that information to the other end users.  A power user can also provide details
(sometimes in the form of screenshots) about a reported problem which can prove
beneficial when troubleshooting and working with the vendor.

Empowered users can accomplish many things, but most
importantly they can make your job easier. 
Don?t leave them out of your plans when rolling out that next
system.  And, as always, let me know your
thoughts and experiences related to this topic. 

by austamm

I do agree strongly with the concept of empowering users. With the ever incresing solutions that need to be provided by IT personnel, one should not be stuck with some routine roles that could easily be assigned to super users. There is evidence of an increase in resource utilisation by users with because of this. I practice this.

Amimu

by the old man

While a crude example,  our folks never had to pump gas.  Now everyone does.

Another is the self check out line at the grocery store..

It's the only way to survive.  The key is finding out where to draw the line.

 

Great Post!

 

by bill elmore

Microsoft paid a visit last week; not the entire company,
mind you, but a couple of disciples to spread the good faith. They worked in a pre-sales capacity and one
had the ominous title of Messaging Specialist.
Messenger, disciple ? what?s the difference, right? Anyway, you?ve probably guessed they were
here to tout the coming of Exchange 2007, explain the added benefits, and get a
pulse for our readiness to upgrade.
Given the fact we are just completing the final stages of an upgrade
from Exchange 5.5 to 2003, I explained that this discussion was a bit
premature. Then they offered us some
water to drink, which we accepted, but discovered it tasted strangely similar
to Kool-Aid.

Exchange 2007 should arrive sometime in the first quarter of
?07, not by the end of this year like you may have heard but didn?t quite believe
anyway. I?d like to know when Service Pack
1 will be available because that is more likely the first time we will begin to
consider another upgrade of our messaging system. Let someone else discover the problems usually
found in the release of a new software version.

The meeting was brief and not filled with much ?meat? as it
was largely meant to answer questions about Exchange 2007 and build excitement
about its impending release. The latest
version will continue Microsoft?s trend of attempting to be your one source
solution provider. And while I can?t
dive into much technical detail in a short blog entry, I can opine my thoughts
on some of the new features being hyped.

Unified Messaging.
Much is being made about the UM integration in the next Exchange
system. I have to admit that I like what
I?ve read and heard to this point about integrating voice and fax access with
my email (pause as I sip my drink).
Sure, aspects of UM have been available before now thanks to third party
vendors who filled in functionality gaps left by previous Microsoft releases. Companies like GFI
or Castelle offer unified fax solutions,
and there are many companies like Adomo
that offer unified voice mail solutions.
But now (through various company acquisitions, of course) Microsoft can
offer the total solution. Their vision
is to have total voice and data collaboration.
Couple Exchange with Microsoft Live Communications Server and you also
can include VoIP to make your unified messaging experience complete (sip).

Security. Microsoft
has rightfully taken a public beating in recent years about the security holes
and deficiencies in their OS releases and other core products. This is a good thing. They are making huge strides to improve
security, and Exchange 2007 is another step in the right direction. If you take a look at the latest published feature
list
, the first and largest section displayed is the one listing numerous
built-in security enhancements. A
significant number include ant-spam and antivirus capabilities. And there is now a new Exchange component
called the Edge Transport server which sets in your company?s DMZ and acts as
the first line of defense for outside facing mail flow. By default, all intra-organizational mail
flow is encrypted. Regulatory compliance
is even addressed through support for Information Rights Management and message
transport and storage rules-based encryption and retention (sip).

Management. Microsoft
is well known for ?wizardizing? every common IT task that can be
automated. Maybe it ?dumbs? down the
average IT pro, but I tend to appreciate a good wizard tool to make my job
easier and faster. Have you ever
suffered through a horribly long and complicated math homework problem only to
be told by your teacher the next day that there was a two-step shortcut? Sure you have. Microsoft sympathizes with your plight (sip)
and has made managing Exchange (almost) entirely possible via the new Exchange
Management Console which happens to be based on the new MMC 3.0. And for those that need to manage from the
command line, there is the Exchange Management Shell. Everything that can be done from the
Management Console, and more, can now be done within a script.

There are many more new features and enhancements (sip)
bundled with the next Exchange release, and I don?t have room to cover them
all. For instance, it is a native 64-bit
application which will increase memory and processor efficiencies and improve
disk I/O. It also offers improved data
replication and search capabilities (sip).
But I digress. From what I?ve
seen so far, Exchange 2007 has much to offer.
Whether it has enough to warrant another upgrade in the near future may
be a different story. My cup is now
empty. I?m done.

by br123456

I would be interested in whether or not the disaster recovery steps are still as much an incomprehensible mess as it is with all the other Exchange versions.  I would gladly trade each and every new feature they have in Exchange 2007 if they could just make disaster recovery 1) quick and 2) easy.  No matter what role the server has which exchange is installed on.  No matter what type of hardware the recovery server has.  No matter if it is a mailbox store, a mailbox, a public folder store or a public folder.  Forget about Recovery Groups, which is more a cludge than anything.  It didn't really fix the problem.  Disaster recovery in Exchange is a nightmare.  Now that MS is integrating faxes, phone messages and other things into the system, rapid and simple disaster recovery is that much more critical.  As it stands now, I would never want Exchange responsible for these new roles if I knew that the disaster recovery mechanisms are still as slow, cumbersome and fraught with peril as they always have been.

by bill elmore

I recently read an opinion column from Dr. John Halamka, a practicing
physician at a teaching hospital, which discussed the pros and cons of
converting from paper to electronic medical records. I found the article to be very interesting
and happened to agree with most of what was written until the final few
paragraphs. He stated that the hospital
where he practiced was going to give patients the option to choose between
having their records stored electronically and storing as traditional paper records
? their choice. What? How can this possibly be something that a
patient can make an informed decision about, and more importantly, why offer
the option in the first place?

Dr. Halamka?s main reason for giving patients their choice
of record storage method stemmed from the publicity of recent data
breaches. He reasoned that though it was
relatively easy for someone, authorized or not, to walk around a hospital and
swipe a handful of patient records, one electronic data breach can compromise
the integrity of thousands of records.
While he makes a valid point that the total number of patients at risk
for identity theft is higher using electronic storage, you shouldn?t just
transfer such an important matter to a person who probably doesn?t understand
the far reaching implications of their decision. And my guess is, if they are ill enough to be
at the hospital, they probably have more pressing topics on their mind than
what format their medical record is kept.
If you?ve been to the hospital recently, you probably remember how many
papers are placed in front of you to sign ? insurance authorization, privacy
rights, acknowledgment of treatment risks, etc.

Please sign beside the
X here, here, here and here.

Yes, whatever you say.
Just let me see the doctor. I?m
sure everyone reads and understands all of the paperwork placed in front of
them, right?

The benefits of converting to an electronic medical record
system are many. Complete records can be
viewed anytime from anywhere, and records can be accessed concurrently by other
hospital staff. Any location with a PC,
proper authorization and access to the hospital network can be used to view an
electronic medical record (EMR). Faster
access from more places means medical staff can make quicker and better informed
healthcare decisions. Greater
coordinated care can be achieved by interfacing the EMR system with hospital
clinical applications, resulting in a more complete care assessment and reduced
critical errors. Improved hospital
workflow efficiencies can result in greater physician productivity and patient
care. Audit logs showing who accessed
which record and when can be maintained by system administrators. The ability to comply with HIPAA and other
government compliancy regulations can be achieved. The list goes on and on.

Likewise, paper records can only be checked out to one
person at a time and must be picked up in person or sent for. This can result in delays in patient care and
potential errors in critical decisions.
Also, many times the paper medical record remains incomplete, even
through follow-up reviews, while it takes time for various labs, x-rays and
tests to make their way into the paper chart.
Access audit logs are often not available.

Besides the above pros and cons, when a person becomes a
patient at a medical facility they grant a certain amount of trust to the
institution to make decisions about how best to provide a safe patient care
environment. In other words, I don?t
need to see everything that goes on behind the big red curtain. There are certain decisions best left to
trained professionals and not second guessed by the average lay man. If the hospital you are seeking care at spent
the money to research and implement an EMR system, you are indirectly opting to
have your medical record stored electronically.
In fact, a decision to install an EMR system is not made as an IT
decision, but requires heavy buy-in from physicians. If your preferred physician practices at a
hospital utilizing EMRs, it is likely that he or she bought in to the benefits
at some point; otherwise, they?d probably be practicing elsewhere.

I?m all for empowering people to make decisions concerning
their own welfare, but certain decisions are best left to trained
professionals. If patient care truly is the
hospital?s number one goal, storing electronic medical records as opposed to
paper records is an easy choice to make.
It pains me to see knee jerk reactions to media reports of data breaches
that could compromise patient care. Hospitals
should make a decision and stick by it.

by jaqui

There are drawbacks, besides the security breaches mentioned.
like the DHS' right to any records so stored from any company with an office in the US.

when the local medical services plan contracted with a us based data storage firm to store all medical records for them, they put themselves in violation of the federal privacy laws.
[ yup Oz, BC Medical Services is in violation of F.I.P.P.A. ]

by nathank9

You hit the nail right on the head Bill, when you walk into a hospital the last thing you want to worry about is data fraud. Paper records have worked well in the past, however it is very easily for a data-hungry employee to just meander through the cabinets looking for data to steal or memorize. HIPAA has done what they can thus far to protect patients and their data, however the moral issues beyond it are what are costing people their medical records these days. You trust hospitals with your life, let's hope hospitals figure it out so that you can trust them with your data as well. 

by Member 27831507

Of course we all know that a sharable file of your health records in your hospital is a 'good thing' but given the state of the National Health Service  (UK) project to automate records and bookings I am very sceptical when someone says  "trust me, I'm a professional"  for two reasons.

1- The quality of data security is poor because of staff turnover is faster than IT know about

2- Of course the media should react...knee jerk or any other kind of jerk...that is why they exist. They also keep the pressure on 'professionals' to act instead of going into denial.  We have a duty of care and have to be ready to explain what we do and why.

But then of course we don't have the level of damages and law suits in the UK as compared with the USA...yet !   Till then we must do our best to help the medical staff do their job....The big benefit is that on a computer screen they can read the history instead of struggling with illegible hand writing....

by derek_r

This is a no-brainer. Notwithstanding that there have been security breaches, well-publicisized ones, no one has suggested that banks revert to the paper-based client account systems of 25 years ago. The benefits too far outweigh the risks; it would be a silly idea and everyone knows it.

So it is with Electronic Health Records (EHR). EHR will finally bring the management of clinical care into the modern world -- and about time, too. I've heard it said, as an argument against EHR (oddly), that people care more about their health records than they do about their financial records. That statement doesn't apply to me; personally, I would be more upset about disclosure of my bank information than I would about a breach of privacy of my medical records. That said -- I care WAY MORE about receiving professional, competent, timely, efficient healthcare than I do about convenient banking.

by master meng

Ya ay yah yah.... the thing is we all like tech, and rely on it daily, but some of us don't seem to be able to control our selves when it comes to a new convenient techie way of doing thins. This reliance on tech is the number one way identity thieves get our info...just stop o think about it, please.

 

 

by master meng

Ya ay yah yah.... the thing is we all like tech, and rely on it daily, but some of us don't seem to be able to control our selves when it comes to a new convenient techie way of doing thins. This reliance on tech is the number one way identity thieves get our info...just stop to think about it, please.

 

 

by john

EMRs are a no-brainer.  The evolution of all business operations to an electronic infrastructure is inevitable.  Computerization of operations in the bloated and ridiculously inefficient medical industry is long overdue.  I am sick of paying over $300/mo for insurance, $3/pill for Rx and then see that nobody in my Dr's office can even figure out the last time I was in there.

My favorite way to pass the hour or more I sit in the waiting room is to stand at the front desk and read the open paper files of other patients that I see laying all around the office.  I am not convinced that Dr's or anyone else in the industry are so concerned about privacy.  I think they are all just scared of knowledge and technology that they do not understand and have not spent a decade in school to learn.

Now, that said, I am concerned about DHS's need to ignore the privacy of medical or any other personal data.  I would recommend that any data storage service employed by any business that keeps private data be used post encryption.  Any discussions about DHS and personal data storage?  Any technologies that can encrypt data at a stage that is immune to the prying eyes of big brother?

by marciaesp

I have been an RN since 1957, worked in many hospital settings, including a physician's office. Medical records have never been totally secure! I am also an amateur computer person, got my first Commodore 64 in 1983, on my 12th computer now. I believe computerized medical records are definately the way to go! The pros out weight the cons so very much in my opinion. In our immediate family alone we have had ancillary hospital personal divulge sensitive, confidential medical information to others three times, all done without the need of a computer! 

Marcia

by vbock

This is a no-brainer.

Would that it were so, in the short term.  Until there's a standard for the EMR data record, the risk of choosing wrong is extremely high for any given player. My husband is a solo practitioner, being squeezed by higher malpractice premiums and lower insurance reimbursements, and we're having to invest thousands of dollars this year in upgraded computers and software because the feds have come up with a new data structure for EDI (Electronic Data Interchange) to handle the billing side.

It's very clear to me that EMR is the future, but we can't afford to invest in a system only to find out that the hospitals, or the docs he shares coverage with, or Medicare, or Blue Cross standardize on something else.

by vbock

This is a no-brainer.

Would that it were so, in the short term.  Until there's a standard for the EMR data record, the risk of choosing wrong is extremely high for any given player. My husband is a solo practitioner, being squeezed by higher malpractice premiums and lower insurance reimbursements, and we're having to invest thousands of dollars this year in upgraded computers and software because the feds have come up with a new data structure for EDI (Electronic Data Interchange) to handle the billing side.

It's very clear to me that EMR is the future, but we can't afford to invest in a system only to find out that the hospitals, or the docs he shares coverage with, or Medicare, or Blue Cross standardize on something else.

by bill elmore

Well, I finally did it. 
Last week I finally allowed myself to let go of a support issue that I
didn?t need to continue supporting.  I?m
sure most techies would agree that sometimes it?s just tough to step away from
a task and let someone else handle it.  Who
better to fix something than you, right? 
You?re never fully confident someone will do as good a job as you would
do; it?s called human nature.  And at the
center of it all is a little thing called trust.

Who better to fix the interface server with the transactions
backing up?  Who can get that SQL Server
cluster back up the quickest when it loses connection to the SAN?  Outbound email isn?t being sent.  Who better to fix that?  The answer, of course, to all of these
questions is the person staring back at you in the mirror ? YOU. 

But then again, if you?re always busy saving the world each
day, who is installing the new systems and upgrades?  Who is performing health checks on your
directory services infrastructure and mail servers?  Who is reviewing system logs and keeping up
to speed on all the latest security patches released by Microsoft this month?  If the answer is still you, you may have a
problem; if not now, then soon.

At some point, we have to transition a new system or upgrade
from the installation and ?baby sitting? phase to the general support and
maintenance phase.  The ?anyone on my
team should be able to troubleshoot this? phase.  That is, of course, assuming you posted build
notes and support documentation for each of your installed systems.  You did do that, right?

Yeah, I thought so, me too. 
Who has time to take screen shots and document support procedures for a
system that is newly installed and, at the moment, stable?  It is agonizingly time consuming and boring ?
not nearly as interesting as saving the world from certain peril.  We generally exist in the workplace to rush
around and extinguish fires and high-five our successes.  There isn?t much glory in pasting Print
Screens in a Word document and creating a Table of Contents with
hyperlinks.  But if you don?t do it
relatively soon after a new installation, you may later find yourself
scratching your head and sifting through notebook pages and emails to figure
out what to include in the documentation. 
And what?s worse, until it?s complete, you will be the one person
supporting the system.

That?s pretty much the scenario I often find myself.  I work a few months or longer to get a new
system in place, and then, as soon as it?s complete and stable, I move on to
the next project.  Documentation is an
afterthought.  But sooner rather than
later the system will hit a bump, and I will get the privilege of fixing it
because I didn?t bother to share support information.  Some of this is because I was too lazy to
document, and some is because sometimes it?s just quicker if I fix it myself.

Or at least it seems to be quicker.  In reality, it?s more costly to the end users
and me.  I end up with too many irons in
the fire so to speak.  I get stretched
too thin and find myself unable to respond to support issues in a timely
manner.  Think about it.  Implement several new systems each year at
multiple sites, multiply that times a few bygone years, and you quickly find
yourself unable to juggle adequate support alone.

The solution is to trust your colleagues, empower them
through communication and adequate support documentation, and realize that it?s
not a good thing to hold a monopoly on all the systems you?ve been given
responsibility for.  It?s easy to believe
that by holding onto knowledge that no one else has, you are more valuable to
your company.  But in reality your job
performance suffers and you become a liability. 
It?s okay to let go.  Really.

by cssatx

The same phenomena happens with managers, although with different outcomes. Most managers got to where they are by having demonstrated some degree of expertise. As a manager you need to allow your team to do what they do best. If you continue to be involved in firefighting and the minutia of the work, how can you become an effective manager. Again, the solution is to trust that those you manage can get the job done ... at least as good as you would do it.

by propellerheadus

I find that most people would rather die than think for themselves, and take responsibility.  I write documentation.  I do knowledge transfer on tools (share point, live meeting, office suite documents, etc).  And I find that in my particular areas of expertise that I'm still the best one to do certain tasks no matter how much I try to transfer the knowledge. 

Perhaps I'm a poor communicator, but I try hard to do exactly as you suggest.  I find that folks give up and pass it to me, as opposed to me going and seeking the tasks out.

by th7711

Agree with Bill and sharing the view from klking@.... Someone is just too lazy to pick up new knowledge or skill. This kind of people should not stay in the field as they have no IT professionalism.  

To resolve this issue, I suggest to define the accountability of each individual member in your team clearly and shift the duty among them. If you have a team less than 3, don?t bother. You don?t have this luxury as you are in the fire-fighting situation everyday.

by the old man

Klking brings up a great point.  There hopefully will always be something we are the best at,, but 10 (give or take) years ago someone in the background who was the best let us fumble through it, make the mistakes that always teach us the most, and empowered us to become the ?best?.

by bill elmore

Here?s a dilemma that?s frustrated many an IT pro for
years. If we truly are in the electronic
age and everything is becoming digitized, why, oh why, are we spending so much
time troubleshooting and accommodating printing issues? Printing is the bane of our existence, always
rearing its ugly head when we least expect it.
We can customize the interfaces of a new system to work with existing
applications and deftly coordinate a multi-site client rollout to appear
seamless to the user, but it?s troubleshooting the printing problems that drive
us absolutely bananas!

Users seem to print more now than ever. Replace a paper system with an electronic
system and what happens? Users print reports
and screen dumps. Most of what?s printed
out is thrown right into the trashcan. A
quick search on the internet reveals that numerous organizations and educational institutions report a
sustained gradual increase in paper usage.
That can be an entirely separate topic for another day, but my point is
electronic systems aren?t decreasing the amount of printing by users, they?re
increasing it. And as it increases, the
more importance is placed on the printing infrastructure and the more IT staffs
walk around with headaches from chasing down the myriad of resulting issues.

To compound the problem, the cost of printers continues to
go down while the quality of lower end printers continues to rise. So it?s becoming increasingly easier for
staff to justify purchasing personal printers.
Everyone can create a reason for why they ?need? a printer of their very
own. Mostly, managers play the
confidentiality card. They can?t be
expected to print performance reviews and other confidential documents on the
departmental printer. Okay, fine. I can
accept that. Plunk a printer down in
their office. But then staff reports
that they need printers for the mobile laptop carts. Reason ? they can?t walk down the hall to the
unit?s main printer. That would negate
the benefit of having the mobile cart in the first place. Then the billing department reports that they
require individual printers to print each customer?s account screen. Reason ?
it?s easier to read the printouts than the screen.

See where this is going?
It?s a runaway train headed down a steep cliff. It appears we?ve spoiled our users into
expecting technology coddling. Think of
someone at home frantically looking for the TV remote instead of walking over
and turning the channel (I?m not saying I?ve never done it.) I?ve
got to have it now and I shouldn?t have to move to get it.

So what is wrong with so many printers scattered around the
workplace? It complicates the printing
infrastructure and can severely hinder the deployment of thin client based
solutions. The more printers installed
in an environment, the greater number of model types, and that means there are
a greater variety of print drivers. It
becomes impossible to keep up with the number of drivers needed on Citrix and
Windows Terminal Servers; keeping up with the model type, platform and whether
it?s PCL 4, 5e, 6 or PostScript (please, anything but PCL 6.)

Printing in thin client environments has improved in recent
years. There are better universal
drivers from companies like HP and Citrix; better but not perfect. And special features such as duplexing are
usually forfeited when using a universal versus model specific driver. Citrix MetaFrame Presentation Server 4.0 has
an improved printing architecture, but still has its challenges. Unless you can keep up with print driver
mappings and experimenting with which driver type works for different
applications, you will always have a fair share of printing issues to
troubleshoot.

For example, a user with an attached scanner connects to a
Citrix server and the session hangs because the server can?t correctly map a
driver for the scanner. All subsequent
client sessions stall keeping anyone else from accessing the published
application, and the print spooler service hangs, not stops, preventing print
jobs from successfully printing. For a
solution, you can ferret out individual printers and add mappings each time, or
choose to only connect a client?s default printer, or even install a local
printer on the server and disable client printer connections altogether. But troubleshooting printing issues will
continue to consume a better part of your time.

Sure, you can attempt to standardize on the printers being
deployed and drivers used. But models
get phased out and replaced, and drivers get updated by users with proper
rights or local IS staff, etc. It?s not
quite as easy to maintain as one would imagine, especially in large
corporations. Depending on the company
you work for, chances are good that IT doesn?t have the political clout needed
to keep certain departments and users at bay when attempting to
standardize. There may be times when you
can?t tell someone ?no? to having a personal printer or ?no? to certain brands
and models.

So what is the solution?
I don?t exactly know. Maybe you
can tell me. IT isn?t generally a
revenue generating department so our influence sometimes falls short compared
to a department that is a company cash cow.
Sound off and let me know your experiences!

by pjcasey75

As a consulting dealing with electronic forms solutions, having also been a printer rep calling on Fortune 100 companies in the past, I can confirm that the electronic revolution, especially web based systems, has increased, not decreased, the amount of printing in the world.  Standardization is a dream mostly unfulfilled.  And, as you noted, the reasons for failing to implement solutions which are already available (centralized printing/scanning/copying/faxing on high capacity departmental multifunction devices or utilizing advanced networked print management tools) are mainly political, not technical.  Lastly, you hit the nail on the head when you mentioned that clout is related to money.

So here's how to find some clout.  You have to frame the argument for change in terms of money.  And then you have to go to someone, usually outside IT itself, like the VP of Sales or the CFO, even the CEO, someone with clout, who's looking for money.  Money to hire people, money to run an ad campaign, money to open a new office, or maybe money to keep from having to lay off precious resources.

No one in your company, and I mean no one, has their arms around how much money the company is literally throwing in the trash can.  Try asking purchasing how much money is spent on paper and toner.  Lots of times they can't really tell you, or if they can, they're missing pieces of the data.  Facilities buys paper and toner for copiers, departments and units buy "office supplies".  This waste is hidden in thousand thimballs all ovrer the place, and no one knows the big picture.  No one budgeted the company's overall cost of printing.  Purchasing may actually buy it all, but who uses the supplies, and for what purpose?  What's the overall budget?  And how far over or under budget (yeah, right) are you?

Until someone internally (outside vendors can give you numbers or do surveys, and because they're vendors, no one will believe them) does a study and proposes a solution WITH NUMBERS, no one will have the impetus for change.  Whining about how much trouble printers are for IT to handle doesn't work either.  Most of the time the attitude is - I want a printer, and it's your job to make it work.  You have to put a cost on it, and go high in the organization to someone who's concerned about that cost.

For IT, troubleshooting printers "consume(s) the better part of your time".  Most people outside IT don't realize how much time you really spend on this.  They think you're doing "cool stuff".  Count the cost of that time and let the company know what else you'd like to do with the time you're planning on saving with your new efficient printer strategy.  Printing is like toilet paper - everyone needs it, everyone expects it, and everyone complains if you don't have it right here, right now, but no one wants to talk about it.   It's not the "cool stuff", but if it consumes the better part of your time, overspending time an money on it needs fixing.  Lastly, if you do decide to tackle this analysis, don't put your most junior IT person on the task just because no one else wants to deal with it.  That action too, reduces "clout" in the eyes of the company.

PJ Casey, Consultant

by bork blatt

I say: "Make 'em walk!"

If they can't justify a walk down the hall to fetch a document they just printed, then the printout can't have been that important, could it?

by br123456

I read an interesting article a few years back about how it came to be that the printing subsystem of Windows 95 (or maybe it was w98) was a massive overhaul of the previous version.  It took an opinionated Alex St. John, then an evangelist at Microsoft, to express that the current printing subsystem of the time was a mess.  He caught a lot of flack and ruffled the feathers of a lot of MS developers at the time, but it did get the attention of Bill Gates.  It was dedided that an overhaul project should proceed.  They did so and in the end, a major overhaul was completed and desktop printers flourished.  Since then, however, the architecture has not seemed to scale up and is viewed by many to be clunky and error prone as described.  Maybe it is time for MS to take a serious look at that architecture again.

by straightshooter

I've joked about this issue frequently over the years and I believe I have designed the perfect solution.

Here it is: The output tray of every printer feeds directly into a paper shredder. This eliminates the loss of productivity caused by someone having to go get the document and then put it in the shredder. Maybe HP or one of the others will jump on this idea. Remember, you heard it here first!

by toilone25

The paper flood is caused in large part by IT's refusal to provide sufficient screen space to allow users to view 2 documents or applications at a time.

I have a 20" screen at home and I can put up 2 window side by side and get real work done on a computer that is not even connected to a printer.  The miniscule screen I have a work requires terrible gyrations or I print out one output to reference while I work on another.

That used to be excusable because scress space was expensive.  Not anymore.  Admit it you IT types all want systems so secure that all of those pesky users are locked out entirely.  "Send them back to a pencil and a Big Chief Tablet."  That's your motto.

by bill elmore

I assume it?s the same situation everywhere, but more and
more vendors seem to play by their own set of rules rather than the
customer?s.  They attempt to anyway.  It?s not enough to review basic system
requirements posted on a web site.  You
have to really ferret out the details of what installing the vendor?s system
means.  Almost like a reporter
researching a good story, you need to know what questions to ask and who to
ask.  You need to analyze the data and
piece together the puzzle.  They may not
always be forthcoming with the information, especially if they think it could
be a deal breaker.

Will users need to be local administrators to run the
client?  Will the application need its
own VLAN or completely isolated network? 
Are there conflicts with their requirements versus your Group Policy
settings for items such as password length or other security settings?  Are there special requirements for running
antivirus or backup software?  Are
certain components still using 16-bit code or defunct unsupported third party
plug-ins?  Does the vendor insist that
their server not be a member server of the company domain?

The list of questions can go on nearly forever, but it?s
important to expose the facts prior to signing a contract or giving your stamp
of approval for all things technical. 
The trend I see occurring is vendors wishing to isolate their application
as much as possible from a customer?s environment; attempting to protect
themselves from support calls and blame due to a change or outage on the customer?s
side.  This is somewhat understandable
given the growing complexity of IT infrastructures and the support nightmares
which can arise.  Finger pointing often
ensues.  But isolating every installed
system just is not feasible or practical. 

As an example, a vendor I am currently working with is
requiring that their servers be in a separate domain and a two-way trust
relationship established with our domain. 
If we wish to instead make them member servers as is our policy, then
they require that we sign a waiver release form to absolve them of
responsibility should a change to our environment cause a system outage.  This all seems ridiculous to me, but the
company reports that ?95%? of their clients go along with the separate domain
scenario.  I have a difficult time
believing that figure unless most other customers are relatively small and have
unstructured IT departments.  In this
case, the vendor is attempting to impose their will on the customer, and
effectively disregard a company?s established IT implementation best practice.  This would set a dangerous precedent if allowed,
and make us susceptible to numerous security threats, not to mention, we would
lose our ability to manage devices on our network.

While segregating systems in an effort to improve network
performance and stability are nothing new, making customers sign responsibility
waiver forms is, at least to me.  Obviously
there are a couple points of contention here. 
The trend toward application isolation wouldn?t be as prevalent if
software makers wrote more sound software that adhered to generally accepted
coding standards, and companies always followed best practices and were
proactive in maintaining their IT infrastructure.  In lieu of a perfect world though, vendors
and their customers should jointly research the environment and software prior
to beginning implementation.  This could
serve to determine potential pitfalls and also develop action plans that are
agreeable to both parties.

Allowing each vendor that walks through your door to set the
rules of engagement will never work in the long run.  Each environment is different than the next,
and each company must create reliable IT policies that protect the stability of
all their supported systems
collectively, not just one going in today.

by Member 24740272

The author seemed to put the blame on software development. "..if
software makers wrote more sound software that adhered to generally accepted
coding standards..." failed to acknowledge the fact that most software projects failed not due to a lack of following coding standards.

One of the top reasons for failure of software development project is that users can't make up their mind of what they want and yet want the project to complete in a timeline that would seemed unreasonable to most software developers.

A tight deadline with alot of changes over and over again is definitely going to result in failed software projects.

Michael, CITPM, PMP

by davidaaaaaaaaa6

After many years of implementing core business and ERP applications I can say without hesitation that the biggest reason for problems at implementation or post implementation are the customer required customizations.  While there are some differences from one business to the next most applications are flexible to allow for most of these differences.  If you are installing a best of breed application and you have done your research you should not need customizations.  If you do then you may want to review your business practices to see if they are inline with the industry standards.

 

The short of it is if you require the vendor to customize the application for your install then it will not be as sound as the base application.  Your vendor is the expert on their application.  If you trust them you should follow their recommendations (not blindly).  If you don?t trust them then suggest to the powers that be that you not do business with them.

by sr10

OK, maybe 95% of the people who actually bought the product signed the waiver. What percentage of the people the vendor called on actually bought? What percentage of the people they called on laughed them out of the building when they mentioned their waiver?

by kovachevg

From a technical stand point, it makes a lot of sense to isolate an application server in a separate domain. That actually helps the customer by protecting him from the complexities of securing an exposed system.

The difficulty in this case springs from the fact that the customer needs to have the expertise to manage this new scenario - now the customer needs to dedicate a skilled system administrator who is proficient in subnetting and network routing and to purchase a reliable VPN solution.

If the vendors were smart enough, they would package their application with the VPN solution that would transparently deliver the services to the customer's netowork. Pitching security and reliablility to complete this sale is paramount.

Vendors and customers alike tend to play the BLAME GAME. It's kind of easier this way, instead of paying a bit more to have a reliable solution. But hey, that's why there is such a thing called oraganizational maturity. Some cusomers and vendors get it, some don't.

by idratherbdiving

We have many vendors that also require such ridiculous things as this.  One of the best is not wanting any virus protection on the machines becasue it may interfere with the vendors poorly written application, but they want you to put it on you network and guarantee it remain virus free.

by angry_white_male

Remember - you're the one holding the checkbook.  Make sure all of these issues are hammered out before signing the conract and writing the check.  Additionally, make sure that the people involved with the software (the guy writing the contract, the dept. head who's purchasing the system, etc...) are on the same page with you.

We've dealt with these issues in the past and thiere's nothing worse than having a system thrown at you when IT was kept out of the loop and having to deal with something that was put together in such a way that goes against every common sense IT thing that you do on a daily basis.

The big thing is remote access so the vendor can provide service - every vendor use a different method - each requiring a different way of accessing it over the internet. 

Make sure IT is involved from the beginning - otherwise, you'll be living with someone else's decision at the expense of your sanity and network security.

 

by chuck1612

Some of my tips on dealing with pushy vendors ... pretty much the same as dealing with a pushy car salesman ...

Know the word "no" - when you hold the $ you have this power - once you spend the $ you give up some of that power - so they answer is "no" until what they offer is worth the "yes."

Techies love to have other techies affirm and bow to their great sage all-knowing uber-geekness. The savvy vendors play to this. Don't fall for it.

Know who you work for. I'm a school district CIO, so I work for kids, their parents, and the taxpayers. My goal is not to make a vendor like me.

There's a lot of crap software out there (especially for the education sector). If you can't "try before you buy" then buyer beware and then some!

If you didn't talk to other customers first, that's on you! "Client list" does not equal "list of clients who actually bought this particular package, are using it successfully, are on the same version being sold to you, signed on to the whole system, and wouldn't be too embarrassed to admit that they made a crappy decision if asked."

Like the blogger said, "stick to your standards." Don't let one vendor get you to bend them. And don't sign stupid waivers!!!

Chuck Longfellow, Director of Technology, Appoquinimink School District, Middletown DE, USA

by bill elmore

Answer honestly. How
often do you use search engines? I
know. That?s an incredibly broad
question. Sure, I use Google, MSN or Yahoo
to find information on web sites just like millions of other web surfers. But how often do you use Enterprise Search tools to find data relevant to performing your
job? That is, disparate data stored not
only on the Internet and your intranet, but across data and email repositories,
content management systems and databases to name a few. Admittedly, the closest I?ve come to using an
enterprise search tool is Google Desktop or our company?s intranet. Finding files on my workstation or links on
the Internet? Yawn. I want to see something that helps me find
that long lost box of CDs in my garage.

Okay, there is nothing that can help me find what I?m
looking for in my garage. (In fact, I
think my wife secretly threw the box away and gets great enjoyment from
watching me fruitlessly search for it.) So,
short of that miracle, there are some very intriguing advancements in search
technology that will become more important as the volumes of data which
companies store continues to grow.

When you stop and consider all the places your company
stores data, it?s daunting to think about how long it would take to search through
each individual location. Today?s
enterprise search tools can not only search every nook and cranny of your
network, but can search for data regardless of the format it?s stored. Tools such as Vivisimo?s Search Engine can search for
data within relational databases, PDF, ZIP and GZIP files, email, MS Word,
Excel, file servers, intranets. The list
goes on and on. Search results aren?t
returned in the common linear lists which make it difficult and time consuming
to sift through either. Instead, premium
search engines can offer results in clustered and conceptual categories. Take a look at some of the online demos by Vivisimo and you
immediately get that ?Aha!? reaction about what should be the norm when you
execute a search.

Another major player, if not THE player in enterprise
search, is a company called Autonomy. It incorporates what it calls Meaning Based
Computing which takes unstructured and disparate data, and enables computers to
create meaningful relationships. This
goes beyond just performing a keyword lookup which only works to find all
documents with an exact match. Instead,
Autonomy also attempts to find results which contain the same or similar
meaning to what is queried and can execute searches based on pattern matching
and language translation.

Many corporate solutions don?t rely on only one search
technology. This is where federated
search systems come in. Federated search
takes one familiar front-end search box and passes the query to multiple search
engines. So, say, a search on your company?s
intranet may use Vivisimo or Autonomy technologies to locate data within your
network, while a ?hook? on the backend may also return results using Google or
MSN. This could also have applications for
companies who wish to point search engines toward data repositories on company
extranets. For instance, a search for a company
purchase order would not only return results from your corporate CRM system,
but also the invoice stored on the outside vendor?s data storage system.

Yes, there are also enterprise search engines such as Fast Search & Transfer (FAST) which
cater solutions toward specific niche markets such as corporate regulatory
compliance, criminal investigation and litigation compliance protection. FAST search engines even have the ability to
search video and audio formats and return results based on closed caption text,
voice-to-text recognition and sound recognition.

Speaking of niche search engines, Splunk is aimed at IT analysts who have spent
countless hours searching for the source of an IT problem. Pretty much nailed all of you, didn?t
it? Splunk allows you to search all data
being ?logged by any service, application or device within your data center,
regardless of source or format? in real time.
When an IT problem is reported, Splunk aims to reduce the mean time to
recovery through live reporting. Perform
a search for a specific error message or incident type and turn it into an
alert that constantly monitors for the event and notifies you when it occurs.

I am pleasantly surprised at the advancements being made in enterprise
search technologies. With the sheer
volume of data being collected and held onto by companies, it makes sense that
IT has rushed in to fill yet another void.
And since the main hurdle of how to index disparate data types seems to
have been conquered, the direction now seems to be focused on what to do with
the search results returned. This is why
so many of the companies mentioned also offer collaboration with Business
Intelligence tools to provide greater data analysis. This should be interesting to watch as the
market continues to mature. Now, if
someone could please help me with my garage?

by bill elmore

Improvements in patient safety make up the largest benefit
that information technology brings to the healthcare field.  There are others, of course, such as reduced
healthcare costs thanks to improved operating efficiencies, but safety should
be at the top of the list.  For all the
fingers pointed back at IT when things go wrong, because things do, it?s also
nice to know that we are installing systems which help save lives.  Look around the office the next time you visit
a healthcare provider to receive medical treatment.  Take time to notice the number of
computerized equipment and systems responsible for your care.  If by some small chance you look around and
notice that most of the technology can be accounted for by the video gaming boy
in the waiting room, you may want to turn around and quickly head for the door
marked EXIT.

Studies released by the
John Hopkins Children?s Center report on the reduced risk to patients which
resulted from the implementation of a computerized drug ordering system and a
web-based dosage calculator.  In short,
computer generated orders were compared to hand written orders and it was found
that twenty-seven percent of handwritten orders were incorrect versus six
percent of the computerized orders.  The
computerized system was able to automatically calculate dosage based on weight
and size, and also included safety checklists as well as warnings about
possible drug interactions.  It should
have been easy to assume that computers would perform more accurate
calculations than people.  The added
bonus was the ability to cross-reference other important information such as
personal history and potentially harmful drug combinations. 

The VA, yes the same VA still being criticized and burned at
the stake for being the only organization to ever misplace data, appears to
have done something right with regards to technology implementation.  They digitized the medical records of Armed
Forces members.  According to the Los
Angeles Times
, this truly proved its worth in the days following the
destruction of Hurricane Katrina as most people seeking medical care were displaced
and without their medical records.  This
forced physicians to guess about the patient?s past history and further
complicated the care delivery process, but not for VA members.  For them, doctors were able to access
prescriptions, records and previous lab results.  This helped improve the accuracy and safety
of the care they received.

There are countless other stories and examples which point
to how much safer healthcare is due in large part to the increasing embrace of
technology.  But I am not disillusioned
either.  Implementations of patient care
systems are often difficult for all involved, and often come with their fair
share of speed bumps.  And technology
alone does not make healthcare safer.  Along
with technology, it takes new approaches from medical professionals and the
modification of old processes.  Decisions
by IT professionals also come into play as we must decide which new
technologies to recommend and install. 
Do we go with thin clients and connect wirelessly to the network?  Do we virtualize servers and
applications?  All of these decisions can
affect the delivery of patient care, sometimes negatively.  Once staff becomes dependent on new systems,
the impact of a down system is felt by all, patients and doctors included.  Paper and pen, on the other hand, don?t go
down.

But despite some drawbacks and challenges, there is zero
doubt that IT can and does make the delivery of healthcare safer for
patients.  There are patient monitoring
systems that monitor a person?s vital signs and alert the appropriate medical
staff, and pharmacy systems that warn of possible allergic reactions and help
prevent overdosing.   Yes, healthcare is
making strong strides in safety thanks to IT. 

by leee

I worked for the VA in 1995-96, as a medical photographer. They were very, very aware of possible lawsuits (even though I understand it's rather difficult for a private individual to sue the government). Frequently something would go wrong, and we'd be ordered to destroy our slides in order to cover up any evidence. Although the procedures were often innovative, the facilities were (to put it nicely) decidedly unsanitary. It was (and still is) truly a hospital of last resort for many who have nowhere else to go. So, I do believe that some of their data loss is intentional - it's a bureaucracy, pure and simple, that can keep meticulous records on their patients while doing the old CYA act more efficiently than most.

I'm curious to know how things have changed in a decade.

by bill elmore

I may anger some vendors with this topic. Okay, I feign to care. Can someone please tell me why software vendors
send installation technicians who know so little about a) the product they are
installing and b) computers in general? Do you ever feel like the tech that just left should pay you for all the training they just received? Working
for a fairly large company I see my fair share of vendors come and go. We upgrade and install new systems every
year, maybe too many. But because of
this, I get the opportunity to work with many fine field ?engineers?.

In some cases, the technician the vendor sends is one of
their own, a corporate employee, and in other instances it is someone from a
local partner or VAR (Value Added Reseller). Either way, I find
that too many times their IT knowledge is severely limited. Get them out of their comfort zone and that?s
it. You may as well take over the
installation. Most arrive with
documentation that walks them through every step of the process. A script, if you will. I can appreciate having a script to reference. The script is a set of instructions that tells
the technician exactly what to do and helps to ensure that nothing is forgotten
as well as keeps their customer sites essentially the same. This can make troubleshooting efforts easier
for their support staff. The problem is,
don?t make them stray too far from the script or you could put the entire
installation in jeopardy.

It?s generally the little things. The tech arrives on-site to discover that
I?ve named the server something other than what his directions indicate;
instead of EMPLHSLP, it?s ADVRPT1. A few
months ago, I went on site to assist a vendor field engineer with a new
installation. It was a good thing too
because his instructions were to install everything to the C: drive. We happen to configure our Windows servers
with two partitions ? a system partition and a data/application partition. I confused him by instructing him to install the
application to E:. The day was then spent
demonstrating how to troubleshoot Windows error messages and editing batch
files to change path statements. I
honestly believe it was the first time he had opened a batch file for
editing. People starting fresh in the IT
field should not be sent to customer sites.
Or, if they are, they should be accompanied by an experienced
professional. It should be noted that he
was a professional, friendly guy who repeatedly thanked me for helping him and
showing him new ?tricks? to use for future installations. I won?t divulge the name, but can say that the
vendor in this case was a large international company that should be able to
hire qualified personnel.

I generally don?t mind helping others in IT, especially
coworkers. But I do mind paying a
company for a service, and then spending time showing their technicians how to
perform basic troubleshooting tasks. You
generally pay a third party to perform an installation or service call because
you?re either too busy to do it yourself or you want to have someone on-site
that knows more about the system than you.
This isn?t an overblown rant over one bad experience either. I see more and more inexperienced or
unknowledgeable technicians. I do not
want to waste valuable time training someone else?s staff, and paying to train
them just adds salt to the wound.

To be fair, there are many field engineers who are very
knowledgeable and good at what they do. I?ve
learned a lot from some and take my hat off to them. We do have a complex environment that may not
be typical of what most support staff sees.
Even so, I would expect the person who arrives to know how to work
around basic problems that almost always arise.
I expect the person to know what Citrix MetaFrame is, and to be able to
work with me when I tell him the server isn?t a physical piece of hardware but
is instead a hosted virtual server. Am I
asking too much?

What are your experiences with vendor field
technicians? Good? Bad?
Some of both I presume. If you
happen to work for a software vendor or VAR, defend yourself and tell me your
side. I know it?s not always black and
white?

by nicknielsen

Having been a vendor field technician in a past life, I can't disagree with everything you say. Yes, you should expect that your VAR/vendor tech is competent in basic
IT tasks. Yes, you would expect that the VAR/vendor will provide a
technician competent in your systems. I have worked with "experienced" technicians who couldn't recognize a command prompt two out of three times. I have also been sent to support systems that I have never seen before. These are training and qualification issues that the VAR/vendor must address. But what often happens is that the project requires an additional hire on a temp basis. Rather than hiring a local fill-in and sending out a tech familiar with the client system, the VAR will send the poor sucker just hired to the client site with no supporting documents or training except the requisite script, which was handed to him on his way out the door.

Scripts are indeed a problem, since most do not allow for deviation, even if the script is
wrong
. Script accuracy is always questionable, even when verified on actual production equipment. I have received more than one installation/configuration
script in my current job that caused me to raise my eyebrows when I
reviewed it before I tried to execute it. My familiarity with the
client systems was what got me through. The poor guy in the paragraph above doesn't even have that advantage. On the other hand, "standard" configurations at the client site often
aren't. Your example of a server name is minor; I have seen standard
configurations vary from power connections on the "wrong" UPS to major
hardware differences that made the upgrade impossible.

Neither side is blameless, neither is perfect. We do our best to work around or through the problems to get the job done.

by lcma

There is no discussion !! ... you are right. I worked for a big software corp for 12 years in Latin-America and had to face that a lot of times myself or through some "junior" staff at hand we had to send to our customer. The problem is money, costs and how important you are for that corporate/VAR/vendor. If you complain a lot maybe they will shift the senior consultant from one project he is currently on to go to your site.

I?m no longer working for a corp and want to add-value to my customers from my new enterprise. One way of doing so is by sending skilled technicians to the field but that narrows the scope of business we can deal with. If we want to grow we have to take risks ... and there begin the problem again ...

As a customer you should complain and never accept less than expected (even if the guy who came is a nice one and you don?t want to cause him trouble). As a vendor you should back your wage with qualify people, the market knows who is who because every more often they have started to share their experiences.

by steve ingham

If the local auto shop does not charge if it finds nothing wrong with your car, why do vendors charge when they supply no meaningful answer to your problem? Both shops spend time diagnosing. How were we sucked into this poor customer service business model????

by maxwell edison

Make a point to the vendor and just send them a bill. Your billing rate times the number of hours (quarter hour minimum and increments) that you had to train the technician. It might be interesting to see how they respond. If they do respond, it might be a good reference for discussing what the tech should and should not know when he's sent out in the first place.

by wayne m.

Custom Costs More

If one wants a non-standard configuration, one must expect to pay more for it.  This includes actual cost, time, reliability, and upgrade costs. 

From the description above, it sounds like the product was intended to reside on the C: drive.  By installing it in a custom configuration that has been untested by the manufacturer, one is accepting the risk of increased product problems.  One is also accepting the increased cost of installation, updates, and maintenance.  There may be significant benefits to having a custom environment, but that does not come without additional costs.

One of the basic tenets of quality is that efficiency and reliability arise out of reduction in variation; in standardization.  I do not know the environment and cannot state an opinion on the better approach for this situation.  Realistically, however, I would assert one should not expect custom operations while paying commodity prices.

 

by sql_joe


In reference to the response by Wayne M.

If the application requires installation on C: to be stable, I question the quality of the application.  We're talking a drive letter here.  

by misceng

For an ordinary consumer life is even worse. I have computer experience but now and then I get a problem which I cannot solve myself. If it is a Microsoft problem I go to "Help and Support" this instructs me to go through all the steps that I have already tried which did not solve the problem. It then tells me to contact my Administrator. Who is the Administrator on a home installation? Fortunately I know how to access the Microsoft Knowledge Base though even that fails me at times.

For other problems the trouble is similar. I contact technical support and have difficulty with the foreign accent but even more difficulty in getting answers of any value because the script the tech support is using covers the checks I have already done but goes no further. This is paid for by high telephone costs. Alternatively I email the company with the problem and get an answer which covers part of the easy bit of the problem but does not offer a solution. I then get an email from some marketing outfit which says how they were glad to be able to help with my query and would I please fill in this survey which in effect wants to know what sales technique will work on me for all sorts of consumer goods..  

 

by bill elmore

I have worked in healthcare IT for most of my professional
career. As I look back, it?s becoming
increasingly difficult to remember what life was like before regulatory
compliance laws such as HIPAA
were in place. IT projects were completed
much like they are today, where time is always of the essence and system
stability is crucial. Our main customer
continues to be the medical staff, and the wellbeing of the patient will always
be our highest priority. But there has
been a definite shift in certain aspects of technology delivery.

It used to be that support and implementation plans would focus
around what was the least disruptive to the physicians, nurses, etc. While that still holds largely true, HIPAA has
become the trump card to staff convenience.
Several years ago it didn?t matter who was logged into a computer when a
nurse accessed patient data. What was
important was that staff could walk up to the nearest PC and quickly retrieve needed
information. Accessibility reigned. It didn?t mean that was the most prudent way
to secure private healthcare data, it was just the path of least
resistance. A stroll down hospital halls
today, however, reveals PCs with screen savers and input boxes awaiting user
authentication. It?s probably not what
staff wants to see, especially with their busy schedules and the number of
patients being cared for, but HIPAA is now dictating that securing sensitive
data is more important than the few extra mouse clicks it takes to complete a
task.

There is something to be said for the weight that physician
voices carry though. They are, after
all, the ones responsible for most of a hospital?s revenue generation. No doctors mean no hospital, and no hospital
means no jobs. The shortage of other
healthcare professionals such as nurses also play a part in the relationship
between medical staff and IT departments.
Prior to HIPAA, hospital users could dictate some of the fine details of
a system rollout and maintenance. They
can still significantly influence the purchase of a new system and its use, but
the new system must now pass a final litmus test for HIPAA compliancy before
being acquired and put into use.

Without government regulations in place, which carry
significant criminal and civil penalties, companies previously erred toward the
side of higher efficiency and a healthier bottom line, even well meaning
companies. And even though network
security and data integrity have always been important, companies haven?t
always spent the money or time necessary to sufficiently reach an acceptable
standard. Companies have long known what
should be done to protect a patient?s personal healthcare data, but the effort
generally wasn?t there. However, money
talks and it is now too expensive not to comply with regulatory laws. Efforts presently place an emphasis on
securing data through encryption and safeguarding corporate procedures against
data breaches. Because CIOs and CEOs are
ultimately responsible for violations, the effort for change has trickled from
the top down.

HIPAA has dictated important changes to more than just end
users. IT staffs must also adhere to
what it takes to be HIPAA compliant. Regulatory
compliance was a tolerable notion when it only meant users had to jump through additional
?hoops? to complete their jobs. But when
IT departments had to change their modus
operandus
, they too discovered that the new laws were difficult to
bear. Domain administrators aren?t used
to having their network or system access restricted, but that?s exactly the
kind of change laws such as HIPAA have brought.
If you don?t have a legitimate reason for accessing private data, access
should be denied. Even the number of IT
staff included in the Domain Administrators group must be considered. Besides being a general sound security
practice, auditors will flag this as a potential HIPAA violation. These are difficult pills for some IT pros to
swallow as they are accustomed to having free reign of their network. But slipping on this slope can mean you?re
searching for a new job tomorrow, so proceed with caution.

I would be interested to hear how other regulatory laws such
as Sarbanes-Oxley
and the Gramm-Leach-Bliley
Act
have affected IT in your organization.
Sound off and let me know!

This discussion is closed to new replies.