$TXT Created by ANDERSON,CURTIS at DEVCUR.ISC-SLC.VA.GOV (KIDS) on WEDNESDAY, 11/21/01 at 13:36 ============================================================================= Run Date: JAN 11, 2002 Designation: OR*3*112 Package : OR - ORDER ENTRY/RESULTS REPORTING Priority: Mandatory Version : 3 SEQ #119 Status: Released ============================================================================= Associated patches: (v)OR*3*88 <<= must be installed BEFORE `OR*3*112' (v)OR*3*102 <<= must be installed BEFORE `OR*3*112' Subject: UNVERIFIED ORDER NOTIFICATIONS DELETION FIX Category: - Enhancement (Mandatory) - Routine Description: ============ Note: This patch can only be installed at sites running CPRS. Documentation: ============== Other aspects of CPRS Notifications/Order Checks are available on our web site: http://vista.med.va.gov/cprs/ An updated CPRS Technical Manual describing the new functionality introduced by this patch is also available. The preferred method is to FTP the files from download.vista.med.va.gov. This transmits the files from the first available FTP server. Sites may also elect to retrieve software directly from a specific server as follows: Albany ftp.fo-albany.med.va.gov Hines ftp.fo-hines.med.va.gov Salt Lake City ftp.fo-slc.med.va.gov This document is in the form of an Adobe Acrobat file and can be found under the name CPRSLMTM.PDF. Routines: ======== ORB3FUP2 ORY112 Issues: ======= 1. [Requested at Camp CPRS 2001] Fixes a problem with the Unverified Order and Unverified Medication Order notifications/alerts. When the Unverified Order and Unverified Medication Order notifications/alerts are triggered for patients with unverified orders (medication and otherwise) from previous admissions, the alert follow-up action considers all unverified orders. This is a problem because if any unverified order exists, the alert is not deleted and nursing and clerical personnel are reluctant to verify orders from previous admissions. This patch changes that by only considering the unverified orders in the current admission when determining if the alert should be deleted or not. If a current admission date/time cannot be found, only the unverified orders from the past 30 days are considered. Thus, with this patch the alert will be deleted if unverified orders exist from previous admissions but not the current admission (or past 30 days.) 2. [Support GMRC*3*17] Adds error-prevention code to the Consult/Request Interpretation notification/alert follow-up action in CPRS List Manager. Consult/Request Interpretation is a new notification/alert introduced with GMRC*3*17. Patch GMRC*3*17 does not need to be installed before this patch OR*3*112. 3. [Support RA*5.0*28] Adds the new notification/alert IMAGING REQUEST CHANGED [#67]. This new notification/alert is triggered from within the Imaging package when a request is changed. The alert follow-up action displays the request before and after the change. Alert recipients are determined by the Imaging package and will be the requesting provider(s) before and after the request is/was changed. Patch RA*5.0*28 does NOT need to be installed before patch OR*3*112. However, the IMAGING REQUEST CHANGED notification/alert will not be functional until AFTER patch RA*5.0*28 is installed. The exported OE/RR package-level parameter values for this new notification are: Parameter Imaging Request Changed --------- -------------------------- ORB ARCHIVE PERIOD 30 DAYS ORB DELETE MECHANISM INDIVIDUAL RECIPIENT ORB FORWARD SUPERVISOR 0 DAYS ORB FORWARD SURROGATE 0 DAYS ORB PROCESSING FLAG DISABLED* ORB URGENCY MODERATE * The notification must be set to Enabled or Mandatory before the notification/alert will be triggered. To do this use the Notification Mgmt option: Select Notification Mgmt Menu Option: 1 Enable/Disable Notifications Set PROCESSING FLAG Parameters for Notifications Processing Flag may be set for the following: 1 User USR [choose from NEW PERSON] 2 Team (OE/RR) OTL [choose from OE/RR LIST] 3 Service SRV [choose from SERVICE/SECTION] 4 Location LOC [choose from HOSPITAL LOCATION] 5 Division DIV [choose from INSTITUTION] 6 System SYS [DEVCUR.ISC-SLC.VA.GOV] Enter selection: 6 System DEVCUR.ISC-SLC.VA.GOV --------- Setting Processing Flag for System: DEVCUR.ISC-SLC.VA.GOV --------- Select Notification: imaging request chaNGED Are you adding IMAGING REQUEST CHANGED as a new Notification? Yes// YES Notification: IMAGING REQUEST CHANGED// IMAGING REQUEST CHANGED Value: e Enabled <=== you could also set the value to (M)andatory ROUTINE SUMMARY: ================ The following is a list of the routines included in this patch. The second line of each of these routines will look like: ;;3.0;ORDER ENTRY/RESULTS REPORTING;**[patch list]**;Dec 17, 1997 CHECK^XTSUMBLD results Routine name Before Patch After Patch Patch List ============ ============ =========== ========== ORB3FUP2 10412456 12004760 31,64,88,112 ORY112 N/A 1368434 112 INSTALLATION INSTRUCTIONS: ========================= This patch should be loaded during non-peak hours to minimize disruption to users. Users may be on the system during installation. On most systems installation will take less than 2 minutes. Systems with heavy user loads or performance problems may take longer. 1. Use the INSTALL/CHECK MESSAGE option on the PackMan menu. 2. Review your mapped set. If any of the routines listed in the ROUTINE SUMMARY section are mapped, they should be removed from the mapped set at this time. 3. From the Kernel Installation and Distribution System Menu, select the Installation menu. 4. From this menu, you may elect to use the following options (when prompted for INSTALL NAME, enter OR*3.0*112): a. Backup a Transport Global b. Compare Transport Global to Current System c. Verify Checksums in Transport Global 5. Use the Install Package(s) options and select the package OR*3.0*112. 6. When prompted 'Want KIDS to INHIBIT LOGONS during install? YES//', respond "NO". 7. When prompted 'Want to DISABLE Scheduled Options, Menu Options and Protocols? YES//', respond "NO". 8. If routines were unmapped as part of step 2, they should be returned to the mapped set once the installation has run to completion. 9. Routine ORY112 is used in the patch installation process. When patch installation is completed this routine is automatically deleted. Routine Information: ==================== Routine Name: - ORB3FUP2 Routine Checksum: Routine Name: - ORY112 Routine Checksum: ============================================================================= User Information: Entered By : ANDERSON,CURTIS L Date Entered : JUN 28, 2001 Completed By: EBERT,AL Date Completed: JAN 11, 2002 Released By : TASTROM,JOSEPH E Date Released : JAN 11, 2002 ============================================================================= Packman Mail Message: ===================== $END TXT