RXPert ContentsRXPert Contents

1Q94 Pages 3 & 4

title.gif (3664 bytes)

March 1994 9th Edition
Written by Bruce Clutcher and Faith Thompson
Edited by Bruce Clutcher Published by Faith Thompson


(By Bruce Clutcher):

According to Doug Kent in Product planning, EVTS tickets should be opened for Model design issues or future development suggestions. If you or your client feel new code, data file components, reports, new options, etc are needed for a particular function, please open up an EVTS ticket. First of all, Tech Support (or related Corporate group) may be able to assist with a simpler solution. Or, they may be able to inform you that the fix or enhancement you are looking for is coming soon to a SUP/SUT near you. At the very least, a model ticket will be opened and routed to Product Planning/Development's queue for review. Product Planning relies on EVTS for planning future development efforts. Doug suggested calling in a ticket for each account where the problem or suggestion occurs - i.e. even though you know one ticket was open already for Hosp/A, open another ticket for Hosp/B if they have the same beef. Each ticket opened is a 'Vote' to develop that feature. Tech Support will associate your new hospital ticket with an exiting model ticket, if one exists.

I will try to report on pharmacy/charting related ticket I know have been opened. Here are a few to start:

- #1089474 (Carilion Health Systems) - when you key in order duration in #hrs for a PRN order, the systems tends to calculate a stop D/T one occurrence less than the specified #hrs duration. A fix is due on the 93.12 SUP/1.94 SUT to move the order start time to the order stop time for a PRN order when %ORSTPTI=1.

- #1082068 (Carilion) - requested that NROUTINE and ROUTINE orders sort together on the MAR/IVAR.

- #1103782 (Carilion) - requested an option be given to sort charting documents and displays by whatever priority the hospital chooses.

- #1264945 (Carilion) - Regenerate Document function needs to print Cart ID on IV labels.

- #1270115 - request for enhancement in Alpha Browse to allow user to browse for active brand name (see Strange But True article below)

- #1275581 (Carilion) - unable to chart a nonrecurring PRN traditional med order (one occurrence is already build and charting won't allow building another occurrence on top of the existing occurrence).

- #1275750 (Carilion) - suggested enhancements to Print Control: 1) option to sort documents in a document group reverse chron. by create D/T; 2) after PF3 Display Document online, you get kicked out to GEMFUN01; 3) When displaying unprinted documents, there is not option to PF3 Display Document; 4) Need !Prev Page support when displaying documents in a document group.

- #1277792 (Carilion) - bug in CHPPO120 which inappropriately stacks the error screen when discontinuing multiple orders and one of the orders cannot be discontinued.

- #1280994 (Holy Redeemer) - suggested enhancement to have CFL/IVPL Updates show patients transferred within a cart (model ticket #1281410).


(By Bruce Clutcher)

  1. You write a DUE ad hoc to pull off the Therapeutic Code (TC) for each ingredient in an IV. What you get is the same TC for all the ingredients. Explanation: only the primary additive's TC is stored with the order in the Med/Sol Segment. This is done through a conditional stack command off screen, RXIVEO01. Even though there is one Med/Sol Segment for each IV ingredient, the TC field acts more like a Rx-specific Order Segment field, i.e. only one value is stored, but stored across all repeating Med/Sol Segments (there are other fields like this, e.g. Rx Additional Directions - there is only one set of directions for the order, they are redundantly stored in each repeating Med/Sol Segment for each ingredient). Ironically, Therapeutic Duplicate Checking is correctly performed against each IV ingredient, even though only the Primary Additive's TC is stored with each ingredient. CHPPRXI1 goes back to the service master for the TC for each ingredient, instead of looking at the Med/Sol Segment.

  2. Your client calls to say they selected Alphabrowse on !ACTIVE, !BRAND NAME. They received a screen full of services, listed by the Brand Name they keyed in. On the right hand side of the screen in the Active Indicator (A-active, N-never active, etc) and all services on the screen have an 'A' for active. When they pick one of the brand name services they get the error that the brand/labeler picked is not active. This is an old problem that was fixed. The active indicator on screen, RXALBR06, was C2113 (the Common Segment active indicator). The model screen has been changed to use C2439 (the Labeler Segment active indicator) to more accurately reflect whether the brand (i.e. labeler) is active or not. If you still have this problem, chances are you need to copy up the new model screen version to your hospital level.

  3. With the above problem fixed, you can look forward to the next strange but true situation. You Alphabrowse on !ACTIVE, !BRAND and your screen, RXALBR06, lists all labelers for that brand whether they are active, inactive, never active, etc. The explanation is that the !ACTIVE search is qualifying against the Common Segment Active Indicator. So you really aren't qualifying on 'ACTIVE, BRAND' services. Instead, the program finds the brand name Labeler Segments, then looks up to the Common Segment to see if the Common Segment is active. Alphabrowse then lists all labelers under that active Common Segment whether the Labeler is active or not. So basically, what you ask for is not what you get. But at least you may look a little more intelligent as you scratch your head and explain this to your client.


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


Judith Mante joined SMS January 31st as a Consultant in SSG. Judith is from England and Holland and currently resides outside Boston.

Dave Einwag joined the Pittsburgh field office as an Installation Director in January, 1994. Dave previously worked as a pharmacist at Presbyterian Hospital.

Welcome to Judith and Dave!


Darryl Miclat accepted a new position as Product Specialist for INVISION and Unity Pharmacy in January, 1994. He now reports to Roger Hott, and will be working with Denise Dunyak to provide marketing support for AEs and Marketing reps. Darryl was formerly with the Washington D.C. office field installation team. Congratulations Darryl!



(by Faith Thompson)

The Pittsburgh Field Office hosted an INVISION Pharmacy User Group meeting on December 3, 1993.

Representatives from several Allegheny Valley Region Hospitals participated in the day's activities.

The Director of Pharmacy and one of the Systems Analysts from Magee Womens Hospital presented information on how they interfaced INVISION Pharmacy to their PYXIS system. An Analyst from Hamot Medical Center led an interesting discussion and presentation on building Ad Hoc reports for Pharmacy. Denise Dunyak, Product Specialist, also gave a demonstration of what you can do with the OAS in building Pharmacy pathways.

The user group was well attended by the AVR client base, and feedback from those who attended was very positive. If anyone would like more information regarding how to initiate and/or organize an event like this, please contact me at the Pittsburgh office, or via Voicemail (17353).

Pages 1-2 Pages 3-4

WB01337_.gif (904 bytes)RXPert Contents