| DESCRIPTION OF ENHANCEMENTS |
SITE file (#59) parameter 'BARCODES ON ACTION PROFILES' for any
1. Use the INSTALL/CHECK MESSAGE option on the PackMan menu.
2. Review your mapped set. If the routines are mapped, they should
be removed from the mapped set at this time.
3. If the estimated number of prescription fills that will be billed as
part of this clean up is extremely high, you may want to disable
journaling for Integrated Billing and Accounts Receivable globals ^IB
and ^PRCA.
outpatient pharmacy site is set to "NO" or is null, all copay eligible
4. From the Kernel Installation & Distribution System menu, select
the Installation menu.
5. From this menu, you may select to use the following options:
(when prompted for INSTALL NAME, enter PSO*7.0*93)
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.
prescription fills released by CMOP for that outpatient pharmacy site,
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.
6. Use the Install Package(s) option and select the package PSO*7.0*93.
after the installation of patch PSX*2*35, would not have been billed. This
7. When Prompted "Want KIDS to INHIBIT LOGONs during the install?
YES//" respond NO.
8. When Prompted "Want to DISABLE Scheduled Options, Menu Options, and
Protocols? YES//" respond NO.
9. When Prompted "Queue copay clean-up Job to run Date/Time:" respond
with the date/time to queue the cleanup background job or "NOW".
patch identifies all such prescriptions and reprocesses them so that the
10. If Routines were unmapped as part of step 2, they should be returned
to completion.
11. If journaling was disabled for globals ^IB and ^PRCA in step 3, it
should be re-enabled upon completion of the post-installation job.
Example Installation:
=====================
appropriate copay charges are generated.
Checking Install for Package PSO*7.0*93
Install Questions for PSO*7.0*93
Want KIDS to INHIBIT LOGONs during the install? YES// NO
Want to DISABLE Scheduled Options, Menu Options, and Protocols? YES// NO
Install Started for PSO*7.0*93 :
Jan 18, 2002@14:39:49
Build Distribution Date: Jan 18, 2002
Installing Routines:
Jan 18, 2002@14:39:49
Running Post-Install Routine: ^PSOCPIBF
The background job to clean up unbilled, released CMOP prescription fills
must
be queued to run and complete before 02/01/2002 when tracking for the
annual copay cap begins.
If no start date/time is entered when prompted, the background job will be
queued to run NOW.
CMOP patch PSX*2*35 was first installed at your facility on SEP 15,
2001@14:15:4
Resolution: This patch will identify all copay eligible released CMOP
The Outpatient Site (File #59) parameter, 'BARCODES ON ACTION PROFILES'
for one or more outpatient sites is either not defined or set to 'No'.
All copay eligible, released CMOP prescription fills from those outpatient
sites would not have been billed since the installation of PSX*2*35.
NOTE: If the estimated number of CMOP prescriptions involved is high
based
on when the patch was first installed and the number of outpatient sites
involved, you may want to disable journaling for Integrated Billing and
prescription fills that were not billed since the installation of patch
Accounts Receivable globals ^IB and ^PRCA while the clean up job
is running.
When the background job is complete, a MailMan message will be sent to the
installer indicating how many copay eligible CMOP prescription fills were
successfully billed.
Background job must be queued to start by Jan 30, 2002 or before.
At the following prompt, enter a starting date/time after JAN 18,
PSX*2*35 and reprocess them so that appropriate copay charges are
2002@14:39:49
and before Jan 31, 2002 or enter NOW to queue the job immediately.
If this prompting is during patch installation, you will not see what you
type.
PSO*7.0*93
--------------------------------------------------------------------------
------
Queue copay clean-up Job to run Date/Time: (JAN 18, 2002@10:00) ??
Queue copay clean-up Job to run Date/Time: (JAN 18, 2002@15:00)
generated. A MailMan message with a Subject of 'Outpatient Pharmacy
Task will be queued to run JAN 18, 2002@15:00 Is that correct? :
Queuing background job to reprocess unbilled copay CMOP Prescription
fills...
Task Queued !
Updating Routine file...
Copay Clean-up' will be sent to the patch installer and holders of the PSO
Updating KIDS files...
PSO*7.0*93 Installed.
Jan 18, 2002@14:40:20
Install Message sent #41853
--------------------------------------------------------------------------
------
[------------------------------------------------------------]
COPAY key documenting the number of CMOP prescription fills that were
100% | 25 50 75 |
Complete [------------------------------------------------------------]
Install Completed
successfully billed.
This patch will look at all CMOP prescription fills released since patch
PSX*2*35 was installed at your facility. If the prescription is copay
eligible and no charge has been generated, the fill will be reprocessed.
This is an EMERGENCY patch and must be installed within 24 hours.
When determining whether a copy charge was missed for a CMOP prescription
done after the release of patch PSX*2*35, we check the patient's current
copay status. If the patient's status changed from "no copay" to "copay"
since the installation of patch PSX*2*35 at the site, it is possible that
the patient could be billed for prescription fills that were not marked as
copay at the time they were originally released.
Note: This clean up is done in a post-install background job. It MUST be
queued to run and complete before 02/01/2002 as tracking for the annual
copay cap goes into effect then. If the background job has not been queued
to run by January 30, 2002 or if the background job has not completed by
January 31, 2002 @ 2359, the MailMan message generated will indicate that
the background job was stopped before completing the clean up.
When queuing the background job, the date that patch PSX*2*35 was first
installed at your facility will be displayed along with information as to
whether any OUTPATIENT SITE file (#59) has the parameter 'BARCODES ON
ACTION PROFILES' set to null or "NO". If so, and the estimated number of
CMOP prescription fills released during that time frame is high, you may
CMOP patch PSX*2*39 is required before the installation of this patch.
want to consider disabling journaling on the Integrated Billing and
Accounts Receivable globals ^IB and ^PRCA before starting the background
job.
Associated NOISs:
=================
CHS-0102-40707
ERI-0102-21090
MAC-0102-60932
BRX-0102-11833
Test Sites:
===========
Erie, PA
Prescott, AZ
Oklahoma City, OK
Chicago HCS, IL
Martinez, CA
Chicago Hines, IL
Routine Summary:
================
The second line now reads as follows:
<TAB>;;7.0;OUTPATIENT PHARMACY;**[patch list]**;DEC 1997
CHECK^XTSUMBLD results:
Problem: The release of the Consolidated Mail Outpatient Pharmacy
Routine Before Patch After Patch Patch List
=============================================================
PSOCPIBC N/A 13213614 93
PSOCPIBF N/A 18167555 93
Installation Instructions:
==========================
Installation should take no longer than 5 minutes. Please do not queue
the job of installing this patch. There is a post-install background
(CMOP) patch PSX*2*35 introduced a potential problem. If the OUTPATIENT
job that will prompt for a date/time to run the clean up. You MUST
respond with a date and time or NOW to queue the job. You will not
be able to see what you are answering for the prompt, but will be given
an opportunity to see what was entered before the clean up job queues.
This post-install job can be run again at a later time by calling the
entry point ^PSOCPIBF from programmer mode.
An example of the install process is included here under the title
"Example Installation". This must be run and finished before 02/01/02.
|
