$TXT Created by ELLZEY,LINDA at DEVFEX.FO-ALBANY.MED.VA.GOV (KIDS) on Thursday, 11/16/06 at 11:08 ============================================================================= Run Date: DEC 19, 2006 Designation: PSO*7*250 Package : PSO - OUTPATIENT PHARMACY Priority: Mandatory Version : 7 SEQ #224 Status: Released Compliance Date: JAN 19, 2007 ============================================================================= Subject: Q1 - TALLY PRESCRIPTIONS WITH MISSING EXPIRATION DATES Category: - Routine Description: ============ This patch will produce a tally report in the form of a MailMan message for all prescriptions with missing expiration dates and prescriptions that are past their expiration dates but have an active status. It also contains corrections for two remedy tickets. 1. The tally report will be sent to the person who installs the patch at the site and to management on FORUM via the MailMan utility. It will be used to determine if a national patch needs to be created for correcting this issue. During installation of this patch, the user may select to run the tally immediately or queue it to run at a later date and time. Should it be necessary to stop the job for emergency or to know the status of the job, a status and stop function is provided. To stop the job, log into programmer's mode and type the D STOP^PSOTEXP1 at the command prompt. The following is an example: >D STOP^PSOTEXP1 TALLY MISSING EXPIRATION DATES Job - set to STOP Soon Check Status to be sure it has stopped and is not running... (D STATUS^PSOTEXP1) To check the status of the TALLY MISSING EXPIRATION DATES job, log into programmer's mode and type D STATUS^PSOTEXP1 at the command prompt. The following is an example: >D STATUS^PSOTEXP1 Currently processing: Date being processed > Dec 09, 2005 RX # > 3011493 To restart the job, the patch must be re-installed. The following is an example of the MailMan message that will be sent to management and the user who installs the patch: Subj: Outpatient Pharmacy PSO*7*250 TALLY MISSING EXPIRATION DATES [#144218] 10/25/06@09:55 12 lines From: PSO*7*250 TALLY MISSING EXPIRATION DATES In 'IN' basket. Page 1 *New* ------------------------------------------------------------------------ The TALLY MISSING EXPIRATION DATES job for the Outpatient Pharmacy patch (PSO*7*250) started OCT 25, 2006@09:55:22 and completed OCT 25, 2006@09:55:27. Excel comma delimited data below, five headings, one data line Note that an institution of 999999999 denotes one was not found during run. ,,,,,,Total Active Rx's ,Before v7 Install,Before v7 Install,After v7 Install,After v7 Install,,With ,Tot Active Rx's,Tot Inactive,Tot Active,Tot Inactive,Total Rx's,Expiration ,Missing Expired,Rx's Missing,Rx's Missing,Rx's Missing,Missing,Date of T-1 Institution,Date,Expired Date,Expired Date,Expired Date,Expired Date,Day 500,1,4,1,2,8,340 Enter message action (in IN basket): Ignore// 2. Remedy tickets 166505 and 166485 related to patch PSO*7*239: A. It was reported that for two sites the CIDC Activity Log Clean-up process did not complete, no error was recorded, and no MailMan message was received stating the job completed. It was found that the problem resulted from a prescription being locked by another process for an extended amount of time which resulted in the CIDC Clean-up process stopping. For consistency in the routines at all sites, the modification to correct this issue is being included in this patch. If your site received the MailMan message stating that the CIDC ACTIVITY LOGS CORRECTION job completed, no action should be taken. Otherwise after installation of this patch, run the CIDC Clean-up routine from programmer's mode to complete the process: >D ^PSOCIDC7 The clean-up routine will store any prescription that cannot be locked for correction. The completion MailMan message was modified to notate whether such problems occurred. If there is not a notation stating prescriptions were locked, no further action is needed. Otherwise from the programmer's prompt type the following to print a report: >D LOCKED^PSOCIDC9 The prescriptions on the locked prescription report may be individually corrected manually by typing the following at the programmer's prompt: >D FIXONE^PSOCIDC9 The prescription number will be prompted, and a message stating that the activity logs were corrected will be displayed. If the manual clean-up process still cannot lock the prescription in order to correct the activity logs, a message stating such will be displayed. Otherwise, a message will be displayed that no corrections are needed. Each prescription completed is notated as such and reprinting the LOCKED^PSOCIDC9 report will show "completed" after each one. B. It was reported that an error occurred when the RPT^PSOCIDC9 report was queued to a printer. This patch corrects the queuing of the report to a printer. To generate the report of all prescriptions affected by the clean-up process, enter the following at the programmer's prompt: >D RPT^PSOCIDC9 Associated New Service Request (NSR): ===================================== N/A Associated Remedy Ticket(s): ============================ 166505, 166485, 168122 Associated E3Rs: ================ N/A Test Sites: =========== LOUISVILLE, KY DURHAM, NC MONTANA HCS NEW YORK HARBOR HCS OKLAHOMA CITY, OK Installation Instructions: ========================== ** Warning, please do not queue this patch to be installed. It has ** an install question that needs to be answered. Installation of this patch may be completed while Pharmacy users are on the system. Installation will take no longer than 5 minutes, but the tally job "TALLY MISSING EXPIRATION DATES" may run for several hours. Suggested time to install: During non-peak. 1. Use the INSTALL/CHECK MESSAGE option on the PackMan menu. 2. From the Kernel Installation & Distribution System (KIDS) menu, select the Installation menu. 3. From this menu, you may select to use the following options (when prompted for INSTALL NAME, enter PSO*7.0*250): a. Backup a Transport Global - this option will create a backup message of any routines exported with the patch. It will NOT backup any other changes such as DDs or templates. b. Compare Transport Global to Current System - this option will allow you to view all changes that will be made when the patch is installed. It compares all components of the patch (routines, DDs, templates, etc.). c. Verify Checksums in Transport Global - this option will ensure the integrity of the routines that are in the transport global. 4. Use the Install Package(s) option and select the package PSO*7.0*250. 5. When prompted "Enter when to Queue the Job to run in date@time format: NOW//", press enter to start the process now or enter a future time to start this job in date@time format. If this prompt is allowed to time out, the job will not run and a prompt will be displayed asking whether to remove the transport global. 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. The second line of each of these routine(s) will look like: ;;7.0;OUTPATIENT PHARMACY;**[patch list]**;DEC 1997 Integrity Checking tools: ======================== CHECK^XTSUMBLD results Routine Before Patch After Patch Patch List -------- ------------ ----------- ---------- PSOCIDC8 11130561 13641768 239,250 PSOCIDC9 6898634 16701792 239,250 PSOTEXP1 N/A 15978212 250 Total number of routines - 3 Routine Information: ==================== The checksums below are new checksums, and can be checked with CHECK1^XTSUMBLD. Routine Name: PSOCIDC8 Before: B28837769 After: B37708540 **239,250** Routine Name: PSOCIDC9 Before: B14993294 After: B60349233 **239,250** Routine Name: PSOTEXP1 Before: n/a After: B64487464 **250** ============================================================================= User Information: Entered By : ELLZEY,LINDA Date Entered : JUN 13, 2006 Completed By: LEONARD,KEN Date Completed: DEC 19, 2006 Released By : CONSENTINO,ALBERT Date Released : DEC 19, 2006 ============================================================================= Packman Mail Message: ===================== $END TXT