RXPert ContentsRXPert Contents

2Q94 Pages 3 & 4

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)

First DataBank just released three new allergy codes:

74 - H2 Antagonists
75 - Potassium Sparing Diuretics
76 - Nicotine

Note: these new codes are already being delivered on the latest NDDF tapes. Model PRCON has not been updated. Therefore your clients may encounter an out-of-sync situation when applying an NDDF update and they try to key in one of these codes in through Service Master Maintenance (the allergy code field is edited against PRCON). To resolve this until a new PRCON can be delivered, just add these new codes to the hospital level of PRCON.


(by Faith Thompson)

Have you ever wanted to print out the contents of a profile (such as PRMNE) with one member per line - instead of one member per page - so that you conserve paper, and have a list that's easier to look at?

Profiles can be printed in two ways:

1. Build Profile - Print Definition --> this option uses a document with syntax "#PRxxxF" where "PRxxx" represents the profile name; each profile member prints on a separate page.

2. Print Profile --> this option uses a document with syntax "˘PRxxxF" (again, "PRxxx" represents the profile name); the document can be defined to print one profile member per line, which saves on paper. Some of the OAS profiles are set up on the Model OAS screen to print this way, but you can set this up for other profiles as well.

To implement option #2 above, follow the steps below:

a. Add the new profile to screen image GEPROF02. Define the immediate detectable probe &/or %KEYINNO on screen GEPROF02 and also in TCL GEPROF02. The definition will be:

  • %RECORD = PCxxxzzz
  • where "PCxxxzzz" is the profile key component.

b. Create a document using syntax "˘PRxxxF" (NOTE: the "cent" sign MUST be the first character, and "F" MUST be the last character). Define the document image using dynamic output lines which contain the profile components that you want to see on the printout. The lines should be defined as "%LINE01", "%LINE02", etc.

Give it a try!

DAY END MAR/IVAR AND DS 22.0 (By Bruce Clutcher)

With the advent of Delivery Systems (DS) 22.0 and the new Zero Down Time (ZDT) feature, the Card Input Deck processing is no longer available. As you know, the Card Input Deck is where the GHST command stacks the driver TCL for the MAR/IVAR For Manual Charting and the MAR/IVAR From Automated Charting.

After DS 22.0 is delivered, you will need to use the Report Scheduling system to automatically process these "day end" reports. On GEMFUN01 select !25 REPORT SCHEDULING. On SCMAIN04 enter '3' for SCHEDULES:

o For the MAR/IVAR For Manual Charting, on screen SCSCUP01:

Action = A (add)
Schedule Name = RXSHRLY
Start Date = (date you want to start the MAR)
Sched Type = C (for Cyclic)
Frequency = HR01
Deviations = +0+0+0+0+0+0+0 <ENTER>
Return to SCMAIN04 and enter '1' - REPORTS. On SCRPUP01 enter the following information:

-> To run the MAR:

Action = A (add)
Report Library = RXSHRLY
Report Name = RXSMAR

-> To run the IVAR:

Action = A
Report Library = RXSHRLY
Report Name = RXSIVAR

o For the MAR/IVAR From Automated Charting:

Action = A (add)
Schedule Name = CHTHRLY
Start Date = (date you want to start the MAR)
Sched Type = C (for Cyclic)
Frequency = HR01
Deviations = +0+0+0+0+0+0+0 <ENTER>
Return to SCMAIN04 and enter '1' for REPORTS. On SCRPUP01 enter the following information to run the MAR/IVAR:
Action = A (add)
Report Library = CHTHRLY
Report Name = MAR/IVAR

Clients who have DS 22.0 and contracted for Med/IV Charting should also have two new programs, CHPPOC51 and CHPPOC5A. These programs are used to evaluate the selection options entered in Report Scheduling and are used to pass the data to the proper fields expected by the MAR/IVAR program, CHPPOC02. These programs also stack the process TCL.

Two items to remember:

First, Report Scheduling does not run in the TEST CICS for RCO clients. To test your multipatient MAR/IVARs, you can hard stack the process TCL or use "Test a TCL" in the OAS tools.

Second, Report Scheduling will not "catch up" if the CICS is down for more than the hour your report was scheduled to run. For example, if your MAR is scheduled for 2:15 and the CICS was down from 1:59 - 3:01, the MAR will not kick off.

Please see the DS 22.0 RCO Customer Upgrade Procedures or the Report Generation Manual for more details.



(By Bruce Clutcher):

  1. #1196515 (model) - unable to credit OP-like-in-a-bed IV orders. In the "IV Credit" function, you get E4802: Pt Must Be an IP To Credit. In the "Enter Credit" function you get E4190: Order Is Charged By The Cart, Use Enter IV Credit. For now you should use Enter Unrelated Miscellaneous Pharmacy Credit. Please call Tech Support and reference this model ticket if you are having problems like this at your hospital.

  2. #1343309 (model) - request to optionally combine priority groupings for the Cart Fill List. If you sort by priority first, then be primary name, your list may appear as if the alphabetic sort is not working. Actually, the NROUTINE sections sorts alphabetically first, then the ROUTINE sections. Most clients would want to combine NROUTINE and ROUTINE groups to sort together. To solve this you could change PRRXO to sort alphabetically as the primary sort; however, you will relinquish your ability to sort by priority.
  3. #1327791 (Shady Grove/ model) - a related TPN/Alt LVP model problem was found if you view IV ingredients in renew. The old order's stop D/T is incorrectly stored in the bottle AUDA. Viewing the ingredients in renew brings the old stop D/T into the bottle AUDA. When you return to the patient AUDA the bogus stop D/T is transferred to the patient AUDA by CHPPRX71. What you may end up with is SYSDATE/TIME for the order start D/T and an old stop D/T, resulting in an error. To resolve this for now, $D stop D/T from the bottle AUDA in renew in TCL, RXPTAUDA.
  4. #1226542 (Shady Grove) - Cart problem - order is active prior to original list run, then gets D/C's, then update run and the order does not show on the update telling the tech to remove.
  5. #1328045 (Shady Grove) - Cart problem - order was D/C'd prior to original list run (not on original list), then update gets run and the order shows on the update telling tech to remove.
  6. #1328039 (Shady Grove/ model) - Cart problem - patient transferred into cart does not show on update display when cart update is pulled.

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

WB01337_.gif (904 bytes)RXPert Contents