| DESCRIPTION OF ENHANCEMENTS |
This patch performs the actual prescription clean up for prescriptions
messages to CPRS and HDR so these two applications can update the
Prescriptions with an expiration date on or before the CUTOFF DATE with
a Pharmacy 'ACTIVE' status
a) Set the STATUS field (#100) in the PRESCRIPTION file (#52) to
EXPIRED.
b) If the CPRS order status is 'ACTIVE'
b1) Update CPRS*
b2) Update HDR (if CPRS is updated).
c) If the CPRS order status is 'NON-ACTIVE'
c1) Update HDR
corresponding order with the expired status on their systems. This patch
NOTE: If the prescription does not have a corresponding CPRS Order
Number, the counter for this specific problem will be
incremented. However, the HDR will not be updated. HDR will
perform their own clean up for these cases.
GROUP 4:
-------
Deleted prescriptions for patients.
will address these problems. Below is a detailed description on this
a) Update HDR
* CPRS will only be updated if the prescription contains the
corresponding CPRS Order Number for the prescription being cleaned
up. Furthermore, CPRS will not be updated if the corresponding
CPRS order is on a 'NON-ACTIVE' status.
The clean up process will start right after the patch is installed. If
process:
it is necessary to stop, restart the job or to know the status of the
job, do the following:
>D ^PSO293PI
Expiration Date clean up job for Outpatient Pharamcy prescriptions
==================================================================
Current status: RUNNING (Last Rx IEN: 2587430)
Select one of the following:
SP STOP CLEAN UP JOB
VW VIEW PARTIAL CLEAN UP JOB RESULTS
QT QUIT
(SP)Stop,(VW)View,(QT)Quit: VIEW// VIEW PARTIAL CLEAN UP JOB RESULTS
Expiration Date clean up job for Outpatient Pharmacy prescriptions
Expiration post-install job clean-up flow:
==================================================================
Current status: COMPLETED ON Nov 06, 2007@17:03:36
DATE AUTO-EXPIRE COMPLETED field:
1. Institution : SITE NAME VAMC (999)
# of Rx's
Group 1: RX'S WITH NO EXPIRATION DATE cleaned up
------------------------------------- ----------
2. Calc exp date > CUTOFF (update HDR) 363
3. Calc exp date < CUTOFF,CPRS active (update HDR/CPRS) 0
------------------------------------------
4. Calc exp date < CUTOFF,CPRS non-active (update HDR) 0
5. No CPRS order# (Update HDR) 0
Group 2: RX'S IN EXPIRED STATUS
-------------------------------
6. CPRS active (update CPRS/HDR) 5,400
7. Exp>366 days,reset date,CPRS order# (update CPRS/HDR) 0
8. Exp>366 days,reset date,no CPRS order# (update HDR) 18
Group 3: RX'S PAST EXPIRATION DATE BUT STILL ACTIVE
In order to explain the process to clean up these prescriptions the
---------------------------------------------------
9. CPRS active (update CPRS/HDR) 0
10. CPRS DC'd or expired (update HDR) 0
11. No CPRS order# (HDR will run own update) 0
Group 4: RX's IN DELETED STATUS
-------------------------------
12. No CPRS order# (update HDR) 2,275
13. TOTAL NUMBER OF PRESCRIPTIONS ANALYZED: 6,653,607
following terms will be mentioned below:
Up-arrow ('^') separated values:
SITE NAME VAMC (999)^363^0^0^0^5400^0^18^0^0^0^2275^6653607
Run Log:
--------------------------------------------------------------------------
SEQ DATE/TIME INITIATOR ACTION
--------------------------------------------------------------------------
1 10/21/07@12:01:25 USER1,TEST PATCH INSTALLATION
2 10/21/07@12:01:25 USER1,TEST DATE AUTO-EXPIRE set: 01/19/08
3 10/21/07@12:01:27 USER1,TEST QUEUED
4 10/21/07@12:01:29 USER1,TEST STARTED
5 10/21/07@18:12:29 USER1,TEST COMPLETED
<END>
Once the clean up process is completed, the same information above will be
sent via Mailman message on FORUM to the user who installed the patch and
to the following support personnel below:
identified by patch PSO*7*283. Patch PSO*7*283 performed a tally, while
CUTOFF DATE:
NAME Role
-----------------------------------------------
Bruun, Jesse HDR
Consentino, Albert EPS
Mohamed, Anwer Developer
Rocha, Marcelo Developer
Ruzbacki, Ron Developer
Willette, Candice Implementation Analyst
Williamson, Eric Project Manager
-----------
Note: The sites will not have to take any action once they receive the
result message above generated by the post-install.
The message
will not be generated from non-production accounts (e.g., test
account).
Besides the clean up process, this patch introduces a change intended to
address a sporadic scenario where a prescription does not contain a
This is the date last processed by the Auto Expiration Background Job.
pointer to the corresponding CPRS order # and it goes through a status
change (e.g. from Active to Expired). Currently, such status change event
is not communicated to HDR. This patch contains a fix to notify HDR of
the status change event for such prescriptions.
This background job is supposed to be run nightly by every site. This date
is stored in the field DATE AUTO-EXPIRE COMPLETED (#49.95) in PHARMACY
SYSTEM file (#59.7) and it was introduced by the patch PSS*1*128 and it
should be populated with a valid date in all site. In case this field is
null, the post-install routine in this patch will set it to to the date
corresponding to 2 days in the past from this patch installation date. For
example, if the patch is installed on March 5, 2008 and the field is null,
this patch will correct the prescriptions with the expiration date and/or
it will be set to March 3, 2008 (in the correct Fileman date format).
CALCULATED EXPIRATION DATE:
--------------------------
The expiration date for prescription with a null expiration date is
calculated by the following formula:
For Rx with no refills:
NUMBER OF DAYS SUPPLY FROM Rx ISSUE DATE (MININUM: 30 DAYS)
status issues. In some cases the date is not present and other cases have
Rx with 1 or more refills:
Non-controlled Substances:
Rx ISSUE DATE + 366 DAYS
Controlled Substances : Rx ISSUE DATE + 184 DAYS
CPRS 'NON-ACTIVE' STATUS:
------------------------
a
The following CPRS statuses: DISCONTINUED, EXPIRED, DISCONTINUED/EDIT and
CANCELLED are considered 'NON-ACTIVE' by Pharmacy in this clean up
process.
This means that Pharmacy will not send a prescription expiration event to
CPRS if the CPRS order status is set to one of these.
PHARMACY 'NON-ACTIVE' STATUS:
---------------------------
The following Pharmacy statuses: EXPIRED, DISCONTINUED, DELETED,
DISCONTINUED BY PROVIDER, DISCONTINUED (EDIT) are considered 'NON-ACTIVE'
wrong date. Furthermore, most of the prescriptions with such problems are
by Pharmacy in this clean up process.
CLEAN UP PROCESS DESCRIPTION:
----------------------------
Prescriptions with an expiration date problem are being analyzed and
cleaned up differently, depending on which GROUP
below they fall under:
not in sync with Computerized Patient Record System (CPRS) V. 3.0 and/or
GROUP 1:
-------
Prescriptions with a null expiration date for patients.
a) Set the CALCULATED EXPIRATION DATE in the EXPIRATION DATE
field (#26) of the PRESCRIPTION file (#52).
b) If the expiration date is on or before the CUTOFF DATE
b1) If the prescription is not already in a Pharmacy 'NON-ACTIVE'
status, set the STATUS field (#100) in the PRESCRIPTION
file (#52) to EXPIRED.
Health Data Repository (HDR) in regards to their status. This patch makes
b2) Update CPRS*
b3) Update HDR
c) If the expiration date is past the CUTOFF DATE
c1) Update HDR
GROUP 2:
-------
Expired prescriptions for patients.
a) If the prescription expiration date is GREATER than 366 days
the correction to the expiration date of these prescriptions and send
a1) A new expiration date will be calculated and set in the
EXPIRATION DATE field (#26) of the PRESCRIPTION file (#52).
a2) Update CPRS*
a3) Update HDR
b) If the prescription expiration date is LESS than 366 days
b1) Update CPRS*
b2) Update HDR (if CPRS is updated)
GROUP 3:
-------
|
