| DESCRIPTION OF ENHANCEMENTS |
This patch will produce a tally report in the form of a Mailman message
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:
During installation of this patch, the user may select to run the tally
>D RPT^PSOCIDC9
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
for all prescriptions with missing expiration dates and prescriptions that
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:
are past their expiration dates but have an active status. It also
>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:
contains corrections for two remedy tickets.
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
1. The tally report will be sent to the person who installs the patch at
,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
the site and to management on FORUM via the MailMan utility. It will be
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:
used to determine if a national patch needs to be created for correcting
>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
this issue.
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
|
