=============================================================================
Run Date: JUN 04, 2020                     Designation: PSO*7*477
Package : PSO - OUTPATIENT PHARMACY           Priority: Mandatory
Version : 7       SEQ #491                      Status: Released
                  Compliance Date: SEP 30, 2020
=============================================================================

Associated patches: (v)OR*3*377        install with patch       `PSO*7*477'
                    (v)PSO*7*457   <<= must be installed BEFORE `PSO*7*477'
                    (v)PSO*7*466   <<= must be installed BEFORE `PSO*7*477'

Subject: CPRS V31.B - DAYS SUPPLY AND COPY

Category: 
  - Routine

Description:
============

 This patch is part of CPRS v31b updates. Below is a list of all the 
 applications involved in this project along with their patch numbers:
   
    APPLICATION/VERSION                                 PATCH
    ---------------------------------------------------------------
    KERNEL v8.0                                         XU*8.0*653
    TOOLKIT v7.3                                        XT*7.3*142
    TEXT INTEGRATION UTILITIES v1.0                     TIU*1.0*290
    WOMEN'S HEALTH v1.0                                 WV*1.0*24
    HEALTH SUMMARY v2.7                                 GMTS*2.7*67
    REGISTRATION v5.3                                   DG*5.3*932
    CLINICAL REMINDERS v2.0                             PXRM*2.0*45
    ADVERSE REACTION TRACKING v4.0                      GMRA*4.0*53
    CONSULT/REQUEST TRACKING v3.0                       GMRC*3.0*88
    OUTPATIENT PHARMACY v7.0                            PSO*7.0*477 
    ORDER ENTRY/RESULTS REPORTING v3.0                  OR*3.0*377
  
 Patches XU*8.0*653 and XT*7.3*142 are being released in their individual 
 Kernel Installation and Distribution System (KIDS) Host files. The other 
 patches (TIU*1.0*290, WV*1.0*24, GMTS*2.7*67, DG*5.3*932, PXRM*2.0*45, 
 GMRA*4.0*53, GMRC*3.0*88, PSO*7.0*477, and OR*3.0*377) are being released 
 in the KIDS multi-package build CPRS V31B REQUIRED PATCHES 1.0.
  
 This patch includes changes to the Outpatient Pharmacy application related
 to DAYS SUPPLY values over 90 days verification when a specific dispense
 drug is not defined in the pending order from CPRS. This patch also
 contains a new function for CPRS to call before authorizing the user to
 copy an Outpatient Pharmacy order.
  
 Below Are some details regarding the two changes in this patch:
  
 1. Patient Prescription Processing [PSO LM BACKDOOR]
    Complete Orders from OERR [PSO LMOE FINISH]
    -------------------------------------------------------------
    When trying to finish an order if the Outpatient Pharmacy user selects a
    dispense drug that has a maximum days supply limit lower than the value
    that was entered in the order by CPRS, the software will inform the user
    that the current value for DAYS SUPPLY is invalid and it will prompt the
    user to enter a new value within the maximum value allowed for the 
    dispense drug chosen, as shown in the example below:
  
    Pending OP Orders (ROUTINE)  Jan 11, 2017@13:52:45        Page:   1 of 2 
    TEST,PATIENT                                                       <A> 
      PID: 666-66-6666                              Ht(cm): _______ (______)
      DOB: DEC 02,1900 (116)                        Wt(kg): _______ (______)
    ------------------------------------------------------------------------
    *(1) Orderable Item: FUROSEMIDE TAB <DIN>                                  
     (2)           Drug: No Dispense Drug Selected                      
                   Verb: TAKE                                            
     (3)        *Dosage: 40MG                                          
                 *Route: BY MOUTH                              
              *Schedule: DAILY                                       
     (4)   Pat Instruct:                                                
      Provider Comments:                                                   
           Instructions: TAKE 1 TABLET BY MOUTH DAILY           
     (5) Patient Status: NBC                                              
     (6)     Issue Date: JAN 5,2017        (7) Fill Date: JAN 11,2017        
     (8)    Days Supply: 180               (9)   QTY (  ): 180              
    ------------------------------------------------------------------------
    +         Enter ?? for more actions                              
    Select Item(s): Next Screen// FN    Finish  
    
    DRUG NAME REQUIRED
    
    Instructions: TAKE 1 TABLET BY MOUTH DAILY
     
    The following Drug(s) are available for selection:
    1. FUROSEMIDE 40MG TAB
    2. FUROSEMIDE 20 MG
    3. FUROSEMIDE 40MG 60'S
    4. FUROSEMIDE 20MG TABS 
  
    Select Drug by number:  (1-4): 1
    
    Invalid DAYS SUPPLY value (180), resetting it to 90 (maximum allowed).
    
    DAYS SUPPLY:  (1-90): 90// 
    
 2. A new Outpatient Pharmacy API called $$ORCOPY^PSOORCPY was created for
    Computerized Patient Record System (CPRS) to call in order to verify
    whether an Outpatient Pharmacy order can be copied or not. It will check
    to verify the dispense drug is still active and still marked for the
    outpatient application. The new API returns the following 
  
    "-1^Not a Valid Outpatient Medication Order." - The prescription record
     cannot be found.  
      
    "0^<Reason>" - O indicates the order cannot be copied and the <Reason> why
    it cannot be copied (e.g., "0^This Drug has been Inactivated.") 
  
    "1" - Order can be copied.
  
 3. A new VistA Integration Control Registration (ICR) #6719 was created to 
    allow the Computerized Patient Record System V. 1.0 (CPRS) to call the new
    Outpatient Pharmacy API $$ORCOPY^PSOORCPY (see #2 above) in order to
    prevent the copy of Outpatient Pharmacy order in certain situations, such
    as dispense drug is inactive or the dispense drug is no longer marked for
    outpatient pharmacy use.
  
 4. The usage of a dosage with an EXCEPT conjunction during the
    prescription order process was removed from Patient Prescription
    Processing [PSO LM BACKDOOR], Discontinue Prescription(s) [PSO C], and
    Complete Orders from OERR [PSO LMOE FINISH] options. For prescriptions
    that have a dosage with an except conjunction, users will no longer be
    able to copy, renew, or reinstate such orders.  Users will be able to
    edit these type orders to remove the except conjunction before
    accepting/finishing the prescription. 
  
    The conjunction prompt will look like:
  
       CONJUNCTION: ??
  
       This code is used to help build a Possible Sig for a complex
       medication dose.  This code usually expands to an "and" or a "then".
       Choose from: 
        A        AND
        T        THEN
  
       CONJUNCTION:
  
    When copying an order that contains an exception conjunction the 
    following message will be displayed on the message bar:
  
       OP Medications (ACTIVE)      Jun 26, 2018@06:09:58      Page: 1 of 4
       FIVE,OUTPATIENT
       PID: xxx-xx-xxxx                        Ht(cm): _______ (______)
       DOB: MAR 9,xxxx (xx)                    Wt(kg): _______ (______)
       SEX: xxxx                            
       CrCL: <Not Found> (CREAT: Not Found)  BSA (m2): _______ 
                                               
                     Rx #: 501229$
       (1) *Orderable Item: SIMVASTATIN TAB
       (2)       CMOP Drug: SIMVASTATIN 10MG TAB
                       NDC: 00006-0735-82
       (3)         *Dosage: 10 (MG)
                      Verb: TAKE
            Dispense Units: 1
                      Noun: TABLET
                    *Route: ORAL (BY MOUTH)
                 *Schedule: QPM
                 *Duration: 7D (DAYS)
              *Conjunction: THEN
      +         Cannot COPY. Invalid 'except' conjunction!
      DC   Discontinue          PR   Partial              RL   Release
      ED   Edit                 RF   Refill               RN   Renew
      Select Action: Next Screen//
  
    Renewals will have similar messaging:
  
      Cannot be renewed - invalid Except conjunction 
  
    Reinstating orders from Patient Prescription Process option will 
    display the following message:
  
      Cannot be Reinstated - dosage contains an invalid Except conjunction
  
    Reinstating orders from the Discontinue Prescription(s) option will 
    display:
  
      Cannot be Reinstated - dosage contains an invalid Except conjunction
  
    or the prescription number will be displayed with the following 
    message:
  
       The Following Rx Number(s) Are Invalid Choices, Expired, 
       Discontinued by Provider, invalid except conjunction or Marked As
       Deleted:
                501222
       Press Return to Continue: 
  
 Patch Components
 ================
   
 Files & Fields Associated:
  
 File Name (#)      Field Name (#)                     New/Modified/Deleted
 -------------      --------------                     --------------------
 PRESCRIPTION       113 (Sub-file #52.0113, field #5   Modified
  
  
 Mail Groups Associated:
  
 Mail Group Name                                       New/Modified/Deleted
 ---------------                                       --------------------
 N/A   
   
 Options Associated:
   
 Option Name                   Type                    New/Modified/Deleted
 -----------                   ----                    --------------------
 N/A
    
 Protocols Associated:
  
 Protocol Name                                         New/Modified/Deleted
 -------------                                         --------------------
 N/A
    
 Security Keys Associated:
  
 Security Key Name                                     New/Modified/Deleted
 -------------                                         --------------------
 N/A
  
 Templates Associated:
  
 Template Name                Type    File Name (#)    New/Modified/Deleted
 -------------                ----    -------------    --------------------
 N/A
  
 New Service Requests (NSRs):
 ----------------------------
 TBD
     
 Patient Safety Issues (PSIs):
 -----------------------------
 N/A  
  
  
 Remedy/CA-SDM Ticket(s) & Overviews:
 -----------------------------------
 1. INC0273638 - VistA Option Discontinue Prescription(s) [PSO C] not
    functioning properly.
  
    Problem 1A:
    -----------
    When using "Discontinue Prescription(s)" [PSO C] option and selecting a
    sensitive patient, if you say "no" to the question, "Do you want to
    continue processing this patient record?", then the option appears to
    discontinue the prescription, but it does not.  Then every subsequent
    prescription you attempt to discontinue via this option will also fail
    to discontinue. Even if you exit [PSO C] and immediately reenter, every
    prescription will fail to discontinue.
  
    Resolution 1A:
    --------------
    Variable PSORX("DFLG") is set in some circumstances but never cleared.
    Once it is set, all discontinues fail. Changed routine PSOCAN to reset
    the variable for each prescription, and notify when it is set that the
    discontinue will not occur.
  
    Problem 1B:
    -----------
    For sensitive patients, the user says no to the prompt, "Do you want to
    continue processing this patient record?". However, the calling routine
    does not check this variable and proceeds to the discontinue prompts
    and questions.
  
    Resolution 1B:
    --------------
    Code was added to routine PSOCAN to stop the discontinue process and
    prompt for a new rx number when the user says no to the prompt "Do you
    want to continue processing this patient record?".
  
    
 TEST Sites:
 -----------
 Atlanta VA Health Care System (Decatur, GA)
 Hampton VA Medical Center (Hampton, VA)
 Northport VA Medical Center (Northport, NY)
 Louis Stokes Cleveland VA Medical Center (Cleveland, OH)
   
  
 Documentation Retrieval Instructions:
 -------------------------------------
 Sites may retrieve the software and/or documentation directly using the
 Secure File Transfer Protocol (SFTP) address as directed by the CPRS
 Implementation team. Installation instructions will be distributed when
 your site begins the implementation process.
  
 Documentation can also be found on the VA Software Documentation Library 
 at: http://www.domain.ext/vdl/
  
 The updated documentation will not be on the vdl until after the phased
 deployment has completed.  
  
 Title                              File Name                 Transfer Mode
 --------------------------------------------------------------------------
 Outpatient Pharmacy -              PSO_7_0_477_MAN_UM.DOC      BINARY
   Manager's User Manual            PSO_7_0_477_MAN_UM.PDF      BINARY
 Outpatient Pharmacy -              PSO_7_0_477_PHAR_UM.DOC     BINARY
   Pharmacist's User Manual         PSO_7_0_477_PHAR_UM.PDF     BINARY
 Outpatient Pharmacy -              PSO_7_SUPPLEMENTAL_UM.DOC   BINARY
   Supplemental User Manual         PSO_7_SUPPLEMENTAL_UM.PDF   BINARY
 Outpatient Pharmacy -              PSO_7_0_477_TECH_UM.DOC     BINARY
   Technician's User Manual         PSO_7_0_477_TECH_UM.PDF     BINARY
  
  
 Patch Installation: 
  
 Installation Instructions:
 --------------------------
 Please refer to the "CPRS v31b Deployment, Installation, Back Out and 
 Rollback Guide" for installation and set-up information. This document is 
 exported as OR_30_377_IG.doc and OR_30_377_IG.pdf and is included in 
 OR_30_377.ZIP and will be emailed to the installation point of contacts by
 the CPRS Implementation team.

Routine Information:
====================
The second line of each of these routines now looks like:
;;7.0;OUTPATIENT PHARMACY;**[Patch List]**;DEC 1997;Build 187

The checksums below are new checksums, and
 can be checked with CHECK1^XTSUMBLD.

Routine Name: PSOCAN
    Before: B55445842   After: B57127881  **11,21,24,27,32,37,88,117,131,
                                           185,253,251,375,379,390,413,
                                           372,416,508,477**
Routine Name: PSOCAN1
    Before: B63054494   After: B64816053  **8,20,24,27,32,131,163,185,
                                           238,372,442,508,477**
Routine Name: PSOORCPY
    Before: B37014700   After: B49627866  **10,21,27,32,46,100,117,148,
                                           313,411,444,468,504,477**
Routine Name: PSOORNW1
    Before: B34134148   After: B35569635  **23,46,78,117,131,133,172,148,
                                           222,268,206,251,379,391,313,
                                           444,469,422,477**
Routine Name: PSORENW
    Before: B54413066   After: B55739643  **11,27,30,46,71,96,100,130,
                                           148,206,388,390,417,313,411,
                                           504,508,550,457,477**
Routine Name: PSOUTL
    Before:B169155979   After:B174200090  **1,21,126,174,218,259,324,390,
                                           313,411,466,477**
 
Routine list of preceding patches: 422, 457, 466

=============================================================================
User Information:
Entered By  :                               Date Entered  : JAN 03, 2017
Completed By:                               Date Completed: JUN 02, 2020
Released By :                               Date Released : JUN 04, 2020
=============================================================================


Packman Mail Message:
=====================

No routines included