$TXT Created by MALMROSE,CARY at ROX-DCM.FO-SLC.MED.VA.GOV (KIDS) on Tuesday, 11/28/06 at 10:07 ============================================================================= Run Date: APR 10, 2007 Designation: OR*3*262 Package : OR - ORDER ENTRY/RESULTS REPORTING Priority: Mandatory Version : 3 SEQ #242 Status: Released Compliance Date: MAY 11, 2007 ============================================================================= Associated patches: (v)OR*3*160 <<= must be installed BEFORE `OR*3*262' (v)OR*3*215 <<= must be installed BEFORE `OR*3*262' Subject: HEALTH SUMMARY CASE seNsITive REPORT PROBLEM Category: - Routine Description: ============ Note: This patch can only be installed at sites running CPRS. This patch addresses an identified Patient Safety Issue (PSI) PSI-06-081 PATIENT SAFETY ISSUE: CPRS, VistAWeb, Health Summary, Remote Data Views CPRS (and the soon-to-be-released version 5 of VistAWeb) can query remote sites for locally defined Health Summary "types". If site "A" has a local Health Summary "type" called "MEDICINE INFO", and the CPRS user does a Remote Data Views lookup for this Health Summary Report, remote sites that have local Health Summary "types" of the same "Name" will return the info back to the CPRS user. However, the comparison of the local "Type" "Name" and the remote "Type" "Name" is case sensitive in part. The "Type" "Name" at site "A" is converted to uppercase and compared to "Type" "Names" at remote sites. But the remote site "Type" "Names" are not converted to uppercase during this comparison. So, if site A requests from site B, the following will occur: Site A: "MEDICINE INFO", site B: "MEDICINE INFO" -> site B returns data Site A: "MEDICINE INFO", site B: "Medicine Info" -> site B returns "MEDICINE INFO NOT DEFINED" Site A: "Medicine Info", site B: "MEDICINE INFO" -> site B returns data Site A: "Medicine Info", site B: "Medicine Info" -> site B returns "MEDICINE INFO NOT DEFINED" ASSOCIATED NSR(S): ================= N/A ASSOCIATED REMEDY: ================= HD149298 -Case sensitivity of Health summaries PARTICIPATING TEST SITES: ======================== Northern California HCS Palo Alto HCS Salisbury,NC REMEDY OVERVIEW: =============== Problem: ------- HD149298 CPRS (and the soon-to-be-released version 5 of VistAWeb) can query remote sites for locally defined Health Summary "types". If site "A" has a local Health Summary "type" called "MEDICINE INFO", and the CPRS user does a Remote Data Views lookup for this Health Summary Report, remote sites that have local Health Summary "types" of the same "Name" will return the info back to the CPRS user. However, the comparison of the local "Type" "Name" and the remote "Type" "Name" is case sensitive in part. The "Type" "Name" at site "A" is converted to uppercase and compared to "Type" "Names" at remote sites. But the remote site "Type" "Names" are not converted to uppercase during this comparison. Resolution: ----------- This patch fixes this problem by removing the case sensitive restrictions in the code, where the NAME and TITLE fields in the HEALTH SUMMARY TYPE file (#142) are used. 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*262): 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*262. 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 following is a list of the routine(s) included in this patch. Checksums were calculated using the utility: CHECK^XTSUMBLD. 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 ============ ============ =========== ========== ORWRP 17368644 17187322 1,10,85,109,132,160,194,227,215,262 ORWRP1 18436645 19649756 10,85,109,160,262 Routine Information: ==================== The checksums below are new checksums, and can be checked with CHECK1^XTSUMBLD. Routine Name: ORWRP Before: B71795450 After: B73080393 **1,10,85,109,132,160,194,227, 215,262** Routine Name: ORWRP1 Before: B74016636 After: B78184924 **10,85,109,160,262** ============================================================================= User Information: Entered By : MALMROSE,CARY Date Entered : JUL 05, 2006 Completed By: ILUSTRISIMO,LUCY Date Completed: APR 05, 2007 Released By : LECLAIR,RAY Date Released : APR 10, 2007 ============================================================================= Packman Mail Message: ===================== $END TXT