RXPert ContentsRXPert Contents

2Q94 Pages 5 & 6

title.gif (2867 bytes)

June 1994 10th Edition
Written by Bruce Clutcher and Faith Thompson
Edited by Bruce Clutcher Published by Faith Thompson


(By Bruce Clutcher)

  1. Last issue I discussed how only the IV's primary additive gets stored across all med/solution segments. However, therapeutic duplicate checking is performed using all ingredients, since CHPPRXI1 goes back to the service master for each ingredient's therapeutic code. My Duplicate/Interaction CHPPRXI1/2 Corporate Contact, Joan Kucewicz (there is no duplicate like Joan, and I interact with her when I can to understand these programs!) adds the following insight into these functions. These 'rules' may aid when assisting clients who report a given therapeutic duplicate not showing:
  1. Last issue we also covered some peculiarities regarding alphabrowsing on brand name. Here is one more strange but true encounter with this function. If you alphabrowse for a given brand name on a service with multiple labels, and the same brand name is found on at least two labelers, and one labeler is the primary default labeler, and you pick the one that is not the primary, you will end up with the primary labeler in your order anyway.

    The explanation is, alphabrowse is only a mechanism for qualifying on the drug name, department, active indicator and type (generic or brand). Once the display of qualifying drug services is built and you select the drug, only the drug's service code is passed to the AUDA. If you are in enter order, CHPPO100 runs, takes the service code and goes through the normal process of finding and unloading the common and default labeler common segments. CHPPO100 doesn't know (or care) what specific brand/labeler you selected from alpha brwose
  1. Tom Campbell discovered a model problem when renewing a TPN/Alt LVP order. If the user views the ingredients in renew, then goes on to complete the order, an IV label prints for the order's last occurrence. The label does not contain any ingredients. Until this is resolved, Tom recommends taking your enter order (ORD) IV label (probably the same one you use in renew) and rename it. Delete out any printing conditions and use this new label in renew (REN).



The following Rx-LIVEs took place since the last issue:

** IDs - please leave Faith or Bruce a Voicemail with your install/LIVE updates - otherwise, we may not be able to give you your due credit in the RxPERT!


Two Users meetings were held recently:

o Tom Campbell hosted the first local Berwyn Office Pharmacy User Meeting May 24th. Approximately 50 were in attendance, representing nine INVISION Pharmacy client sites.

Jack Cooper (SMS Regional Manager) spoke on The Integrated Health Network. Ken Stewart (SMS Sr. Products Requirements Administrator) presented INVISION Pharmacy And The Future, outlining the new Client Server Pharmacy (see article below). Doug Kent (SMS Sr. Product Analyst) followed with an INVISION Pharmacy Development Update, discussing soon-to-be-released enhancements.

Francine Noronha, R.Ph. (Pharmacy Functional Analyst - Bryn Mawr Hospital) discussed their hospital's Med IV Charting install. Steve Harrison (Pharmacy Tech, Hamilton Medical Center) showed the Profile Display/ Pharmacy Function Menu build from their hospital. Earl Sloskey, R.Ph. (Assis. Dir. of Pharmacy, Taylor Hospital) showed the sliding scale insulin feature using an OAS adaptation. The meeting concluded with a round table discussion, with users sharing various building techniques.

o The INVISION Pharmacy System User Group Meeting was held at the Reno Hilton June 5th, in conjunction with the ASHP Annual Meeting in Reno, NV.

Doug Kent and Ken Stewart shared the same topics as mentioned above with the Berwyn meeting.

Various users presented install/building OAS adaptations. Bonnie Levin, Pharm.D. (Director of Pharmacy, Greater Laurel Beltsville Hospital), Chairperson, INVISION Pharmacy User Group, shared the results of a recent survey sent to all INVISION Pharmacy Users.


(by Bruce Clutcher)

As you have probably heard, SMS will be offering INVISION clients a new Client Server Pharmacy product on a RISC/UNIX (i.e. RISC is the PC/architecture, and UNIX is the operating system) platform, based on the Unity Pharmacy feature and function. This product will be offered to INVISION clients as the departmental solution for their pharmacy needs.

The new Client Server Pharmacy will be integrated to/from INVISION through a series of existing (ADT and financial) and soon-to-be-developed (Med/IV Orders) interfaces. The goal is to continue to achieve and support the same integration to INVISION that exists in today's scenario. INVISION's Med/IV Orders will continue to play some part in the INVISION product line.

Ken Stewart and other Corporate planners are busy working out the details for this bold new step in SMS's pharmacy offering. Rather than discussing the details of this project, and what it means to all of us, we will refer you to a Question/Answer document Ken will release by early June, detailing this new pharmacy departmental solution. So stay tuned!


Improve installation quality and efficiency, increase customer ownership of SMS systems, and sustain top project team performance! Sound too good to be true? Well, this is exactly what the SMS Strategic Services Group (SSG) has been doing with the Installation Project Team Building Program (IPTB). Over the past three years SSG's Management and Team Development practice (MTD) has delivered nearly 50 IPTB programs with tremendous response from both customers and SMS Field personnel. Participant evaluations on a 5-point excellence scale average 4.6 for 1994! Now, Pharmacy can take advantage of these benefits.

Grant Beauchamp, MTD Consulting Manager, describes the objectives and structure of the program like this. The SMS approach to installing systems addresses the traditional technical and operational concerns of our customers. However, we also realize that the ultimate success of any project depends more on PEOPLE than product or technology. Excellent teamwork, effective change management, and strong buy-in are key to a successful implementation. IPTB is a standard component of the INVISION, UNITY, and SIGNATURE installation methodologies. It has also been used successfully in LAB and TSD installations. The program achieves the following objectives for the Customer-SMS installation project team:

  1. Establishes a cooperative, team approach between Customer and SMS personnel
  2. Builds reliable ground rules for how the project organization structure will operate
  3. Clarifies the roles and responsibilities of individual project team members
  4. Establishes clear expectations and common goals between Customers and SMS
  5. Identifies and addresses roadblocks to the success of the project

These objectives are accomplished in an exciting day-and-half program (1-day for hospitals under 100 beds) that promotes team self-sufficiency, and real work on the installation's critical success factors. From the start, team leaders and members are encouraged to be responsible and accountable for building and maintaining a high performing team.

IPTB program details, fees, customer list, program evaluation results, and other information are immediately available upon request. To receive information or talk with Grant about tailoring a program for your project call him at ext. 2019 (mail code E8A).

Pages 1-2 Pages 3-4 Pages 5-6

WB01337_.gif (904 bytes)RXPert Contents