Education system offers IS naming exampleby Jeff BurdickEmerald Communications and Training Committee Joe double-clicks an icon on his monitor that looks like a palm tree. Up comes a log-in screen for the Oacis CD, or Clinical Display, also known as the Clinical Information System, Clinical Repository, or Clinical Data Base. It may even be called the Electronic Medical Record (EMR), known also as Emerald here at MUSC. Information systems in use at MUSC are known to different users by different names. How does this happen? It may be a matter of tradition, since the name given to an application when it’s first installed tends to stick with people. In some cases it’s the result of a concerted name-branding campaign that determines how people refer to a particular system. Though not unique to Information System (IS), the situation is often compounded by the rapidly changing environment associated with IS technology. When the system many people use for patient registration, medical record functions and patient billing in the hospital was first installed, it was supplied by a company called Professional Healthcare Systems, or PHS for short. T-shirts were issued, articles were published, training and documentation were widely distributed, and everyone referred to this system as the PHS System. Through the years the original company was purchased by Keane Inc., and many users then began (and continue) to call this system the Keane System. Although there are now almost a dozen separate modules comprising this system, the registration and patient accounting module (the largest or “flagship” module) retained the Patcom name. In a marketing effort undertaken during 1999 this name was changed to Patcom Plus to reinforce the significant improvements needed to accommodate the year 2000 (Y2K) and a new platform/architecture. This is similar to other consumer advertising and again is not unique to information systems. But how many people are familiar with other names for the modules now supplied by the Keane vendor, like MPI (Master Patient Index), MediData (coding and abstracting), Chart Management (tracking and completion), ARMS (Account Receivables Management System), MNE (medical necessity) and so on? Generally it’s only those users who are intimately familiar with a particular Keane-supplied module (or sometimes technical support staff) that make the distinction between the Patcom Plus module and one of the other application modules. A similar paradigm may be found in the automobile industry. Though a company like Chevrolet, Ford or Toyota manufactures and supplies vehicles, they are probably best known to drivers by model names like Camaro, Mustang or Camry. Now that we know why there are so many names for the information systems we use, what can we do to reduce confusion among the uninitiated? Again, it may be helpful to consider equivalent solutions in other industries. Having adopted new drug names at an increasingly rapid pace, the pharmaceutical industry is now struggling with renewed standardization efforts brought about by patient safety issues. Unfortunately, IS standardization has traditionally been a slow process that lags behind changing technology and terminology. Consequently, it’s unlikely that a solution will emerge from the adoption of industrywide generic names for IS applications. Another possible approach is to use the system’s complete name when referring to a particular system at MUSC. This “long name” would identify the current vendor name first, the current module or product name next, then finally the application itself. Thus, to clearly communicate the reference, the preferred name would be the Keane MediData module for coding and abstracting, or the LanVision OCC module for on-line chart completion. Not surprisingly, few users have the knowledge or inclination to be so specific when referring to the icon they access for the needed system. The best solution to name game confusion may be the one that emerged with the purchase and imminent implementation of the new Web-based employee education system. The system was selected to provide interactive employee training as well as a tracking mechanism for the mandatory education required by various regulatory agencies. While the name of the system supplied to MUSC is Webinservice, and the vendor is called MCStrategies, it was decided that a single name with a corresponding graphic should be used throughout MUSC to refer to this system. A contest to name the system produced more than 100 entries, and a prize was awarded to the employee submitting the winning entry. The designated name, CATTS (for Computerized Annual Training and Tracking System), will be used to identify this system in all commun-ications as it is piloted and sub-sequently rolled out. Regardless of any name changes that may occur with the contracted vendor or the commercial product, a single name should reduce confusion for many years ahead at MUSC. Look for future Catalyst articles to see how the implementation of this system is progressing. Meanwhile, there are no easy answers in the name game. The chart on page 6 was compiled to assist with using “long names” for some of the major systems currently utilized by MUHA employees, but it’s important to note that there are more than 50 IS applications in the Medical Center alone. Given the name changes that occur regularly in all these systems, the challenge to keep up is ongoing. If you have an idea about how to rise to this challenge, send an e-mail
to emerald@musc.edu.
Information System (IS)—long namesMedical Micro Systems, Inc.Module (or Product Names): OverSite What people call it: OverSite Application/Functional Description: Ambulatory Scheduling--Schedules patients with multiple resources (physicians, rooms, equipment); automatically pre-registers on the Keane System; and generates patient reminders and Chart pull lists. Vendor: Keane, Inc.
Vendor: Cerner
Vendor: IDX
Vendor: Cerner
Vendor: McKesson, HBOC
Vendor: MediServe
Vendor: Agfa
Vendor: PMSI
Vendor: Dinmar
Vendor: LanVision
Vendor: McKesson, HBOC
Vendor: Amcom
Catalyst Online is published weekly, updated as
needed and improved from time to time by the MUSC Office of Public Relations
for the faculty, employees and students of the Medical University of South
Carolina. Catalyst Online editor, Kim Draughn, can be reached at 792-4107
or by email, catalyst@musc.edu. Editorial copy can be submitted to Catalyst
Online and to The Catalyst in print by fax, 792-6723, or by email to petersnd@musc.edu
or catalyst@musc.edu. To place an ad in The Catalyst hardcopy, call Community
Press at 849-1778.
|
|