$TXT Created by HARTIN,JIM at DAYT17.FO-BAYPINES.MED.VA.GOV (KIDS) on Monday, 10/23/06 at 10:33 ============================================================================= Run Date: OCT 25, 2006 Designation: OR*3*250 Package : OR - ORDER ENTRY/RESULTS REPORTING Priority: Mandatory Version : 3 SEQ #234 Status: Released Compliance Date: NOV 25, 2006 ============================================================================= Associated patches: (v)OR*3*215 <<= must be installed BEFORE `OR*3*250' (v)OR*3*220 <<= must be installed BEFORE `OR*3*250' Subject: CORRECT LAB QUICK ORDER DISPLAY VITALS_ORQQVI EXPERT SYSTEM Category: - Routine Description: ============ This patch addresses the following issues: 1. The LAB Quick Orders not displaying (CH) LAB Quick Orders. 2. Expert System VITALS^ORQQVI not finding all vital measurements. 3. Display Patient Alerts and Alert Recipients, display truncating Order number. ASSOCIATED REMEDY: ================= 1 HD0000000130830 Can create a lab personal quick order - but then cannot accesss it. 2 HD0000000133644 VITALS^ORQQVI TAG NOT WORKING 3 HD0000000070022 PUG-0203-51090 Order number truncated in notifications PARTICIPATING TEST SITES: ======================== Alexandria,LA Hines,IL Puget Sound HCS REMEDY OVERVIEW: =============== 1. HD0000000130830 Can create a lab personal quick order - but then cannot access it. Problem: ======== Personal Quick Orders created from any CHEMISTY LAB Quick Order are not displayed. Solution: ========= The display of LAB Quick Orders RPC was hard coded to only look for the display type of LAB. The RPC routine was modified to include all the display types under the parent display group LAB, this includes the following: LABORATORY CHEMISTRY HEMATOLOGY MICROBIOLOGY BLOOD BANK ANATOMIC PATHOLOGY ELECTRON MICROSCOPY SURGICAL PATHOLOGY AUTOPSY CYTOLOGY 2. HD0000000133644 VITALS^ORQQVI TAG NOT WORKING Problem: ======== An on site developer using a local call noticed that the routine returns the patient vital measurements but was not returning a complete list. Solution: ========= The routine that searches a temp global returned from GMRVUTO had a typo which left out a node subscript, causing some vitals to be missed. The typo was corrected, allowing a complete search and list of vitals. 3. HD0000000070022 PUG-0203-51090 Order number truncated in notifications Problem: ======== When using [ORB3 ALERT RECIPIENTS] "Display Patient Alerts and Alert Recipients", the Order # of the order alerted to is displayed. But in the case of some alerts the Order # is being truncated. Making it useless, if being used to trouble shoot problems. Solution: ========= Due to the limit of characters on a display line in VISTA and length of the Alert title as well as the increasing length of the Order # the number was truncated. The title of the alert "Order(s) needing clarification: Flagged 03/13 18:30" was abbreviated in this display only, to: "Order needs clarifying: Flagged 03/13 18:30", to accommodate the limited space. The title is followed by the Order number, which in some sites is going up to 10 characters. The new display line will look like the following: 1 Order needs clarifying: Flagged 03/13 18:30 [12596972] 3/13/06@18:30 INSTALLATION INSTRUCTIONS: ========================== This patch should be loaded during non-peak hours to minimize disruption to users. Installation will take less than 1 minute. Users may remain on the system. 1. Use the INSTALL/CHECK MESSAGE option on the PackMan menu. 2. From the Kernel Installation and Distribution System Menu, select the Installation menu. 3. From this menu, you may elect to use the following options (when prompted for INSTALL NAME, enter OR*3.0*250): a. Backup a Transport Global b. Compare Transport Global to Current System c. Verify Checksums in Transport Global 4.. Use the Install Package(s) option and select the package OR*3.0*250. 5. When prompted 'Want KIDS to INHIBIT LOGONs during the install? YES//' respond NO. 6. When prompted 'Want to DISABLE Scheduled Options, Menu Options, and Protocols? YES//', respond NO. ROUTINE SUMMARY: =============== The second line of each of these routine(s) 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 ============ ============ =========== ========== ORB3U1 13042731 13753718 9,74,88,91,105,179,220,250 ORQQVI 8493184 8533995 10,198,215,250 ORWDLR32 9961998 11284141 10,85,141,215,250 Routine Information: ==================== The checksums below are new checksums, and can be checked with CHECK1^XTSUMBLD. Routine Name: ORB3U1 Before: B62203040 After: B66271462 **9,74,88,91,105,179,220,250** Routine Name: ORQQVI Before: B39228695 After: B39275783 **10,198,215,250** Routine Name: ORWDLR32 Before: B52893091 After: B56521033 **10,85,141,215,250** ============================================================================= User Information: Entered By : HARTIN,JAMES Date Entered : MAR 17, 2006 Completed By: ILUSTRISIMO,LUCY Date Completed: OCT 24, 2006 Released By : HINES,RICK Date Released : OCT 25, 2006 ============================================================================= Packman Mail Message: ===================== $END TXT