RXPert Contents

1Q95 Pages 5 & 6

1. #678 (April 1, 1994) Rounds Report - (4.94 SUP/94.2 SUT) - Provides a synopsis of information from the patient’s medical record.

2. #715 PRN IVs - (9.94 SUP/94.4 SUT) - Supports titratable IV orders.

3. #716 (May 1994):

- Clinical Order Enhancements including Comprehensive Order Session (Preconfirmation) (3.94 SUP/94.2SUT), Orders As Written (concatenation of a 60 character description) (3.94 SUP/94.2SUT), Duplicate Check Enhancements (provides the 60 character concatenated description and order stop D/T on the dup/interaction screen) (3.94 SUP/94.2SUT), Rounds Report, Enhanced Convenience Order Sets (can include meds, IVs and Complex Meds in one order set) (2.95 SUP/ 95.2SUT) (see Customer Memo #804 dated January 27, 1995), and Med Browse (combines generic/brand name search and optional qualifiers on route and/or dosage form) (2Q95)

- Enhancements To Print/Display Order Comments will allow the user to exclude specific order comments from Display/Print Patient Orders (3.95 SUP/95.2SUT).

- Display/Print Orders Approaching Stop Date - Allows the Display/Print Patient Orders to qualify on whether the Order Stop D/T falls within a certain range Orders (7.94 SUP/94.3SUT)

4. #F717 (November 18, 1994) Medication and IV Cart Processing Enhancements (9.94 SUP/94.4 SUT) - Provides an option to release the terminal where cart processing is being performed by sending the cart processing programs into background using CHPPGHST.

5. #750 (October 7, 1994) Enhancements To Order Charting And Medication/IV Charting (10.94 SUP/94.4 SUT)

- New target/source Charted/Uncharted Orders Report

- MAR/IVAR From Automated Charting enhancements (clarifying occurrence charting that occurs around midnight and providing an inactive order message line)

- Display Summary MAR/IVAR

- Inventory and delivery of the MAR/IVAR From Automated Charting to all INVISION Pharmacy Clients whether they have purchased Med/IV Charting or not

6. #766 (November 18, 1994) Enhancements To Predefined Common IV (PCI) (12.94 SUP/ SUT 95.1) - Now allows an ingredient to be added or revised in a PCI.

7. #F804 (January 27, 1995) Enhanced Convenience Order Sets (2.95 SUP/95.2 SUT) - Contains the details preannounced in Customer Memo #716.

u Printing the MAR on a remote printstation (e.g., in DP and not on a CICS printer).

The MAR/IVARs, Cart Fill Lists (CFL) and several other CICS-based COBOL reports process more like 'forms' than a report, at least as far as the print subsystem is concerned. Most hospitals prefer to print the MAR on the nurse station printers and the CFL in pharmacy on the CICS printers. To route the MAR to each nurse station CICS printer, put a condition in each target document's document group section and value a different document group based on the nurse station ID. Since MARs' primary sort is nurse station, the nurse station's MARs will queue up and print at the appropriate document group. Only the first document group for that nurse station is evaluated for the routing condition. All other documents for that nurse station's document group will follow the first page.

To route the MAR or other target/source document report to the remote print station, follow these steps:

- Use 'BACKGRND' for the target document's document group.

- Find the appropriate ROI number associated with the remote printer location.

- Go into profile PRFLX and key in your (target) document name (key) (e.g., for the MAR/IVAR From Automated Charting you will only need to add OCMARDF1. Remember, the other target documents, OCMARDF2, OCIVARF1 and OCIVARF2 will follow the routing processing of OCMARDF1). Enter the ROI number you wish the document to route to. Enter a descriptor so you can find the report job by that name when you do a /LIST. A typical entry in PRFLX may look like this:

Ÿ Enter Print Format ID: OCMARDF1

Ÿ And The ROI Number Associated With It: 552

Ÿ Optional DRS Report Name: MARMRCOPY

NOTE: You will not be able to control the nurse station order queue-up in the /LIST; i.e., the nurse station order in the CICS print control queue will not necessarily match the queue order in the /LIST.

u The MAR/IVAR From Automated Charting allows you to process the MAR/IVAR time window based either on either internal calculations based on iterances of the patient’s admit date, or on externally-fed start and stop D/T’s. The internal calculation processing based on admit date is used for the true "Day End" retrospective legal document MAR/IVAR. The externally-fed date processing would be used if you are using the MAR/IVAR as an administration guide or medication rounds list for the physicians.

- To process either the multiple patient (CHPPOC02) or single patient (CHPPOC01 - e.g., if you probe !Reprint Last Night’s MAR/IVAR off screen, OCPMAR01) automatically using the patient’s admit date, set %OCMARWF=1 in your process TCL. The programs will figure out the MAR/IVAR start/stop dates based on the patient’s admit date and the MAR and IVAR duration found in profile, PROC4. The programs use 00:01 and 24:00 as the start/stop times.

- To process either the single or multiple patient MAR/IVAR using externally-fed start/stop date/times, set %OCMARWF=0 in your process TCLs. You can then either DVA your start/stop date/times in the process TCLs in %OCMARBD, %OCMARED, %OCMARBT and %OCMARET respectively (you can use %SYSDATE or %SYSTIME as a indirect DVA reference). Or, if using the Scheduling System, the CHTHRLY MAR/IVAR entry will prompt you for a relative start/stop date and explicit start/stop time. You can use +/- references in #days to %SYSDATE. Remember, the total duration cannot exceed your duration entry in PROC4. The relative #days reference can be +/- 999 days. Please refer to the DS 22.0 document for further explanation of these parm settings.

u The MAR/IVAR From Automated Charting calls the source document, OCMARDFI (held in %OCMAROI), to put out the Order Priority, Charting History, Reason/Effect, No Orders and End of Nurse Station banner messages. The programs (CHPPOC01/2) move the appropriate hard coded literal (e.g., ‘ROUTINE ORDERS’) into %OCMSG1 (the %field found in the model OCMARDFI document). You cannot change the program-supplied literals (obviously) and you cannot eliminate %OCMSG1 and replace the field with your own literal on OCMARDFI. Doing so would put the same custom literal on OCMARDFI every time this document is called in the above-mentioned scenarios.

To create your own banner lines, you can take advantage of the new %OCBANR1-6 fields. The model %OCMAROI/OCMARDFI values are overridden if any of the following %OCBANRn fields are found in the AUDA for the appropriate delimiter situation:

%OCBANR1 - Routine Order Banner
%OCBANR2 - PRN Order Banner
%OCBANR3 - Pre-Op, Stat, Urgent Banner
%OCBANR4 - Inactive Routine Order Banner
%OCBANR5 - Inactive PRN Order Banner
%OCBANR6 - Inactive Pre-Op, Stat, Urgent Banner

The programs will move the appropriate hard coded literal into %OCMSG1 in each of these lines. No model document exists to pair up with the %OCBANRn field. Just DVA your custom literal in the appropriate %OCBANRn field. This gives you a little more flexibility with how to present your banner literal.

u To prevent nursing personnel from charting a routine or PRN dose as administered at a future D/T, place an edit behind the admin D/T fields on screens, OCENCH01 and OCENCH03, limiting the admin D/Ts to a value less than/equal to %SYSDATE and %SYSTIME.

 

Pages 1-2

Pages 3-4

Pages 5-6

RXPert Contents