OUTPATIENT PHARMACY (60)    PACKAGE (9.4)

Name Value
NAME OUTPATIENT PHARMACY
PREFIX PSO
DEVELOPER (PERSON/SITE) SAB/B'HAM
DEVELOPMENT ISC BIRMINGHAM
CLASS National
CURRENT VERSION 7.0
ADDITIONAL PREFIXES
  • APSP
SHORT DESCRIPTION OUTPATIENT LABELS, PROFILE, INVENTORY, PRESCRIPTIONS
VERSION
  • 6.0
    DATE DISTRIBUTED:   2002-11-22 00:00:00
    PATCH APPLICATION HISTORY:
    • 153
      DATE APPLIED:   1996-09-22 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      PSO*6*153 patch transort the routine PSOHELP1 whaich was omitted in
      PSO*6*102.  
      
    • 163 SEQ #162
      DATE APPLIED:   1997-12-15 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      See the patch description PSO*6*163.
      
    • 164 SEQ #163
      DATE APPLIED:   1997-12-22 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      See the patch description PSO*6*164.
      
    • 165 SEQ #164
      DATE APPLIED:   1998-01-20 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      See the patch description PSO*6*165.
      
    • 166 SEQ #165
      DATE APPLIED:   1998-02-20 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      See the patch description PSO*6*166.
      
    • 167 SEQ #166
      DATE APPLIED:   1998-03-05 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      See the patch description PSO*6*167.
      
    • 168 SEQ #167
      DATE APPLIED:   1998-04-03 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      See the patch description PSO*6*168.
      
    • 169 SEQ #168
      DATE APPLIED:   1998-06-22 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      See the patch description PSO*6*169.
      
    • 170 SEQ #169
      DATE APPLIED:   1998-07-12 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      See the patch description PSO*6*170.
      
    • 173 SEQ #170
      DATE APPLIED:   1998-09-23 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
       
      This patch contains modifications required by the implementation of the
      NATIONAL DRUG FILE (NDF) package's APIs and the MailMan package's file
      changes contained in patch XM*7.1*50.
      
    • 174 SEQ #171
      DATE APPLIED:   1998-11-19 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      See the patch description PSO*6*174.
      
    • 154
      DATE APPLIED:   1996-10-02 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      This is the build for Patch PSO*6.0*154.
      
    • 177 SEQ #172
      DATE APPLIED:   1998-12-29 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      This patch corrects a problem created by PSO*6*174.  If an Rx with at
      least one refill is placed on hold, an undifined error will occur.
      
    • 172 SEQ #173
      DATE APPLIED:   1999-02-23 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      This patch addresses several problems reported via NOIS: 
          involved did not include a necessary CMOP cross reference.  The cross
          reference has been included.
       
      3)  NAN-0498-41811 depicts a condition where an Rx written for a
          controlled substance had a one year expiration date rather than the
          required limit of 6 months. A check has been inserted and the
          expiration date of 6 months is forced on controlled substances.
       
      4)  A medical center using Outpatient Version 7.0 noticed that the cancel
          date from an Rx being renewed was transferred to the renewed Rx.
       1) CLE-0397-41373 describes a situation where editing the QTY field (#7)
          Research disclosed (also for V 6.0) that this was only happening if
          the Rx being renewed was already canceled before the renewing action
          was taken. If, as is normal, the Rx status was changed to cancel
          DURING the renewing action, the cancel date was not transferred to the
          new Rx. The code was modified to delete the old cancel date during
          renewals.
          or the QTY field (# 52.1,1 refill quantity) results in an update of
          the CURRENT INVENTORY field (#50) in the DRUG file (#50). The software
          was modified to prevent updating the CURRENT INVENTORY during edit.
       
       2) GNH-0298-42078 reports that when attempting to change the suspense
          date for a patient's Rxs using the Change Suspense Date [PSO PNDCHG]
          option, the lookup fails to find the patient's name.  The lookup
      
    • 156 SEQ #174
      DATE APPLIED:   1999-03-16 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      PSO*6.0*156 provides an interface between Outpatient Pharmacy V 6.0 and
      CIRN V 1.0. The event points within the OP software calls an entry point
      provided by the CIRN package, EN^RGEQ("RX",IRXN).
      
    • 176 SEQ #175
      DATE APPLIED:   1999-03-16 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      This patch makes a functional change to the Partial Prescription [PSO
      RXPAR] option.  Partial prescriptions will be prohibited if a prescription
      has a "canceled", "non-verified", or "pending" status. 
       
      This change is consistent with updated functionality
      included in Outpatient Pharmacy V. 7.0.
      
    • 155 SEQ #154
      DATE APPLIED:   1997-02-04 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      Miscellaneous patch.
      1) Allow users to reprint Rx's filled at CMOP facilities.
      2) Fix Refill Quantities in Drug Acct
      3)This patch fixes a problem that could occur after processing Rx's in the
      Process Drug/Drug Interactions option. If any Rx's are processed in this
      option, and the user then goes directly to the New Prescription Entry
      option and enters new Rx's, a duplicate label of the Rx processed in the
      Process Drug/Drug Interactions option could possibly print. This patch
      fixes the problem.
      
    • 158 SEQ #156
      DATE APPLIED:   1997-04-01 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      CMOP/OUTPATIENT PHARMACY enhancement patch to allow users to designate, at
      the patient level, mailing criteria.
      
    • 159 SEQ #157
      DATE APPLIED:   1997-05-28 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      See the patch description PSO*6*159.
      
    • 160 SEQ #158
      DATE APPLIED:   1997-06-02 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      See the patch description PSO*6*160.
      
    • 152 SEQ #159
      DATE APPLIED:   1997-08-19 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
       
      This is the CHAMPUS Billing patch for Outpatient Pharmacy (PSO*6*152).
      
    • 161 SEQ #160
      DATE APPLIED:   1997-11-18 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      See the patch description PSO*6*161.
      
    • 162 SEQ #161
      DATE APPLIED:   1997-11-27 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      See the patch description PSO*6*162.
      
    DATE INSTALLED AT THIS SITE:   1996-07-02 00:00:00
  • 7.0
    DATE DISTRIBUTED:   2005-11-19 00:00:00
    PATCH APPLICATION HISTORY:
    • 1
      DATE APPLIED:   1999-04-16 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      PSO*7.0*1 - 1.26.97
      modified.  They are: PSOHLNE1, PSOHLNE2, PSOHLNEW, PSOHLSIG, PSOHLSIH,
      PSOHLSN, PSOHLSN1, PSOORUT1, PSON52, PSORN52, and PSORN52C.
       
      PSOREF: Fixed problem on speed refill of invalid Fill Date selection prompts
      if the 1st Rx in the list is expired.  In this routine there's an entry
      point that's used by CPRS to help determine if an Rx is refillable.
      There's a potential problem when refill requests are made and the Pharmacy
      Orderable Item are missing from the Rx.  In order to prevent a
      possible undefined error from occurring an addition check was added to
      determine if there's an orderable item is for that drug in the Rx.
       
       
      When a refill was in suspense, some cross references were being corrupted
      in the Rx Suspense File. These changes fix that problem. Also added a
      cross reference to the Fill Date field. What this does is if an Original
      Fill is in suspense and has not yet been printed, if the Fill Date is
      edited, then we now update the suspense date with the new Fill Date.
      Routines: PSOUTL, PSOUTLA. The Fill Date field (#22) in the Rx file (#52)
      will be sent out in this patch.
       
      Added addition code to prevent refills from being deleted when removing
      PSOCLO1: A problem was reported about Clozapine Rxs and when there are
      Rxs from Hold,  Routines: PSOUTL, PSOHLD
      valid lab results.  The problem has to do with the lab results being
      returned as zero when a number should be returned.
        
      After the installation of version 7.0 in Washington's production account
      a number of allocation errors begin to occur.  In an attempt to manage
      the number of variables in the partition several routines have been
      
    • 17
      DATE APPLIED:   1999-04-16 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
       
       
      3. Corrected a possible problem of barcode on and off sequences being changed
      and made invalid for label printers.  This could happen if a label device is
      selected, then an Action Profile device is selected, and the site parameter
      is set to print barcodes on action profiles.  If there are Rx labels to print
      again the Barcode On and Barcode Off sequences for the Action Profile printer
      become the sequences for the Label printer, which may not work if the printers
      selected are different types.  Routines PSOSD, PSOSD1, PSOSDP
       
       4. Corrected a problem reported when using the Delete a Prescription
      1. Corrected problems with the nightly cost compile jobs.  The problems are
      [PSO RXDL] option.  If an original fill is released, and a refill is
      entered but not yet released, the user can mark the prescription as
      deleted without first returning to stock the original fill. Routine PSORXDL
       
      that the number of requests by patient was not being counted correctly and 
      a problem with the nightly compile where data for the previous day was being
      reset.  Routines: PSOCSTD, PSOCSTM
       
      2. Corrected a problem with the nightly job that compiles the AMIS data. The
      problem is that all partials was not being counted correctly.
      Routine: PSOAMIS0
      
    • 70 SEQ #103
      DATE APPLIED:   2002-06-26 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      1. If a site has the External Interface outpatient site parameter set to
         will make that correction.
       
      2. This patch will fix errors that can possibly occur when the external
         interface encounters bad prescription data.
       
      3. It was reported by some sites that if the site has multiple dispensing
         machines, when the prescription is entered at one of these machines,
         the same prescription gets transmitted to the other machines. This
         patch is setting the HLL("LINKS") array to dynamically specify one or
         more recipients for the HL7 message to insure that the prescription
         either "2:SEND ALL ORDERS AND DON'T PRINT LABEL" or "3:SEND MARKED 
         entered at one of the devices will not be transmitted to the others.
       
       
                              ***** NOTE *****
      The new software design will be using the Dynamic Addressing setup as
      described in the following steps:
       
      1. It is recommended for the site to have only one Client and one Server
         Protocol, and to delete the LOGICAL LINK (LL) field (#770.7) of the
         PROTOCOL file (#101) for those Client and Server Protocols. Then the
         ORDERS AND DON'T PRINT", a problem can occur when issuing a partial
         site would need to create a LL for every "machine" that it has.
       
      2. Deriving the LL for each prescription using the following methods:
       
       a) The software will use the LL entry from the CPRS ORDERING INSTITUTION
          subfile (#59.08) multiple of the OUTPATIENT SITE file (#59) if there
          is a Clinic associated with the prescription, and the Institution
          derived from that Clinic has an entry in this CPRS ORDERING
          INSTITUTION subfile (#59.08) multiple of the OUTPATIENT SITE file 
          (#59) with an associated LL.
         prescription. If there is already an original fill or refill suspended 
       
       b) The LL on the top level will be used for the prescription in
          the following cases:
          - If there is no Clinic associated with the prescription.
          - If there is a Clinic associated with the prescription, but the
            Institution derived from that Clinic does not have an entry in the
            CPRS ORDERING INSTITUTION subfile (#59.08) multiple of the 
            OUTPATIENT SITE file (#59) with an associated LL for that Outpatient
            Site entry.
       
         for a prescription, and a partial prescription is issued, the suspended
       c) If the LL can't be derived through the previous steps then it's
          defaulted to "PSO LLP1" (sent out with Outpatient Pharmacy package).
         fill will be removed from suspense, and the status of the prescription
         will be set to Active when the partial prescription is sent to the 
         external interface. The prescription fill should remain in suspense,
         and the status of the prescription should remain Suspended. This patch
      
    • 107 SEQ #104
      DATE APPLIED:   2002-07-24 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      This patch replaces all occurrences of *13 with $C(13) in the Outpatient
      Pharmacy V. 7.0 package in order to make it vendor independent as per
      SOP 192-104.
      
    • 99 SEQ #105
      DATE APPLIED:   2002-08-14 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      1. When finishing a pending order entered through Computerized Patient
      with the order contains a 2, 3, 4, or 5. This patch makes this change. A
      message has also been added that will be displayed during the finish
      process only when the quantity is automatically updated by the software,
      due to edits of any of these fields.
       
      2. There are occurrences throughout the Outpatient Pharmacy package where 
      Possible Dosages and Dispense Units per Dose are displayed, and if that 
      numeric data begins with a decimal point, such as ".5," then that is how
      it is displayed, as ".5". This patch will make change to add a leading
      zero to these displays, so ".5" will now be displayed as "0.5". This
      Record System (CPRS), and fields are edited during the finish process that
      change will not apply to Local Possible Dosages. It will only apply to
      Possible Dosages and Dispense Units per Dose.
       
      3. When prescriptions are entered that contain Possible Dosages, the Noun 
      that is applied to the Dosing Instruction comes from the DOSAGE FORM file 
      (#50.606). If that Noun ends in "(S)" or "(s)", such as TABLET(S) or 
      CAPSULE(S), the software will adjust the Noun based on the Dispense Units 
      per Dose. For example, if the Noun is TABLET(S), then the software will 
      change the Noun to TABLET if the Dispense Units per Dose is one or 
      less, and the software will change the Noun to TABLETS if the Dispense 
      are used in the automatic Quantity calculation such as Days Supply or
      Units per Dose is greater than one. When prescriptions and pending orders 
      are edited, this conversion of the Noun does not always take place. This 
      patch makes the change to convert the Noun to it's proper form when edits 
      are made.
       
      4. When finishing a pending order using either the Patient Prescription 
      Processing [PSO LM BACKDOOR ORDERS] option, or the Complete Orders from
      OERR [PSO LMOE FINISH] option, an undefined error could occur if the
      ListMan action "EA Enter/Edit Allergy/ADR Data" is selected to add or edit
      allergy information. This patch fixes this problem.
      Schedule, a recalculation is done on the Quantity of the prescription,
       
      5. There is an order check for drugs with data entered in the MAXIMUM DOSE
      PER DAY field (#4) of the DRUG file (#50), that divides Quantity by Days
      Supply, and if that's greater than the MAXIMUM DOSE PER DAY, an order
      check is given. A problem occurred when this order check was given when
      finishing an order entered through Computerized Patient Record System
      (CPRS). If an '^' is entered at the 'Do You Want to Edit Days Supply and
      Quantity Fields?' prompt, the user will exit the process, but the
      subsequent prompts for that order are still given, even though the order
      will not be finished because of the '^' that was entered. This patch will
      whether the edits created a new order or not. A request has been made to
      suppress those remaining prompts after the '^' is entered.
       
      6. When an active prescription is copied using the CO Copy (OP) hidden
      action in Patient Prescription Processing [PSO LM BACKDOOR ORDERS] option,
      and if the CONJUNCTION field (#5) of the MEDICATION INSTRUCTIONS sub-file
      (#52.0113) of the PRESCRIPTION file (#52) is deleted using the @ key, then
      the software does not trigger the duplicate drug check and as a result
      duplicate active prescriptions are created. Also it was observed that
      deleting this field by using the @ key during the process of
      creating/editing a prescription, the software prompts the question
      not recalculate the Quantity based on these edits when finishing a pending
      "Deleting this conjunction will delete the dosing sequence that follows!",
      even when no conjunctions are defined. In such a situation this patch will
      display a message "Invalid Entry - nothing to delete" and will loop back
      to the CONJUNCTION field (#5) of the MEDICATION INSTRUCTIONS sub-file 
      (#52.0113) of the PRESCRIPTION file (#52) prompt.
      order from CPRS if any of the Schedules associated with the order contain
      PRN, or if the drug is a Schedule 2, 3, 4, or 5, meaning the DEA,
      SPECIAL HDLG field (#3) of the DRUG file (#50) for the drug associated
      
    • 108 SEQ #106
      DATE APPLIED:   2002-09-06 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      1. A site reported a problem with the maximum refills calculation for an 
      of 7 days even if the pending order had 14 days supply. This patch ensures
      that the DAYS SUPPLY field (#8) is set to a maximum of 7 or 14 days 
      depending on the DISPENSE FREQUENCY field (#2) of the CLOZAPINE PATIENT
      LIST file (#603.01). NOIS TUA-0302-31000
       
      3. In Patient Prescription Processing [PSO LM BACKDOOR ORDERS] option, if 
      the CO Copy (OP) hidden action is used first and then if a pending order 
      is completed, the software displays the clinic name of the CLINIC field 
      (#5) of the PRESCRIPTION file (#52) that was in the previous prescription 
      that was copied. This patch corrects this problem. NOIS CON-0602-11684
      order placed through the Computerized Patient Records System (CPRS) V. 
      1.0. The problem occurred if a free-text dosage was used. This patch 
      corrects this problem. NOIS UNY-0302-12906
       
      2. When finishing a pending order for a Clozapine drug using either the 
      Patient Prescription Processing [PSO LM BACKDOOR ORDERS] option, or the
      Complete Orders from OERR [PSO LMOE FINISH] option, the software sets the
      default DAYS SUPPLY field (#8) of the PRESCRIPTION file (#52) to a maximum
      
    • 88 SEQ #107
      DATE APPLIED:   2002-09-27 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      1. A potential patient safety issue is being addressed in this patch.
       
      2. This patch corrects a problem where prescriptions are automatically
      discontinued by a date of death entry or 3 days after a patient has been
      admitted to the medical center.  The problem occurred when the
      prescriptions are reinstated.  The fill dates are not being reset correctly
      to the dates prior to being automatically discontinued.
      Currently when a date of death is entered into the Date Of Death field
      (#.351) in the Patient file (#2), all active prescriptions are automatically
      discontinued.  The patient safety issue is when a date of death is entered
      in error, which can cause the patient to missed their next fill because the
      Outpatient Pharmacy system has no way of determining which prescriptions were
      Discontinued and which ones should be reinstated.  This patch and the
      DG*5.3*455 patch will correct this.
        
      
    • 111 SEQ #108
      DATE APPLIED:   2002-10-25 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      This patch is in support of the HUI/VHA CIO SD&D Pharmacy Data 
      this functionality, nothing needs to be done besides installing the 
      patch. If sites want to utilize this functionality, more information on 
      the setup and the data elements are documented at:
       
       
      This patch also fixes a problem of an undefined error that can occur 
      when entering a new prescription. At the PATIENT INSTRUCTIONS prompt, if 
      text is entered greater than 32 characters in length, without any spaces,
      an error will occur. This patch will fix the error, and the user will now 
      be re-prompted for PATIENT INSTRUCTIONS when this occurs.
      Interchange project. The project provides a method for the one-way 
      electronic transfer of prescription orders from an external system to 
      VistA.
       
      This patch exports the PSO RECEIVE ORDER Protocol, the PSO RECEIVE HL7 
      Application Parameter, and the PSO LLPO HL Logical Link. These can be 
      used to recieve new orders and cancel orders from an outside source into 
      the Outpatient Pharmacy Vista database. If sites do not wish to utilize 
      
    • 114 SEQ #109
      DATE APPLIED:   2002-11-08 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
       
      2. If a prescription is put on HOLD and later on is UNHELD, the user is
         always prompted for "FILL (or REFILL) DATE" and "MAIL/WINDOW". This 
         was allowing the user to overwrite the original fill/refill date on
         file, even after the prescription had already been released. This  
         was misleading, giving users the impression that the prescription
         would be filled and the labels would print. Since the prescription
         had already been released, the fill and the label print did not 
         happen. Once this patch is installed, these two fields will only be
         asked if the prescription (or refill) has NOT yet been released.
       
      1. If a returned to stock prescription is put on HOLD, then UNHELD and a
      3. If one of the copay exemption questions applies to a patient, but has
         never been answered, under the RESET COPAY STATUS/CANCEL CHARGES
         [PSOCP RESET COPAY STATUS] option, the default for the question: "Do
         you want to enter/edit any copay exemption flags? N//" will be changed
         from N to Y.
       
      4. The MailMan message which is generated when a copay exemption question
         applies but has not been answered generated errors at at least one
         site when there was no provider in the prescription. This patch adds a
         check for the provider field being null and if so, does not attempt to
         label prints, the label is not marked as a reprint, so the
         queue the MailMan message to a non-existent provider.
       
      5. When using Backdoor Orders, if the user selected to edit the 'PATIENT
         STATUS' and '# OF REFILLS' (5,11) of a prescription, the possible 
         range for number of refills was showing as '(0-999999999999)'. This 
         allowed the user to enter any value between '0' and '999999999999'.
         Once this patch is installed this problem will be corrected and the
         actual maximum number of refills will be shown as the maximum value 
         for the range.
         
         prescription cannot be released until the label reprint option is used.
      6. When the user tried to delete a single dosage from a set of 4 or more
         dosages (complex dosage), the system was not deleting. It would accept
         the deletion, but when the user tried to accept the changes, it would 
         block with the message "dosage missing!". This patch will fix this 
         problem and the user will be able to delete such dosages.
       
      7. When an order entered through Computerized Patient Record System
         (CPRS) is finished in Pharmacy, and an edit is made that generates an
         automatic recalculation of the quantity of the prescription, a message
         is displayed to the screen indicating that the quantity has been
         This patch will mark the label as being a reprint and also will set the
         updated. There are also occurrences when the quantity is updated
         automatically and that message is not displayed, such as editing after
         a Copy, or editing after entering a new prescription but prior to
         accepting, or editing after accepting an edit that creates a new order.
         With this patch, the quantity update message will display every time an
         edit is made and a new quantity is automatically calculated.
       
      8. When entering a new prescription, at the PATIENT INSTRUCTIONS prompt,
         if text is entered greater than 32 characters in length, without any
         spaces, an error will occur. This patch will fix the error, and the
         reprinted label indicator in the prescription file so that a returned
         user will now be re-prompted for PATIENT INSTRUCTIONS when this occurs.
         to stock prescription can be released when unheld.
       
        
      
    • 115 SEQ #110
      DATE APPLIED:   2002-11-22 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      Associated patches: (v)PSO*7*95  <<= must be installed BEFORE `PSO*7*115'
      in the PHARMACY PATIENT file (#55)).
      2) Then place an order from CPRS for an outpatient pharmacy patient
      already in the PHARMACY PATIENT file (#55), but is missing the PATIENT
      STATUS field (#3) in that file.
      3) Then finish the orders in outpatient pharmacy for the patients in 1)
      and 2) in that order, entering "^" for the Patient Status prompt for the
      second patient. The entire entries for the second patient will be deleted
      from the PHARMACY PATIENT file (#55), because a local variable from the 
      last new patient still existed.
       
       
      This patch ensures that the local variable is killed between each patient.
       
      Since the PHARMACY PATIENT file (#55) can contain both inpatient and
      outpatient pharmacy information, the post-install routine will handle
      rebuilding both types. It will send a MailMan message upon completion
      indicating whether any missing entries were found and rebuilt for the
      Inpatient Medications V. 5.0 orders or Outpatient Pharmacy V. 7.0
      cross-references. The message will also show the global(s) that contain
      the affected entries.
      PSO*7*115 fixes a problem which may have caused some entries from the
      PHARMACY PATIENT file (#55) to be deleted. This patch also provides a
      post-install clean-up routine to rebuild any missing entries.
       
       
      Before this patch, an example of how this problem could happen is:
      1) Place an order in CPRS for a brand new outpatient pharmacy patient (not
      
    • 129 SEQ #111
      DATE APPLIED:   2002-11-22 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
       
       
       
      Patch PSO*7*129 will create a MailMan message containing a list by patient
      name of any cross references that were rebuilt by PSO*7*115. The subject
      of the MailMan message will be one of the following:
       
      Subj: PHARMACY PATIENT File (#55)  NO ENTRIES TO LIST
      Subj: PHARMACY PATIENT File (#55)  LIST IN USE
      Subj: PHARMACY PATIENT File (#55) listing of rebuilt entries
       
      PSO*7*115 fixed a problem which may have caused some entries from the
      A MailMan message with the first subject would occur if there was nothing
      in the temporary global created by patch PSO*7*115. That temporary global
      is kept for 30 days. The second subject would occur if the post-install
      job for patch PSO*7*115 is currently running. In this case, the
      post-install job for patch PSO*7*129 can be queued later by running
      ^PSOPOST8 from programmers mode.
       
      The MailMan message is sent to the installer of the patch and holders of
      the PSNMGR key.
      PHARMACY PATIENT file (#55) to be deleted and a post-installation routine
      in that patch reset the missing entries.
       
      Patch PSO*7*129 should not be installed until the post-install job of
      patch PSO*7*115 has run to completion. When it is complete, a MailMan
      message is sent to the installer of PSO*7*115 with a subject line of:
      Subj: PHARMACY PATIENT File (#55) search for missing entries
      
    • 127 SEQ #113
      DATE APPLIED:   2002-12-20 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      The Deputy Undersecretary for Health for Operations and Management (10N) 
      audits to discover and correct any patterns of inappropriate address
      changes. An option created with this patch will facilitate the review of
      the audits.
       
      Audits consume disk space on the VistA system so audit results cannot be 
      stored indefinitely. Pharmacy Managers should negotiate a timeframe for 
      the regular review of the audits so that the audits can be purged from 
      the system when no longer needed. The suggested fields for auditing are:
       
      STREET ADDRESS [LINE 1]    (#.111)
      convened a task force in April 2002 to review the controlled substance 
      STREET ADDRESS [LINE 2]    (#.112)
      STREET ADDRESS [LINE 3]    (#.113)
      CITY                       (#.114)
      STATE                      (#.115)
      ZIP CODE                   (#.116)
      ZIP+4                      (#.1112)
      TEMPORARY STREET [LINE 1]  (#.1211)
      TEMPORARY STREET [LINE 2]  (#.1212)
      TEMPORARY STREET [LINE 3]  (#.1213)
      TEMPORARY CITY             (#.1214)
      process in VHA. The task force returned several recommendations. One of 
      TEMPORARY STATE            (#.1215)
      TEMPORARY ZIP CODE         (#.1216)
      TEMPORARY ZIP+4            (#.12112)
       
       
      The new option exported with this patch is named Patient Address Changes
      Report [PSO ADDRESS CHANGE REPORT], and will be placed under the
      Supervisor Functions [PSO SUPERVISOR] menu option. This option prints a
      report that shows changes made to the various address fields listed above
      from the PATIENT file (#2), over the date range specified. The report can
      the recommendations was to modify the Outpatient Pharmacy package to 
      be run for one patient, or for all patients. A field can only be tracked
      and shown on this report if the VA FileMan AUDIT function was turned on
      for the field at the time the field was edited.
      provide a record of all address changes.
       
      Medical Center Pharmacy Managers are encouraged to contact their IRM and 
      arrange the regular auditing of changes to address and temporary address 
      fields in the Patient file (#2). Pharmacy Managers should monitor these
      
    • 3
      DATE APPLIED:   1999-04-16 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      Fixed problem reported in Tuscaloosa, local NOIS PHA-0198-N0090. If a
      and PSODIR3.
       
      In the Outpatient package there's a Listman action that allows the user to
      print medication instruction sheets. This action when used does not turn off
      the Listman screen controls.  This patch corrects that.  Routine: PSOHELP.
       
      Fixed problem reported in Tuscaloosa, local nois PHA-0198-N0104.
      When the Autocancel on Admission job ran, it was not canceling
      prescriptions that were issued on the same day as the admission, but
      it should have been canceling them.
      reprint was done in Listman on one Rx in the Patient Prescription
      Processing option, then the user finished some Rx's in the Complete
      Orders from OERR option, the comments from the reprint would carry over
      to the Label Log entries for the Rx's finished in the Complete option.
      Routine: PSORXRPT
       
      SAC 2.2.1.1 prohibits parameter passing on the first line.3 routines
      have formal lists on the first line.  Routines: PSOORDRG, PSODIR2,
      
    • 122 SEQ #114
      DATE APPLIED:   2002-12-20 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      The Edit Data for a Patient in the Clozapine Program [PSOL EDIT] option 
      and the Register Clozapine Patient [PSOL REGISTER PATIENT] option will no     
      longer check for race, sex, or zip code for Outpatient Pharmacy in the
      Clozapine Program.  All three checks are no longer necessary.
      
    • 124 SEQ #115
      DATE APPLIED:   2003-01-15 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      Description:
         The primary problem is that when these prescriptions were being
         transmitted to the CMOPs and they were behind on dispensing, the
         prescriptions were being rejected because the prescriptions had
         already expired. The default of 5 is being changed to 30 to
         accommodate the CMOPs and to allow the patients to receive their
         medications in a timely manner. Prescriptions will no longer expire
         before 30 days elapses from the Issue Date when the day supply is
         less than 30 days and there are no refills.  If a minimum of 1 refill
         is entered the one year/six month rule still applies.
       
      ===========
       
      2. This patch also includes a correction to initialize the line 
      counter for the "SIG1" entries in the PRESCRIPTION file (#52). Before 
      this fix, the count could be incorrect sometimes which could cause
      problems for external interfaces.
       
      3. This patch corrects a problem that caused a null subscript error.  
      This would happen if records were being created in the PENDING OUTPATIENT
      ORDERS file (#52.41) and an attempt was made to pull up the patient's
      medications in the Computerized Patient Record System (CPRS) at the same
       
      moment.
       
      1. Currently, if a non-controlled substance prescription is entered with
         a day supply less than 5 days and there are no refills, the expiration
         date defaults to 5 days from the issue date.  If a controlled substance
         prescription is entered with a day supply less than 5 days without
         refills, the expiration date is the Issue Date plus the Days Supply.
      
    • 121 SEQ #116
      DATE APPLIED:   2003-01-23 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      1) When an order entered through Computerized Patient Record System 
      includes default and maximum values for various fields during the order
      entry process, whether the order is being entered through CPRS V. 3.0 or 
      Outpatient Pharmacy V. 7.0. A request has been made to not update the
      PATIENT STATUS field (#3) of the PHARMACY PATIENT file (#55) when the
      Patient Status is edited during the finish process if ADMINISTERED IN
      CLINIC was entered as the Pick Up for the order in CPRS V. 3.0.
       
      2) Outpatient Pharmacy V. 7.0 patch PSO*7*111 introduced new functionality
      that enables the Outpatient Pharmacy V. 7.0 package to receive New and
      Discontinue Pharmacy orders from an external system. When these orders are
      (CPRS) V. 3.0 is finished in Outpatient Pharmacy V. 7.0, fields can be
      received, an immediate update is then sent from Outpatient Pharmacy V. 7.0
      to CPRS V. 3.0. A problem has been reported on the Discontinue orders,
      when the update is sent from Outpatient Pharmacy V. 7.0 to CPRS V. 3.0. In
      some cases, CPRS V. 3.0 will enter the current user into the DC'ed BY
      field (#62) in the ORDER file (#100). Since the only defined user on the
      system for this process could be the person who started the HL7 filers,
      this patch makes the change to send the requesting provider as the current
      user when the discontinue messages are sent to CPRS V. 3.0. This fix will
      only affect orders received from an external system using the interface
      introduced in patch PSO*7*111.
      edited during that finish process. One of those fields is the PATIENT
      STATUS field (#3) of the PRESCRIPTION file (#52). When this field is
      edited during the finish process, not only does that field get updated for
      that prescription, but the PATIENT STATUS field (#3) of the PHARMACY
      PATIENT file (#55) also gets updated. Then when the next prescription is
      entered for that patient, the PATIENT STATUS field (#3) of the PHARMACY
      PATIENT file (#55) is used as the default Patient Status, and that
      
    • 110 SEQ #117
      DATE APPLIED:   2003-02-04 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      After installing patch PSO*7*107, some sites have reported problems in
      Baker 2000, etc. If your site is using any class 3 software, please get
      the corrections for these dispensing machines before installing this
      patch.
      printing labels, notably when there are bar codes in the label. In patch
      PSO*7*107, we replaced the carriage return control code *13 with $C(13) to
      make it vendor independent. The problem is that the $C(13) under DSM/VMS
      does not initialize the column position to zero. This patch fixes this
      problem.
       
      Please note: This patch and the associated patch PSO*7*107 are not 
      compatible with class 3 software for automated dispensing machines such as
      
    • 116 SEQ #118
      DATE APPLIED:   2003-03-01 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      The purpose of this patch is to support the implementation of Internet 
      Prescription Refill for Outpatient Pharmacy V. 7.0. This request has links
      to the Health eVet project that will provide a mechanism to obtain copies
      of key portions of their medical record, personalize that record with
      relevant educational information and provide links to electronic service
      delivery capabilities, such as prescription refills. The veteran will be
      able to request a prescription refill and review his prescription profile
      by using a web based interface on the internet.
      
    • 112 SEQ #119
      DATE APPLIED:   2003-03-29 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      When performing drug lookups, two issues were identified. First, the user
       
       Select DRUG: hep
             Lookup: VA DRUG CLASS  CLASSIFICATION
       HEPARIN ANTAGONISTS  BL200
          HEPARIN ANTAGONISTS
           Lookup: DRUG  NATIONAL DRUG CLASS
         PROTAMINE SULFATE 5ML INJ         BL200
                ...OK? Yes// N  (No)
       
           Lookup: DRUG  GENERIC NAME
      was not aware of which item was being matched. For example, was the match
       
            1   HEPARIN 1,000 UNIT/ML 10ML INJ           BL100
            2   HEPARIN 1,000 UNITS/ML 30ML            BL100
            3   HEPARIN 10,000 UNITS 4ML           BL100
            4   HEPARIN BEEF 1,000 UNITS/ML 30ML           BL100
            5   HEPARIN, LOCK  100 UNIT/ML 1ML           BL100
       Press <RETURN> to see more, '^' to exit this list, OR
       CHOOSE 1-5:
            6   HEPATITIS-B IMMUNE GLOBULIN           IM500
       CHOOSE 1-6:
      for the GENERIC NAME of the drug or was it the SYNONYM. The second issue
      had to do with the search matching to the NATIONAL DRUG CLASS NAME first,
      before checking for a GENERIC NAME. This patch makes two changes to the
      drug lookup. First, the search will display the item being searched on.
      Second, if one or more matches are found on an item, but the user doesn't
      select one of the matches displayed, the search will continue through all
      other items. A sample screen display follows:
      
    • 134 SEQ #120
      DATE APPLIED:   2003-03-29 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      1. When Pharmacy orders are entered through Computerized Patient Record 
      System (CPRS), certain order checks are performed by Pharmacy during 
      this process. One of the order checks is the duplicate drug class order
      check. The software is currently looking for an exact match of the 5
      characters that make up the drug class. It should only look for a match of
      the first 4 characters. This patch corrects the problem.
      
    • 130 SEQ #121
      DATE APPLIED:   2003-03-29 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      1. When actions are not allowed to be taken on a specific order in
       
      2. When completing renewal orders entered through Computerized Patient
         Record System (CPRS), there is a possibility of getting an undefined
         variable PSOX("STATUS") error. This error occurs if the prescription 
         was originally entered through Outpatient Pharmacy, and the DEA,
         SPECIAL HDLG field (#3) of the DRUG file (#50) of the drug made it
         renewable, but not refillable. Then if that order is renewed through
         CPRS, the error can occur when Pharmacy finishes that order. This patch
         fixes this problem.
       
         Outpatient Pharmacy because that order is being acted upon by another
      3. Duplicate active prescriptions are being found in Outpatient Pharmacy,
         due to an order being renewed through CPRS at the same time a fill for
         that prescription is being transmitted to Consolidated Mail Outpatient
         Pharmacy (CMOP). A check is being added with this patch to not allow
         the renewal of an Outpatient order through CPRS if that order has a
         fill being loaded for transmission to the CMOP. The message that will
         show to the provider will be "Rx is loading into a CMOP transmission".
         user, a message is sometimes displayed that does not say who the other
         user is that has that order locked. This patch will change the message,
         wherever possible, to display the name of the user that has that order
         locked. All of the places where this message is displayed within the
         Outpatient Pharmacy package could not be fixed with this patch, because
         some of the routines were already in other patches. The changes will be
         made in those other places by those other patches.
      
    • 137 SEQ #122
      DATE APPLIED:   2003-04-17 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      1. One site has reported an excessive number of prescriptions getting
       
      This patch corrects the problem but will not do any back-billing.
      Information gathered from the results of this patch will be used by the
      VHA Central Office to determine whether back-billing will be done for
      these fills. A subsequent patch may be released to perform this
      back-billing.
       
        a. At release of a fill, if the Service Connected flag has a "Yes"
      answer, a call will be made to Integrated Billing to see if the Service
      Connected question even applies for this patient anymore. If not, the
      automatically (incorrectly) changed at release from Copay to No Copay
      answer will be set to null in Outpatient Pharmacy and an update
      transaction will be sent to CPRS to change their copy of the answer to
      null.
       
        b. A post-install job will loop through all released prescriptions
      starting from 02/04/2002 (the date that the $7 copay amount went into
      effect) and will tally the number of fills that could have been billed.
      The results of this patch will be maintained in a temporary location for
      a limited time in order to speed the processing of any eventual
      back-billing.
      with a reason of "Service Connected". It was determined that this is
       
       
      A MailMan message with a subject of "Subj: Patch PSO*7*137 Copay tally"
      will be sent to the patch installer and holders of the PSO COPAY key
      indicating the number of fills that have a potential for being
      back-billed.
       
      A second MailMan message will be sent to developers of the patch on FORUM
      with a subject of "Subj: 'institution' - COUNTS. This message will
      contain formatted tallies of fills eligible to be back-billed for 2002
      happening because the Service Connected question does not apply for the
      and 2003.
       
      The MailMan messages will not contain any patient information.
       
      2. A problem was encountered when a patient who had previously reached
      his annual copay cap had activity that brought his copay amount below the
      annual cap. When that happens, Integrated Billing (IB) will look for any
      previous fills that weren't billed because of the cap and will attempt to
      bill for those. The problem occurred when the previous unbilled fill had
      been returned to stock, Outpatient Pharmacy had an error in the process
      patient anymore, but the Computerized Patient Record System V. 1.0(CPRS)
      that should have sent a cancel for those "potential bills" (fills that
      would have been billed if the patient had not already reached his annual
      copay cap), so IB attempted to initiate a charge for those. On returned to
      stock refills, the refill level is removed from the prescription file, so
      filing the IB-initiated charge caused undefined errors.
       
      Solution:
      The canceling portion of the return to stock processing was corrected to
      handle "potential charges".
      passes the Service Connected question's answer from the renewed from or
      copied from prescription to Outpatient Pharmacy V. 7.0.
       
      Solution:
      
    • 120 SEQ #123
      DATE APPLIED:   2003-05-01 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      The purpose of this patch is to provide the ability to print Outpatient 
      Pharmacy V. 7.0 prescription labels on laser printers. The output will 
      include the Patient Medication Information sheets.
       
      The new functionality will only be available on printers properly defined 
      in the TERMINAL TYPE file (#3.2).
      
    • 18
      DATE APPLIED:   1999-04-16 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      1. This patch will attempt to make more POSSIBLE SIGS acceptable when
      3. This patch also fixes a problem of the Log of Suspended Rx's report not
      always showing the correct routing.
       
      finishing CPRS entered orders in Outpatient Pharmacy. It will cut down
      on the number of POSSIBLE SIGS that start "TAKE TAKE", and also cut down
      the number of times the Dose Form noun is repeated, "TABLETS TABLETS".
       
      2. This patch fixes the problem of the last refill being deleted when an
      Rx is canceled or expired, after that refill had been transmitted to the
      CMOP.
       
      
    • 123 SEQ #124
      DATE APPLIED:   2003-06-03 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
       
      they should have been.
       
      Solution:
      The post-install job for patch PSO*7*137 identified potential prescription
      fills that should have charged a copay. The starting date for examining
      whether the released fills should have been charged a copay was
      02/04/2002 (the date that the $7 copay amount went into effect). A
      post-install job for this patch will use the global created by patch
      PSO*7*137 to do the back-billing for the identified fills. If the global
      has been removed from the system, the identification portion will be done
      One site reported an excessive number of prescriptions getting
      again by the post-install of this patch before doing the back-billing.
       
      A MailMan message with a subject of "Subj: Outpatient Pharmacy Copay
      Clean-up" will be sent to the patch installer and holders of the PSO COPAY
      key indicating the number of fills that were successfully billed. If any
      fills were billed, the MailMan message will contain information on how to
      print a report by patient name of prescription fills that were billed.
       
      A second MailMan message will be sent back to FORUM to some outpatient
      pharmacy developers. This MailMan message's information will be compiled
      automatically (incorrectly) changed at release from Copay to No Copay
      with messages from other sites and forwarded to the Austin Automation
      Center for their use in addressing a mail-out to the veterans affected by
      the back-billing.
      with a reason of "Service Connected". It was determined that this was
      happening because the Service Connected question does not apply for the
      patient anymore, but the Computerized Patient Record System (CPRS) V. 3.0
      sends the Service Connected question's answer from the renewed from or
      copied from prescription. For non-service connected veterans, prescription
      fills that were flagged as Service Connected were not charged a copay when
      
    • 119 SEQ #125
      DATE APPLIED:   2003-06-28 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      1. This patch contains a post-install job, which will correct a status
       
         For deleted Outpatient Pharmacy V. 7.0 orders, the post-install 
         job will change CPRS V. 1.0 orders with an active status to a status of
         deleted and will also change the stop date in CPRS V. 1.0 to the date
         deleted if the CPRS V. 1.0 status is Discontinued by Provider.
       
      2. This patch also corrects the problem of an extra delimiter being
         stored in the PRESCRIPTION file (#52) if an up-arrow (^) was entered
         for the LOT# field (#24) when editing a prescription. A symptom of this
         problem is a null subscript error when trying to access the DIVISION
         mismatch between Outpatient Pharmacy V. 7.0 orders which have been
         field (#20) of the PRESCRIPTION file (#52).
       
         The post-install job will look for any entries with a null division and
         if the positions of the date fields appear to be shifted, it will
         remove the extra delimiter from the PRESCRIPTION file (#52).
       
          
         Upon completion of the post-install job a MailMan message will be sent
         to the patch installer with a subject of "Subj: Outpatient/CPRS Status
         clean-up". The message will indicate how many mismatched statuses were
         deleted and the corresponding orders in the Computerized Patient Record
         corrected and how many prescriptions with missing divisions were
         corrected.
       
          
       3. During the building of the Patient Profile through the Patient 
          Prescription Processing [PSO LM BACKDOOR] option, one of the 
          criteria for forcing the Status to SUSPENDED of prescriptions 
          that had an entry in the RX SUSPENSE file (#52.5) was at times
          found to be incorrect. If the entry in the RX SUSPENSE file
          (#52.5) was flagged as not printed, the software would force the
         System (CPRS) V. 1.0. The initial problem could have occurred if the
          prescription status to SUSPENDED. After this patch is installed,
          the software will also check if the prescription has already been
          transmitted to Consolidated Mail Outpatient Pharmacy (CMOP) V. 2.0
          system, and if so, the status will not be changed.
       
      4. When trying to edit a prescription, and the edit is not allowed 
         because either the order or patient is locked by another user, the 
         message indicating that the order or patient is locked will not always 
         contain the person's name that has the lock. This patch corrects the 
         problem.
         Outpatient Pharmacy V. 7.0 package mistakenly sent an "active" message
       
      5. When the user edited a prescription in such a way that caused a new
         prescription to be created, the new prescription was not being 
         displayed in the Bingo Board. This patch corrects the problem.
         The prescription number from the previous edit could be associated to
         the next patient's list of prescriptions to be listed on the Bingo
         Board.  This patch also corrects this problem.
         to CPRS V. 1.0 on an old order, making it active in CPRS V. 1.0 when it
         should be Discontinued, Expired, or Canceled. Patch PSO*7*86 updated
         the status in CPRS V. 1.0 for orders that were Canceled or
         Discontinued.
      
    • 138 SEQ #126
      DATE APPLIED:   2003-07-15 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      1. During testing of PSO*7*120, it was discovered that there was a 
      3. In preparation for future enhancements to language handling within 
      label print, a change was necessary to allow the bottle label information 
      to print in a different language from the one on the pharmacy fill 
      document. This patch makes this change.
       
      4. The final contract award for the laser label stock made a slight 
      modification to the location of the perforation about the fill document. 
      This patch makes the modification to the printer setup routine to 
      accomodate this change.
      problem with the entry of 'y' at the prompt "Print adhesive portion of 
      label only? ". The lowercase 'y' was being treated as a NO response. This 
      patch corrects this problem by handling either upper or lower case YES, 
      YE or Y as yes.
       
      2. A problem was found with the documentation of the Integration 
      Agreements in routine PSOLLU2. This patch corrects this problem.
       
      
    • 117 SEQ #127
      DATE APPLIED:   2003-07-15 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      1. This patch provides new functionality that allows the Veteran Affairs 
      2. This patch also addresses the following NOIS issues: 
       
      a) ISB-0702-32646 
       
      For drugs that have possible dosages, if the dosage is edited using Patient
      Prescription Processing [PSO LM BACKDOOR ORDERS] option, the software
      calculates the new DISPENSE UNITS PER DOSE field (#1) of the MEDICATION
      INSTRUCTIONS sub-file (#113) of the PRESCRIPTION file (#52), accordingly. At
      the confirmation prompt that follows immediately if you respond "NO",
      meaning not to accept the new value, the software does not revert the
      Medical Centers to print a patient's prescription bottle label in another 
      DISPENSE UNITS PER DOSE field (#1) back to it's original value. This patch
      fixes this issue.  
       
      b) CAH-0402-31866 
       
      When entering a new prescription using the Patient Prescription Processing
      [PSO LM BACKDOOR ORDERS] option, if that prescription is discontinued before
      it goes to the label queue prompt, currently, the label "LABEL QUEUE/CHANGE
      PRINTER/SUSPEND or '^' to bypass Q//" is prompted. If this is the only order
      in that session then there is no label to print and therefore the label queue
      language.  This functionality is accomplished by identifying which patients
      prompt should not be displayed. This patch fixes this problem.  
       
      c) ISH-0902-40182 
       
      Between the time an order was placed in Computerized Patient Record System
      (CPRS) V.1.0 and the time the order is processed in the backdoor pharmacy,
      if the dispense drug is made inactive, then there is a possibility of
      getting an undefined error if a "?" is entered when editing the dosage
      prompt . Since the drug is inactive the software does not gather the
      available dosages and as a result the undefined error. In order to process
      have another language preference. To identify patients as having another
      such an order (avoiding the undefined error), this patch will provide the
      user the option of making a free text dosage entry.  
       
      d) LIT-1102-71356 
       
      When a site merges two patients together, the PHARMACY PATIENT file (#55)
      contains all of the prescriptions from the "merged from" patient and the
      "merged to" patient under the internal entry number of the "merged to"
      patient. The old patient's internal entry number is kept in the PRESCRIPTION
      file (#52) for any prescriptions that were originally filed with that
      language preference use the Update Patient Record [PSO PAT] option and the
      number. If a new prescription is ordered for a drug that is already in the
      prescription profile, the order entry process will discontinue the old
      prescription correctly.  The problem is that if the discontinued order
      belongs to the old patient internal entry number, the new prescription order
      is filed with the old patient's internal entry number in the PHARMACY
      PATIENT file (#55) and the PRESCRIPTION file (#52) and doesn't appear on the
      prescription profile. This patch corrects this problem.  
       
      3. A more descriptive message will now be given to the user when an order is
      accessed, and that order is locked by another user, when copying a 
      Patient Record Update [PSO PATIENT RECORD UPDATE] protocol action and enter
      prescription, selecting a pending order, discontinuing a prescription, and
      processing a non-verified prescription.  
       
      4. If pre-POE prescriptions are renewed or edited to create a new prescription,
      the resulting prescription may have a missing SIG. This patch corrects the
      problem.  
      Yes in the new field OTHER LANGUAGE PREFERENCE field (#106) in the PHARMACY
      PATIENT file (#55).  
       
      
    • 126 SEQ #128
      DATE APPLIED:   2003-07-15 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      This patch is a partner patch with the Consolidated Mail Outpatient
       
      Solution: Several steps have been taken to reduce the time needed for
      transmissions.  A special index built with 'type' and 'division' has been
      added to CMOP INDICATOR field (#3) in the RX SUSPENSE file (#52.5) that
      optimizes the picking of prescriptions for each transmission.
       
      2. Problem:   In support of the Hawaii DoD project, Pharmacy Data 
      Management (PDM) needs to know when changes are made to entries in the 
      DRUG file (#50). To meet this need a call needs to be made to PDM V. 1.0 
      routine PSSHUIDG at line tag DRG whenever an edit is made to the DRUG 
      Pharmacy V. 2.0 (CMOP) patch PSX*2*41. PSO*7*126 must be installed before
      file (#50).
       
      Solution: The routine PSOCMOP has been modified to call the PDM routine 
      PSSHUIDG
      when an edit is made to the DRUG file (#50).
       
      Environmental Check:
      ====================
      An environmental check routine will run to check if the RX # (#.01) field
      in the RX SUSPSENSE file (#52.5) is populated before continuing with
      the CMOP patch at remote facilities. This patch will be adding new data 
      install.  If this field is missing, the following message will appear:
       
      Checking the RX Suspense file for missing .01 fields.
       
      667    (A list of entry numbers that are missing the #.01 field)
      ...
       
      The Suspense file #52.5 has been found to have entries without a .01
      field.
      Please call NVS to clear this problem.
      dictionaries to be used in conjunction with the CMOP patch PSX*2*41.
      <CR> - to continue:
       
      You will need to log a NOIS to National Vista Support (NVS) to have this
      problem resolved before the installation can continue.
       
      1. Problem: VISNs have been combining facilities and the running time of
      transmissions is becoming very long.  The number of divisions has grown
      to about fifty in the largest VISN.  This means 100 transmissions must be
      processed each day.
      
    • 142 SEQ #129
      DATE APPLIED:   2003-08-02 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
       
      the copay charge is held for 90 days before going out in the patient
      statement. If the patient had coverage on the release date, the copay
      bills and insurance bills should be reviewed to determine if the
      copayment charge is applicable because of possible insurance payment.
       
      If the copay charge should be credited, it can be removed by using the
      Reset Copay Status/Cancel Charges [PSOCP RESET COPAY STATUS] option.
       
      The temporary global ^XTMP("PSOCPIB3" from the patch PSO*7*123 install is
      kept for 90 days, so this report must be run within that time frame. To
      This patch provides a report listing all back-billed patients from patch
      run the report, enter D ^PSOCPIB5 from the programmer's prompt. It prints
      in 80-column format and can be queued to print.
      PSO*7*123. For each back-billed copay fill it indicates whether the
      patient had prescription insurance coverage as of the release date and/or
      billed date for the fill. If the copay charge has been cancelled since
      patch PSO*7*123 was installed, that information appears instead of the
      insurance information.
       
      If the patient had prescription insurance coverage on the billed date,
      
    • 131 SEQ #130
      DATE APPLIED:   2003-08-02 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      Pharmacy Benefits Management (PBM) Strategic Healthcare Group in 
      Kernel V. 8.0
      Computerized Patient Record System (CPRS) V. 1.0
      Pharmacy Data Management (PDM) V. 1.0
      Outpatient Pharmacy (OP) V. 7.0
      Controlled Substances (CS) V. 3.0
       
      This is the PSO patch that provides the following new functionality.
       
      1. This Outpatient Pharmacy patch contains the software changes to process
         digitally signed orders entered via the Computerized Patient Record
      collaboration with the Drug Enforcement Administration (DEA), requested
         System (CPRS) V. 1.0 for schedule II controlled substances. This patch
         lays the foundation for the future implementation of the Public Key
         Infrastructure (PKI) once the Drug Enforcement Administration's (DEA)
         regulations are revised and published, and will not be fully functional
         in this patch.
       
      2. This patch will ensure that no refills will be allowed for any
         Outpatient Pharmacy prescription for a drug that contains an "F" in the
         DEA SPECIAL HDLG field (#3) of the DRUG file (#50). This NON REFILLABLE
         ("F") code was introduced by the Pharmacy Data Management (PDM) V. 1.0
      the development of the first Public Key Infrastructure (PKI) VistA pilot
         patch PSS*1*61.
      project, named Electronic Prescription Order Entry for Schedule II
      Controlled Substances. The objective is to develop an electronic order
      entry system for Schedule II controlled substances using digital
      signatures. To make this project viable, modifications to the following
      packages were identified:
      National Drug File (NDF) V. 4.0
      
    • 145
      DATE APPLIED:   2003-09-12 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      This is the Phase I patch of the Transitional Pharmacy Benefit Project
      1) The patient must be a veteran.
      (3) Documentation can also be retrieved from VISTA Documentation Library
      (VDL) on the Internet at the following address,
      http://www.domain.ext/vdl.
       
      2) The veteran must be enrolled for VA health care system before
         July 25, 2003.
       
      3) Before July 25,2003, the veteran must have requested their first 
         primary care appointment with the VA.
       
      4) The veteran must have no active prescriptions dispensed by the local 
         VHA pharmacy, excluding Supply and Investigational items, for the past 
      (TPB). This project provides functionality for the "Medication Prescribed 
         485 days from October 22, 2003.
       
      5) The veteran must be waiting more than 30 days for their first 
         appointment with a Primary Care Physician on or after October 22, 
         2003, or the veteran is deemed eligible via an Electronic Wait
         List/Scheduling extract run at each local site.
       
       
       
      This patch is being sent out as a combined build, along with patch 
      by Non-VA Physicians" to accommodate the Veterans Health Administration 
      SD*5.3*300.
                  
       
      Outpatient Pharmacy will provide the following functionality in this 
      patch:
       
      1. A Post-Install routine will scan through the PATIENT file (#2)
      and the SD WAIT LIST file (#409.3), and will populate the new Outpatient
      Pharmacy TPB ELIGIBILITY file (#52.91) with patients eligible for the
      Transitional Pharmacy Benefit. Patients will either be entered into the
      (VHA) Directive 2003-047 that allows Department of Veterans Affairs (VA) 
      file as eligible, or ineligible. If they are entered into the file as
      ineligible, an exclusion reason will also be entered into the file. Please
      refer to the documentation for more details.
        
      The average run time of the Post-Install at the test sites was 1 hour.
       
       
      2. The following new options are provided in this patch:
         a. A new report option, TPB Patient Report [PSO TPB PATIENT REPORT], 
            will be provided to display the patients in the TPB ELIGIBILITY file
      to furnish medications from non-VA physicians. It mandates that for
            (#52.91). Various sort criteria are provided.
         b. The Transitional Pharmacy Benefit Patient Enter/Edit [PSO TPB  
            PATIENT ENTER/EDIT] option will allow sites to add new patients, and
            edit existing patients. Note: This option will be set initially to
            "Out of Order", until the post-install runs to completion.
         c. The TPB Institution Letter Enter/Edit [PSO TPB INSTITUTION LETTERS]
            option allows the user to edit each TPB institution's information
            elements that are to be printed on the letters to be sent to the
            patients.
         d. The Report TPB Patients Letters Printed/NOT Printed [PSO TPB LETTERS
      eligible veterans that meet certain criteria, VHA will fill prescriptions
            PRINTED REPORT] option provides the user the ability to generate a
            report of patients' letters printed or not printed.
         e. The Print TPB Patient Letter(s) [PSO TPB PRINT LETTERS] option
            provides the ability to print TPB letters to be sent to patients.
                              
       
      KIDS Build and Documentation Retrieval:
      ======================================================
       
      The KIDS Build and VISTA documentation are available on the 
      written by non-VA physicians and dentists. To determine eligibility, a
      ANONYMOUS.SOFTWARE directory at one of the following Office of Information
      (OI) Field Offices.
       
       
      Sites may retrieve documentation in one of the following ways:
       
      (1) The preferred method is to FTP the files from
          download.vista.domain.ext, which will transmit the files from the 
          first available FTP server.
        
      patient must meet the following criteria:
      (2) Sites may also elect to retrieve documentation directly from a
          specific server as follows:
       
          Albany          ftp.fo-albany.domain.ext
          Hines           ftp.fo-hines.domain.ext
          Salt Lake City  ftp.fo-slc.domain.ext
       
       
      The software distribution includes: 
       
       
          FILE NAMES                    DESCRIPTION
       
          PSO_TPB_ELIGIBILITY_1_0.KID   KIDS Build         
          PSO_7_P145_IG.PDF             Installation Guide
          PSO_7_UM_R0803.PDF            User Manual
          PSO_7_P145_UM_CP.PDF          User Manual Change Page Document
          PSO_7_TM_R0803.PDF            Technical Manual
          PSO_7_P145_TM_CP.PDF          Technical Manual Change Page Document
          PSO_7_P145_RN.PDF             Release Notes
       
      
    • 144 SEQ #132
      DATE APPLIED:   2003-09-12 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      This patch contains enhancements in support of drug-drug interaction
      order check exclusions. In addition, the National Drug File patch PSN*4*70
      is required to support this function. When both patches are installed,
      drug-drug interactions will be excluded for specifically identified drugs.
      The list of drugs and VA products flagged for exclusion can be found using
      the options Local Drugs Excluded from Drug-Drug Interactions and VA Products
      Excluded from Drug-Drug Interactions contained on the National Drug File
      Reports menu within the National Drug File.
      
    • 146 SEQ #133
      DATE APPLIED:   2003-09-24 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      This is the Outpatient Pharmacy patch, (Phase II), for the Transitional
      domain is needed for the Health Level Seven (HL7).
      in the NEW PERSON file (#200) must be set to 'No'. Any prescription
      entered, verified, or completed through this option will be flagged as a
      TPB RX.
       
       
      8. When patients or prescriptions  are selected or presented in the 
      following options, and the patient is eligible for the TPB benefit, a 
      warning will be given that this patient is eligible for the Transitional 
      Pharmacy Benefit. This warning is given because any new order created 
      through these options for a patient eligible for the TPB benefit will not 
      extracts of the TPB Patient information.
      be flagged as a TPB prescription, since the new option, PSO TPB RX ENTRY
      [TPB Rx (Prescription) Entry] was not used:
       
      Patient Prescription Processing [PSO LM BACKDOOR ORDERS]
      Complete Orders from OERR [PSO LMOE FINISH]
      Edit Prescriptions [PSO RXEDIT]
      Barcode Batch Prescription Entry [PSO BATCH BARCODE]
       
       
      9. Anytime a prescription is discontinued, a check will be done on that 
       
      prescription and patient. If the prescription is a TPB prescription, and 
      the patient is still eligible for the Transitional Pharmacy Benefit, and
      that patient has no more active TPB prescriptions, then the INACTIVATION
      OF BENEFIT DATE field (#2) of the TPB ELIGIBILITY file (#52.91) will
      automatically be set to the current date, making that patient ineligible
      for the benefit. Also, the INACTIVATION REASON CODE field (#3) of the TPB
      ELIGIBILITY file (#52.91) will automatically be set to 'ALL RX'S 
      INACTIVE'.
       
       
       
      10. Anytime a patient is inactivated in the TPB ELIGIBILITY file 
      (#52.91), a check will be done on the default Rx Patient Status for that 
      patient on the PATIENT STATUS field (#3) of the PHARMACY PATIENT file 
      (#55), and if that Rx Patient Status is 'NON-VA', it will be set to null.
       
       
      11. When entering new prescriptions through either the Patient 
      Prescription Processing [PSO LM BACKDOOR ORDERS] or the Complete Orders 
      from OERR [PSO LMOE FINISH], the Rx Patient Status of 'NON-VA' will not 
      be selectable, since these orders cannot be flagged as TPB prescriptions.
      2. A Post-Install routine is included that will scan the TPB ELIGIBILITY
      file (#52.91) and check each patient to see if that patient is flagged
      with a DATE OF DEATH entry in the PATIENT file (#2). If that patient has a
      DATE OF DEATH entry, and the patient is still active in the TPB
      ELIGIBILITY file (#52.91), that patient will be marked inactive in the TPB
      ELIGIBILITY file (#52.91).
      Pharmacy Benefit Project (TPB).
       
       
      3. A new 'NVA' code has been added to the SC/A&A/OTHER/INPATIENT field
      (#6) of the RX PATIENT STATUS file (#53), to distinguish prescriptions 
      entered as part of the TPB project. The field will now be named
      SC/A&A/OTHER/INPATIENT/NVA. The 'NVA' code will automatically be assigned 
      to the 'NON-VA' Rx Patient Status entry that is being exported with this 
      patch.
       
       
       
      4. A new field named TPB RX, field (#201), has been added to the 
      PRESCRIPTION file (#52). The software will automatically set this field 
      to 'Yes' for any prescription that meets all of the TPB requirements.
       
       
      5. The following fields were added to the NEW PERSON file (#200) by Kernel
      patch XU*8.0*311:
       
      53.91     NON-VA PRESCRIBER
      53.92     TAX ID
      1. An Environment check routine is included in the patch, and the install 
      53.93     EXCLUSIONARY CHECK PERFORMED
      53.94     DATE EXCLUSIONARY LIST CHECKED
      53.95     ON EXCLUSIONARY LIST
      53.96     EXCLUSIONARY CHECKED BY
       
      The following Outpatient Pharmacy options have been modified to allow the 
      editing of these new fields in the NEW PERSON file (#200):
       
      Add New Providers [PSO PROVIDER ADD]
      Edit Provider [PROVIDER EDIT]
      will be aborted if either of the following 2 conditions are met. If you
      View Provider [PSO PROVIDER INQUIRE] 
         
       
      6. The following fields have been added to the PHARMACY SYSTEM file 
      (#59.7). These fields will be used by the HL7 extracts of TPB Patient 
      information:
       
      46.1    TRANSMISSION START DATE
      46.2    TRANSMISSION END DATE
      46.3    BATCH CONTROL ID
      already have an entry named 'NON-VA' in the RX PATIENT STATUS file (#53),
      46.4    NUMBER OF MSH COUNT
      46.5    NUMBER OF LINES COUNT
       
      The HL7 extract will automatically be done on all patients upon initial 
      patch install, then the job will be automatically queued to run every 
      evening at 6:00pm, and the extract will check the day of the week, and 
      only send data on Sundays. In addition to the fields listed above, the 
      patch also exports the following to enable the HL7 extracts:
       
      OPTION:
      the install will be aborted, because this patch exports an entry with that
         PSO AUTOQUEUE JOBS 
         PSO TPB HL7 EXTRACT
       
      PROTOCOL:
         PSO TPB EV 
         PSO TPB SUB
       
      HL7 APPLICATION PARAMETER:
         PSO TPB-AAC   
         PSO TPB-PHARM
      same name. If you have not created an entry in the DOMAIN file (#4.2) 
       
      HL LOGICAL LINK:
         PSOTPBAAC   
       
       
      The TPB HL7 Data Extract/Transmission [PSO TPB HL7 EXTRACT] option has 
      been added to the jobs that can be requeued from the Queue Background 
      Jobs [PSO AUTOQUEUE JOBS] option.
                                        
       
      named "TPB-AUSTIN.DOMAIN.EXT", the install will be aborted, because that
      7. A new stand-alone option, PSO TPB RX ENTRY [TPB Rx (Prescription)
      Entry], is being exported with this patch. This option will provide the
      capability to enter TPB prescriptions for TPB eligible patients. Included
      in this option will be the ability to enter/edit Provider Information, 
      and the ability to enter/edit Allergy information. Only patients eligible
      for the TPB benefit will be selectable through this option. When entering
      the prescription information, the RX Patient Status must be 'NON-VA', and
      the Provider that is selected for the prescription must meet the following
      2 criteria: the NON-VA PRESCRIBER field (#53.91) in the NEW PERSON file
      (#200) must be set to 'Yes', and the ON EXCLUSIONARY LIST field (#53.95)
      
    • 19
      DATE APPLIED:   1999-04-16 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      This patch is being issued to bring the critical documents into compliance
      with the Year 2000 mandate.  Some of the key documents are Rx labels and
      action profiles.
      
    • 136 SEQ #134
      DATE APPLIED:   2003-10-02 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
       Problem: 
         The Patient Merge patch XT*7.3*73 fixed this problem to appropriately
         update the PATIENT field (#2) in the PRESCRIPTION file (#52) for
         future patient merges. Patch PSO*7*136 has a environment check routine
         PSOPI136 to update this field with the correct patient's internal
         entry number ("merged to").  At the completion of this job, a MailMan
         message with the subject "PSO*7*136 PRESCRIPTION file (#52) - Patient
         Merge clean up", will be sent to the installer notifying the start
         time and time of completion.  The message will provide a list of
         prescriptions with the corrected patient's internal entry number.
         It will also list prescriptions that had the CPRS status adjusted to
       ========
         match the Pharmacy status.
       
         The Patient Merge process was not updating entries in the PRESCRIPTION 
         file (#52) with the new patient's internal entry number (IEN).
       
       Solution:
       =========
       
      
    • 139 SEQ #135
      DATE APPLIED:   2003-10-02 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
       
         exist.
       
             NTE|3|
              :
       
      7. WIM-0603-20338
         The Print from Suspense File [PSO PNDLBL] option allows an user
         to queue the printing of the labels at a later time by Taskman. A
         problem was found when the original task was re-queued through the
         Taskman Requeue Tasks [XUTM REQ] option by a different user. Once
         the labels printed, the label print activity log for the prescription
       
         was recorded as being performed by the second user, the one who
         re-queued the Taskman task, which is wrong. This patch makes the
         correction to keep the user who queued the label print through the
         Print from Suspense File [PSO PNDLBL] option in the label print
         activity log.
       
      8. MAC-0603-60315
         Patch PSO*7*124 introduced the following change:
       
               Currently, if a non-controlled substance prescription is entered
       
               with a day supply less than 5 days and there are no refills, the
               expiration date defaults to 5 days from the issue date. If a
               controlled substance prescription is entered with a day supply
               less than 5 days without refills, the expiration date is the
               Issue Date plus the Days Supply. The primary problem is that
               when these prescriptions were being transmitted to the CMOPs and
               they were behind on dispensing, the prescriptions were being
               rejected because the prescriptions had already expired. The
               default of 5 is being changed to 30 to accommodate the CMOPs and
               to allow the patients to receive their medications in a timely
      2. CLA-0303-20198
               manner. Prescriptions will no longer expire before 30 days
               elapses from the Issue Date when the day supply is less than 30
               days and there are no refills.  If a minimum of 1 refill is
               entered the one year/six month rule still applies.
       
         This created a problem for some sites with a rehab unit where some
         patients go out on Authorized Absence every weekend. The site then
         enters a prescription with a patient status of AUTHORIZED ABSENCE and
         no refills and a small number for days supply (3 or 4 days). Before,
         such prescriptions expired within 5 days from the issue date and no
         The Manual Auto Expire Rxs [PSO MANUAL AUTO EXPIRE] option was
         longer showed on the Medication Profile screen. Now, after PSO*7*124
         was installed, such prescriptions remain active for at least 30 days.
         The result is that multiple prescriptions for a single drug are listed
         in the Medication Profile screen. Active prescriptions with a patient
         status of AUTHORIZED ABSENCE can contain the same drug already in
         another active prescription for the same patient.
         Once this patch is installed, prescriptions with a patient status of
         AUTHORIZED ABSENCE and no refills will have the expiration date
         calculation reversed to a minimum of 5 days from the issue date,
         instead of the 30 days introduced by patch PSO*7*124.
         initially provided to synchronize the expired order status between
       
      9. PUG-0603-50491
         This NOIS call reported a problem with the patient security check for
         the Complete Orders from OERR [PSO LMOE FINISH] option. An example of
         a patient security check is when an employee tries to get access to
         his own medical record and is denied. In the case of the menu option
         mentioned above, such security checks were not being performed when
         the user selected to process ALL the patients with pending orders.
         Also, when processing by clinic, route or priority, there were no
         security checks performed. The only time the security checks were
         Outpatient Pharmacy prescriptions and Computerized Patient Record
         performed was when the user selected to process a single patient.
         When this patch is installed, this problem will be resolved and the
         Complete Orders from OERR [PSO LMOE FINISH] option will perform the
         security checks consistently for all the possible selections when
         finishing pending orders.
       
      10. CON-0703-11685, MAR-0703-21567 & SBY-0703-31538
          When trying to reinstate discontinued prescriptions for a patient that
          had the DATE OF DEATH field (#.351) in the PATIENT file (#2) entered
          and then deleted, the user was getting an "Undefined variable DA"
         System (CPRS) V. 1.0 order entries. And as such, the start date was set
          error. This problem was introduced by patch PSO*7*117, more
          specifically by the changes described in item #2b which was made to
          address NOIS call CAH-0402-31866. This patch corrects the problem
          with the use of that variable.
       
      11. MIN-1202-40079, FRE-0303-60233 & RIC-0603-21344
          In some situations where a patient is being accessed by Inpatient
          Pharmacy Version 5.0, if an attempt is made to finish orders in
          Outpatient Pharmacy Version 7.0, a message is received that the
          patient is in use. Then if an "^" is entered for the PATIENT STATUS
         to the date Outpatient Pharmacy Version 7.0 was installed minus 120
          prompt, the cross-reference entries in the PHARMACY PATIENT file (#55)
          could be deleted for that patient. This patch corrects the problem.  A
          follow-up patch will provide a clean up to rebuild missing
          cross-references.
       
      12. HUN-0603-21419 & WPB-0803-30273
          There has been some instances where a prescription from one patient
          was being displayed on the Bingo Board for a different patient. This
          patch kills a variable that could accidentally get carried over    
          between patients.
         days. A few sites have reported that some of the very old
      1. BIR-0203-30502
         prescriptions, specifically those that are 120 days prior to the date
         Outpatient Pharmacy Version 7.0 was installed, show an active status
         when viewed via FileMan. In order to scan the PRESCRIPTION file (#52)
         and flag such orders as expired, this option has been modified to
         provide the user the flexibility to select a start date and the default
         is set to the date Outpatient Pharmacy Version 7.0 was installed minus
         120 days.
       
      3. CLE-0303-42391
         This NOIS call reported that the PROVIDER COMMENTS field (#39) of the
         This NOIS call reported the following software error that happened
         PRESCRIPTION file (#52) was being lost when a prescription was renewed
         from Outpatient Pharmacy. A correction was made to send the comments to
         CPRS when the prescription is renewed from Outpatient Pharmacy.
       
      4. ISB-0403-31630
         This NOIS call reported a problem in the display of Allergy severity
         in the Patient Prescription Processing [PSO LM BACKDOOR ORDERS]
         option, on the Detailed Allergy Display screen. The content of the
         field "Severity:" was limited to one, and only one, value. The possible
         values were: MILD, MODERATE or SEVERE. The first Severity on file was
         with a FastFill machine:
         displayed. Since it is possible to have more than one Severity per
         Allergy, this display was changed to show all the Severities on file,
         along with the dates on which each one was observed. See example below:
       
              Before:     Severity: MODERATE
       
              Now:        Severity: 04/07/03 MODERATE
                                    04/15/03 MILD
                                    04/17/03 SEVERE
       
       
         Besides the changes to this display, the HL7 message for External
         Interfaces was also changed. The ZAL segment will have one for each
         severity observed. Before, it would have only one entry for the
         oldest severity observed. Furthermore, the date the severity was
         observed is being added as field #8 of this segment. From the same
         example from above, here is how the ZAL segment will look:
       
           Before:
            ZAL|530|NIACIN 100MG TAB |ALLERGY|DRUG|VERIFIED|MODERATE
       
         $ZE= ACK+2^PSOHLSG:1, %DSM-E-UNDEF, undefined variable HL("APAT"),
           Now:
            ZAL|530|NIACIN 100MG TAB |ALLERGY|DRUG|VERIFIED|MODERATE|20030407|
            ZAL|530|NIACIN 100MG TAB |ALLERGY|DRUG|VERIFIED|MILD|20030415|
            ZAL|530|NIACIN 100MG TAB |ALLERGY|DRUG|VERIFIED|SEVERE|20030417|
       
      5. ANN-0902-40951
         An undefined error was reported when using the Patient Prescription
         Processing [PSO LM BACKDOOR ORDERS] option. If the drug of an active
         order is edited, but the user quits without saving the changes and a
         new order for the same drug is placed immediately afterwards, the error
              -DSM-I-ECODE, MUMPS error code: M6
         could occur. This patch fixes this issue.
       
      6. LAS-0503-60830 & BRX-0603-11755
         The "NTE|2|" segment in the HL7 message generated for external
         interfaces is composed by the concatenation of the following Freetext
         fields from the OUTPATIENT SITE file (#59) in this order:
       
             Field #   Name
             ------------------------------------------
             1005      NARRATIVE FOR REFILLABLE RX
       
             1006      NARRATIVE FOR NON-REFILLABLE RX
             1004      NARRATIVE FOR COPAY DOCUMENT
       
         When building this segment, the routine PSOHLSG2 was skipping one line
         between the content of each field. This line is being interpreted by
         some external interfaces, such as Optifill, as the end of the "NTE|2|"
         segment, because all it contains is a carriage return character. This
         caused the external interface to reject messages with only a carriage
         return in the line. To solve this problem a blank space will be
         inserted between the content of each field. In the example below, the
         The routine was corrected to reinitialize the variable if it does not
         blank space will be added where the arrow ("->") is pointing.
       
              :
             NTE|2|
             Call in your refill on your touch-tone phone.
             Outside the metropolitan area: 1-800-123-4567.
           ->
             The copay required is $7.00 for every 30 day or less supply of
             medication or $21.00 for a 90-day supply. Be sure to indicate your
             complete SSN on your check.
      
    • 125 SEQ #136
      DATE APPLIED:   2003-10-23 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      1. If pre-Pharmacy Ordering Enhancements prescriptions are renewed or
      edited to create a new prescription, the resulting prescription may have a
      missing SIG. This patch corrects the problem for edited prescriptions.
      Other Pharmacy V. 7.0 patches have made the correction for renewals.
       
      2. This patch also corrects a null subscript error that happens if the
      full patient name is entered in the Bingo Board User [PSO BINGO USER]
      option.
      NOIS - SBY-0803-31924
      
    • 141 SEQ #137
      DATE APPLIED:   2003-11-07 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      1. A site reported a problem with printing labels with long SIGs. If 
      contained SIG instructions that ran over one label. On the 2-n copies, 
      not all of the SIG printed correctly. This patch corrects this problem by 
      appropriately printing all of the SIG information on all copies.
      NOIS: MON-0703-50217, MAD-0603-41794, SPO-0603-50792, MAC-0803-60872
       
      3. A site reported a problem that long mailing addresses were being 
      truncated on the mailing label. This patch corrects this problem by 
      adjusting the font size lower until the entire address will print. 
      NOIS: NIN-0803-40514
       
      there were no spaces in the SIG, the label print would get into an 
      4. A site reported a problem with a long drug name overflowing onto the 
      warning label section. This patch corrects this problem by adjusting the 
      font size down until the drug name fits on the bottle label. In addition, 
      a utility is included to build the information into the TERMINAL TYPE 
      file (#3.2) for bolding the drug name at different fonts. Once the patch
      is installed, run the routine PSOLLU3 in programmer mode. Once you have
      updated all current laser label devices, the routine may be deleted.
      NOIS: TOM-0503-41452 
       
      5. A site reported a problem with receiving an error if there was a TAB 
      infinite loop. This patch corrects this problem by making the SIG print 
      character in the SIG text. This patch corrects this problem by handling 
      the entry of non-visible characters. NOIS: BRX-0703-12341, 
      WPB-0703-32079, SBY-0703-30153
       
      6. A site reported a problem with the printing of the Method of Pickup 
      information. It was being truncated if it was over about 20 characters. 
      This patch corrects this problem by adjusting the font and allowing this 
      information to print on multiple lines. NOIS: ANN-0503-42213 
       
      7. A problem was discovered with printing the narrative information on 
      break on spaces and commas. If there are no spaces and no commas, the SIG 
      the label. Under certain conditions, the text would not wrap correctly. 
      This patch corrects this problem by wrapping on the character size if the 
      text between spaces is too long for the allocated area on the label.
       
      8. A site reported a problem with adjusting the left margin of the laser 
      label print. The 'Qty' header wouldn't properly adjust. This patch 
      corrects this problem by adding the ability to move the line that prints 
      quantity information. NOIS: IRO-0503-40327
       
      9. A site reported a problem of no physician name or an incorrect name 
      print will break on a character basis. 
      printing on the bottle label. This happened if the SIG was too long to 
      fit on the bottle label, but was not too long to fit on the filling 
      document. This patch corrects the problem. NOIS: SHR-0703-72297, 
      CLL-0803-41010
      NOIS: SAM-0703-21864, SAM-0703-21873, IND-0703-41198, FAV-0603-70287, 
      MUS-0603-70207, SBY-0503-32205, CTX-0803-71468
       
      2. A site reported a problem when printing multiple copies of labels that 
      
    • 135 SEQ #138
      DATE APPLIED:   2003-11-21 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
       
      ScripTalk(R) Talking Prescriptions will provide the ability for VA points
      of care to purchase and distribute adaptive equipment to patients who are
      unable to read the traditional label on prescription bottles. This patch 
      provides a way to print to a microchip-embedded label that can be applied 
      to a medication bottle. When the label is held next to a ScripTalk(R) 
      reader, the reader will read the contents of the label aloud to the 
      patient. This improves patient safety for patients with substantial loss 
      of vision as it allows them to safely determine the contents and 
      administration schedules of their medications.
       
      This patch contains routines, new options, new Data Dictionary fields, and
      ScripTalk(R) is a registered trademark of En-Vision America.
       
      In addition to the ScripTalk changes, this patch corrects some laser
      labels formatting problems in the warning label and method of pick-up
      sections. 
       
      NOTE: As part of the laser labels corrections, the utility routine that 
      was used in patch PSO*7*141 has been modified. A correction for the return
      mail initialization control code in the TERMINAL TYPE file (#3.2) has been
      added. Once the patch is installed, run the routine PSOLLU3 in programmer
      documentation for implementing the ScripTalk(R) 'talking' prescription
      mode. Once you have updated all current laser label devices, the routine
      may be deleted.
      labels functionality, which will greatly benefit visually impaired
      veterans.
       
      Thanks to Rob Silverman at Hines for his extensive research and
      development work for a class III solution, upon which this patch is based.
       
      
    • 153 SEQ #139
      DATE APPLIED:   2003-12-31 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      1. A new code has been added to the INACTIVATION REASON CODE field (#3)
      in an HL7 message to Austin. This patch exports a new mail group, PSO TPB
      HL7 EXTRACT. Members of this mail group will receive weekly mail messages
      concerning the HL7 extract of TPB patient information. These messages
      will either display information that the message generation was
      successful, or display information that the message generation was
      unsuccessful, along with a reason why it was unsuccessful. Upon install,
      the installer will be prompted for the coordinator of the mail group. The
      Post-Install routine of this patch will automatically add the patch
      installer as a member of the mail group.
       
      of the TPB ELIGIBILITY file (#52.91). The code is PATIENT UNREACHABLE.
      The Post-Install routine PSO153PS will also set the AUTOSTART field (#4.5)
      of the HL LOGICAL LINK file (#870) of the PSOTPBAAC HL Logical Link to
      "Enabled".
       
      A correction has been made to the HL7 message to distinguish between
      a new record and an edited record.
       
      3. The weekly HL7 transmission to Austin is found to cause problems at few
      sites due to some bad "AX" cross-references of the TPB ELIGIBILITY file
      (#52.91). This patch fixes this issue.
      This code will now be selectable when manually inactivating a patient
       
      4. There is a possibility of getting a null subscript error when using the
      View Provider [PSO PROVIDER INQUIRE] option to view the provider details
      after either of the following circumstances:
       
      a. When a new provider was added using the Add New Providers [PSO PROVIDER
         ADD] option, and "No" was the response to the NON-VA PRESCRIBER field
         (#53.91) of NEW PERSON file (#200).
      b. When a Provider was edited using the Edit Provider [PSO PROVIDER EDIT]
         option, and "No" was the response to the NON-VA PRESCRIBER field
      from the TPB ELIGIBILITY file (#52.91). It will also display, when
         (#53.91) of NEW PERSON file (#200), and then an "^" was entered prior
         to responding to the prompts for these fields of the NEW PERSON file
         (#200):
         TAX ID field (#53.92)
         EXCLUSIONARY CHECK PERFORMED field (#53.93)
         DATE EXCLUSIONARY LIST CHECKED field (#53.94)
         ON EXCLUSIONARY LIST field  (#53.95)
         EXCLUSIONARY CHECKED BY field (#53.96)
       
      This patch corrects the error.
      appropriate, on the reports generated by the Report TPB Patients Letters
       
      5. When selecting a provider using the TPB Rx (Prescription) Entry [PSO
      TPB RXENTRY] option, if the provider is unauthorized to write med orders
      or flagged as inactive, there are currently no alerts or warnings
      indicating that the provider cannot be selected. This patch will provide
      one of the following messages during provider selection if such conditions
      are encountered:
       
      a. This Provider is not Authorized to Write Med Orders. Use the Edit
         Provider [PSO PROVIDER EDIT] option to change the Authorization flag.
      Printed/NOT Printed [PSO TPB LETTERS PRINTED REPORT] option, and the TPB
       
      b. This Provider is flagged as Inactive. Use the Edit Provider
         [PSO PROVIDER EDIT] option to change the Inactive Date.
       
      c. This Provider is not Authorized to Write Med Orders and flagged as
         Inactive. Use the Edit Provider [PSO PROVIDER EDIT] option to change
         them.
       
      6. The FAX NUMBER field (#.136) of the NEW PERSON file (#200) has been
      added to the following options, for display and for editing:
      Patient Report [PSO TPB PATIENT REPORT] option.
      Add New Providers [PSO PROVIDER ADD] option
      Edit Provider [PSO PROVIDER EDIT] option
      View Provider [PSO PROVIDER INQUIRE] option
       
      This enhancement is requested by E3R 18457.
       
      7. This patch provides an API to the Scheduling V. 5.3 package that
      returns a list of all patients eligible for the TPB, to be used for
      reporting purposes.
       
      2. Every Sunday, Transitional Pharmacy Benefit (TPB) patient data is sent
      
    • 151 SEQ #140
      DATE APPLIED:   2003-12-31 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      1.  Currently, the HealtheVet system invokes the Outpatient Pharmacy
      enhancement.
       
      Furthermore, besides the information that Outpatient Pharmacy V. 7.0 
      currently returns to the HealtheVet system, it is also requested that two
      new fields be made available to them: Outpatient Pharmacy Division and
      Prescription Refill Status. This patch provides this information in the
      requested format.
       
      2. The HealtheVet team has requested an additional Outpatient Pharmacy
      V. 7.0 Application Program Interface (API) to provide Outpatient Pharmacy
      V. 7.0 application to order a prescription refill and to check the status
      division information. The information requested is Inactive Status,
      Division Name, Area Code, Phone Number, and Refill Narrative Text. This
      patch makes the required information available.
       
      Note: Sites installing this patch will not notice any changes unless they
      are using the HealtheVet Internet Prescription Refill system.
      of the prescription refill process. The required input parameters include
      Integration Control Number (ICN), Social Security Number (SSN), and
      Prescription number (Rx #). This has caused a duplication in functionality
      and slow response time. To help speed up the process, a minor enhancement
      has been requested that will eliminate the use of ICN and remove the cross
      checking of SSN because the HealtheVet system itself verifies the accuracy
      of the SSN and supplies the patient number. This patch would provide this
      
    • 158 SEQ #141
      DATE APPLIED:   2004-01-31 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      Since the release of patch PSO*7*146, Transitional Pharmacy Benefits 
      Pharmacy's AMIS Report option [PSO AMIS] and Daily AMIS Report option 
      [PSO DAILY AMIS] will be modified to display this field in a new NVA 
      column.
       
      If you install this patch and wish to include all past prescriptions with 
      a Patient Status of Non-VA for past dates, you must run the Recompile 
      AMIS Data option [PSO AMIS RECOMPILE].
       
      Keep in mind that if you ran the AMIS report in the past, the counts will 
      be different when you re-run the report for that past date, since the 
      (TPB), there has been an increase in the number of prescriptions which 
      compile will now include prescriptions with a pharmacy patient status of 
      Non-VA. Also note that the recompile is system intensive and should be 
      run after hours.
      have a pharmacy patient status of Non-VA. Pharmacy's current AMIS Report 
      option [PSO AMIS] and Daily AMIS Report option [PSO DAILY AMIS] do not 
      include Non-VA prescriptions in any of their counts. 
      This patch will modify the Compile AMIS Data (NIGHT JOB) option [PSO AMIS 
      COMPILE] and the Recompile AMIS Data option [PSO AMIS RECOMPILE] to 
      include the Non-VA prescription counts in a new NVA field (#17) in the 
      DIVISION multiple (#59.11) of the OUTPATIENT AMIS DATA file (#59.1). 
      
    • 160 SEQ #142
      DATE APPLIED:   2004-01-31 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      This is the Outpatient Pharmacy patch for the Transitional Pharmacy Benefit
            wrong Outpatient Pharmacy prescription processing options, such as
                     provider the patient was not prescribed any medication, his/her
                     TPB eligibility remained active, when in reality it should have 
                     been inactivated.
        
            Solution: A Post-Install process will search for TPB eligible patients 
                      and automatically inactivate the TPB eligibility of the 
                      patients that fulfill both of the following
                      requisites:
                         
                        a) Patient does not have any "active" TPB prescription(s) on
            the Patient Prescription Processing [PSO LM BACKDOOR] option and Complete
                           file. The prescription statuses considered as "active"
                           are the following:
                           ACTIVE, NON-VERIFIED, HOLD, DRUG INTERACTIONS, SUSPENDED
                           and PROVIDER HOLD.  
          
                                                AND
          
                        b) Patient has had an appointment at a designated TPB Clinic
                           (determined through a set of clinic stop codes) since the
                           date his/her TPB benefit began.
            Orders from OERR [PSO LMOE FINISH] option.
           
            Report: At the end of this process, a Mailman message will be sent to
                    the new mail group PSO TPB GROUP. The patients reported on this 
                    message were inactivated as TPB patients by the Post-Install
                    process The fields reported on this message are: PATIENT NAME,
                    LAST 4 DIGITS OF SSN, APPOINTMENT DATE/TIME, VA CLINIC NAME.
         
         3) PATIENT'S TPB BENEFIT INACTIVATION (ENHANCEMENT - CONTINUOUS PROCESS)
            ---------------------------------------------------------------------
            Outpatient Pharmacy software will be notified by the Scheduling software
        
            every time a patient has an appointment at a VA clinic. If the patient
            is eligible for the TPB benefit, the appointment was at a designated TPB 
            Clinic (determined through a set of clinic stop codes) AND the patient
            does not have any "active" (see list of statuses on item #2a above) TPB 
            prescription(s) on file, this patient will have the TPB eligibility 
            automatically inactivated. A Mailman message will be sent to the PSO TPB
            GROUP mail group with the following information:
             
                The following patient had the TPB (Transitional Pharmacy Benefit)
                Benefit automatically inactivated because the following appointment
         b) Patients who did not wish to take advantage of the TPB benefit or who are
                was found: 
         
                           Patient         : LAST,FIRST(9999)
                           VA Clinic       : EAST MIDWAY CLINIC
                           Appointment Date: DEC 02, 2003@11:15
        
         4) REPORT OF PATIENTS WITH TPB AND NON-TPB Rx's (NEW REPORT)
            [PSO TPB PATIENT RX REPORT]
            ---------------------------------------------------------
            This new report is being released as a stand-alone option. It will 
            not prescribed medication after a VA appointment are still active for
            print a list of TPB eligible patients that have "active" TPB and
            Non-TPB prescriptions on file. The report can be for ALL or selected 
            institutions, as well as for ALL or selected TPB patients. It will be
            sorted by the INSTITUTION NAME first, then by the PATIENT NAME. There
            will be a page-break for each individual institution. The column
            headings on the report are: PATIENT NAME (LAST4SSN), VA Rx#, TPB Rx#, 
            DRUG NAME. This report should be assigned to the site TPB Coordinator,
            Pharmacy ADPAC and any other individual deemed appropriate by the site.
            
      In order to allow the unflagging of TPB prescriptions as described in 1) 
            the TPB benefit in the system.  The inactivation of the TPB benefit is 
      above, the TPB RX (#201) field in the PRESCRIPTION (#52) file is being 
      changed from "UNEDITABLE" to "EDITABLE". 
            automatic when the last active TPB prescription is discontinued either 
            through an Outpatient Pharmacy package action or through an action taken
            in CPRS. The entry of a prescription/order will not inactivate the 
      (TPB) project. This phase consists of automated processes and additional
            benefit unless the result is that the last active TPB prescription is
            discontinued as a result of the new entry. 
         
      This patch is comprised of four components that will help the sites identify
      and fix the data discrepancies described above. It will also provide them 
      with new tools to monitor events that could have an impact on patient's TPB
      eligibility. And in some cases the patient's TPB eligibity will be updated
      automatically.
        
      Below is a detailed description of each component:
      tools designed to assist the sites for which Transitional Pharmacy Benefit
       
         1) MARKING TPB PATIENT Rx's AS TPB (ONE-TIME PROCESS - POST INSTALL)
            -----------------------------------------------------------------
            Problem: Because some prescriptions have been entered through the
                     wrong menu options (see item a) above), these Rx's have not 
                     been correctly identified as TPB prescriptions. In other 
                     words, they have a different patient status than "NON-VA" AND
                     do not contain a TPB flag in PRESCRIPTION file (#52), and 
                     therefore, are not identifiable as prescriptions filled
                     under the TPB program.
      data have not been accurately reported.
       
            Solution: A Post-Install process will search for prescriptions filled
                      under the TPB program which are not marked as such and
                      will mark these prescriptions as TPB. The two requisites 
                      that must be fulfilled for a prescription to be marked as 
                      TPB, are:
          
                        a) The prescription was entered during the period that
                           the patient's TPB benefit was active.
       
        
                                            AND
       
                        b) The provider for the prescription is a "NON-VA"
                           provider.
                         
                      If the requisites above are fulfilled, the following 
                      updates will be done for the prescription:
       
                        a) Patient status will be changed to "NON-VA".
                        b) If an UNIQUE TPB clinic is identified (STOP CODE
      Two of the most common events that have contributed to the discrepancies
                           equals 161) for the site, clinic will be changed to
                           this clinic.
                        c) The TPB flag will be set in PRESCRIPTION file (#52).
           
            Report: At the end of this process, a Mailman message will be sent
                    to the newly created mail group called PSO TPB GROUP. The 
                    patients reported on this message had at least one Prescription
                    edited by the Post-Install process. The sites will have the
                    ability to enter the coordinator of this new mail group at time
                    of installation of this patch. Even if the coordinator is not
      in the TPB data are:
                    entered, this patch assures that at least the installer of the
                    patch is a member of the mail group. The fields reported on this
                    Mailman message are: PATIENT NAME(LAST4SSN), Rx#, DRUG NAME, 
                    PROVIDER NAME, CLINIC (Old and New) and the Rx PATIENT STATUS
                    (Old and New).
         
            Important: If the site identifies prescriptions on this report that
                       have been wrongly flagged as TPB, it is possible to manually
                       remove the TPB flag from  such prescriptions through FileMan.
                       Just repeat the steps below for each prescription you wish
        
                       to remove the TPB flag (as in this example):
       
                       VA FileMan 22.0
          
                       Select OPTION: ENTER OR EDIT FILE ENTRIES  
          
                       INPUT TO WHAT FILE: PRESCRIPTION
                       EDIT WHICH FIELD: ALL// TPB RX  
                       THEN EDIT FIELD:
            
         a) TPB prescriptions have been entered for TPB eligible patients via the
                       Select PRESCRIPTION RX #: 123457690A  TYLENOL 250MG
                       TPB RX: YES// @
                          SURE YOU WANT TO DELETE? Y  (Yes)
          
        
         
         2) INACTIVATING PATIENT'S TPB BENEFIT (ONE-TIME PROCESS - POST INSTALL)
            --------------------------------------------------------------------
            Problem: Since not all patients eligible for the TPB program chose to
                     take advantage of the TPB benefit or, after seeing the VA 
      
    • 154 SEQ #143
      DATE APPLIED:   2004-03-30 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      SBY-1003-30858
          Outpatient Pharmacy Version 7.0, a message is received that the
          patient is in use. Then if an "^" is entered for the PATIENT STATUS
          prompt, the cross-reference entries in the PHARMACY PATIENT file (#55)
          could be deleted for that patient.
       
      This patch has a post install clean-up routine that will:
       
      1. Look for entries in the PHARMACY PATIENT file (#55) affected by the
         problem above and will rebuild the missing cross-references.
       
      Prescriptions are not seen in Patient Prescription Processing 
      2. Once the cross-reference is rebuilt for a specific patient, the post
         install will check if the patient has been merged and in case the
         patient's prescriptions still contain the old patient internal entry 
         number, it will correct them with the new patient number in the 
         PRESCRIPTION file (#52). The database problems caused by
         patient merges have been fixed by PSO*7*136, however, patient entries
         in the PHARMACY PATIENT file (#55) with the problem above, could have
         been missed by PSO*7*136 cleanup job. 
         This step of this cleanup will make sure these entries are fixed.
       
      [PSO LM BACKDOOR ORDERS] option and in Computerized Patient Record System 
      During Installation of this patch the user will be asked: "Queue the
      Post-Install to run at what Date@Time: ". If the prompt is not 
      answered, the patch WILL NOT be installed. After the post install
      routine is run to completion at the time the user indicated, a MailMan
      message with the subject "PHARMACY PATIENT File (#55) missing entries"
      containing the list of prescription cross-references rebuilt will be sent
      to the person installing the patch. The prescriptions will then appear in
      the Patient Prescription Processing [PSO LM BACKDOOR ORDERS] option and
      the CPRS Meds Tab if they are not past their expiration date.
      (CPRS) Meds Tab but are seen in View Prescriptions [PSO VIEW] option and 
      CPRS Orders Tab.
       
      PSO*7*139 corrected the following problem:
          In some situations where a patient is being accessed by Inpatient
          Medications Version 5.0, if an attempt is made to finish orders in
      
    • 15
      DATE APPLIED:   1999-04-16 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      1. When using the Patient Record Update [PSO PATIENT RECORD UPDATE]
       
      installed, that prescription will show on the unreleased report, even
      though a Filling label never printed.
       
      12. This patch fixes an error that involves incorrect medications showing
      up on a Medication profile for a patient. This can occur if there is
      invalid data in the PHARMACY PATIENT file (#55). A patient validation
      check is being added to prevent this problem. Also in the Medication
      profile, an error could occur if a profile is run on a patient, and the
      orders for that patient have not yet been backfilled to CPRS. This error
      can only occur shortly after the installation of Outpatient Pharmacy
      3. Corrected a problem reported in NOIS ALB-0498-50730 associated with
      version 7.0.
      the Medication Profile [PSO P] option.  The problem happens when the
      report is sorted to print by Class or Medication and a cutoff date (number
      of days) is entered, the Rxs that have been canceled print beyond the
      selected number of days.  Routine: PSOP2
       
      Corrected another problem reported in NOIS CON-0798-11780 when printing
      the Med profile by a selected date range.  The problem is that when a date
      range is entered the first time and the user attempts to run the report
      action, the site parameter that controls the editing of Patient
      again and chooses a date range earlier that the initial date, the user is
      not allowed to do so.  Routine: PSOP1
       
      4. Corrected a problem where a possible undefined error could occur when
      the cross reference on the DATE OF DEATH field (#.351) on the PATIENT file
      (#2) is executed.  The problem could occur when the APOSD cross reference
      is executed. Routine: PSOCAN3
       
      5. Added a 'Press Return to Continue' prompt when using the Speed Release
      action.  The problem was when there were many Rx's to be released, the Rx
      Information Management System (PIMS) patient data was being ignored.
      number scrolled off the screen.  For users without scroll back
      capabilities, this caused users to question as to what Rx's were being
      released. Routine: PSODISP3
       
      6.When editing the original Fill Date of a prescription that is in
      suspense and queued for Consolidated Mail Outpatient Pharmacy (CMOP)
      transmission, it is possible that duplicate "AQ" cross references will
      exist for that suspense entry. This could cause the prescription to be
      sent to the CMOP twice. In addition to fixing this problem, any invalid
      "AQ" cross references will be deleted by this patch. Routines: PSOUTLA,
      Routine: PSOLMPAT
      PSOPOST3
       
      7.This patch addresses a problem reported by some sites concerning the
      Complete Orders from OERR [PSO LMOE FINISH] option. Currently under this
      option, the site will only see Pending Outpatient orders that have a
      Related Institution that matches the Related Institution for the
      Outpatient Site that the user is signed in under. The problem occurs when
      an order is received from Computerized Patient Record System (CPRS) from a
      Clinic that is related to an Institution that is not found as a Related
      Institution for any of the Outpatient Pharmacy sites. When this happens,
       
      the only way for those orders to be completed is for the user to select
      that patient under the Patient Prescription Processing [PSO LM BACKDOOR
      ORDERS] option.
       
      To fix this problem, this patch adds a new field to the OUTPATIENT SITE
      file (#59) called CPRS ORDERING INSTITUTION (#8). Multiple entries can be
      entered in this field. This can be done using the Site Parameter
      Enter/Edit [PSO SITE PARAMETERS] option. Upon installation of this patch,
      a conversion is done to move the Institution that is currently in the
      Related Institution field for each Outpatient Site to the first entry in
      2. This patch will enable the interface between Outpatient Pharmacy
      this new field. After the installation of the patch, if there is still
      only one entry in the new CPRS ORDERING INSTITUTION field (#8) for an
      Outpatient Site, then the Complete Orders from OERR [PSO LMOE FINISH]
      option will not change for the user. However, sites can now enter multiple
      Institutions in this field for an Outpatient Pharmacy site, and if a site
      does this, the user will be prompted for an Institution when entering the
      Complete Orders from OERR [PSO LMOE FINISH] option. After the user selects
      an Institution, then the Pending Orders that will be shown to the user for
      completing will be those Pending Orders from Clinics that are associated
      with that Institution selected.
      version 7.0 and the Clinical Information Resource Network (CIRN) once CIRN
       
      8. A problem has been reported concerning the Order Summary that is
      displayed after selecting the RX (Prescriptions) [PSO RX] option. The
      first number displayed is the "Orders to be completed for all divisions".
      Then the user can choose to view an order summary, which breaks down all
      of the orders by Routing, (Window, Mail, and Clinic). The problem is that
      the total of the "Orders to be completed for all divisions" does not
      always match the total of the breakdown by routing. The reason is that not
      all Renewals that are received from CPRS have an associated routing. To
      resolve this, when Outpatient Pharmacy receives a Renewal from CPRS with
      is installed. There will be no change in functionality for Outpatient
      no routing, a Mail routing will automatically be entered for the Renewal.
      This patch will also automatically update any current Pending Renewals
      with no routing to a Mail routing.
       
      9. This patch fixes a problem of the patient not always being displayed
      on the Bingo Board automatically when using the Release Medication
      [PSO RELEASE] option.
       
      10. This patch provides a new sort capability when using the Complete
      Orders from OERR [PSO LMOE FINISH] option. Orders can now be Finished by
      Pharmacy sites that do not have CIRN installed.
      Clinic, or by Clinic Sort Group. Within either of these sorts, orders will
      be Finished on a first in/first out basis by Patient. Clinic Sort Groups
      can be added/edited in the Enter/Edit Clinic Sort Groups [PSO SETUP
      CLINIC GROUPS] option, which is found under the Maintenance (Outpatient
      Pharmacy) [PSO MAINTENANCE] menu option.
       
      11. This patch fixes a problem of a prescription showing up on the
      unreleased report, when only an Interaction label printed, and not a
      Filling label. If a prescription is entered before the version 7.0
      install, and a Drug Interaction label printed, then version 7.0 is
      
    • 164 SEQ #144
      DATE APPLIED:   2004-03-30 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      There is one occasion where in the Outpatient Pharmacy application
         are entered through through CPRS, Rx B and Rx C. Rx B is a 
         duplicate of Rx A. When finishing Rx B, an order check happens
         and Rx A is DC'd. Select Rx C and select to edit the Patient 
         Instructions field. If this field was NULL before, it will now
         show a default value, which is the content of the Patient 
         Instruction field from Rx A ("FOR ALLERGIES").
         
      This problem will be corrected by installing this patch.  
      where the PATIENT INSTRUCTIONS field content from one prescription 
      can be carried over to another prescription automatically. This 
      problem was identified in the Complete Orders from OERR [PSO LMOE
      FINISH] and Patient Prescription Processing [PSO LM BACKDOOR] menu 
      options. The scenario that this problem happens is the following:
       
         Patient has Rx A, which is active and the Patient Instructions 
         field is not NULL (e.g. "FOR ALLERGIES"). Two new prescriptions
      
    • 155 SEQ #145
      DATE APPLIED:   2004-04-27 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      1. Scheduling V. 5.3 package is moving the patient appointment information
      the patient appointment information in the Action Profile (132 COLUMN
      PRINTOUT) [PSO ACTION PROFILE ] option, with the new APIs.
       
      2. NOIS OKL-0204-7052
      The Action Profile (132 COLUMN PRINTOUT) [PSO ACTION PROFILE ] option is
      supposed to list only the active med orders if zero is entered for the
      prompt "Profile Expiration/Discontinued Cutoff:  (0-9999): 120//", but
      it also shows discontinued med orders. This patch ensures that if the
      cutoff days is zero, only the active med orders will be listed. For
      all other cutoff days the report will show the discontinued and expired
      stored in the APPOINTMENT sub-file (#2.98) of the PATIENT file (#2) and 
      med orders.
      the APPOINTMENT sub-file  (#44.001) of the HOSPITAL LOCATION file (#44) to
      the Government Off-the-Shelf (GOTS) database. Eventually, these sub-files
      will be deleted from the Scheduling files. As part of the Scheduling
      Replacement Project, Scheduling V. 5.3 package is providing a series of
      Application Programmer Interface calls (APIs) that will be used to get the
      patient appointment information from the new GOTS database. This is the
      Outpatient Pharmacy V. 7.0 patch that replaces all direct references to
      
    • 133 SEQ #146
      DATE APPLIED:   2004-04-27 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      1. OKL-1202-71318
         Yes//'. When selecting 'Yes', the software does not update the changes.
         This patch fixes this problem.
       
      2. MOU-1202-31080
         Using Patient Prescription Processing [PSO LM BACKDOOR ORDERS] option,
         when the drug of an active order is edited, the software checks for the
         change and prompts 'Do You want to Edit the SIG? NO//' and accordingly
         alerts the user with the message 'This change will create a new
         prescription!'. During the completion process of new orders entered
         through Computerized Patient Record System (CPRS), if the drug is
         When using the Patient Prescription Processing [PSO LM BACKDOOR ORDERS]
         edited, the software currently does not make any such checks on the
         edited drug. This patch ensures that the same functionality that is
         provided to the drug edits of an active order, is incorporated into the
         drug edits during the completion of orders entered through CPRS.
         Also the completion of pending order process is enhanced in this patch
         to display the message "Pending Order Not Updated!" in the message box
         when an up-arrow (^) is entered at any of the dosage prompts to quit
         the process. This is similar to "Prescription Not Updated!" message
         that is provided when quitting during an edit of an active order with
         an up-arrow (^).
         option to edit the dispensed drug on an active order, if there is more
       
      3. CLL-0403-41585
         When using the Patient Prescription Processing [PSO LM BACKDOOR
         ORDERS] or the Complete Orders from OERR [PSO LMOE FINISH] option, to
         complete orders entered through Computerized Patient Record System
         (CPRS), you cannot edit the Orderable Item using the synonym of that
         Orderable Item. This patch corrects this problem.
       
      4. HWH-0303-40364
         When entering complex orders using Patient Prescription Processing
         than one drug tied to that Orderable item, if a different drug is
         [PSO LM BACKDOOR ORDERS] option, if an up-arrow (^) and 3 characters
         are entered at the conjunction prompt in order to correct one of the
         dosage fields, the software goes into an endless loop going back to the
         beginning of the complex dosage. This happens only if the 3 characters
         entered do not point to one of the dosage fields. This patch fixes this
         problem. We also fixed the following related issue: Currently, to jump
         to the Limited Duration field within the dosage edit, you need to enter
         "^DUR" or "^dur", not "^LIM" or "^lim", as expected by many users. This
         patch provides the option of entering "^LIM" or "^lim" or "^DUR" or 
         "^dur", to jump to the Limited Duration field.
         selected from the displayed drug list, the software prompts 'Do You
       
      5. SBY-0503-30615
         Using Patient Prescription Processing [PSO LM BACKDOOR ORDERS] option,
         when the Orderable Item of an active order is edited to a different
         item, this will alert the user with the message 'New Orderable Item
         selected. This edit will create a new prescription!', and it will do 
         the order checking. During order checking process if it encounters any
         drug interactions with other active prescriptions, it will display the
         following:
       
         want to Edit the SIG? NO//'. On selecting 'Yes' you are prompted for
           '***CRITICAL*** Drug Interaction with RX #9999999'
           'DRUG: ASPIRIN BUFFERED 325MG TAB' (the drug it had interaction with)
           'Do you want to Continue? Y// '.
       
         At this prompt if you enter 'No' or up-arrow (^), or you enter 'Yes'
         and for the next prompt 'Do you want to Process medication METHOTREXATE
         2.5MG TAB: P// ?', (drug that is tied to the Orderable Item you
         selected to), if you enter '0' or '^' to Abort, there is a possibility
         of getting an undefined variable error PSODRUG("OIN"). This patch
         corrects this problem.
         these fields: dosage, verb, dispense unit, noun, route, schedule,
       
      6. MAC-0503-60991
         Using the Patient Prescription Processing [PSO LM BACKDOOR ORDERS]
         option, when the drug of an active order is edited to a drug that is
         tied to a different Orderable Item, the software prompts 'Do You want
         to Edit the SIG? NO//'. On selecting 'No', you are alerted with the
         message 'This change will create a new prescription!'. When you accept
         the new order, since the dosage information is incomplete you will be
         forced to enter the dosage information. At the prompts; Verb, Schedule,
         Limited Duration or Conjunction, if you enter up-arrow (^) with the
         duration or the conjunction. If changes are made to any of these
         intention of quitting the order process, you are prompted to fill the
         rest of the fields. When it prompts you 'Is this correct? YES//', on
         selecting 'Yes', there is a possibility of getting an undefined
         variable error PSOX("ENT"). This patch corrects this error.
         fields, you are prompted  'Are You Sure You Want to Update Rx 999999?
      
    • 152 SEQ #147
      DATE APPLIED:   2004-05-07 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
       
      2. CLE-0203-40018
         When trying to refill a drug that is unmarked for Outpatient Pharmacy use,
         the options Refill [PSO REFILL] and Refill (OP) [PSO SPEED REFILL] act
         differently.  The Refill [PSO REFILL] option does not allow this and the
         Refill (OP) [PSO SPEED REFILL] does allow this, and should not.  This
         patch will correct the Refill (OP) [PSO SPEED REFILL] option to not allow
         refills of a drug that is unmarked for Outpatient Pharmacy Use.
       
      3. CMC-0602-30921
         National Drug Codes (NDC) starting with non-numeric characters were not
      1. CPH-0203-41084 
         being displayed under the "Comments" column on the CMOP Event Log section
         of the View Prescription [PSO VIEW] option. This patch corrects this issue
         by modifying the display to accommodate these National Drug Codes (NDC).
       
      4. NYH-0903-12478
         When a Health Level Seven (HL7) message is generated, the ZRL segment
         Sequence 13 (Non-Refillable), Sequence 14 (Refill Status) and Sequence
         20 (Fill Number) are not populated even though there are refills for the
         prescription. This patch will correct this issue by populating these
         Sequences for the ZRL segment.
         When using the options Patient Prescription Processing [PSO LM BACKDOOR
       
      5. ISB-0203-32155
         This patch resolves compliance issues with the Standards and Conventions
         Committee's (SACC) standard regarding the documentation of Database
         Integration Agreements (DBIA).  This patch will correct this issue by
         adding this documentation.
       
      6. ISB-0903-31952
         This patch resolves compliance issues with the Standards and Conventions
         Committee's (SACC) standard regarding the format of the first line of a
         ORDERS] and Complete Orders from OERR [PSO LMOE FINISH] to complete a 
         routine.  In this case, there was an extra space before the date.  This
         space has been removed to comply with the standard.
       
      7. PSO*7*152 TRACKER MESSAGE [#37406428] Response #8
         During the testing of this patch in Oklahoma City an undefined error
         occurred.  This error has been corrected in this patch.
         pending order, if the number of refills is five and the days supply is 60,
         the current logic calculates the maximum number of refills to two instead
         of five. This patch corrects this issue by modifying the maximum refills
         calculation to account for this scenario.
       
      
    • 167 SEQ #148
      DATE APPLIED:   2004-05-21 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      NOIS TOM-0104-41317
       
      1. Look for entries in PRESCRIPTION SUSPENSE file #(52.5) affected by 
         the problem above and will reset the "CMP" cross-reference for entries
         within 6 months from the date of install that have not been printed.
         If there are any "CMP" entries existing that do not have a
         corresponding internal entry number in the PRESCRIPTION
         SUSPENSE file (#52.5), the "CMP" entry will be deleted.
       
      2. During Installation of this patch the user will be asked: "Queue the
         Post-Install to run at what Date@Time:  ". If the prompt is not answered,
      When using the Patient Prescription Processing [PSO LM BACKDOOR ORDERS] 
         the patch WILL NOT be installed. After the post install routine 
         is run to completion at the time the user indicated, a MailMan message 
         with the subject "PRESCRIPTION SUSPENSE File (#52.5) reset "CMP" XRef" 
         containing the list of prescriptions will be sent to the person installing 
         the patch.
       
      3. It is possible that an old prescription in a non-transmitted state might
         be reset to a current division and be set up for transmission to CMOP.
         Please review the mailman report and make modifications if necessary 
         before turning the CMOP transmission back on.
      option to edit the division on an original prescription or refill that 
       
      NOTE: ** THE POST-INSTALL SHOULD BE QUEUED TO RUN AT OFF-PEAK HOURS NOT
               INTERFERING WITH CMOP TRANSMISSION TIMES AT YOUR SITE. **
      is suspended for CMOP, the possibility exists that the prescription will 
      not be sent to CMOP due to an invalid cross-reference.  
      This patch will fix this issue by maintaining the CMOP compound index 
      in the PRESCRIPTION SUSPENSE file (#52.5) correctly.
       
      This patch has a post install clean-up routine that will :
      
    • 157 SEQ #149
      DATE APPLIED:   2004-05-21 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      The Chief Business Office (CBO) is requesting modifications to several
      Software to support the Combat Veteran (CV) initiative is being developed
       
      In the event that a patient is eligible for more than one copay
      exemption, the CV prompt will be presented to the pharmacist first.
       
      A 'YES' or 'NO' response will be stored in the COMBAT VETERAN field
      (#122) of the PRESCRIPTION file (#52). This is a new field introduced in
      this patch.
       
      2. The Integration Agreement (IA) 2534 provides CPRS the copay related
      questions that need to be asked during the outpatient medication order
      and introduced in a phased implementation strategy. The reason for this
      entry process. This IA is modified to include the CV copay classification,
      if applicable.
       
      3. The PENDING OUTPATIENT ORDERS file (#52.41) that stores the pharmacy
      orders (new/renew) entered via CPRS is modified to include the provider
      response to the CV question. The provider response will be stored in the
      COMBAT VETERAN field (#110.1) of the PENDING OUTPATIENT ORDERS file
      (#52.41). The COMBAT VETERAN field (#110.1) is a new field introduced in
      this patch.
       
      type of deployment is due to the complexity of the functionality and the
      4. During the release of a prescription, medication copay exemptions are
      re-evaluated to see if there is a change in the billing status. This logic
      is modified to include the CV copay classification. If a copay exemption
      question applies and is unanswered, a MailMan message is generated. This
      message is sent to the pharmacist, ordering provider, and holders of the
      PSO COPAY key, to get answers to the exemption questions and reset the
      prescription copay status if needed, using the Reset Copay Status/Cancel
      Charges [PSOCP RESET COPAY STATUS] option .
       
      5. The Reset Copay Status/Cancel Charges [PSOCP RESET COPAY STATUS] option
      number of product line dependencies. Phase I: Combat Veteran Interim
      is modified to include the CV copay classification wherever applicable.
       
      6. During label printing of a prescription, if a prescription is deemed
      billable then the software does a check on the following copay exemption
      fields of the PRESCRIPTION file (#52):
      117          MILITARY SEXUAL TRAUMA
      118          AGENT ORANGE EXPOSURE
      119          IONIZING RADIATION EXPOSURE
      120          ENVIRONMENTAL CONTAMINANT
      121          HEAD AND/OR NECK CANCER
      Solution (CVIS) was a VistA only solution that involved development in
      122          COMBAT VETERAN
      If the prescription is identified as copay exempt, the software will
      print "NO COPAY".
      the Integrated Billing (IB) and Registration/Enrollment product lines.
      It provided the logic to identify those veterans who met the criteria for
      the combat veteran eligibility and provided billing reports
      cross-referenced against this identifier to aid in the copayment billing
      process. Phase II of this initiative will involve multiple product lines
      Veterans Health Information Systems and Technology Architecture (VistA)
      and additional VistA only development. The main goals of Phase II will be
      to fully automate the copayment billing processing of combat vets based on
      episode of care by providing the appropriate questions at check-out as
      supplied by CPRS.
       
      Product lines that have a stake in Phase II development include
      Enrollment/Registration (VistA), IB, Outpatient Pharmacy, Consolidated
      Mail Outpatient Pharmacy (CMOP), CPRS/TIU, Patient Care Encounter (PCE),
      Ambulatory Care, Event Capture, Scheduling and PTF. The National Patient
      Care Database (NPCD) will also require modifications to capture workload
      packages to support implementation of VHA Directive 2002-049 - "Combat
      reporting. The patches are listed below in the order that they must be
      installed:
      Outpatient Pharmacy
          PSO*7*157
          PSX*2*50
      PCE/PTF/Event Capture/Scheduling  - PIMS Host file
          PX*1.0*130
          SD*5.3*325
          DG*5.3*565
          EC*2.0*54
      Veterans Are Eligible For Medical Services For 2-Years After Separation
      Integrated Billing
          IB*2.0*247
      CPRS
          OR*3.0*190
      Product Features
      There are three main areas addressed by this enhancement:
      a. Identification/Notification of a CV Status veteran seeking medical care
         - The clinical applications shall obtain the CV Status for those
           veterans who qualify as such per the directive.
         - The CV Status identification shall be displayed to the appropriate
      From Military Service Notwithstanding Lack Of Evidence For Service
           audience (pharmacist, clinician providing care, intake personnel,
           schedulers, etc.).
         - Provider shall be able to identify whether care provided CV veteran
           was for a condition potentially related to combat service in the same
           manner as identification of exposure related care; care for SC
           conditions, etc.
      b. Assistance in the communication of a treatment being determined as
         Combat Related
         - Provide a means for the billing and pharmacy software package to
           identify these patients and services provided care for a combat
      Connection", which iterates VA's policy to provide medical care and other
           related condition.
      c. Automatically precludes inpatient and outpatient medical care,
         prescription and Long-term care copayments for CV Status veterans whose
         treatment/service has been deemed combat related.
       
      This is the Outpatient Pharmacy patch PSO*7*157 that provides the
      functionality changes to accommodate the new copay classification called
      "Combat Veteran".
       
      1. For the following options, when creating a new order, renewing an
      medical services to combat veterans despite the absence of proof of
      existing order, copying an existing order to a new order, or editing an
      existing order that results in a new order, the copay status of the
      prescription needs to be determined for billing purposes.
       
      a. Patient Prescription Processing [PSO LM BACKDOOR ORDERS]
      b. TPB Rx (Prescription) Entry [PSO TPB RX ENTRY]
      c. Barcode Batch Prescription Entry [PSO BATCH BARCODE]
      d. Complete Orders from OERR [PSO LMOE FINISH]
       
      Depending on the patient eligibility, the software currently provides
      service connection.
      the following copay exemption questions to the pharmacist during
      prescription finishing process:
       
      "Is this Rx for treatment of Vietnam-Era Herbicide (Agent Orange)
      exposure?"
       
      "Is this Rx for treatment of ionizing radiation exposure?"
       
      "Is this Rx for treatment of environmental contaminant exposure during the
      Persian Gulf War?"
       
       
      "Is this Rx for treatment of Military Sexual Trauma?"
       
      "Is this Rx related to treatment of Head and/or Neck Cancer?"
      and/or Neck Cancer veterans;
       
      To fulfill the Directive 2002-049, this patch will add the following
      Combat Veteran (CV) copay exemption question to the current copay list:
       
      "Is this Rx potentially for treatment related to Combat?"
      
    • 162 SEQ #150
      DATE APPLIED:   2004-05-21 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      This patch will fix two similar issues regarding missing text
          was previously truncated will now be moved to a new line.
       
      2.  When printing prescription labels there is a potential that some 
          lines will be skipped from printing on the prescription in the
          warning label section.  This issue was happening in rare cases
          when lines in the warning label had been deleted and new lines
          were added.  Modifications have been made to print the warning
          labels lines when this scenario is encountered.
      on the printed prescription labels.
       
      The two issues this patch resolves are:
       
      1.  When printing prescription labels there is a potential that part 
          of the Narrative Text lines will be truncated.  Modifications
          have been made to resolve this problem while preserving the 
          narrative text format entered by the customer.  The text that 
      
    • 163 SEQ #151
      DATE APPLIED:   2004-05-21 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      1. DAY-1202-41933
       
      2. SPO-0104-50404
         An internal problem in the software was causing an error during the
         Renewal process. This error occurred when a Transitional Pharmacy
         Benefit prescription was renewed and the PATIENT STATUS field (#3)
         of the PHARMACY PATIENT file (#55) had not previously been set.
         Once this patch is installed this problem will be resolved.
         An internal problem in the software was causing the content of the
         comment field, entered when a prescription was discontinued, to be 
         replaced by a 0 (zero). This problem was detected when printing the
         Activity Log for the discontinued prescription. The comment field for
         the DISCONTINUED activity was displaying a 0 (zero) instead of the 
         original comments entered by the user who discontinued the
         prescription. Once this patch is installed this problem will be
         resolved.
      
    • 132 SEQ #152
      DATE APPLIED:   2004-05-21 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      Joint Commission for Accreditation of Healthcare Organizations (JCAHO)
      System (CPRS), Outpatient Pharmacy, Pharmacy Data Management, Inpatient
      Medications and National Drug File (NDF).
      requires that patients' use of OTC medications, Herbal supplements,
      medications prescribed by the VA but purchased by the patient at an
      outside pharmacy, and medications prescribed by providers outside the VA
      be documented in patients' medical records.  These four categories of
      medications will hereafter be referred to as Non-VA Meds. In September
      2002, a team with members from different applications was put together to
      come up with a national solution to address this requirement. The
      applications involved in this project are Computerized Patient Record
      
    • 176 SEQ #153
      DATE APPLIED:   2004-07-02 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      This patch addresses the problem introduced by the Outpatient Pharmacy
      introduced by patch PSO*7*155.
      patch PSO*7*155.
       
      In the Action Profile (132 COLUMN PRINTOUT) [PSO ACTION PROFILE] option,
      the print by 'Clinic' function was not working correctly after installing
      the patch PSO*7*155. One of the problems was related to queuing the report
      to the printer. The report would show on the screen instead of the
      printer. It also resolves the problem "device or file not open" reported
      in NOISs LEB-0404-21298 and NCH-0404-41348. This patch fixes all problems
      
    • 20
      DATE APPLIED:   1999-04-16 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      1. This patch fixes an error that can occur in the Change Suspense Date 
      Pharmacy can return a flag to CPRS that tells CPRS to not ask the Service
      Connected question for that particular Outpatient Pharmacy order.
       
      3. A new input transform for the QTY (#.04) field of the PARTIAL DATE
      subfile (#52.2) of the PRESCRIPTION file (#52) is being sent out in this
      patch. It changes a Write statement to a VA FileMan call to comply with
      current standards.  
       
      4. This patch corrects a problem with discontinuing multiple Rx's at one
      time. NOIS CON-0698-12208.  
      [PSO PNDCHG] option. When using this option, if "YES" is entered at the
       
      5. In the medication procedure call that returns inpatient and outpatient 
      detailed information, new data elements were added.  NOIS PUG-0298-51400.
       
      6. Corrected a problem with editing drugs in prescriptions and the cost
      for the drug not being updated properly. NOIS TUA-0798-32558.
       
      7. This patch corrects a problem of a possible incorrect CLINIC (#5)
      field entry for a prescription. If a prescription is renewed from CPRS,
      then Finished in Pharmacy, the Clinic for that prescription is the
      "Do you want to delete Rx's from suspense for this patient" prompt, and
      original Clinic for the "Renewed from" prescription, but is should be the
      Clinic where the prescription was Renewed. NOIS: CON-0998-10826
       
      8. This patch corrects a problem when a drug is changed in an Rx, but does
      not create a new order, the cost for that Rx did not update.
      NOIS: TUA-0798-32558 
       
      9. Enhanced the Cost Management Cost compile to use the release date and 
      include partials. This change allows the management report to be
      consistent with the Cost and AMIS reports. NOIS: NCH-0698-40147
      that patient has an unreleased refill that has printed from suspense,
       
      10. Added new option to allow cost of an Rx for a specific drug to be
      updated after the cost has been updated in the DRUG file (#50). NOIS:
      NCH-0698-42420 and NYN-0998-11680.
       
      11.  This patch corrects a problem reported in NOIS CAH-1198-32272. The 
      problem happens when using the speed renew action, the incorrect number of
      refills for controlled substances was being stored and displayed.
       
      12.  Added a newing statement to the supported reference PSOORDER to try
      an error could occur. NOIS STX-0898-71717.  
      to protect variables of other packages.
       
      2. This patch exports an entry point that can be called by Computerized
      Patient Record System (CPRS) during Outpatient Order Entry. Based on the
      patient and the Dispense Drug selected (when applicable), Outpatient
      
    • 171 SEQ #154
      DATE APPLIED:   2004-07-02 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
       If a Pharmacist selects Multiple prescriptions in the Patient
       other pharmacist, once it is removed, the next entry added to the 
       ending file will contain the same internal entry number. If this new
       entry is a new order  (instead of a discontinued order or something
       else), when the first pharmacist gets to that item from his selection
       list, the information that is displayed is from the "New" order. So the
       pharmacist could unknowingly finish the prescription thinking it was
       for the patient that he is viewing on the profile . The order does get
       filed under the correct patient, just not the patient that the 1st
       pharmacist was processing. This patch corrects this problem by
       verifying that the pending order is for the same patient that the
       Prescription option ([PSO LM BACKDOOR ORDERS]) and one or more of these
       pharmacist is viewing.
       prescriptions are 'Pending', the possibility exists that another
       Pharmacist could have previously run the Complete Orders from OERR
       ([PSO LMOE FINISH]) option and already selected one of these orders to
       finish.  Locking on the pending order does not occur until the
       pharmacist pulls up that order to edit it. Once an order is finished,
       it is removed from the PENDING OUTPATIENT ORDERS file (#54.21). If the
       very last entry in the pending file is the one being finished by the
      
    • 175 SEQ #155
      DATE APPLIED:   2004-09-03 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      The VistA Fee Basis Package will be replaced by a new application in a 
      file (#52), and the local VistA FEE BASIS PHARMACY INVOICE file (#162.1)
      for fee basis patients. Accessing the FEE BASIS PHARMACY INVOICE file
      (#162.1) by Outpatient Pharmacy is provided by Integration Agreement (IA)
      203. With the VistA Fee Basis Package migrating to a new platform, the Fee
      Basis Encapsulation project is replacing IA 203 with IA 4395. IA 4395 will
      provide Outpatient Pharmacy with the fee basis prescription count and cost
      data either from the local VistA Fee Basis file or from the Fee 
      Replacement system. This will isolate the Outpatient Pharmacy from future
      changes as the fee replacement system is implemented. This patch will
      modify the Nightly Management Data Compile Job [PSO MGMT NIGHTLY COMPILE]
      phased approach. The new application will be hosted by the Health 
      option, to make a call to the new API, $$RXSUM^FBRXUTL(), documented by IA
      4395 that provides the fee basis prescription count and cost for a given
      date.
      As the VistA Fee Basis Package is moving towards a National database, the
      new API may also return a string value of 
      "-1^exception_number^exception_text", indicating an exception has 
      occurred. To accommodate this exception, this patch will also generate a
      new mail message to the holders of the PSORPH security key. Following is
      an example of this mail message:
       
      Administration Center, which is located at Denver, CO. A future phase of 
      Subj: FEE Basis Cost Data - Incomplete Nightly Job  [#156131]
      04/29/04@18:41  9 lines
      From: OUTPATIENT PHARMACY PACKAGE  In 'IN' basket.   Page 1  *New*
      -------------------------------------------------------------------
      **************************************************
      *** FEE Basis Cost data was not collected for  ***
      *** the period 04/26/04 to 04/29/04.           ***
      ***                                            ***
      *** The reason reported was:                   ***
      *** Valid station number not specified         ***
      the VistA Fee replacement project will have the pharmacy invoices entered 
      ***                                            ***
      *** You may have to manually recompile this    ***
      *** data at a later date.                      ***
      **************************************************
       
      This message will help in the future for site to manually recompile the
      missing fee basis prescription count and cost for the noted dates from the
      Fee Replacement system.
       
      Note:
      and processed using the Fee replacement system.
      The Cost of Prescriptions [PSO MGMT REPORT RX COSTS] option and the Cost
      of Prescriptions [PSO MGMT MONTHLY RX COSTS] option, provides the daily
      and monthly prescription cost report. While testing this patch it was
      observed that the average participating pharmacy prescription cost under
      the column heading "AVG PARTIC PHARM RX", was incorrect and displays a
      zero value even with data present. This patch fixes this problem.
       
      The Nightly Management Data Compile Job [PSO MGMT NIGHTLY COMPILE] option
      is scheduled to run nightly. This option populates the OUTPATIENT PHARMACY
      MANAGEMENT DATA file (#59.12) with cost related data from the PRESCRIPTION
      
    • 166 SEQ #156
      DATE APPLIED:   2004-09-03 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      1. CHA-0204-30749
      2. CAH-1203-31567, DUB-0204-30722, NYH-120311822, WPB-1203-31609
         The functionality exists to modify the DEA, SPECIAL HDLG (#3) field
         of the DRUG (#50) file to contain an "F".  This code signifies that
         this drug in not refillable.  If the # OF REFILLS (#9) field of the
         PRESCRIPTION (#52) file is modified after the DEA, SPECIAL HDLG (#3)
         field has been changed to an "F", the # OF REFILLS (#9) field for
         the prescription is automatically reset to 0.  This is causing the
         prescription display to show the 'Refills Remaining' as a negative
         number. This patch will change how this situation is handled.  If a
         prescription has refills and the DEA, SPECIAL HDLG (#3) field has been
         Currently, if the NARCOTICS NUMBERED DIFFERENTLY (#1000) field in the
         changed to include an "F", the # OF REFILLS (#9) field will be changed to
         the actual number of refills given and the following message will be
         displayed:
         "The drug has been changed and no longer allows refills."
         If no refills had been given, the # OF REFILLS (#9) field will be set to
         0 and the following message will be displayed:
         "No refills allowed on this drug."
       
      3. FGH-1203-31351
         If a prescription was transmitted to CMOP, then put on hold, it
         OUTPATIENT SITE (#59) file is set to Yes, all prescriptions that have
         removes the fill date. It is then released and when the hold is
         removed, it does not prompt for a fill date since it is released,
         therefore the possibility exists that if the Fill Date is blank the
         subsequent fills will be rejected by the CMOP transmission.
         This patch will prompt the user for a fill date with a default of
         the released date if a prescription is unheld after it is released
         and fill date field is blank.
         a drug with a DEA, SPECIAL HDLG (#3) field if file DRUG (#50) that contains
         an "A" (Narcotics) are numbered differently than other prescriptions.  This
         patch will change the check of the DEA, SPECIAL HDLG (#3) field in
         the DRUG (#50) file to check for all Schedule II drugs, denoted by
         a "2" in the DEA, SPECIAL HDLG (#3) field, instead of just an "A".
         
      
    • 172 SEQ #157
      DATE APPLIED:   2004-09-17 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
       1. LEX-0303-42244 & CTX-0504-70229
          possibility exists that a carriage return could be included in
          the NTE2 segment.  This will cause the Optifill machine to reject
          the entire HL7 message.  This patch will resolve this problem.
       
       3. CLE-0404-40219
          When a pharmacist finishes an order using the Patient Prescription
          Processing option (PSO LM BACKDOOR ORDERS) for a patient and does
          not exit back to the menu prompt, the possibility exists that the
          patients order could still be locked.  This would prevent other
          pharmacists from accessing this order until the original pharmacist
          While finishing a prescription using the Patient Prescription
          exits back to to the menu prompt.  This patch will resolve this
          problem.
          Processing option (PSO LM BACKDOOR ORDERS) for a controlled
          substance the number of refills could be set to eleven instead
          the maximum aloud, which is five.  This patch will resolve this
          problem.
          
       2. HOU-0404-71083
          When transmitting an HL7 message to the Optifill machine, the
      
    • 173 SEQ #158
      DATE APPLIED:   2004-09-24 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
        When using the option Print from Suspense File (PSO PNDLBL) the
        possibility exists that duplicate labels could be printed if
        this option was used previously and is still running.  This patch
        will resolve this issue by delaying the second job until the first
        job finishes.
      
    • 180 SEQ #159
      DATE APPLIED:   2004-10-15 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
       If a drug has been unmarked for Outpatient Pharmacy use by using the
       option Drug Enter/Edit [PSS DRUG ENTER/EDIT] then a pharmacist tries to
       refill a prescription that uses this drug, they will not be allowed.
       This patch will modify this behavior by allowing a prescription to be
       refilled even after the drug has been unmarked for Outpatient Pharmacy
       use.
      
    • 156 SEQ #160
      DATE APPLIED:   2004-10-29 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
       There are three patches to support the Outpatient Pharmacy Automation 
       refer to the individual patch description of the other patches to get the 
       names of the documentation files.  
       
       Each patch will share the same starting description with more detail 
       for each patch in the corresponding namespace patch number.  There is 
       only one installation guide.  It can be found on the anonymous 
       directory.  The name of the installation guide is 
       PS_OUTPATIENT_AUTOMATION_INTERFACE_IG.doc.  
       
       
       Interface project. These patches should be installed separately in the 
       The patch enhances the current Health Level Seven (HL7) interface to 
       ensure that the interface is compatible with all current Outpatient 
       Pharmacy V. 7.0 automation systems used by the Veterans Affairs 
       Medical Centers (VAMCs).  The current national VISTA HL7 interface is 
       written to HL7 standard V. 2.2.  Automated dispensing systems, such as 
       the Baker APS Pharmacy 2000, are currently using an interface written to 
       V. 2.3.1 standard using locally developed software.  The automated 
       dispensing systems have committed to be HL7 V. 2.4 compliant.  
       
       This patch includes the following new features: 
       following order: 
       1. Enhance the current Outpatient Pharmacy V. 7.0 HL7 interface to 
          the current HL7 V. 2.4 standard.  
       2. Creates a bi-directional interface.  The interface transmits 
          outpatient pharmacy data to multiple vendor systems utilized by VAMCs 
          and receives dispensed prescription data from the vendor systems.  
       3. The dispense completion message received back from the vendor will 
          automatically release the prescription in VISTA if the FILE RELEASE 
          DATE/TIME field (#105.1) is set to YES in the PRESCRIPTION file (#52).  
       4. The interface sends outpatient pharmacy prescription release 
          information to the vendor once a prescription is manually released.  
                         PSO*7*156      Outpatient Pharmacy 
       5. The BusinessWare interface engine at each medical center is used 
          to pass the HL7 data through from VISTA to the dispensing system.  
          There is no data manipulation on BusinessWare's part.  
       6. Enhance the activity log entries for the sequence of events for a 
          prescription's activity in the PRESCRIPTION file (#52).  
       7. Add a fourth selection to the OUTPATIENT SITE file (#59), EXTERNAL 
          INTERFACE field (#5).  This selection is titled 'SEND MARKED ORDERS 
          AND PRINT LABEL'.  
       8. This patch allows dispensing system printer(s) to be entered and used
          when selected, and the interface is in use, sending an HL7 message
                         PSS*1*82       Pharmacy Data Management 
          to the dispensing system.
       9. This patch added new functionality for reprinting Rxs and using the 
          external interface.  If a reprint of an Rx is requested the user is 
          asked if they want to resend the Rx to the external interface.
                         PSN*4*84       National Drug File 
       
       They contain routines, templates, options, and data dictionary changes to 
       implement the Outpatient Pharmacy Automation Interface features.  Please 
      
    • 189 SEQ #161
      DATE APPLIED:   2004-10-29 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      1. PSO*7*156 provided a two-way interface that returns a dispensing
      the prescription labels that follows.
      NOISs: SAM-0604-21393, BAC-1203-40321, WIM-0604-20277
       
      3. When pulling an original fill early from suspense and printing
      prescription labels using a laser printer the last dispense date is not
      being updated correctly. When prescription are pulled from suspense the
      fill date and the last dispense date should always reflect the date the fill
      was pulled from suspense.  NOISs: HON-0904-62008, SAJ-0804-70774
      message to VistA from the dispensing machine that indicates
      dispensing of medication has completed.  When this dispensing message
      is returned the first entry in the activity log for the prescription is
      overwritten. This patch corrects this problem.
       
      2. When printing a prescription using a laser printer, the patient has a
      language preference other than English, and more than one prescription is
      entered and printed, text from the first prescription label is printing on
      
    • 159 SEQ #162
      DATE APPLIED:   2004-11-24 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
       1. FAV-0501-71064, FGH-1199-32693, WIM-0704-21673, WPB-0604-31928
       
       2. SBY-0504-30082
          During a routine edit of a prescription using the option
          [PSO LM BACKDOOR ORDERS] (Patient Prescription Processing) the
          possibility exists to receive an 'undefined variable' error in
          the program PSOORED2 at line VER+4.  This patch will resolve this
          issue.
          and MAD-0504-40315
          When making an appointment using the [SDAM APPT MGT] Appointment
          Management or [SDMULTICLINIC] Multiple Clinic Display/Book options
          the possibility exists that an error could be generated in the
          program SDAMEVT or SDMUTL1.  This error is caused by the
          Outpatient Pharmacy programs responsible for returning
          prescription information in the Appointment options.  This patch
          will resolve this issue.
      
    • 182 SEQ #163
      DATE APPLIED:   2004-11-24 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      WPB-0304-31149
      Solution: For a Scriptalk patient, if the sig is greater than 196 
      characters and the scriptalk label is printed, the human readable section 
      will print in English and its Spanish translation as follows:
       
      "SIG IS TOO LONG. REPRINT A NON-VOIDED VISTA LABEL AND PLACE OVER THIS 
      SCRIPTALK LABEL"
       
      "INDICACIONES MUY LARGAS. IMPRIMA UNA ETIQUETA DE VISTA VALIDA Y 
      APLIQUELA SOBRE ESTA ETIQUETA DE SCRIPTALK EN LA BOTELLA."
       
      When a partial is processed for a Scriptalk patient, the scriptalk 
      HIN-0104-41546
      When using [PSO SCRIPTALK PATIENT ENROLL ] option, the message displayed 
      is offset and incomplete. This patch will display the full message.
       
      BIG-0404-70352
      1. When a patient has more than one eligibility code defined and the 
      patient profile is accessed using the [PSO LM BACKDOOR ORDERS] option, it 
      only displays one eligibility.
       
      2. When the patient status is not defined, and the patient is accessed, it
      printer label generated prints with the full quantity instead of the 
      only displays one eligibility. 
       
      This patch will display multiple eligibilities defined for the patient.
      partial quantity. This issue is resolved with this patch.
       
      CLE-0304-40723
      Problem: For a Scriptalk patient, if the sig is greater than 196 
      characters and the scriptalk label is printed, it truncates the sig.
       
      
    • 21
      DATE APPLIED:   1999-04-16 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      1. Prior to the installation of this patch, if a new prescription is
      CMOP criteria. Because the routing gets changed from Window to Mail, the
      prescription will be suspended for CMOP, instead of suspended locally.
       
      2. This patch provides the Controlled Substances package an entry point to
      call that will delete the last refill of a prescription. When posting
      and releasing a prescription in Controlled Substances, if that
      prescription has been discontinued, it will not be released and the refill
      will be deleted. This functionality will be available when patches
      PSO*7*21 and PSD*3*11 are installed, though the patches are not dependent
      on each other for installation.
      entered at a site running the Consolidated Mail Outpatient Pharmacy (CMOP)
       
      3. This patch fixes an error that could occur when putting a prescription
      on Hold through the Patient Prescription Processing [PSO LM BACKDOOR
      ORDERS] option. If the prescription has refills, and the user enters an
      '^' at the PHARMACIST NAME prompt, an error could occur. A change has also
      been made to the Activity Log comments when putting a prescription on
      Hold. Currently, if the prescription has an entry in the RX SUSPENSE file
      (#52.5), the comments always end in "removed from SUSPENSE", regardless of
      whether or not the fill has been printed from suspense. This patch makes
      the change to only add those comments if the suspense fill has not yet
      package, and that prescription is for a CMOP drug and is given a future
      been printed. NOIS OKL-1098-71710
       
      4. This patch enhances the functionality of editing prescriptions. An
      option is being added under the Rx (Prescriptions) [PSO RX] menu option
      called Edit Prescriptions [PSO RXEDIT]. This option will allow editing of
      prescriptions by entering prescription number(s). Editing will still be
      available through the Patient Prescription Processing [PSO LM BACKDOOR
      ORDERS] option, but this new option provides an alternative editing
      capability. In addition, if a key field of a prescription is edited (field
      that generates a Reprint label request), and the field edited is a field
      Fill Date and marked as Window for the routing, that prescription will not
      of the last fill that has been released, a prompt will now be given that
      asks if a Reprint label should be printed. If a key field is edited of a
      fill that is not the last fill, and that key field is contained in the
      last fill, a Reprint label will not be generated.
       
      5. This patch fixes a problem of an incorrect refill date possibly being
      assigned to a refill. After suspending a new prescription to the future,
      if a refill is then done and a refill date of today is entered, the
      future fill date from the new prescription can possibly be assigned to
      the refill date. NOIS ALX-1198-71519
      be suspended for CMOP. Even if all of the other CMOP criteria are met, it
       
      6. This patch provides a new Order Summary of Pending Outpatient orders.
      This new summary is by Clinic. To have this functionality, the
      verified patch PSO*7*15 must also be installed. Patch PSO*7*15 is not
      required for installation of this patch, but the new Order Summary by
      Clinic will not be available until that patch is installed.
       
      7. This patch fixes a problem reported for sites running Tricare. Partial
      prescriptions are being sent for Tricare billing, but they should not.
      This patches fixes the problem.
      will be suspended locally because of the Window Routing. Because of
       
      8. A problem has been reported that occurs when a Pharmacist verifies a
      prescription entered by a Technician. If the Pharmacist edits the
      prescription after it is accepted, but before the Label prompt, it can
      possibly be flagged as a Reprint prescription, when it should not be.
      Also, if it is a CMOP prescription, it may print locally instead of
      going to the CMOP because of the Reprint status.
      numerous requests to change this functionality, this patch will
      automatically change a Window routing to Mail for new prescriptions
      entered with a Future Fill Date that get suspended, and meet all of the
      
    • 118
      DATE APPLIED:   2004-12-28 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      This project consists of 12 patches that work together to create a new
       GMPL*2*27
       GMRV*4*15
       LR*5.2*295
       OR*3*157
       PSS*1.0*62
       PSJ*5.0*90
       PSO*7*118
       PX*1.0*119
       RA*5*33
       YS*5.01*77
      Clinical Reminders index global. The purpose of this index is to provide
       
      The purpose of this patch (PSO*7*118) is to lay the groundwork for these
      changes by creating new cross-references in the PRESCRIPTION file (#52)
      that will be responsible for updating the new Clinical Reminders index
      global. These are the new cross-references added to the PRESCRIPTION 
      file (#52) and the fields used as the trigger-points. The type of these
      cross-references is 'New', not 'Traditional'.
       
        X-ref  File/Sub-file              Trigger-point field(s)
        ----------------------------------------------------------
      rapid access to clinical data. All of the standard Clinical Reminders
        ACRO   PRESCRIPTION (#52)         DAYS SUPPLY (#8)   
                                          RELEASED DATE/TIME (#31) 
       
        ACRR   REFILL (#52.1)             DAYS SUPPLY (#1.1)
                                          RELEASED DATE/TIME (#17)
       
        ACRP   PARTIAL (#52.2)            DAYS SUPPLY (#.041)  
                                          RELEASED DATE/TIME (#8)
      finding types are included in the index.
       
      The 12 patches that comprise this project are:
       
       PXRM*1.5*12
       DG*5.3*478
      
    • 185 SEQ #165
      DATE APPLIED:   2004-12-28 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      ***********************************NOTE***********************************
      (HDR) to receive clinical data about patients the patient must have an
      Integration Control Number (ICN) and Treating Facility (TF) List. VistA
      under certain circumstances allows backdoor entry of clinical activity to
      be recorded for a patient without "requiring" a patient to have an ICN.
      The immediate needs of the HDR have identified several issues within the
      existing PIM to uniquely identify patients through the ICN enumeration
      process. PIM services are tied into VistA at several points. In the
      current VistA structure, up front identity management is done only within
      Registration via several different menu options, as that has been the
      traditional entry point of patients into the system. In addition, there
      This patch does NOT conflict with CoreFLS and can be installed at CoreFLS
      are "hooks" within Appointment Management, which assign a local ICN after
      the patient has received care. Subsequently, the national ICN is obtained
      through a nightly job or via manual resolution of the local ICN. The
      requester states that the current method does not support good business
      practices for updating patient identity traits at appropriate entry points
      and does not provide the full functionality of the benefit of the ICN in
      linking all patient data together.
       
      This is the Outpatient Pharmacy patch PSO*7*185 that places the ICN check
      (hooks) within the Outpatient Pharmacy V. 7.0 options, to dynamically
      sites.
      assign a local ICN for a patient if one was not found.
       
      Outpatient Pharmacy will not make any changes to options where the
      patient look up is done via the FileMan DIC call on the PATIENT file
      (#2). As part of the PIM project, the Master Patient Index V. 1.0 package
      will send out a separate patch that will have the ICN "hooks" in place.
       
      In Outpatient Pharmacy, the following options do not use the standard
      patient lookup (FileMan DIC call on the PATIENT file (#2)), as the
      primary input for selecting orders.
      **************************************************************************
       
      Release Medication [PSO RELEASE]
      Return Medication to Stock [PSO RETURNED STOCK]
      Reset Copay Status/Cancel Charges [PSOCP RESET COPAY STATUS]
      Complete Orders from OERR [PSO LMOE FINISH]
      Barcode Batch Prescription Entry [PSO BATCH BARCODE]
      Discontinue Prescription(s) [PSO C]
      Edit Prescriptions [PSO RXEDIT]
      Reprint an Outpatient Rx Label [PSO RXRPT]
      View Prescriptions [PSO VIEW]
       
      Pull Early from Suspense [PSO PNDRX]
       
      For these options, a check is put in place to see if the INTEGRATION
      CONTROL NUMBER (ICN) field (#991.01) of the PATIENT file (#2) is populated
      by calling the API #2701, $$GETICN^MPIF001(DFN). If it is not populated
      then a call is made to the API #3300, $$MPIQQ^MPIFAPI(DFN) that will
      populate the INTEGRATION CONTROL NUMBER (ICN) field (#991.01) of the
      PATIENT file (#2).
       
      Note: This patch also carries a fix for NOIS PAL-0804-60841.
      PATCH OVERVIEW
      Patch PSO*7*175 - FEE REPLACEMENT ENCAPSULATION PROJECT, calls the API
      #4395, $$RXSUM^FBRXUTL(DATE,STATION_NUMBER), to collect the fee basis
      prescription count and cost for a given date and the approving Veterans
      Affairs Medical Center (VAMC) station number. The station number that is
      passed to the API is the STATION NUMBER field (#99) of the INSTITUTION
      file (#4), which constitutes a 3 digit station number plus any modifiers.
      The API #4395 requires only the first 3 digits of the station number
      otherwise it will return an error message, "Valid station number not
      specified". This patch fixes this problem.
      Gail Graham, Director of Information Assurance requested that a process
      of Patient Identity Management (PIM) be created that uniquely identifies a
      patient prior to providing care. In order for the Health Data Repository
      
    • 181 SEQ #166
      DATE APPLIED:   2005-01-18 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      This patch supports the VistA Data Extraction Framework (VDEF)
      effort, allowing changes to the PRESCRIPTION file (#52) to be transmitted
      to the Health Data Repository (HDR). The activation of the transmission 
      will be handled with the sites on an individual basis. Until that 
      activation occurs, the changes included in this patch will not affect 
      any Pharmacy functionality.
      
    • 190 SEQ #167
      DATE APPLIED:   2005-01-18 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      This patch is phase 2 of the patches that support the VistA Data
      PROTOCOL:
         PSO VDEF RDE O11 OP PHARM PRES HR
         PSO VDEF RDE O11 OP PHARM PRES VS
         PSO VDEF RDS O13 OP PHARM PPAR HR
         PSO VDEF RDS O13 OP PHARM PPAR VS
         PSO VDEF RDS O13 OP PHARM PREF HR
         PSO VDEF RDS O13 OP PHARM PREF VS
       
      HL7 APPLICATION PARAMETER:
         HDRPPAR
      Extraction Framework (VDEF) effort, allowing changes to the PRESCRIPTION
         HDRPREF
         HDRPRES
         PSO VDEF IE SIDE 
                            
      The routine PSOVDFK is used as the KIDS Post-Install routine to install 
      specific components for the Outpatient Pharmacy package in several VDEF
      namespace globals that VDEF uses to construct a message.  It uses the VDEF
      API POSTKID^VDEFVU to do this.  The specific components that are sent to
      Post-install routine are:
       
      file (#52) to be transmitted to the Health Data Repository (HDR). The
      1.      HL7 Message Type
      2.      HL7 Event Type
      3.      VistA Domain Subtype
      4.      HL7 Protocol Event Driver name
      5.      Application's Custodial Package name
      6.      Name of the routine that does the message extraction
      7.      VDEF Event Description
      8.      VDEF Event Subtype description
       
      The POSTKID^VDEFVU routine uses the components to create event-specific
      activation of the transmission will be handled with the sites on an
      parameters in VDEF files.
       
      The patch cannot be installed until VDEF 1.00 is installed. 
       
       
      ** IMPORTANT **
       
      Sites should not install this software prior to your assigned HDR
      installation date; doing so may cause complications with your BCMA
      application with versions prior to PSB*3*4. You will be contacted
      individual basis. Until that activation occurs, the changes included in
      approximately two weeks prior to your HDR installation date and provided
      with instructions on when and in what order to install these patches and
      the VDEF software. Additionally, sites should not configure or attempt to
      utilize the VDEF software associated with these patches prior to your
      assigned HDR installation date, at which time Technical Support Office
      personnel will work with you to activate that application and start your
      data transmissions to the HDR database. (If you do not know your HDR
      installation date, you can find that information by going to 
      <http://vaww.teamshare.domain.ext/hdr_implementation/> and selecting 
      "Implementation Schedule" from the Quick Launch panel on the left side of 
      this patch will not affect any Outpatient Pharmacy functionality.
      the page.) 
       
      The following build components are being exported with this patch:
       
      
    • 177 SEQ #168
      DATE APPLIED:   2005-01-18 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
       
      The Label/Profile monitor field has 250 as the minimum value, but the 
      software that uses that field sets the minimum value to 1000.
      Each time the printer is used, an entry is made in the Label/Profile 
      monitor and if the monitor holds more entries than specified by this 
      parameter, the oldest entry is deleted.
      The documentation and field specifications for Label/Profile monitor 
      allows you to enter a minimum value of 250.  The field specification and 
      file manager documentation will be changed to allow a minimum value of 
      1000.
      While going through the option to finish an outpatient pharmacy order
      [PSO LMOE FINISH], if the patient status field is left blank the first 
      time it is asked for, the program will ask for the patient status again.
      If the user doesn't enter the patient status the second time, an error is
      generated.
      This patch will resolve this problem.
       
      2)HUN-0304-21898
      
    • 193 SEQ #169
      DATE APPLIED:   2005-01-18 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      1. PSO*7*156 provided a two-way interface that returns dispensing
      information to VistA from the dispensing machine that updates the 
      PRESCRIPTION file (#52) when dispensing of medication is completed.
      Since being released to the field, it has been determined that additional
      data validation checks were needed on the data being returned.
      This patch includes those additional data validation checks.
       
      3. When viewing a prescription using the View Prescriptions [PSO VIEW]
      option, the initiator of activity does not display, however, if viewing from
      the profile, it does display. NOIS: MAC-1104-61559
      information to VistA from the dispensing machine that updates the 
      PRESCRIPTION file (#52) when dispensing of medication is completed.
      When developing this new two-way interface the Label/Profile Monitor
      Reprint [PSO B] option was not enhanced to send label reprints to the
      external interface.  BRX-0803-10283
       
       
      2. PSO*7*156 provided a two-way interface that returns dispensing
      
    • 184 SEQ #170
      DATE APPLIED:   2005-03-11 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
       
          
       2. SHE-0404-51324
          The potential exists to modify the number of refills for a
          controlled substance from a maximum of 5 to 11.  This can happen
          in the Patient Processing Option [PSO LM BACKDOOR ORDERS] while
          finishing a renewed order.
       
       3. DAY-0604-41287
          An issue was identified in the Imaging software that allowed the
          software to automatically select a patient based on name even if
       1. MOU-1203-30359
          multiple patients existed with the same name.  A fix is being
          included in Pharmacy to kill an internal variable to not allow
          this behavior.  This change does not affect the pharmacy application
          in any way.
       
       4. CLL-0604-40968
          When using the Return Medication to Stock [PSO RETURNED STOCK]
          option it is possible to get the following message:
          
          Original Fill CANNOT be Returned!
          When using the Return Medication to Stock [PSO RETURNED STOCK]
          This fill entered before installation of version 6.  There are no
          refills.
          
          This message is generated when the pharmacist try's to return a
          medication to stock for a prescription that has a fill date that
          is less than the date Version 6.0 of the Outpatient Pharmacy
          application was installed.  This message will be removed.
          option for a controlled substance, the pharmacist is allowed to
          up-arrow ("^") out of the comments field even though it is a
          required field.  When this happens, some Controlled Substance
          files are partially updated and will cause the medication to be
          returned twice.  This patch will resolve this issue by not allowing
          the pharmacist to up-arrow out of the comments field.
      
    • 188 SEQ #171
      DATE APPLIED:   2005-03-11 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
       During order entry in backdoor Outpatient Pharmacy, Order checks are
       exists for the same drugs.
       not being performed on Non-VA medications if other medications exist.
       The possibility also exists that when a 'critical interaction'
       exists and is displayed, this critical interaction could be displayed
       for subsequent orders even though a 'critical interaction' does not
       exist on the order currently being entered.
       
       When entering an order via backdoor Outpatient Pharmacy or CPRS, a
       critical interaction could be skipped if a significant interaction
      
    • 194 SEQ #172
      DATE APPLIED:   2005-04-01 00:00:00
      APPLIED BY:   USER,ONE
    • 192 SEQ #173
      DATE APPLIED:   2005-04-01 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      SPELLING ERROR AND QUANTITY CHANGING
      
    • 14
      DATE APPLIED:   1999-04-16 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
       
      and will not auto-suspend to the next scheduled refill date.
      Routine: PSOREF0
       
      3. Fixed Null Subscript error reported in NOIS WAS-0498-21833. The error
      occurs when Outpatient Pharmacy receives a Discontinue message from CPRS on
      an entry in the PENDING OUTPATIENT ORDERS File (#52.41) with missing
      data.  Changed messaging to recognize the UR order control code.
      Routine PSOORUTL
       
      4. In the View Prescriptions option, the help text given to the user at the
      1. This patch fixes a possible undefined error that could occur when
      VIEW PRESCRIPTION prompt if the user enters a "?" is misleading. The
      help text says that Patient Name can be entered, but it can't. This patch
      will remove the "M" from the DIC(0) variable. Routine PSORXVW
      a new Outpatient Pharmacy division is added and the Daily and/or Monthly
      Management Cost Reports are run.
      Routines: PSOMGMN1, PSOMGMN2, PSOMGMN3, PSOMGRP1, PSOMGRP2, PSOMGRP3
       
      2. If an OP Rx is filled on 6/5 and the patient quickly returns the refill
      form for processing, on 6/13, before the scheduled refill date 6/26.  The
      bar code option [PSO BATCH BARCODED] will not accept the refill request
      
    • 186 SEQ #174
      DATE APPLIED:   2005-04-01 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
       This patch will correct two DEA (Drug Enforcement Agency) Special
       Handling issues, one while completing the prescription via the PSO LM
       BACKDOOR ORDERS option, and one while refilling a prescription via the
       Barcode Batch Prescription Entry option on the PSO BARCODE MENU.  This
       patch will also correct a null subscript error while verifying a
       prescription via the PSO LM BACKDOOR ORDERS option.
      
    • 165 SEQ #175
      DATE APPLIED:   2005-04-01 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      This supported #1878 has been updated to include new data elements at the
       FINISHING PERSON
       MEDICATION INSTRUCTION sub-file fields:
       DOSAGE INSTRUCTION, DISPENSE UNITS PER DOSE, UNITS, NOUN, 
       DURATION, CONJUNCTION, ROUTE, SCHEDULE, VERB
      request of Pharmacy Benefit Management (PBM).  See DBIA #1878 for
      complete description.
       
      The follow data elements from the Prescription file (#52) were added.
       NDC (original, refill, partial)
       LOGIN DATE (original, refill, partial)
       TPB RX
       EXPANDED PATIENT INSTRUCTIONS 
      
    • 165
      DATE APPLIED:   2005-04-01 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      The routine PSOORDER, which supported DBIA #1878 has been updated to 
       LOGIN DATE (original, refill, partial)
       TPB RX
       EXPANDED PATIENT INSTRUCTIONS 
       FINISHING PERSON
       MEDICATION INSTRUCTION sub-file fields:
       DOSAGE INSTRUCTION, DISPENSE UNITS PER DOSE, UNITS, NOUN, 
       DURATION, CONJUNCTION, ROUTE, SCHEDULE, VERB
      include new data elements at the request of Pharmacy Benefit Management 
      (PBM).  See DBIA #1878 for complete details.
       
       
       
       
      The following data elements from the Prescription file (#52) were added.
       NDC (original, refill, partial)
      
    • 161 SEQ #176
      DATE APPLIED:   2005-04-26 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      This patch is part of the Outpatient Pharmacy V. 7.0 Laser Labels
        2. Contact your vendor to make adjustments based on the new data stream.
      lastname,firstname.
        4. When the routing is "Window", the word "Window" will be bolded.
       
      Pharmacy fill card section changes:
      ==================================
        1. Seconds will be removed from the label date/time.
        2. A new API will return the text for the DRUG WARNING list. The DRUG 
      WARNING entries will be separated by commas. If an entry in the list does 
      not have an "N" (for "New"), it is from the RX CONSULT file (#54).
      Otherwise it is from the WARNING LABEL-ENGLISH (#50.625) or the 
       
      WARNING LABEL-SPANISH (#50.626) file.
        3. A new line containing the patient location and status is being added
      beneath the DRUG WARNING list, so the list is being moved up slightly on
      the label.
        4. Patient name and last portion of the social security number are 
      bolded.
        5. If the bottle cap is "non-safety", it will be bolded.
        6. Currently long SIG's that do not fit on one pharmacy fill card label
      print only 4 lines of SIG on the first label and up to 4 lines on each
      continuation label. This patch increases the number of lines of the SIG 
      Although implementing OPAI is not mandated at this time, it is expected 
      that print on each pharmacy fill card label to reduce the total number of
      labels needed.
        7. The words "3rd Party Rx" and the NDC number are added when that 
      information is available. (Added for HIPAA/NCPDP).
       
      Patient fill section changes:
      ============================
        1. The barcode will print every time even if there are no refills.
        2. The site telephone number will print when the "PHONE IN OR MAIL THIS 
      REFILL REQUEST" prints.
      to be in the future, so option 1 is the preferred solution. By 
        3. The text "n refills left until MMM DD,YYYY is changed to "May refill 
      nX by MMM DD,YYYY".
       
      Prescription Document PMI section changes:
      =========================================
        1. The PMI will print in the patient's language preference.
        2. The white spaces between sections of the PMI document will be 
      reduced to result in a few more lines fitting on the page.
        3. If there are more than 5 warning labels, the additional warnings 
      will print at the top of the PMI section.
      implementing OPAI, future changes to the label format will not affect the 
       
      Trailing document changes:
      =========================
        1. The patient's phone number followed by an underline will print on 
      the address change form.
        2. In the Allergies/ADR section, the name and last six digits of the 
      social security number will be made larger and will be bolded.
        3. In the Allergies/ADR section, if the HOSPITAL LOCATION file (#44), 
      TYPE field (#2) type equals "W" for any prescription printed for this 
      patient in the current print job, then the word "INPATIENT" will print 
      dispensing equipment interface.
      on the line following the patient name.
        4. In the Allergies/ADR section, if some sections do not have data, the 
      header will not print. If no information exists, "No Assessment Made" 
      will print after the Verified Allergies heading.
        5. In the refill narrative or copay narrative sections, if there are 
      more than seven lines from the original text, only the first seven lines 
      will print. (They could appear as more than seven lines if there is some 
      wrapping of the text).
        6. If the Multi-Rx refill section is blank, the SITE NUMBER field 
      (#.06) from the OUTPATIENT SITE file (#59) will print bottom right
      *************************************************************************
      justified.
       
      A utility routine is included in this patch to change some of the control
      codes in the TERMINAL TYPE file (#3.2). 
      Once the patch is installed, running the routine PSOLLU4 in programmer
      mode will make slight adjustments to PATIENT FILL INITIALIZATION, 
      PHARMACY FILL DOCUMENT WARNING, MAILING LABEL INITIALIZATION, and RETURN 
      MAIL INITIALIZATION settings.
      Note: you must have your FileMan access set to '@' to run the routine. 
       
      To fully implement all portions of the new functionality, the 
      following are needed:
      Phase II project for printing prescription labels.
        1. Patch PSS*1*87 from Pharmacy Data Management V. 1.0 (PDM),to provide 
      an API for retrieving warning labels from the new data source.
        2. Patches PSN*4*86 and PSN*4*88 from the National Drug File V. 4.0
      (NDF) to create and populate a new gender field in the WARNING
      LABEL-ENGLISH file (#50.625) and the WARNING LABEL-SPANISH file (#50.626).
        3. Patch PSX*2*54 from the Consolidated Mail Outpatient Pharmacy V. 2.0
      (CMOP) to modify the way warnings are sent to CMOP.
       
       
       This patch includes:
       
        1. Referencing a new commercial data source for printing prescription 
      warning labels.        
        2. Printing warning labels and Patient Information Sheets (PMI) by the
      patient's PMI language preference setting.
        3. A new MAILING COMMENTS field (#.081) is added to the OUTPATIENT SITE
      file (#59.7) to be used for a site to enter anything they would like to 
      show on the Mail Address label. (i.e. whether mailing is "Forwarding 
      service requested" or  "Address service requested"). The PSO SITE INPUT 
      TEMPLATE for the OUTPATIENT SITE file (#59.7) is changed to allow the 
      input of data into the new mailing comments.
      ***** NOTE TO SITES USING AUTOMATED FILLING EQUIPMENT *****
        4. A new Manual Print of Multi-Rx Forms [PSO LM MULTI-RX PRINT] option
      is added under the Rx (Prescriptions) [PSO RX] option as well as under 
      the OTH hidden action while in the patient's profile to reprint the 
      Multi-Rx Refill Request form on laser label stock without having to
      reprint the entire prescription's labels. The functionality is also
      changed to stop printing the Multi-Rx refill form on reprints.
        5. Various changes to the content/format of the labels - detailed below
      under each label section.
        6. Correction to only print one ScripTalk label when SIG is continued.
      (NOIS CLE-0304-40723. (The other part of this NOIS is addressed in patch
      This patch changes the format and content of the laser labels print 
      PSO*7*182, so this NOIS is not included in the associated patch list 
      below)).
        7. A new Signature Log Reprint [PSO SIGLOG REPRINT] option is added
      under the Rx (Prescriptions) [PSO RX] option. (Added for HIPAA/NCPDP).
        8. A change was made to not keep exact duplicates of the control code 
      settings (e.g. when running the set-up routine as a test site and again 
      when the patch is installed in production). NOIS PUG-1103-52110
        9. The other NOIS's listed below were for items already included in the
      Laser Labels Phase II specifications.
       
      stream. If you are using automated dispensing equipment that relies on 
      Bottle label section changes:
      ============================
        1. Currently long SIG's that do not fit on one bottle label print only 4
      lines of SIG on the first bottle label and up to 4 lines on each 
      continuation label. This patch increases the number of lines of the SIG 
      that print on each bottle label to reduce the total number of labels
      needed. This also will allow the overlapping of the multiple labels on the
      bottle to eliminate the need for cutting the labels to make them fit.
        2. The text "Mfr_________" will print for all prescriptions on the same 
      line as the "Discard after" information.
      the data stream sent to the laser labels port, you have 2 options:
        3. The text "May refill nX by MMM DD,YYYY" or "NO REFILLS LEFT" or "NO 
      REFILL" was added between the "Discard after..." line and the Qty: line.
        4. On the trailing documents, a signature log will print in the bottle 
      label section for the patient to sign for the medications received. 
      (Added for HIPAA/NCPDP).
        
      Warning label section changes:
      =============================
        1. A new API will be called to determine which warnings to print.
        2. Warnings will print in English or Spanish depending on the patient's 
        1. Implement the Outpatient Automation Interface (OPAI) (available with
      PMI preference.
        3. If there are fewer than five warning labels, the warning labels will 
      be bottom-justified.
        4. If the DEA, SPECIAL HDLG field (#3) in the DRUG file (#50) begins
      with numbers 1,2,3,4 or 5. The NO TRANSFER warning label from the RX
      CONSULT file (#54) entry number 20 will print in the appropriate 
      language.
        5. The new data source contains some lengthy warnings, especially the 
      Spanish translation. For the smallest font, this patch allows a 4th line
      of text to print, if needed.
           released patch PSO*7*156) or 
        6. The top warning label was sometimes printing on or over the 
      perforated line. For some fonts, this patch reduces the white space 
      between the lines of the first warning to make it fit.
       
      Mail address section changes:
      ============================
        1. The current date will print in the upper right corner.
        2. If there are any mailing comments defined, they will print after the 
      MAIL field (#.03) of the PHARMACY PATIENT file (#55).
        3. Patient name will print first name first instead of 
      
    • 195 SEQ #177
      DATE APPLIED:   2005-05-25 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      Display Patient Record Flag consistently when finishing outpatient 
      pharmacy orders via the Complete Orders from OERR [PSO LMOE FINISH]
      option.
      
    • 196 SEQ #178
      DATE APPLIED:   2005-06-11 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      If a user runs option Return Medication to Stock in the Outpatient 
      Pharmacy menu and then goes into the Controlled Substances option
      Balance Adjustments, the dispensing site defaults to the one chosen when
      doing the Return Medication to Stock option.
      
    • 202 SEQ #179
      DATE APPLIED:   2005-06-11 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      This patch corrects the duplicate medication checking of meds that were
      ordered initially as both a NON-VA and an Outpatient med. This occurs in
      Patient Prescription Processing [PSO LM BACKDOOR ORDERS] option when you
      verify a Non-Verified med
      
    • 199 SEQ #180
      DATE APPLIED:   2005-07-09 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      DEATH ENTRY PROBLEM
      
    • 174 SEQ #181
      DATE APPLIED:   2005-08-13 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      1. Partial deletion causing error. This patch fixes this problem.
      2. Methadone drug being the only drug released when the Nightly
      Management Data Compile Job is run causing error.
      This patch fixes this problem.
      
    • 203 SEQ #182
      DATE APPLIED:   2005-08-13 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      Correct error when trying to add a NON-VA Med order to the PHARMACY 
      PATIENT file #55 in the "NVA" multiple file #55.05.
      
    • 13
      DATE APPLIED:   1999-04-16 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      Patch to Patch for PSO*7*15.
      
    • 205 SEQ #183
      DATE APPLIED:   2005-08-13 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      This patch adds the VUID (VHA Unique Identifiers) from the VA PRODUCT file
      (#50.68) to the Outpatient Pharmacy VDEF (Vista Data Extraction Framework)
      message that sends prescription information to the HDR (Health Data
      Repository). It also replaces Set of Code fields in the message with
      VUIDs. It also adds a check to screen out prescription information for
      test patients from being sent to the HDR.
      
    • 210 SEQ #184
      DATE APPLIED:   2005-08-13 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      Correct a word wrapping problem with Provider Comments and Patient 
      Instructions when there is a very large word, greater than 30 characters.
      Usually the word is a list seperated by commas with no spaces.
      
    • 204 SEQ #185
      DATE APPLIED:   2005-09-05 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      1. My HealtheVet team in preparation for the My HealtyVet V. 1.0
       
          Calling AP1 component will return the following status:
       
         -5      DFN does not match RX
         -4      Unable to resolve patient
         -3      Unable to resolve prescription
         -2      Status is pending
         -1      Result is back but not picked up
          0      Other error
          1      Filed in PRESCRIPTION REFILL REQUEST file (#52.43)
          package (Internet Prescription Refill project), requested an
       
          Calling AP2 component will return the following status:
       
          -6     RX not in file #52.43
          -5     DFN does not match RX
          -4     Unable to resolve patient
          -3     Unable to resolve prescription
          -2     Status is pending
          -1     Result is back but not picked up
           1     Filled
          additional Outpatient Pharmacy V. 7.0 Application Program Interface
           2     Not Filled
           n^x   n - Date the refill request was processed.
                 x - The result of the processing. This will be either FILLED or
                     NOT FILLED.
       
           Calling AP5 component will return the following status:
       
           -6     RX not in file #52.43
           -4     Unable to resolve patient
           -3     Unable to resolve prescription
          (API) #4687, to provide details of all (active, verified, on hold,
           -2     Status is pending
            0     The update was not successful. This will occur if any of the
                  information provided (DFN, RX #) are invalid.
            1     The update was successful.
       
       3. A new PATIENT field (#9) was added to the PRESCRIPTION REFILL REQUEST
          file (#52.43) that is a pointer to the PAITENT file (#2).  A new
          "AC" cross reference was added, to index the file by PATIENT field
          (#9) and PRESCRIPTION IEN field (#8). The existing "AA", and "AB"
          cross references were removed.
          suspended, discontinued, pending and expired), prescriptions for a
       
       Note: This patch carries a Pre-install routine that will delete the
       Data Dictionary (DD) of the PRESCRIPTION REFILL REQUEST file (#52.43)
       before the install of the new DD. This file is not in use currently,
       however, it will not destroy any data in the test systems.
       For more details, please refer to the installation guide or the technical
       manual of the My HealthyVet V. 1.0 package.
          patient within a given date.
       
       2. Also the existing API #3768 has been modified to provide the following
          status for Internet refill requests (used internally):
      
    • 209 SEQ #186
      DATE APPLIED:   2005-09-05 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      Corrects the following problems: 1) OPAI does not have an interface to 
      the Drug Accountability package. 2) OPAI when a code comes back to 
      indicate it did not dispense the drug, VistA Outpatient Pharmacy 
      indicates on the acitivity log that it did not, but actually does release 
      the drug,  3) On a refill from OPAI, the Copay is not billed correclty.
      
    • 215 SEQ #187
      DATE APPLIED:   2005-09-05 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      Produce a Tally message & report of all Outpatient Pharmacy refills that 
      were released via the OPAI 2.4 automated interface since the install of 
      patch PSO*7*156.
      
    • 143
      DATE APPLIED:   2005-09-05 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      PSO*7.0*143 = Outpatient Pharmacy Clinical Indicator Data Capture (CIDC) KIDS
      
    • 198 SEQ #189
      DATE APPLIED:   2005-10-20 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      Correct partially built NTE6 segment sent via OPAI, correct run-on words 
      in the PMI segment in HL7 messages sent via OPAI, and correct PSO 
      Management Reports from skipping Released RX's with date and no times.
      
    • 217 SEQ #191
      DATE APPLIED:   2005-10-20 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      Prompt for a Tally or Back-Bill run and based on this response either 
      produce a Tally or Back-Billing message & report of all Outpatient
      Pharmacy refills that were released via the OPAI 2.4 automated interface
      since the install of patch PSO*7*156.
      
    • 221 SEQ #192
      DATE APPLIED:   2005-11-15 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      PFP PSO*7.0*221 UPDATE TO PSO*7.0*174
      
    • 219 SEQ #193
      DATE APPLIED:   2005-12-02 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      This patch is a follow up for Outpatient Pharmacy Clinical Indicator Data
      and environmental indicator (EI) questions was not set correctly for non
      charge to the patient's insurance carrier.
       
      Note: The SC question is now asked for Veterans who are SC>49% in order to
      determine if the Rx can be billed to a third party insurance. These 
      Veterans will NOT be charged a VA copay.
       
      Supply and investigational drugs are not charged a VA copay but could be
      reimbursable by third party insurance.
       
      Enter message action (in IN basket): Ignore// 
      service connected (NSC) patients, as a result the following issues were
       
      c.  In CPRS, SC/EI related questions were not asked for supply items 
      and investigational drugs (remedy ticket 11421). CPRS and backdoor 
      Outpatient Pharmacy users will be required to complete SC/EI questions for
      supplies and investigational drugs. Supply items and investigational drugs
      could be reimbursable by third party insurance. Also, a VA copay will not
      be charged for these.
       
      2.  During use of Complete Orders from OERR option [PSO LMOE FINISH], the
      default answers for SC/EI's for CPRS SC>50% renewed orders were
      reported:
      occasionally displaying the previous orders answers during the finish
      process.  A modification was made to display the SC/EI information entered
      during the CPRS renewal process.  This anomaly was encountered during
      unit testing, and there is no associated remedy ticket.
       
      3.  For renewal orders in Complete Orders from OERR option [PSO LMOE 
      FINISH] and Patient Prescription Processing option [PSO LM BACKDOOR 
      ORDERS], a message was erroneously displayed after the SC/EI prompts for
      SC>50% prescriptions.  The following is an example of the message
      displayed when eligibility is changed or the user enters an up arrows (^)
       
      at an outpatient classification prompt.  Note that the bracketed
      information can be SERVICE CONNECTED or NON SERVICE CONNECTED depending
      upon the user's response to the question.  Or if the user up arrows (^)
      out of the prompt, the default answer determines the value.
       
                 Was treatment for a Service Connected condition? YES// ^
                 This Renewal has been designated as [SERVICE CONNECTED]
                 Please use the 'Reset Copay Status/Cancel Charges' option to
                 make corrections.
       
      a. In CPRS, the SC related questions were incorrectly prompted for NSC
      The "Please use the 'Reset Copay Status/Cancel Charges' option to make
      corrections" sentence will no longer be displayed for supply items,
      investigational drugs, and SC>50% patients.  The first sentence will
      remain in order to continue to inform the user of the answer stored for
      the prompt.  Note that similar messages are displayed for environmental
      indicator prompts and this change applies to them. The associated remedy
      tickets are 11393 and 113931.
       
      4.  For CPRS prescription orders finished using the Complete Orders from
      OERR option [PSO LMOE FINISH] or the Patient Prescription Processing
      patients, and it should not have done so. It should prompt SC/EI question
      option [PSO LM BACKDOOR ORDERS], a copay related message was displayed for
      SC>50% patients, supply items and investigational drugs.  The following is
      an example, and please note that bracketed information can be either COPAY
      or NO COPAY depending on the providers response to the clinical indicator.
       
           Do you want to enter a Progress Note? No//   NO
       
                  SC Percent: 40%
                  Disabilities: NONE STATED
       
      only if applicable.(remedy ticket 114219).
           This Rx has been flagged by the provider as: [NO COPAY]
       
           Was treatment for Service Connected condition? YES
       
      The "This Rx has been flagged by the provider as: [COPAY/NO COPAY]"
      message will no longer be displayed for SC>50% patients, supply items, 
      and investigational drugs.  There is no associated remedy ticket.
       
      5.  When an edit that creates a new order is performed in Outpatient 
      Pharmacy, a message is displayed to notate that the orderable item was
       
      changed.  This message is displayed in the Complete Orders from OERR
      [PSO LMOE FINISH] option and the Patient Prescription Processing option
      [PSO LM BACKDOOR ORDERS]. The following is an example:
       
            CARBAMAZEPINE 100MG TAB
            PROVIDER,NAME           PROVIDER,NAME
            # of Refills: 3
       
            The Pharmacy Orderable Item has changed for this order. Please
            review any existing medication copay exemption defaults carefully
      b. Holders of the PSO COPAY key, the ordering provider, and the finishing
            for appropriateness.
       
            SC Percent: 40%
            Disabilities: NONE STATED
       
            Was treatment for Service Connected condition? YES// 
       
      The above message has been modified to the following:
       
            The Pharmacy Orderable Item has changed for this order. Please
      pharmacist were receiving increased volumes of mailman messages in 
            review any existing SC or Environmental Indicator defaults carefully
            for appropriateness.
       
      Technical Description:
      ----------------------
      The following correlates to each sequence in the Functional Description 
      above and the routines modified are shown in parentheses by each function:
       
      1.  The SCNEW^PSOCP API was returning PSOTG("SC")="" variable for NSC
      patients which caused CPRS to erroneously prompt for them.  Also due to
      Capture (CIDC) patch PSO*7*143.
      Outpatient Pharmacy.  Mailman messages were incorrectly sent for NSC
      this, Mailman messages for "RX COPAY STATUS REVIEW NEEDED" information was
      sent in error for NSC prescriptions at release of the prescription. These
      issues were corrected, and the PSOCPE routine was modified to show the
      patient's eligibilities and disabilities as well as impart more accurate
      information.
       
       2.  Modified renewal routines to always pull SC/EI information from the
      data passed on the renewed order from CPRS (PSORENW1, PSORN52, PSORN52D).
      This change affects renewals from CPRS and backdoor Outpatient Pharmacy
      orders.
      patients upon refill, new, and renewed orders (remedy ticket 114219).
       
      3.  For SC>50% prescriptions, supply items and investigational drugs,
      eliminated the display of "Please use the 'Reset Copay Status/Cancel
      Charges' option to make corrections." sentence (PSOCPB, PSOMLLD2,
      PSOMLLDT), but it will continue to be displayed for SC<50% prescriptions.
       
      4.  For SC>50% prescriptions, supply items and investigational drugs,
      eliminated the display of "This Rx has been flagged by the provider as:
      [COPAY/NO COPAY]" (PSOCPB, PSONEWF, PSORN52).  This message will continue
      to be displayed for SC<50% patients.
      These messages have been eliminated.  Mailman messages will still be
       
      5.  For SC 0-100%, supply items and investigational drugs, modified the 
      wording of the message displayed when a prescription edit that creates a 
      new order is performed (PSOCPB, PSONEWF, PSONEWG).
      generated for the following scenarios:
       
                       SC percentage
                       - age changed   E/I question
           Type        to >0%          added?          Mailman Message sent?
           ---------   --------------  -------------   -------------------------
           NSC         N               N               N        
       
       
           NSC         N               Y               Y only if question was
                                                           not answered before
                                                           the prescription is
                                                           released
       
           NSC         Y               N/A             Y if question was not
                                                           answered before the
                                                           prescription is
                                                           released
      Functional Description:
       
           SC=>0%<50%  N/A             Y               Y  however, NO mailman
                                                            message will be sent
                                                            if any SC/EI = YES
                                                            on the original
                                                            prescription 
       
           For SC>50% prescriptions and if patient has a new SC/EI added, the
           appropriate questions will be asked upon RENEW or COPY of the
           original prescription. At release, a MailMan message will not be sent
      ----------------------
           if the patient, patient status, or drug is exempt from copay.
       
      Because the information requested by these Mailman messages are used to 
      determine the final VA copay and/or insurance billable status, the text 
      and format has changed.  The subject line was changed from "RX COPAY 
      STATUS REVIEW NEEDED" to "PRESCRIPTION QUESTIONS REVIEW NEEDED" and the
      body of the message has additional information.  Also, the eligibility and
      disability information is now included after the patient name. The
      following is an example:
       
      This Outpatient Pharmacy patch PSO*7*219 corrects the following issues:
      Subj: PRESCRIPTION QUESTIONS REVIEW NEEDED (800)  [#164897] 10/07/05@13:39
      37 lines
      From: OUTPATIENT PHARMACY PACKAGE  In 'IN' basket.   Page 1  *New*
      -------------------------------------------------------------------------
       
      PATIENT,TEST  (XXXX)  
      Eligibility: SC LESS THAN 50%     SC%: 10
                   REIMBURSABLE INSURANCE
       
      Disabilities: ARTHRITIS-10%(SC), FOREARM CONDITION-5%(NSC), 
       
                    FOREARM CONDITION-4%(NSC), BENIGN EYE GROWTH-0%(NSC), 
                    LOSS OF FIELD OF VISION-20%(SC), 
       
      Rx# #######B (1)    NO COPAY
      AMITRIPTYLINE 100MG
       
      Due to a change in criteria, additional information listed below is needed
      to determine the final VA copay and/or insurance billable status for this 
      Rx so that appropriate action can be taken by pharmacy personnel.
       
      1.  The Application Program Interface (API) that is provided to 
      Is this Rx for a Service Connected Condition?
       
       
      Enter RETURN to continue or '^' to exit: 
       
       
      Subj: PRESCRIPTION QUESTIONS REVIEW NEEDED (800)  [#164897]   Page 2
      --------------------------------------------------------------------------
       
      This message has been sent to the provider of record, the pharmacist who
      Computerized Patient Record System (CPRS) with the service connection (SC)
      finished the prescription order, and all holders of the PSO COPAY key.
       
      Providers:
      Please respond with your answer to the question(s) as a reply to this
      message. The prescription will be updated by the appropriate staff.
       
      Staff assigned to update the Prescription responses:
      Please use the RESET COPAY STATUS/CANCEL CHARGES option to enter the 
      responses to the questions above, which may result in a Rx copay status
      change and/or the need to remove VA copay charges or may result in a
      
    • 12
      DATE APPLIED:   1999-04-16 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
       1. Changed code at STRX+2^PSOBINGO to prevent long response time when "??" is
      this happens is that the protocol PSO Cancel has three (3) synonyms attached to
      it, DC, Discontinue, and Cancel.  The PSO Cancel synonym will be removed from
      the protocol.  The patch PSO*7*12 will delete the protocol PSO CANCEL and then
      re-install it.  NOIS: WNY-0398-11863 
       
      3. When "DN" (down one line) is entered, or down arrow on the keyboard is 
      pressed to navigate down a line in ListManager on the OP Medications profile
      screen, a message states that "DN is not a valid selection".  NOIS:
      WNY-0398-11862 
       
      entered at the "Enter Rx #:" prompt. This option lists a patient's 
      4. Restored functionality that allows sites to use separate monitors to display
      the same display group data multiple times. In V.6.0, sites could start each
      monitor by selecting the same display group by using the Start Bingo Board
      Display [PSO BINGO START] option. Functionality in V.7.0 was inadvertently 
      removed. When a site attempts to start multiple monitors the message that 
      "Board has already been started!" is displayed.  
       
      Sites that have bingo board setup to auto-start using a dedicated device will
      not be allowed to start the same display group multiple times. This would
      result in a <Device Not Available> error message.  Routine: PSOBGMGR.  NOIS:
      prescriptions after selecting the patient.  The problem is that the screen 
      WNY-0398-12812.  
      looped through the entire PRESCRIPTION file (#52). Routine: PSOBINGO NOIS:
      WNY-0498-10082 
       
      2. When the "C" is entered to copy a prescription, the computer response is 
      "DC", and then the "Are you sure you want to discontinue? No//" prompt is 
      displayed.  "C" should call the "COPY" action, not "Discontinue".  The reason
      
    • 212 SEQ #194
      DATE APPLIED:   2005-12-02 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      PREVENT THE Monthly Rx Cost Compilation OPTION FROM RUNNING MORE THAN 
      ONCE CON-CURRENTLY USING VARIBALE LOCKING TECHNIQUES.
      
    • 211 SEQ #195
      DATE APPLIED:   2005-12-02 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      This patch will modify the order process to require a physician to have a 
      DEA# or VA# to order controlled substances.
      It will also modify Script Talk label so if the instructions are more than
      three lines, the message that the signature is too long will print 
      instead.
      
    • 216 SEQ #196
      DATE APPLIED:   2005-12-02 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
       
      spreadsheet provided for this project dated 2/11/05.
       
      The PSO SITE INPUT TEMPLATE is changed to include the new field. Through
      the PSO SITE PARAMETERS [Site Parameter Enter/Edit] option, the user can
      add, edit, or delete the NCPDP assigned licensed pharmacy number.
       
      When the patch is installed, a post-install job will be queued to
      populate the NCPDP number and a MailMan message will be sent indicating
      the NCPDP numbers for each active division and site. If there is already
      a value in the NCPDP number field, this patch will not overwrite it.
      This patch will create and populate a new NCPDP NUMBER field (#1008) in
       
      Example MailMan message:
      Subj: NCPDP NUMBER POPULATION  [#164410] 08/30/05@21:55  10 lines
      From: PATCH PSO*7*216  In 'IN' basket.   Page 1
      --------------------------------------------------------------------------
      -----
      Patch PSO*7*216 - POPULATE NCPDP NUMBER FIELD POST-INSTALL
      This message is being sent to the installer of the patch and holders of
      the PSORPH key.
       
      the OUTPATIENT SITE file (#59). This field is needed for the Remote Data
      Please validate that the NCPDP number is correct for each active DIVISION 
      and
      SITE NUMBER. If missing or incorrect, enter the correct number using the
      Site Parameter Enter/Edit option.
       
      DIVISION:  EXT  SITE NUMBER:  500  NCPDP NUMBER: 0000001
      DIVISION: TROY  SITE NUMBER:  514  NCPDP NUMBER: NO NUMBER FOUND
      -------------------------------
      This
      patch will create and populate the NCPDP NUMBER field (#1008) in the
      Interoperability Department of Defense (DoD) Clinical/Health Data 
      OUTPATIENT SITE file (#59). This field is needed for the Remote Data 
      Interoperability Department of Defense (DoD) CHDR application.
       
      NCPDP stands for the National Council for Prescription Drug Programs
      formerly referred to as the National Association of Boards of Pharmacy 
      Number (NABP).
       
      The PSO SITE INPUT TEMPLATE is changed to include the new field. Through
      the PSO SITE PARAMETERS [Site Parameter Enter/Edit] option, the user can
      add, edit, or delete the NCPDP assigned licensed pharmacy number.
      Repository (CHDR) application.
       
      When the patch is installed, a post-install job will be queued to 
      populate the NCPDP number and a MailMan message will be sent indicating 
      the NCPDP numbers for each active division and site. If there is already 
      a value in the NCPDP number field, this patch will not overwrite it. 
       
      Example MailMan message:
      Subj: NCPDP NUMBER POPULATION  [#164410] 08/30/05@21:55  10 lines
      From: PATCH PSO*7*216  In 'IN' basket.   Page 1
      --------------------------------------------------------------------------
       
      -----
      Patch PSO*7*216 - POPULATE NCPDP NUMBER FIELD POST-INSTALL
      This message is being sent to the installer of the patch and holders of
      the PSORPH key.
       
      Please validate that the NCPDP number is correct for each active DIVISION 
      and
      SITE NUMBER. If missing or incorrect, enter the correct number using the
      Site Parameter Enter/Edit option.
       
      NCPDP stands for the National Council for Prescription Drug Programs
      DIVISION:  EXT  SITE NUMBER:  500  NCPDP NUMBER: 0000001
      DIVISION: TROY  SITE NUMBER:  514  NCPDP NUMBER: NO NUMBER FOUND
      formerly referred to as the National Association of Boards of Pharmacy
      Number (NABP). The numbers being used to populate the field come from a
      
    • 220 SEQ #197
      DATE APPLIED:   2005-12-02 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      This patch adds the NCPDP (National Council for Prescription Drug 
      Transaction Service) application.
      Programs) number from the OUTPATIENT SITE file (#59) to the Outpatient
      Pharmacy VDEF (Vista Data Extraction Framework) message that sends
      prescription information to the HDR (Health Data Repository). VistA must
      collect and maintain this information and make this number readily 
      available for application interfaces to store and forward to meet 
      requirements for the CHDR (Clinical Data Repository / Health Data
      Repository) project to provide this number to the DoD (Department of
      Defense). This is a required field in the DoD PDTS (Pharmacy Data
      
    • 213 SEQ #198
      DATE APPLIED:   2005-12-02 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      This patch contains Application Program Interfaces (APIs) that will be 
      place, the calling applications will not be required to make any changes, 
      because these APIs will be flexible enough to retrieve the requested data 
      from the new data source, when the time comes.
       
      These are the files that are affected. If any application is making 
      direct global reads or writes to any of these files, they must be 
      replaced by using the APIs exported with this patch.
       
      File Name:                               File Number:
      PRESCRIPTION                                 52
      used by calling applications that currently do direct global reads or 
      PENDING OUTPATIENT ORDERS                    52.41
      RX SUSPENSE                                  52.5
      CLOZAPINE PRESCRIPTION OVERRIDES             52.52
      TPB ELIGIBILITY                              52.91
      RX PATIENT STATUS                            53
      OUTPATIENT SITE                              59
      writes to the Outpatient Pharmacy files.  Since the PRESCRIPTION file 
      (#52), PENDING OUTPATIENT ORDERS file (#52.41), RX SUSPENSE file (#52.5), 
      CLOZAPINE PRESCRIPTION OVERRIDES file (#52.52), TPB ELIGIBILITY file 
      (#52.91), RX PATIENT STATUS file (#53), and OUTPATIENT SITE file (#59) 
      are being replaced as part of the Pharmacy Re-engineering project, any 
      direct M-based global reads or writes to these files must be replaced by 
      calling the APIs provided in this patch. When the new data source is in 
      
    • 218 SEQ #199
      DATE APPLIED:   2005-12-21 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      Issue a warning message and do not allow a refill to be deleted when the 
      refill was sent to an external dispense machine is is still pending
      release from that machine.
      
    • 207 SEQ #200
      DATE APPLIED:   2006-01-12 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      This patch adds the capability of doing order checking between local VA 
      to occur. When turned on, the remote order checking includes checks for
      duplicate drugs, duplicate drug classes, drug interactions, and drug
      allergies.
       
      In addition to the new functionality, there are several help desk tickets
      related to erroneous drug interactions with non-VA meds. The problem
      and fix have been identified as a variable being carried over from prior 
      drug checks that should have been killed in between. Because the routine
      that needs to be fixed is already being changed as part of the RDI
      project, the change to kill the variable at the end of the interaction 
      facilities and remote VA or Department of Defense (DoD) facilities where 
      checking will be included in this RDI patch.
      veterans have received prescriptions. This Remote Data Interoperability 
      (RDI) functionality includes receiving data from the Health Data
      Repository (HDR) in order to perform the order checking against remote
      data.
       
      After the release of this patch, a Computerized Patient Record System
      (CPRS) patch will turn on a flag which enables the remote order checking
      
    • 226 SEQ #201
      DATE APPLIED:   2006-01-12 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      This is the second follow up patch for Outpatient Pharmacy Clinical
       
      released, total un-released, and total cancelled copays.
       
      2.  A summary Mailman message will be sent to Management for their 
      review.  It can be cut and pasted into a .TXT file.
       
      3.  A detailed report by Veteran and fill number can be produced on 
      demand by entering D RPT^PSOCIDC3 at the programmers prompt. 
       
      4.  To check the status of the COPAY CANCEL background job while it is
      running, then type from the direct programmers prompt the command 
      1.  For only edited prescriptions ordered prior to patch PSO*7*143 being 
      D STATUS^PSOCIDC1.
       
      5.  If you need to stop the COPAY CANCEL background job for any reason,
      then from the direct programmers prompt, type the command D STOP^PSOCIDC1.
      installed, the routine that passes information from Outpatient Pharmacy to
      CPRS was passing an extra value and was not passing the Combat Veteran
      indicator.  An edit to days supply, quantity, etc. on a prescription 
      results in a background transmission of data to CRPS.  This type of data
      was passed and updated in CRPS correctly.  Because CPRS does not 
      currently update SC/EI's for edited prescriptions, there were no adverse
      affects.  However, Outpatient Pharmacy sends all data for consistency, and
      this was corrected.  There are no associated remedy tickets for this
      Indicator Data Capture (CIDC) patch PSO*7*143.  The first follow-up patch
      change.
       
      2.  A dollar sign ($) was being displayed for exempt from copay
      prescriptions, and it was being displayed up until the prescription was
      released.  Also, 'COPAY' was being printed on the label for this type 
      of prescription.
       
      3.  Copays were erroneously being charged for non-service connected (NSC)
      prescriptions fills that had an environmental indicator flagged as
      "Yes".   And, copays were charged for some service connected (SC) <50%
      was PSO*7*219, and the follow-up patches were split into two patches in
      prescriptions, and this was due to a "RX COPAY STATUS REVIEW NEEDED"
      Mailman message being sent instead of prompting the user for the SC/EI
      information.  Patch PSO*7*219 corrected this issue, but PSO*7*226 cancels
      the erroneously billed copay(s) as well as restores the copay related
      fields in PRESCRIPTION file (#52).
       
      When installing this patch, the 'copay correction' portion of this patch
      is optional.  Each site can determine if they would be better suited to
      run this automated process or correct them manually.  If you answer N (No)
      to running the copay correction process and change your mind later, then
      order to quickly get the issues resolved by patch PSO*7*219 into the field
      have your IRM run ^PSOCIDC1 from the programmers prompt.  Please keep in 
      mind that by not running the copay correction process that those
      prescriptions where the IBQ node was not stored correctly will continue to
      generate a copay until the fill is copied or renewed.
       
       
      Technical Description:
      ======================
      The following correlates to each sequence in the Functional Description:
       
      immediately.
      1.  In background processing, the PSOHLSN2 routine passes information from
      Outpatient Pharmacy to CPRS when orders are created, edited, copied or
      renewed from backdoor order entry.  Even though CPRS does not 
      currently update SC/EI information for edited prescriptions, Outpatient
      Pharmacy passes them for consistency.  The code that handles pre-CIDC
      edited prescriptions passed an extra value and did not pass the Combat
      Veteran indicator.  Because CPRS does not update SC/EI's for edited
      prescriptions, there were no adverse affects.  A change was made to pass
      the Combat Veteran indicator and not pass the extra value.
       
       
      2.  Because a value denoting copay was allowed to remain in the COPAY 
      TRANSACTION TYPE field (#105) for exempt from copay prescriptions, the
      $ sign was incorrectly being displayed and "COPAY was being printed on 
      the prescription label.  Modifications were made to eliminate the display
      of the $ sign for exempt from copay fills which in turn eliminates the
      printing of 'COPAY' on the label.  Also, modifications were made to
      eliminate this value for NSC and SC<50% prescriptions for all affected
      fills finished between the installation date of patch PSO*7*143 until
      present. This patch re-examines the PRESCRIPTION file (#52) for any NSC
      and SC<50% prescription that has an ICD node and does not have an IBQ
      Functional Description:
      node.  Using the SC/EI answers stored on the ICD node, the IBQ node is
      defined and the COPAY TRANSACTION TYPE field (#105) is defined
      appropriately.
       
      3.  For those prescriptions that were erroneously billed a copay from 
      the installation of PSO*7*143 until present, this patch evaluates any
      prescription that was billed, that has an ICD node, but does not have an
      IBQ node.  Using the SC/EI answers stored on the ICD node, the IBQ node is
      defined.  Then, if a yes answer is defined for any SC or EI, IB is
      notified to cancel copay for the fill.
      =======================
       
      This patch prompts the user during installation when to run the copay
      correction process.  The job name for this process is 'CANCEL COPAY'.  It
      provides summary Mailman messages, and a detailed Results Report by
      Veteran that can be run from Programmer mode.  Also, a Query Status of Job
      function as well as a Stop Job Command function is provided.  See the
      reports and samples section below for details and images of these
      features.
       
       
      This patch PSO*7*226 corrects the following:
      Reports Section:
      ================
       
      * See the sample section below for images of these features.
       
      1.  The CANCEL COPAY process will produce a summary mail message of its 
      findings and display instructions on how to print a detailed report by 
      Veteran.  This MailMan message will be sent to all users that hold the 
      'PSO COPAY' security key and the installer of the patch.  This message 
      contains results by year and 30, 60, and 90 day fills for total 
      
    • 227 SEQ #202
      DATE APPLIED:   2006-02-13 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      The Transitional Pharmacy Benefit (TPB) project that was providing
      Step II-The installation of this patch will automatically inactivate all
      5. This patch will set the AUTOSTART field (#4.5) of the HL LOGICAL LINK
         file (#870) of the PSOTPBAAC Logical Link to "Disabled", to prevent
         restarting of the PSOTPBAAC logical link by TaskMan after a system
         reboot.
       
      6. The TPB data extraction job is queued to run daily and transmit
         data to the AAC every Sunday. This patch will remove the TPB HL7 Data
         Extract/Transmission [PSO TPB HL7 EXTRACT] option from the Task
         Manager.
       
           the TPB functionality.
      Note:
           - The post install routine (PSO227PO) included in this patch
             addresses all items in step II except #3.
           - Most of the TPB routines that are transported in this patch are
             modified to "QUIT" if they are ever called by any other routine.
       
      ***********************************************************************
      ***                    Step I - Manual Step                         ***
      ***********************************************************************
      The data transmission of TPB eligible patient from the TPB ELIGIBILITY
      file (#52.91) is performed by the PSOTPBACC HL7 logical link.
      By now most of the sites would have shut down this link. To check
      whether this link is enabled or shutdown, do the following:
      functionality to furnish medications prescribed by Non-VA Physicians
       
        a) Use the HL7 Main Menu [HL MAIN MENU] option and select the
           Systems Link Monitor [HL MESSAGE MONITOR] option, you should see the
           following screen:
       
                      SYSTEM LINK MONITOR for BIRMINGHAM, AL. (Test System)
                      MESSAGES  MESSAGES   MESSAGES  MESSAGES  DEVICE
           NODE       RECEIVED  PROCESSED  TO SEND   SENT      TYPE     STATE
       
           LL2VISN    51        51         85        51         NC      Open
      needs to be shut down as the period for its eligibility expired on
           NPTF       0         0          163       0          N       Halting
           PSBCOTS1                        2397                         Shutdown
           PSD HLLP                        38                   N       Halting
           PSO DISP   1380      1380       10130     1380       NC      Openfail
           PSO LLP1                        238                  N       Halting
           PSOTPBAA                        28                           Enabled
           PSU SEND                        13
           TEST       21        21         21        21         SS      Idle
       
           Incoming filers running => Zero     TaskMan running
      October 22, 2004.  Inactivation of the TPB functionality will be done in 2
           Outgoing filers running => Zero     ***LINK MANAGER NOT RUNNING!!!***
                                                   Monitor OVERDUE
          Select a Command:
       
        b) If the PSOTPBAAC logical link is enabled then you need to shut down
           the link by doing the following:
           - Use the HL7 Main Menu Option [HL MAIN]
           - Select the Filer and Link Management Options
              [HL MENU FILER LINK MGT]
           - Select the 'Start/Stop Links' option [HL START]
      steps, a manual step and a automatic step.
           - At the 'Select HL LOGICAL LINK NODE: ' prompt, type PSOTPBAAC and
             press enter. The system will prompt 'Okay to shut down this job?',
             answer 'YES' and press enter.
             The system will display the following message:
             'The job for the PSOTPBAAC Lower Level Protocol will be shut down.'
           - To ensure the link is shut down use the Systems Link Monitor [HL
             MESSAGE MONITOR] option and make sure the status is 'Shutdown'
             (step a. above).
      *************************************************************************
      *** Step II - Automated Step                                          ***
       
      *************************************************************************
      1. This patch disables the following menu options by placing them to
         be out of order:
            - TPB HL7 Data Extract/Transmission [PSO TPB HL7 EXTRACT]
            - TPB Institution Letter Enter/Edit [PSO TPB INSTITUTION LETTERS]
            - Report TPB Patients Letters Printed/NOT Printed
               [PSO TPB LETTERS PRINTED REPORT]
            - Transitional Pharmacy Benefit Patient Enter/Edit
               [PSO TPB PATIENT ENTER/EDIT]
            - TPB Patient Report [PSO TPB PATIENT REPORT]
      Step I-To make sure that the Health Level Seven (HL7) data transmission
            - Report of Patients with TPB and Non-TPB Rx's
               [PSO TPB PATIENT RX REPORT]
            - Print TPB Patient Letter(s) [PSO TPB PRINT LETTERS]
            - TPB Rx (Prescription) Entry [PSO TPB RX ENTRY]
       
      2. Inactivation of all active TPB patients
         This patch will scan all the entries in the TPB ELIGIBILITY file
         (#52.91) and will stuff the INACTIVATION OF BENEFIT DATE field (#2)
         of the active patients with today's date and the INACTIVATION REASON
         CODE field (#3) with the code "10-PROGRAM ENDED".
            of TPB eligible patients to the Austin Automation Center (AAC) is
       
      3. When a prescription is discontinued, routine PSOTPCAN is called to
         check if that's the last active TPB prescription for an Active TPB
         patient, and if so, the patient TPB patient is inactivated from TPB
         ELIGIBILITY file (#52.91). Based on the fact that there will be no
         active TPB patient upon installing of this patch, routine PSOTPCAN is
         modified to quit without checking for last active TPB prescription.
       
      4. Prior to this patch, Outpatient Pharmacy software used to be notified
         by the Scheduling software every time a patient has an appointment at a
            shutdown.
         VA clinic. If the patient is eligible for the TPB benefit, the
         appointment was at a clinic defined as primary care for the TPB program
         (determined through a set of clinic stop codes) AND the patient does
         not have any "active" TPB prescription(s) on file, this patient will
         have the TPB eligibility automatically inactivated (introduced by
         PSO*7*160). As all active TPB patient's will be inactivated (item #2
         above), there is no need for this functionality to continue. This patch
         will stop this functionality by removing the PSO TPB SD SUB protocol
         entry from the SDAM APPOINTMENT EVENTS Scheduling protocol.
       
      
    • 229 SEQ #203
      DATE APPLIED:   2006-03-08 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      This is a follow-up patch to PHARMACY REENGINEERING ENCAPSULATION
      DBIA 4822 (PSO525AP) is updated to include omitted fields, Printed (#2) and 
      CMOP INDICATOR (#3) from the RX SUSPENSE file (#52.5).  
       
      DBIA 4827 (PSO59) is updated to include omitted fields, SITE DEA NUMBER (#1)
      and SITE (NATIONAL NAME) (#2) from the OUTPATIENT SITE file (#59).
      CYCLE 2 APIS FOR OUTPATIENT PHARMACY patch (PSO*7*213).
       
      The following changes are made in this path to the following application 
      program interfaces (APIs): 
       
      DBIA 4820 (PSO52API) is updated with newing of variable to prevent possible 
      undefinded errors.  
       
      
    • 2
      DATE APPLIED:   1999-04-16 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      PSO*7.0*1 (1.26.98)
      Medication profiles.  The problem is that prescriptions that had been marked
      as deleted were printing on the short and long profiles.  Routine: PSOP
       
      Fixed problem of incorrect message given to user on the Listman status
      bar saying "Label will Reprint due to edit!", when no data was
      actually changed during the editing of the Rx, and no label will be
      printed.  Routines: PSORXED, PSORXED1.
       
      A NOIS was entered on the Tuscaloosa VAMC local NOIS system describing the
      wording in a prompt as misleading.  The prompt appeared to allow users to 
       
      select multiple entries.  However, this select prompt is meant to allow a 
      single selection and not multiple.  The wording will be changed from 'Select 
      Refill' to 'Select a Refill'.  Routine: PSOORED2.
       
      When prescriptions are returned as not dispensed by CMOP Host, and edited
      by Pharmacy, they are not automatically re-suspended back to CMOP for 
      transmission.  Routines: PSOCMOP, PSOCMOPC, PSORXED, PSORXED1
      This patch installs new functionality that allows the action profile to be
      printed in an 80 column format.  When there's an attached DUE questionnaire
      it too prints in an 80 column format.
      Routines: PSOSD, PSOSD0, PSOSD1, PSOSD2, PSOSD3, PSOSDP, and PSODACT,
      PSOBMST, PSODEDT.
       
      This patch corrects a problem in the compiling of the data for the
      
    • 22
      DATE APPLIED:   1999-04-16 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      1. This patch makes a change to the Barcode Batch Prescription Entry
      for one prescription at the same time, trying to queue the first one and
      suspend the second one to a later date. If this is done, the label that
      prints for the first refill will indicate that it is for the suspended
      refill, instead of the first refill. This patch corrects the problem.
       
      3. This patch fixes an undefined error that can occur when processing
      telephone refill requests for sites that use the Mumps Audiofax software.
      The problem occurs because a required Outpatient Pharmacy site variable can
      possibly be killed in the Action Profiles. Then if the Mumps Audiofax
      telephone refill requests are processed, an error could occur.
      [PSO BATCH BARCODE] option. Prior to this patch, if Renewals were
       
      4. A problem has been reported concerning the PSO EXPIRE PRESCRIPTIONS
      job. This is the daily job that sets prescriptions to an expired status
      the day after the expiration date. The job is initialized using the Expire
      Prescriptions [PSO EXPIRE INITIALIZE] option. A situation could occur
      where the last refill gets deleted if a label has printed and the fill has
      not yet been released. The refill should only get deleted if no label has
      printed for that prescription refill. This patch fixes the problem.
       
      5. A problem has been reported by sites that involves lines overwriting
      processed through this option, and if the first three prompts (Fill Date,
      one another on a terminal. This was caused by the Outpatient Pharmacy
      version 7.0 package making a call to List Manager when the call should not
      have been made. This patch corrects the problem.
       
      6. This patch fixes an undefined error that can occur on the Bingo Board
      display, as a result of an invalid cross-reference.
      Mail/Window, and Queue/Suspend) were answered Today for Fill Date, Mail,
      and Queue, any Consolidated Mail Outpatient Pharmacy (CMOP) prescriptions
      would print locally. This patch makes the change to suspend these
      prescriptions for CMOP.
       
      2. This patch fixes a problem that can occur when processing two refills
      
    • 230 SEQ #204
      DATE APPLIED:   2006-03-08 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      NO ASSESSMENT MADE FOR ALLERGY PRINTING.
      
    • 223 SEQ #207
      DATE APPLIED:   2006-04-10 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      INACCURATE OR NO DATA POPULATING THE CANCEL DATE FIELD
      
    • 235 SEQ #208
      DATE APPLIED:   2006-04-10 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      This patch adds the proper escape sequences to the Outpatient Pharmacy
      messages. This patch fixes that problem.
       
      A request has also been made add two new trigger events, those being when
      the status of a prescription changes from Active to Suspended, and from
      Suspended to Active. This patch add those trigger events.
       
      The name of the Institution has also been added to the message.
      VDEF (Vista Data Extraction Framework) message that sends prescription
      information to the HDR (Health Data Repository). This will help avoid 
      errors that can occur when special delimiting characters are found in 
      Vista fields.
       
      This patch also makes modifications to the trigger events that send 
      prescription information to the HDR, using the VDEF. A problem was
      reported where the Clinical ID information was not being sent in some
      
    • 242 SEQ #209
      DATE APPLIED:   2006-05-04 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      CORRECT THE OPTION PSO INTERNET REFILL, THE "Q" OPTION FROM SENDING
      MULTIPLE RX #'S FROM DIFFERENT PATIENTS TO THE LABEL PRINT ROUTINES.  ALSO
      CHANGE THE DEFAULT "Q" OPTION TO "S" FOR SUSPEND.
      
    • 214 SEQ #210
      DATE APPLIED:   2006-05-04 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      A site reported a problem with the Outpatient prescription status of 
      SUSPENDED. In some cases, it was being interpreted as being 
      non-refillable. A patient safety incident was entered regarding this 
      problem. The interim solution is to modify the Outpatient Pharmacy V. 7.0 
      (OP) Applications Program Interface (API) that returns the prescription
      status. Instead of returning SUSPENDED, the API will return ACTIVE/SUSP. 
      There will be no change to the display in the OP application.
      Remedy Ticket: HD67681
      
    • 148
      DATE APPLIED:   2006-05-25 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      The National Council for Prescription Drug Programs (NCPDP) standard was
        
          the payer's response and move on with the filling process; override
          the reject by resubmitting the claim or postpone the processing of the
          prescription by taking no action when the reject is received. For
          prescriptions that have been electronically submitted to the third
          party payer, an indicator is displayed on the Patient Prescription
          Processing screen. This indicator will take the form of "e" next to
          the prescription number (e.g.,"2090303$e").  
        
          A new section called REFILL TOO SOON/DUR REJECTS (Third Party) has
          been created in the Medication Profile screen to single out
         APPLICATION/VERSION                                  PATCH
          prescription that had an electronic claim rejected by third party
          payers for REFILL TOO SOON or DUR reasons. Prescriptions under this
          section have certain restrictions. Basically, they cannot be renewed,
          refilled, reprinted, copied or released until the REJECT is resolved.
          When an individual prescription is selected, the user will have a new
          hidden option called REJ - View Reject, which will allow them to
          resolve the REJECT and remove it from the REFILL TOO SOON/DUR REJECTS
          (Third Party) section.
         
          The prescription release option was modified to perform NDC (National
         -----------------------------------------------------------------
          Drug Code) validation for electronically billable prescriptions. When
          the user selects a new NDC a new claim is submitted to the payer
          before the prescription is released.
         
          In the OP Medications screen, a new DAW CODE field (#81) of the 
          PRESCRIPTION file (#52) was created for electronically billable
          prescriptions and can be edited by selecting '21' at the 'Select
          Action' prompt. For non-electronically billable prescriptions this
          field is not displayed at all.
          
         OUTPATIENT PHARMACY (OP) V. 7.0                      PSO*7*148
          When the electronically billable prescription is released, this option
          will allow the user to edit the NDC code for the prescription. In the
          OP Medications screen the NDC field is listed under the Drug field
          and can be edited by selecting '2' to edit the drug at the 'Select
          Action' prompt. For sites that do not allow Drug editing, the option
          '2' will allow editing of the NDC only.
       
      2.  Return Medication to Stock [PSO RETURNED STOCK] option 
       
          The Return Medication to Stock function was modified to notify the
         INTEGRATED BILLING (IB) V. 2.0                       IB*2*276
          third party payer that a previously billed prescription was not
          actually filled. If the prescription was previously billed to a third
          party payer and a payable response was received, the claim will be
          reversed, and the pharmacy user will see messaging stating that the
          third party claim was submitted for reversal. If a claim for the
          prescription was previously rejected by the third party payer, the
          user will see a message indicating that no reversal was required. If
          the prescription was not previously billed to a third party payer, no
          message regarding electronic billing will be displayed.
       
         PHARMACY DATA MANAGEMENT (PDM) V. 1.0                PSS*1*90
      3.  Delete a Prescription [PSO RXDL] option 
       
          The message for Delete a Prescription was modified to perform in the 
          same manner as the Return Medication to Stock function described
          above.
        
      4.  Pull Early from Suspense [PSO PNDRX] option 
        
          The Pull Early from Suspense function was modified to submit a third 
          party claim for the prescription. A message will display to notify the
         CONSOLIDATED MAIL OUTPATIENT PHARMACY (CMOP) V. 2.0  PSX*2*48
          user of the status of the claim as it is going through the submission 
          process.  
       
      5.  Print from Suspense File [PSO PNDLBL] option 
       
          This option was modified to submit third party claims in the same
          manner as stated above except the Print from Suspense File function
          will be performed in the background. No user interaction will occur.
        
      6.  ePharmacy Menu [PSO EPHARMACY MENU] menu
         ACCOUNTS RECEIVABLE (AR) V. 4.5                      PRCA*4.5*230
       
          This new menu was created for electronic billing related options. It
          is being placed under the Rx (Prescriptions) [PSO RX] menu. Two new
          options are being added under this new menu:
       
          6.1 Third Party Payer Rejects - Worklist [PSO REJECTS WORKLIST] option
       
              This option is used to process third party payer rejects that have
              clinical significance. For now, only DUR (Drug Utilization Review)
              and REFILL TOO SOON rejects are being considered as having
         ELECTRONIC CLAIMS MANAGEMENT ENGINE (ECME) V. 1.0    BPS*1*1
              clinical significance.
       
          6.2 Third Party Payer Rejects - View/Process [PSO REJECTS 
              VIEW/PROCESS] option
       
              This option performs the same functionality as the option above.
              However, the user has more filtering capabilities through this
              option. In addition, closed/resolved rejects can only be viewed by
              using this option.
                
       
      7.  Release Medication [PSO RELEASE] option 
       
          The prescription release process was modified to perform NDC (National
          Drug Code) validation for electronically billable prescriptions. When
          the user selects a new NDC, a new claim is submitted to the payer
          before the prescription is released. Besides this option, the 
          prescription can be released from the Medication Profile screen and
          from the Outpatient Rx's [PSD OUTPATIENT] option in the Controlled
          Substances application.
         
      adopted under the Healthcare Insurance Portability and Accountability Act
      Veterans Health Information Systems and Technology Architecture (VistA)
      8.  View Prescriptions [PSO VIEW] option
        
          This option was changed to include two new sections: ECME Log and ECME
          REJECT Log. Information about third party payer submission and rejects
          will be displayed under these sections.
          
      9.  Edit Prescriptions [PSO RXEDIT] option
       
          The new DAW CODE field (#81) of the PRESCRIPTION file (#52) was
          created for electronically billable prescriptions and can be edited
      software applications and infrastructure were enhanced, in order to allow the
          through this option. For non-electronically billable prescriptions,
          the field is not displayed at all.
          
          Once an electronically billable prescription is released, this option
          will allow the user to edit the NDC code. The NDC code is displayed on
          the screen just below the Drug field, and can be edited by selecting
          field '2' to edit the Drug. For sites that do not allow Drug editing,
          the field '2' can be used to edit the NDC code only.
       
      10. The NDC field (#4) under the CMOP EVENT multiple (#52.01) of the
      electronic transmission of outpatient pharmacy prescription claims (WINDOW
          PRESCRIPTION file (#52) has been renamed to NDC RECEIVED. This field
          holds the NDC that was received from the CMOP facility with the
          dispensing message. The renaming was necessary due to the addition of 
          the NDC SENT field (#12) under the same multiple that is being created
          by this project (see below item 11).
        
      11. A new NDC SENT field (#12) is being created under the CMOP EVENT 
          multiple (#52.01) of the PRESCRIPTION file (#52), to store the NDC
          that was transmission to CMOP. This field is used for electronic 
          billing purposes to analyze the difference between the NDC sent to
      and MAIL fills) to third party payers via the network connections available
          CMOP and the actual dispensed NDC by the CMOP facility.
       
      12. A new DAW CODE field (#81) is being created on the PRESCRIPTION
          file (#52) and also under the REFILL multiple (#52.1) of the
          PRESCRIPTION file (#52). This field contains the NCPDP DAW used in the
          electronic claims submission to third party payers (insurance
          companies).
       
      13. A new RE-TRANSMIT FLAG field (#82) is being created on the 
          PRESCRIPTION file (#52) and also under the REFILL multiple (#52.1) of 
      through the Austin Automation Center (AAC). VistA will be enhanced to receive
          the PRESCRIPTION file (#52). This field is used to indicate that a
          claim should be electronically re-transmitted to the 3rd party payer
          (insurance company). It will be primarily used by CMOP and local mail
          prescriptions.
         
      14. A new multiple REJECT INFO field (#52.25) has been created on the
          PRESCRIPTION file (#52) to store information about DUR and Refill Too
          Soon Rejects returned by 3rd party payers. 
          The following fields are part of this multiple:
       
      electronic adjudicated responses from the third party payers, which include
              .01   NCPDP REJECT CODE      
                1   DATE/TIME DETECTED     
                2   PAYER MESSAGE          
                3   REASON                 
                4   PHARMACIST             
                5   FILL NUMBER            
                6   GROUP NAME             
                7   PLAN CONTACT           
                8   PLAN PREVIOUS FILL DATE
                9   STATUS   
      real-time processing for Drug Review Utilization and Refill Too Soon rejects.
               10   CLOSED DATE/TIME 
               11   CLOSED BY
               12   CLOSE REASON
               13   CLOSE COMMENTS
               14   REASON FOR SERVICE CODE
               15   PROFESSIONAL SERVICE CODE
               16   RESPONSE ID
               17   OTHER REJECTS     
               18   DUR TEXT          
               19   RESULT OF SERVICE CODE
      Reject information will be displayed to the pharmacist as the prescription is
               20   INSURANCE NAME    
               21   GROUP NUMBER      
               22   CARDHOLDER ID 
               23   RE-OPENED
       
          Two new cross-references named "REJDAT" and "REJSTS" were created for
          this multiple in the PRESCRIPTION file (#52). The "REJDAT" uses the
          DATE/TIME DETECTED field (#1) and the "REJSTS" uses the STATUS field
          (#9).
      being processed. The pharmacist will have the capability to take the
      appropriate action to ensure patient safety or to override the reject and
      (HIPAA) for pharmacy claims. The HIPAA NCPDP - GLOBAL project involves six
      resubmit the claim to the payer for payment. When a status of "PAYABLE" is
      returned by the payer for a released prescription, VistA will automatically
      create the bill in IB, authorize it and immediately create the receivable in
      the AR application. Since the exact amount being paid by the payer is known,
      a decrease adjustment will be automatically generated and applied so that the
      receivable is equal to the net amount due from the payer.
       
      The system also provides electronic payment matching capability (for
      electronically billable outpatient pharmacy prescriptions) using the existing
      Electronic Data Interchange (EDI) Lockbox functionality which processes other
      different applications that have been significantly changed to enable VA
      electronic payments from third party payers. This real-time electronic claims
      processing capability will be provided in accordance with the HIPAA, EDI
      and the NCPDP mandated format standards, specifically NCPDP Telecommunication
      Standard V. 5.1. Additional functionality delivered with this project 
      includes:
       
         . Auto-Release/Outpatient Pharmacy Automation Interface (OPAI) Integration.
         . Back-billing capability to allow electronic billing of claims from within
           the IB application.
         . Capability to MOVE a group of subscribers from one insurance plan to
      Medical Centers to perform third party electronic billing for prescriptions
           another while automatically "expiring" the old plan, which is a major
           time saver.
         . Pharmacy Dispensed As Written (DAW) prescription processing.
        
      Overview of the Process:
        
      When a prescription is about to be filled and dispensed by the pharmacy, the
      OP application submits the prescription to the new ECME application. ECME then
      contacts IB to verify whether or not the prescription is electronically
      billable. If so, ECME gathers the information necessary to generate a NCPDP
      using the NCPDP standard. 
      claim. The claim information is passed to the VistA Health Level Seven (HL7)
      package. The HL7 package then sends the billing information to the AAC, where
      it is routed to the corresponding third party insurance via Emdeon (formerly
      WebMD).
        
      Once the payer processes the information, the response coming back from the
      payer is passed back to the site that made the request, and the information
      is stored in the ECME package. If the third party payer accepted the claim,
      the adjudicated information is passed along to IB. If the claim was rejected
      the problem can be worked on and a new claim can be submitted to the payer.
       
        
      For electronically billable CMOP prescription processing, the third party
      claim is sent before the prescription information is transmitted to the
      CMOP facility to be filled. Once the adjudicating response is electronically
      received from the third party payer, if there are no Drug Utilization Review
      or Refill Too Soon rejects, the prescription is then transmitted to the CMOP
      facility. When the CMOP center sends the dispensing information back to VistA,
      the National Drug Code (NDC) information is checked against the NDC sent to
      the third party payer and, if different, a new claim is generated in the
      background and is sent to the third party payer. In case the CMOP facility
      Below is a list of all the applications involved in this project along with
      indicates that it is unable to fill a "PAYABLE" prescription fill, a reversal
      is automatically submitted to the third party payer for the corresponding
      fill.
       
      This patch modifies the OP application to perform real-time electronic claim
      submission to third party payers. It will also enable OP users to see and act
      on third party payer rejects such as Drug Utilization Review (DUR) and Refill
      Too Soon rejects along with their daily normal prescription processing 
      activities. The following areas of OP have been changed:
        
      their patch number:
      1.  Patient Prescription Processing [PSO LM BACKDOOR ORDERS] option 
       
          At the point that the prescription is verified, the New Order, Edit,
          Renew, Refill, and Pull Early from Suspense functions will begin the
          third party billing evaluations. If IB determines that the
          prescription is third party billable, a message will be displayed on
          the user's screen stating that the claim is being submitted to ECME
          and it will also show the progress of the claim. If the payer rejects
          the claim for DUR or Refill Too Soon, the payer's information will be
          displayed, and the user will be given the opportunity to either ignore
      
    • 149 SEQ #212
      DATE APPLIED:   2006-07-11 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      The Registration application has released enhancements designed to
      functionality made available by the Registration application. More
          IMPORTANT FUNCTIONALITY CHANGE:
          ==============================
          - A new prompt "Do you want to update the Permanent address/phone?
            //N" will be displayed before editing the permanent address/phone
            information to give the user a chance to skip it. If the user
            responds with "N", the control will go to the CNH CURRENT field
            prompt. Otherwise, the user will go through editing the
            address/phone information fields.
       
          - When entering a new or updating an existing patient permanent
      specifically, the update of the patient permanent address through the
            address, the information is not saved to the database until the
            prompt above "Are you sure that you want to save the above changes?"
            is answered YES. If the application times out or an '^' (up-arrow)
            is entered in any of the permanent address fields above, the changes
            are NOT saved.
      Outpatient Pharmacy application will be enhanced with the new 
      functionality that was recently released by the Registration application
      with the patch DG*5.3*522.
       
      For sites that have patch IVM*2*108 installed, the address history will
      captured in the IVM ADDRESS UPDATE LOG File (#301.7).
       
      Two places in the Outpatient Pharmacy application will be affected by
      provide a more accurate and cleaner update of the patient address. One
      this change:
       
       1) Menu option: Update Patient Record    [PSO PAT]
       2) Patient Information screen, option PU - Patient Record Update
       
       Note: The Patient Information screen can be reached through the menu 
             options Patient Prescription Processing [PSO LM BACKDOOR ORDERS]
             and Complete Orders from OERR [PSO LMOE FINISH].
       
      The examples below show how the patient permanent address edit was before
      of the things included in the enhancements is the automatic population
      and how it is going to be changed after this patch is installed:
        
          BEFORE THIS PATCH:
          =================
           :           :            :            :
           :           :            :            :
          STREET ADDRESS [LINE 1]: 123 FAKE ST <RET>
          STREET ADDRESS [LINE 2]: <RET>
          STREET ADDRESS [LINE 3]: <RET>
          CITY: PLANO <RET>
      of city, state, and county based on entry of a zip code. For more
          STATE: TEXAS <RET>
          ZIP+4: 75024 <RET>
          COUNTY: COLLIN <RET>
               1   COLLIN       085
               2   COLLINGSWORTH       087
          CHOOSE 1-2: 1 <RET>  COLLIN     085
          PHONE NUMBER [RESIDENCE]: 972-555-1234 <RET>
          CNH CURRENT:
           :           :            :            :
           :           :            :            :
      detailed information about this and the other enhancements recently 
       
          AFTER THIS PATCH:
          ================
           :           :            :            :
           :           :            :            :
          Do you want to update the Permanent address/phone? NO// YES
          STREET ADDRESS [LINE 1]: 123 FAKE ST <RET>
          STREET ADDRESS [LINE 2]: <RET>
          ZIP+4: 75024 <RET>
       
      released by the Registration application, please refer to the patch 
               Select one of the following:
       
                    1         PLANO*
                    99        FREE TEXT
       
          CITY: // 1  <RET> PLANO*
          STATE: TEXAS <DISPLAY>
          COUNTY: COLLIN <DISPLAY>
          PHONE NUMBER [RESIDENCE]: 972-555-1234 <RET>
          PHONE NUMBER [WORK]: 972-555-4321 <RET>
      description of DG*5.3*522.
          BAD ADDRESS INDICATOR: ? <RET>
       
          Please enter 1 if the address is 'UNDELIVERABLE', 2 if the patient
          is 'HOMELESS', or 3 for 'OTHER' bad address reasons.
          Choose from: 
          1        UNDELIVERABLE
          2        HOMELESS
          3        OTHER
       
       
        
          BAD ADDRESS INDICATOR:  <RET>
          Are you sure that you want to save the above changes? NO// YES <RET>
          Change saved.
       
          CNH CURRENT:
           :           :            :            :
           :           :            :            :
       
       
          NOTES:
      This patch is responsible for updating Outpatient Pharmacy with the new
          =====
          1) Multiple ":"'s above indicate that other fields have been 
             suppressed to abbreviate the example.
          2) <RET> indicates the <RETURN> key.
          3) <DISPLAY> indicates that the field was displayed and was not 
             editable.
          4) BAD ADDRESS INDICATOR is a new field introduced by the 
             Registration application. For more information on this field,
             please refer to the documentation for that application.
       
      
    • 232 SEQ #213
      DATE APPLIED:   2006-07-11 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      CORRECT SEVERAL PROBLEMS INCLUDING AMIS COMPILER TO FIND AND INCLUDE RX'S 
      THAT HAVE A DATE WITH NO TIME FOR RELEASE/DATE FIELD IN PRESCRIPTION FILE,
      A NULL SUBSCRIPT ERROR DURING BINGO BOARD STARTUP, DO NOT MAIL ISSUE WHEN
      OPAI SENDS HL7 MESSAGE, AND INCREASE DNS PORT NUMBER FIELD IN OUTPATIENT
      SITE FILE.
      
    • 237 SEQ #214
      DATE APPLIED:   2006-08-24 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      CORRECT CLOZAPINE OVERRRIDE LIST ERROR AND CORRECT FINISHING OF PENDING 
      ORDERS THAT ARE OLDER THAN A YEAR AND ARE BASICALLY EXPIRED.
      
    • 244 SEQ #215
      DATE APPLIED:   2006-08-24 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      Prevent newly Discontinued Rx's due to edit from being sent to the
      External Dispense Machines.
      
    • 24 SEQ #21
      DATE APPLIED:   1999-05-10 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      1. This patch makes it possible to exempt certain Ward Locations from the
      Autocancel Rx's on Admission [PSO AUTOCANCEL1] option.
       
      2. This patch adds a Requesting PROVIDER prompt to the discontinue
      and speed discontinue dialogue. When an order is discontinued, this new
      prompt will be asked after the Nature of Order prompt. The requesting
      provider information will be used to update the Computerized Patient
      Record System (CPRS) order. The CPRS order will now reflect the correct
      provider that requested the discontinue of the order. This new prompt
      will only be given when an order is discontinued through one of
      the Discontinue ListMan actions, or the Discontinue Prescription(s) [PSO
      Autocancel Rx's on Admission [PSO AUTOCANCEL1] option. When that job runs,
      C] option.
       
      3. This patch fixes a problem that can occur when removing a prescription
      from Hold in the Patient Prescription Processing [PSO LM BACKDOOR ORDERS]
      option. This problem can only occur for sites that are using vendor
      software to bill prescriptions for Tricare. When removing a prescription
      from Hold, the software currently checks to see if the prescription
      is eligible for Tricare billing, and can possibly resubmit the
      prescription for Tricare billing. A problem can occur if it continues
      to be rejected by Tricare. This causes the prescription to remain in a
      and it comes across a patient that is on a Ward Location designated as
      Hold status, and there is no way to print a filling label for that
      prescription. After this patch is installed, any prescription that is
      removed from Hold will not automatically go through the Tricare process.
      These prescriptions will either print locally or suspend. Then it would
      be possible to manually resubmit billing for that prescription, but now
      a filling label will first print for these prescriptions.
       
      4.This patch fixes an undefined error that can occur when trying to
      reinstate a prescription for a deceased patient.
      exempt from the Autocancel Rx's on Admission [PSO AUTOCANCEL1] option, the
      prescriptions for that patient will not be canceled. To designate a Ward
      Location as exempt from this job, use the Site Parameter Enter/Edit [PSO
      SITE PARAMETERS] option. Under the Outpatient System Parameters section of
      that option, there is a field called EXEMPT WARD FROM AUTOCANCEL (#40.19),
      and here you can designate any number of Ward Locations as exempt from the
      
    • 247
      DATE APPLIED:   2006-09-23 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      This patch supports the National Council for Prescription Drug Programs (NCPDP) 
      instructions please refer to the installation steps provided in each of the 
      stand-alone patches.
       
      Enhancements included in the release of the six patches are a new option that 
      will enable the user to reopen a closed Electronic Claims Management Engine
      (ECME) claim; updates to the Rx Activity Log; and permanent storage of Claims
      activity information as reported by the ECME Billing Events Report.   
          
      This patch modifies the Outpatient Pharmacy (OP) V. 7.0 application in the
      following areas: 
      standard which was adopted under the Healthcare Insurance Portability and 
       
      1. When the DAW CODE was edited on a released Consolidated Mail Outpatient 
         Pharmacy (CMOP)  prescription it was not triggering an automatic claim 
         reversal/re-submit to the third party payer. This patch corrects the 
         problem. Editing the DAW CODE on a released CMOP prescription will work
         similar to editing a WINDOW prescription, it will reverse/re-submit a
         claim.
       
      2. The ECME Reject section of the prescription activity log was changed in
         the following ways: 
      Accountability Act (HIPAA) for pharmacy claims. This patch is one of six to be
         
         2.1) The column header "Date/Time" was changed to "Date/Time Rcvd" because
              a new column is being created (see 2.3).
         2.2) "DRUG UTILIZATION REVIEW" in the "Reject" column will now display as
              "DUR" for space saving purposes.
         2.3) A new column is being created called "Date/Time Resolved" on the
              right hand side to display the Date/Time the reject was resolved.
       
      3. The option Third Party Payer Rejects - Worklist [PSO REJECTS WORKLIST]
         is being changed to allow the user to print a label for window
      released.  Three patches will be released in a KIDS multi-build distribution 
         prescriptions after a reject is resolved. The label print prompt will only
         be available if the prescription is active and no label was printed for
         the fill which reject was resolved. The following prompts will be 
         presented to the user:
       
            Print Label? YES // YES
          
            Select LABEL DEVICE:
       
      4. When the user resolved a third party reject using the 'Override Reject'
      containing: BPS*1*3, PSO*7*247, and IB*2*342.  Three patches will be released
         action from the Third Party Payer Rejects - Worklist [PSO REJECTS 
         WORKLIST] option, the entry in the Prescription activity log 
         corresponding to this event was not displaying the NCPDP override codes
         entered by the user. Before this fix the comment displayed as 
         'Submitted to ECME:REJECT WORKLIST-E PAYABLE'. After this patch is
         installed the comment will be logged as 'Submitted to ECME:REJECT 
         WORKLIST-DUR OVERRIDE CODES(NN/AS/1B)-E PAYABLE', as an example.
      individually and they are: PRCA*4.5*247, PSX*2*62, and PSS*1*115.  There is no 
      recommended order to installing the stand-alone patches and they can be 
      installed independently of the multi-build as there is no dependency between 
      the multi-build distribution and the stand-alone patches.  For more specific 
      
    • 222 SEQ #217
      DATE APPLIED:   2006-09-23 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      The Department of Veterans Affairs National Clozapine Coordinating Center
      read the patch description of YS*5.01*90 for complete details of this new
      enhancement.
       
      This Outpatient Pharmacy patch PSO*7*222 contains the following
      must-do-work enhancements for Clozapine dispensing:
       
      1. Adjust the business rules to disallow prescription processing without
         override if 3500/mm3>WBC>3000/mm3 and 2000/mm3>ANC>1500/mm3.
         These levels require twice weekly blood testing until the WBC
         stabilizes above 3500/mm3 and ANC above 2000/mm3 with no signs of
      (NCCC), is requesting modifications to Veterans Health Information Systems
         infection.
      2. Modify routine logic to recognize the new monthly status and apply the
         appropriate restrictions for lab draw checks.
      3. Add a new field to the PRESCRIPTION file (#52) to store ANC value and
         modify routine logic to require both a WBC and ANC be drawn and
         reported before drug dispensing is allowed.
      4. Modify routine logic to prevent local users from editing the Patient
         Status within Clozapine module.
       
      This patch transports the following fields:
      and Technology Architecture (VistA) Outpatient Pharmacy and Mental Health
      1. The field length of the WBC RESULT field (#302) of the PRESCRIPTION
         file (#52) is modified from 3 to 5 digits to accommodate values up to
         99999 as these values will be stored in 1000s.
      2. A new field ANC RESULTS field (#304) is added to the PRESCRIPTION file
         (#52) to store the ANC test value.
      3. The field name of REASON FOR LOCKOUT field (#4) of the CLOZAPINE
         PRESCRIPTION OVERRIDES file (#52.52) is changed to REASON FOR OVERRIDE.
         The set of codes have been modified and three new codes were added. The
         modified Data Dictionary (DD) is as follows:
       
      applications to meet revisions in the Food and Drug Administration (FDA)
         52.52,4       REASON FOR OVERRIDE    0;5 SET (Required)
                              '1' FOR NO WBC IN LAST 7 DAYS;
                              '2' FOR NO VERIFIED WBC;
                              '3' FOR LAST WBC RESULT < 3500;
                              '4' FOR 3 SEQ. WBC DECREASE;
                              '5' FOR LAST ANC RESULT < 2000;
                              '6' FOR 3 SEQ. ANC DECREASE ;
                              '7' FOR NCCC AUTHORIZED;
       
       
      monitoring requirements for blood monitoring in patients being treated
      The Outpatient Pharmacy patch PSO*7*227, TRANSITIONAL PHARMACY BENEFIT
      (TPB) inactivation, was placing the TPB HL7 Data Extract/Transmission [PSO
      TPB HL7 EXTRACT] option out of order. Sites testing patch PSO*7*227
      recommended that we remove this task totally from the OPTION SCHEDULING
      file (#19.2). Therefore, a post-install routine (PSOP222) is included in
      this patch PSO*7*222 to delete the TPB HL7 Data Extract/Transmission [PSO
      TPB HL7 EXTRACT] option from the OPTION SCHEDULING file (#19.2).
      The post-install routine will also provide the following changes:
      1. As the patch PSO*7*227 inactivated the TPB functionality, the security
         access codes for the TPB ELIGIBILITY file (#52.91) still remains open.
      with Clozapine.
         These codes will be changed to "@" sign restricting access to
         programmers only.
      2. The read access code of the PRESCRIPTION REFILL REQUEST file (#52.43)
         is currently set to "@" sign (programmer access). As per the
         Electronic, Error and Enhancement Report (E3R) 19725 request, this will
         be changed to "Pp" (Pharmacy Package) access.
       
      This patch PSO*7*222 is associated with the MENTAL HEALTH V. 5.01 patch
      YS*5.01*90 and patch YS*5.01*90 is a required patch for PSO*7*222. Please
      
    • 233 SEQ #218
      DATE APPLIED:   2006-11-22 22:20:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      This patch enhances the usage of Application Program Interfaces (APIs) to
      the patient's address when appropriate. If the patient has the BAD ADDRESS
      time the label printed.
       
      6. In the Complete Orders from OERR [PSO LMOE FINISH] option, after the 
      prompt to display the medication profile and after the patient name and 
      social security number are shown, if the patient's address is flagged 
      with a Bad Address Indicator, a warning message is displayed. If the 
      temporary address is active, that information is displayed. The user
      will not be prompted to update the address.
       
      Example:
      INDICATOR field set and no active temporary address, this is referred to
      Do you want to see Medication Profile? Yes// NO
       
                PERPATNM,FRED (666-00-0777)
       
              WARNING: The patient address is indicated as a bad
                       address (UNDELIVERABLE).
                       * Temporary address is active *
       
      Press Return to continue: 
       
      as a BAI condition in this description.
      7. The Action Profile (132 COLUMN PRINTOUT) [PSO ACTION PROFILE] option 
      is modified to display **BAD ADDRESS INDICATED-(REASON)" where REASON is 
      UNDELIVERABLE, HOMELESS, or OTHER.
       
      8. Although the Transitional Pharmacy Benefits (TPB) options have been 
      disabled, to keep the changes consistent, the routine to print TPB letters
      is modified to look at the BAI condition and print "** BAD ADDRESS
      INDICATED ** if applicable.
       
      9.The Patient Address Changes Report [PSO ADDRESS CHANGE REPORT] option 
       
      is modified to display additional mailing address-related fields from the
      PATIENT file (#2) and some fields related to the mail setting from the
      PHARMACY PATIENT file (#55). The user should use FileMan to turn 
      on auditing for the following fields in order for them to be displayed 
      in this report. (Fields added to this report by this patch are indicated
      with a "*" in front of the field name).
       
      a. For the PATIENT file (#2), turn on auditing for:
       
      STREET ADDRESS [LINE 1] field (#.111)
      Note: Related changes for the Outpatient Pharmacy Automation Interface
      ZIP+4 field (#.1112)
      STREET ADDRESS [LINE 2] field (#.112)
      STREET ADDRESS [LINE 3] field (#.113)
      CITY field (#.114)
      STATE field (#.115)
      ZIP CODE field (#.116)
      * BAD ADDRESS INDICATOR field (#.121)
      * TEMPORARY ADDRESS ACTIVE? field (#.12105)
      TEMPORARY STREET [LINE 1] field (#.1211)
      TEMPORARY ZIP+4 field (#.12112)
      (OPAI) and Consolidated Mail Outpatient Pharmacy (CMOP) will be done in
      TEMPORARY STREET [LINE 2] field (#.1212)
      TEMPORARY STREET [LINE 3] field (#.1213)
      TEMPORARY CITY field (#.1214)
      TEMPORARY STATE field (#.1215)
      TEMPORARY ZIP CODE field (#.1216)
      * TEMPORARY ADDRESS START DATE field (#.1217)
      * TEMPORARY ADDRESS END DATE field (#.1218)
       
      b. For the PHARMACY PATIENT file (#55), turn on auditing for:
      * MAIL field (#.03)
      patches PSO*7*200 and PSX*2*54.
      * MAIL STATUS EXPIRATION DATE field (#.05)
       
      10. By request of a pharmacy workgroup, two new codes were added to the
      PRESCRIPTION file (#52) HOLD REASON field (#99):
                                      '7' FOR BAD ADDRESS; 
                                      '8' FOR PER PATIENT REQUEST; 
       
       
      11. A Bad Address Reporting Main Menu [PSO BAI REPORT] option is added 
      under the Output Reports [PSO OUTPUTS] option which includes the
       
      following:
      a. Bad Address Suspended List [PSO BAI SUSPENDED] option
      This option identifies prescriptions for veterans with a BAI Condition
      giving the opportunity to be proactive regarding prescriptions that when
      Printed or Pulled Early from Suspense, would be unable to be mailed.
       
      b. List Prescriptions Not Mailed [PSO BAI NOT MAILED] option  
      This option provides a report of prescriptions with a routing of Mail that
      were not mailed due to a bad address. This is based on the last label
      activity entry being flagged as a bad address and a route other than
       
      "WINDOW". If the address is corrected and a label reprinted, this
      prescription would no longer show on the report.
       
      12. The View Prescriptions [PSO VIEW] option is changed to show Bad 
      Address Indicated if BAI flag is set and no active temporary address. 
      Example:
      VIEW PRESCRIPTION:    713449A     ACETAMINOPHEN 325MG TAB  
       
                               
      Rx View (Active)              Aug 30, 2006@18:44:09          Page:    1 
      The following changes are made in this patch:
      of    5 
      OUTPATIENT,ONE ** BAD ADDRESS INDICATED-(UNDELIVERABLE)
        PID: 666-00-0146                                 Ht(cm): _______ 
      (______)   
        DOB: DEC 00,1953 (52)                             Wt(kg): _______ 
      (______)   
      the Registration Package V. 5.3 to check the setting of the BAD ADDRESS
       
      1. A new security key PSO ADDRESS UPDATE is added. Either the EDIT 
      PATIENT DATA field (#.123) in the PSO SITE file (#59) must be set to 
      "Yes" or the user must have this new security key in order to be
      prompted to update the address (permanent and/or temporary addresses).
       
      2. When selecting a patient name in the Patient Prescription Processing 
      [PSO LM BACKDOOR ORDERS] option, if the patient's address is flagged with
      a Bad Address Indicator, then a warning message is displayed. If the 
      EDIT PATIENT DATA is set to Yes or the user holds the new
      INDICATOR field (#.121) in the PATIENT file (#2) and to update the
      PSO ADDRESS UPDATE security key, he will be asked if he wants to update
      the patient's address. If there is a valid temporary address, a message to
      that effect is displayed before the prompt to update the address.
       
      Example:
        PSOOUTPATIENT,ONE (000-00-0777)
       
              WARNING: The patient address is indicated as a bad
                       address (UNDELIVERABLE).
                       * Temporary address is active *
      permanent and temporary addresses. The BAD ADDRESS INDICATOR (referred to
      Do you want to update the address/phone? N// YES
      Update (P)ermanent address, (T)emporary, or (B)oth: BOTH// 
       
      3. In the Medication Profile [PSO P] option, the Patient Prescription 
      Processing [PSO LM BACKDOOR ORDERS] option, and the Complete Orders from
      OERR [PSO LMOE FINISH] option, the following changes were made:
      a. When the medication profile is displayed, the letter "B" (for bad
      address) is added to the status column if the last label activity for that
      prescription indicated a BAI condition. If the address is corrected and
      label reprinted, "B" no longer appears on the profile.
      as BAI in this description) is one of the fields presented when using the
       
      Example:
       
                          Medication Profile Sorted by ISSUE DATE
                                                               REF
       Rx#         Drug                                     ST REM  Issued  
      Last Fill
      --------------------------------------------------------------------------
      -----
      $300920A     ACETIC ACID 2% OTIC SOL 15 ML            DCB  5 07-20-06 
      API to update permanent address fields.
      07-20-06
           QTY: 1             SIG: INSTILL 2 DROPS AD AS NEEDED  
      $100002514C  SIMVASTATIN                               S   5 06-29-06 
      12-10-06
           QTY: 150           SIG: ONE IV TWICE A DAY
      $300927      UREA 10% LOTION                          AB   5 06-29-06 
      06-29-06
           QTY: 1             SIG: APPLY SPARINGLY TO AFFECTED AREA AS NEEDED
       
      b. If there is no ending date for the temporary address, the fact that the
       
      address was temporary was not being displayed in the patient profile.
      This patch adds the temporary indication including the text "(no end
      date)" if no ending temporary date exists.
       
      Example:
       
      Disabilities:                                                             
           
            (Temp Address from AUG 28,2006 till (no end date))
      LINE1                  
      Outpatient Pharmacy V. 7.0 options are modified to not print the 
      ANYTOWN                                       PHONE: 
      555-1212                   
      TEXAS  
      77379                                                                    
       
       
      4. The Input Template [PSO OUTPT] is modified to remove temporary
      address update prompts. Instead, a new API to the Registration Package 
      V. 5.3 is used for updating temporary address for the Update Patient
      Record [PSO PAT] option and the Patient Record Update [PU] action (within
      patient's address if a bad address is indicated and to prompt to update
      the patient profile). This option and action are also changed to check for
      the user holding the PSO ADDRESS UPDATE security key or the EDIT PATIENT
      DATA field is set to "Yes" before the user is prompted to update the
      addresses.
       
      5. The following changes are made to laser label printing:
      a. If BAD ADDRESS INDICATOR is set and there is no active temporary
      address, the Mailing label prints ** BAD ADDRESS INDICATED ** and does not
      print the rest of the mailing address.
      b. An additional label log entry added for bad address indicated at the
      
    • 239 SEQ #219
      DATE APPLIED:   2006-11-22 22:31:31
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      The following describes all of the changes included in this patch:
      activity log entry was created with a reason of "RETURNED".  For those
                                                 
      C.  For a patient defined as SC<50 but had a null SC percentage value 
      defined, backdoor Outpatient Pharmacy was asking the SC prompt but not
      storing the answers. The SC prompt is only displayed for those
      prescriptions that the Scheduling DBIA #1579 and/or the Integrated 
      Billing (IB) DBIA #125 determines that it should be asked.  Upon release
      of the fill, a "PRESCRIPTION QUESTIONS REVIEW NEEDED" mailman message
      requesting entry of the SC field was sent to holders of the PSO COPAY
      key.  Because this functionality uses the same checking mechanism as
      non-exempt new orders, the following functions were affected by this
      prescriptions where copay was cancelled, a copay activity log was
      change:  copies, renews and edits that create a new order. This patch will
      store the SC answer for null SC percentage values.
       
      D.  The SC prompt was not asked in Computerized Patient Record System 
      (CPRS), but was asked in backdoor Outpatient Pharmacy. No default answer
      was shown in backdoor due to the question not being asked in CRPS.  This
      occurred for any SC percentage that the SDCO22 API (#1579) returned a
      value that indicated to not ask the SC question but IB returned a flag
      that indicated that the SC question should be asked.  This problem occurs
      for a variety of SC percentages based on how the patient's eligibility is
      generated. The following are examples of those types of entries made by
      defined in enrollment.  This patch will tell CPRS to ask SC for this
      scenario.
       
      E.  It was found that edits made to SC and/or EI's during COMPLETE ORDERS
      FROM OERR [PSO LMOE FINISH] option and the finish function in the PATIENT
      PRESCRIPTION PROCESSING [PSO LM BACKDOOR ORDERS] option were not reflected
      in CPRS.  With the CIDC patches, a new standardized segment was created to
      pass SC, EI's and ICD-9 diagnosis codes and use of the old segment was
      discontinued. When the CPRS CIDC switch is off, CPRS is looking at the old
      segment for updated orders. This patch adds the functionality to send both
      PSO*7*226.
      ZSC and ZCL segments.
       
      F.  When using the edit function in the PATIENT PRESCRIPTION PROCESSING
      option [PSO LM BACKDOOR ORDERS], the total number of entries in the ICD
      DIAGNOSIS multiple (#52311) was being defined as one number less than it
      should have been.  For example, eight diagnosis codes entered but the 
      multiple shows seven as the total number of entries for the multiple.  The
      diagnosis codes were displayed correctly to the user.  This patch will
      store the correct number of entries when edits are performed.
       
       
      G.  The PSOHLNE3 API IA (#4666) was defining an activity log entry that 
      stated "Clinical Indicators and SC/EI's were updated from a CPRS e-sig 
      edit..." for all prescriptions passed through the API.  Also, it was 
      needlessly defining a copay activity log entry for supply items and
      investigational drugs.   Last, it was storing a copay activity log entry
      (copay to no copay) that was set erroneously when the provider edits
      SC/EI's during sign of a verbal/telephone order leaving the prescription
      as no copay.  This API is used to pass data from CPRS to OP when a verbal
      or telephone order is signed in CPRS when the CPRS CIDC Switch is on.  
      This patch limits the setting of the activity log to only those
      Activity Log Example:
      prescriptions where SC, EI's and/or ICD's were changed during sign order.
      And, it eliminates setting the copay activity log for supply items and
      investigational drugs as well as eliminating the erroneous "copay to no 
      copay" activity log entry.
       
      H.  The RESET COPAY STATUS/CANCEL CHARGES option [PSOCP RESET COPAY 
      STATUS] was overlaying the previously stored diagnosis code when storing
      updated information.  Also, the default answer for SC was not being
      displayed for SC<50% patients.  This patch corrects these issues.
       
       
      I.  When the CPRS CIDC switch is turned on, the B cross reference was 
      not being defined in the ICD DIAGNOSIS field (#311) in PENDING OUTPATIENT
      ORDERS file (#52.41).  For telephone/verbal orders signed in CPRS and 
      CPRS renewals, the B cross reference was not being defined in the ICD
      DIAGNOSIS field (#52311) in PRESCRIPTION file (#52).  This was not
      reported as an issue, but the correction is being made in this patch.
       
       
      Technical Descriptions:
      =======================
        1   11/28/05    X-INTERFACE    ORIGINAL       PHARMACIST,ONE
      1.  For Remedy Ticket 130112:
       
      A.  A snapshot of the ACTIVITY LOG sub-file (#40) and the COPAY 
      ACTIVITY LOG sub-file (#107) will be stored in ^XTMP("PSOCIDC7") node,
      and will be available for 90 days.
       
      B.  The "BKGD CIDC UPDATE" activity log entry will be removed and the 
      ACTIVITY LOG sub-file (#40) will be re-subscripted to eliminate the
      missing node. The removed entry will be inserted in the COPAY ACTIVITY LOG
      sub-file (#107).  The date given in the old activity log entry will be
          Comments: Prescription sent to external interface.
      used as the COPAY ACTIVITY LOG field (#.01) for the new entry. The copay
      activity log will be sorted by dates within the existing entries and
      including the new entry, then they will be stored back into the COPAY
      ACTIVITY LOG sub-file (#107). The comment for the new copay activity log
      entry as well as any existing copay activity log entries will be changed
      to state "CIDC CLEANUP" instead of "BKGD CIDC UPDATE".
       
      C.  Because the copay to no copay or vice versa information was not 
      recorded in the old Activity log entry, those values can only reflect the 
      current state of the prescription, and it's thought that they should not
        2   11/28/05    RETURNED       ORIGINAL       POSTMASTER
      be stored on the new entry.
       
      D.  To print the report of all prescriptions updated by the Clean-up 
      routine, type the following from the programmer's prompt using the print 
      device that you prefer.
       
           >D RPT^PSOCIDC9
            DEVICE: HOME//     UCX/TELNET     RIGHT MARGIN:80//
       
          Patch PSO*7*239 - Corrected Activity and Copay Activity logs
       
          Comments:  BKGD CIDC UPDATE
       
           Note that this report reflects all prescriptions where the activity
           and/or copay activity logs were corrected. For detailed information,
           please view the activity and copay activity log on the prescription.
       
           Date printed: MAR 6,2006@14:09:25                       Page: 1
           ===============================================================
           PATIENT NAME     (SSN)       DIV          RX# 
           ---------------  -------  --------------  ------------
           PATIENT,ONE      (B3453)  TROY, NY        200037
        3   11/29/05    X-INTERFACE    REFILL 1       PHARMACIST,TWO
           BPATIENT,TWO     (B0033)  TROY, NY        200049
           BPATIENT,TWO     (B0033)  TROY, NY        200050
       
      E.  The following is an example of a status query for the Clean-up 
      routine, and it must be run from programmer's mode:
       
           >D STATUS^PSOCIDC7
          
            Currently processing:
                  Date being processed > Nov 3, 2005
          Comments: Prescription sent to external interface.
                                  RX # > 1375666
       
      F.  A stop function has been provided in case the system needs to be
      shut down for an emergency or other reason.  Then when the system is back
      up and you are ready you may restart the job, it will resume where it
      left off.  You may restart by entering D ^PSOCIDC7 at the programmer's
      prompt.  The following is an example:
       
           >D STOP^PSOCIDC7
       
       
            Outpatient Activity Logs Correction Job - set to STOP Soon
       
            Check Status to be sure it has stopped and is not running...
              
                         (D STATUS^PSOCIDC7)
       
      G.  The Clean-up routine can be executed from the programmer's 
      prompt instead of through the patch installation.  Also, restarting the
      Clean-up routine after using the stop function described above is 
      performed in the same manner.  Below is an example how to perform this 
      Copay Activity Log Example:
      function:
       
           >D ^PSOCIDC7
       
           ****************** SELECT RUN OPTION ******************
           Do you want to run the activity logs correction process? Y or N// YES
           Enter when to Queue the CIDC ACTIVITY LOGS CORRECTION job to run in 
           date@time format:  NOW//
       
           ===================================================
       
           Queuing background job for CIDC ACTIVITY LOGS CORRECTION...
           Start time: Month day, year@time
           ===================================================
           *** Task #NNNNN Queued! ***
       
       
      2. The following correlates to the items described in number two in the
      Functional Description section:
       
      A. The renew process has been modified to store the changed value
        1   02/01/06    COPAY RESET          ORIGINAL       PHARMACIST,ONE
      for SC in the PRESCRIPTION file (#52).
       
      B. This patch will remove all of the functionality that stored the
      unnecessary IBQ node.
       
      C.  Outpatient was modified to store the SC value for patients with a null
      SC percentage which eliminates the sending of a "PRESCRIPTION QUESTIONS
      REVIEW NEEDED" Mailman message.
       
      D.  The check for the PSOSCMX variable was restored to the PSOCP
          Comment:-BKGD CIDC COPAY CANCEL  Old value=Copay   New value=No Copay
      routine.  
       
      E.  This patch adds the functionality to send both ZSC and ZCL segments to
      CPRS. The ZSC passes SC/EI's only.  The ZCL node passes SC, EI's, and
      ICD-9 Diagnosis codes.
       
      F.  This patch will correctly store the third and fourth piece of the zero
      node of the ICD DIAGNOSIS multiple (#52311) of PRESCRIPTION file (#52).
       
      G.  The PSOHLNE3 API IA (#4666) was changed to only store entries in the 
        2   02/01/06    REMOVE COPAY CHARGE  ORIGINAL       PHARMACIST,ONE
      ACTIVITY LOG multiple (#40) when SC, EI's, and/or ICD's were edited.  
      For supply items and investigational drugs, no copay activity log entries 
      will be stored.  Also, it was modified to prevent storage of a copay
      activity log entry (copay to no copay) that was set erroneously when the
      provider edits SC/EI's during sign of a verbal/telephone order leaving the
      prescription as no copay.
       
      H.  The RESET COPAY STATUS/CANCEL CHARGES [PSOCP RESET COPAY STATUS] 
      option has been modified to not overlay the previously stored 
      ICD-9 Diagnosis code with a null value and to display previously entered
          Comment: RX EDITED -BKGD CIDC COPAY CANCEL
      SC values as a default answer.
       
      I.  The B cross reference will be set for the ICD DIAGNOSIS field (#311)
      in PENDING OUTPATIENT ORDERS file (#52.41) and in the ICD DIAGNOSIS field
      (#52311) in PRESCRIPTION file (#52) for CPRS renewals/verbal/telephone 
      orders.
      1.  For Remedy Ticket 130112:
       
      To eliminate any confusion, patch PSO*7*239 provides an Activity Log 
      Correction process/Clean-up routine.  This routine will take the activity
      log entries created by patch PSO*7*226, move them to the copay activity
      log, and then subsequently will delete the activity log entries.  Also,
      the comment on the copay activity log entries where copay was cancelled as
      well as those entries moved to the copay activity log will be changed to
      "CIDC CLEANUP".  The activity log will be resequenced to eliminate any
      missing nodes, and the copay activity log will be resequenced to insert
      the new entries by date and time.  The following are examples of the
       
      updated entries:
       
        -Note that sequence two from the above example was removed and the
         third sequence was moved up.
       
        1   11/28/05    X-INTERFACE    ORIGINAL       PHARMACIST,ONE
          Comments: Prescription sent to external interface.
        2   11/28/05    X-INTERFACE    REFILL 1       PHARMACIST,TWO
          Comments: Prescription sent to external interface.
       
      After installation of patch PSO*7*226, it was reported that the activity
        -The next entry shows an Activity log entry moved to Copay Activity log:
       
        1   11/28/05    COPAY RESET       ORIGINAL         POSTMASTER
          Comment: CIDC CLEANUP
       
        -The following shows a cancelled Copay Activity Log entry comment
        updated to "CIDC CLEANUP:
       
        1   02/01/06    COPAY RESET          ORIGINAL       POSTMASTER
          Comment: CIDC CLEANUP  Old value=Copay   New value=No Copay
      log entries generated by the patch were confusing. A large part of patch
        2   02/01/06    REMOVE COPAY CHARGE  ORIGINAL       POSTMASTER
          Comment: CIDC CLEANUP  
       
      This patch provides a listing of all prescriptions where the activity log
      was updated by the Clean-up routine, a means of checking the status of the
      Clean-up routine, and a means of stopping the Clean-up job if needed.  A
      detailed description of these functions is located in the Technical
      description.
       
      When installing this patch, the activity log Clean-up portion of this
      PSO*7*226 was to cancel any erroneously billed copays and to define any
      patch is optional.  However, it is highly recommended that it be run for 
      consistency and maintainability.
       
      Once the Clean-up routine has completed a mailman message will be sent to 
      the user who installed the patch.  The following is an example:
       
          Subj: Outpatient Pharmacy PSO*7*239 CIDC ACTIVITY LOGS CORRECTION  
          [#200121] 03/06/06@13:56  4 lines
          From: PSO*7*239 CIDC ACTIVITY LOGS CORRECTION  In 'IN' basket.   Page
          1 *New*
      missing IBQ nodes on the prescription using the SC/EI answers stored on
          
      -------------------------------------------------------------------------
          The CIDC ACTIVITY LOGS CORRECTION job for the Outpatient Pharmacy
          patch (PSO*7*239) started MAR 06, 2006@13:56:04
          and completed MAR 06, 2006@13:56:04.
       
          Enter message action (in IN basket): Ignore//
       
      2. The following issues were found during unit testing for backdoor 
      Outpatient Pharmacy orders, and the corrections are included in this
      the ICD node.  For those prescriptions where the IBQ node was defined, an
      patch. 
       
      A.  When a prescriptions with an exempt patient status is renewed and the
      user changes the value of service connected (SC), the default value was
      stored instead of the changed value.  This only occurred for the SC
      prompt.  The renew process has been modified to store the changed value.
       
      B.  When prescription information was stored when the RX Patient Status 
      was exempt from copay, the IBQ node was being stored needlessly.  This
      patch will remove the functionality that stored this node.
      
    • 238 SEQ #220
      DATE APPLIED:   2006-11-22 22:34:06
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      THIS PATCH WILL FIX TWO PROBLEMS.
       
      PROBLEM 1: AN ERROR OCCURS WHEN DISCONTINUING ALL PRESCRIPTIONS FOR A
      PATIENT.
      PROBLEM 2: REINSTATED DRUG DOSAGES DISPLAY ON OTHER PRESCRIPTION
      
    • 201 SEQ #221
      DATE APPLIED:   2006-11-22 22:36:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      This Outpatient Pharmacy patch is part of the Patient Financial Services
      replacement system.  The project consists of the implementation of the 
      defined, that value will be passed to the COTS billing system for all 
      division having prescriptions filled. If the CHARGE LOCATION is not
      defined for any division and the PFSS switch is turned on, the
      prescription information will not pass to IB or the COTS billing system.
       
       
      Technical Description:
      ======================
       
      At FINISH of the prescription fill:
      billing replacement system, business process improvements, and 
       
      1. The new IB API #4664 GETACCT^IBBAPI will be called to request a PFSS
      ACCOUNT REFERENCE and it will be stored in the PRESCRIPTION file (#52) on
      the fill level. For original fills, it will be stored in the PFSS ACCOUNT
      REFERENCE field (#125), and for refills it will be stored in the PFSS
      ACCOUNT REFERENCE field (#21). These references uniquely identify the
      prescription to the COTS billing system.
       
      2. The array of data passed using the GETACCT^IBBAPI call encompasses all 
      of the minimum required data elements as stated in the PFSS SRS-SDD IBB 
      enhancements to VistA to support integration with the COTS billing
      Generic API document.  The following outlines data passed from 
      Outpatient Pharmacy:
       
        $$GETACCT^IBBAPI(VAR1,VAR2,VAR3,VAR4,.ARR1,,,.ARR4,.ARR5,VAR5,,)
          Where:  
            VAR1 = Patient Identifier (Patient IEN)  
            VAR2 = PFSS Account Reference  
            VAR3 = HL7 Event Code          
            VAR4 = Application Location Reference
            ARR1 = ARR1(2) Patient Class, ARR1(3) Patient Location,
      replacement system.  Significant changes to VistA legacy systems and 
                        ARR1(7) Attending Physician, ARR1(44) Admit 
                        Date/Time (Fill Date), ARR1(50) Alternant Visit
                        ID (Prescription IEN)
            ARR4 = ARR4(n,3) Diagnoses Code, ARR4(n,6) Diagnosis Type 
            ARR5 = ARR5(n,2) Type
            VAR5 = Medical Center Division
       
      3. After IB returns the PFSS ACCOUNT REFERENCE to Outpatient Pharmacy,
      IB will pass the GETACCT information to the COTS billing system via the
      VistA Data Extraction Framework (VDEF) and will store the returned PFSS
      ancillary packages are necessary.
      Account Number external value in the PFSS ACCOUNT file (#375).
       
       
      At RELEASE of the prescription fill:
       
      1. The new IB API # 4665 GETCHGID^IBBAPI will be called to request a PFSS
      CHARGE ID.  This information is used to uniquely identify the fill in the
      IB and will be stored in Prescription file (#52) on the fill level. For
      original fills, it will be stored in the PFSS CHARGE ID field (#126), and
      for refills it will be stored in the PFSS CHARGE ID field (#22).  No data
       
      is passed using this API.
       
      2. Next, the new IB API #4665 CHARGE^IBBAPI will be called to pass
      prescription and copay information.  This information will be stored in
      the PFSS CHARGE CACHE file (#373).  IB will batch the charge information
      and pass it on to the COTS billing system via VDEF.
       
      3. The array of data passed using the CHARGE^IBBAPI call encompasses all 
      of the minimum required data elements as stated in the PFSS SRS-SDD IBB 
      Generic API document.  The following outlines data passed from Outpatient
      Some of the PFSS software components are not operational until the PFSS 
      Pharmacy:
       
           $$CHARGE^IBBAPI(VAR1,VAR2,VAR3,VAR4,.ARR1,,.ARR3,.ARR4,.ARR5,,,)
             Where:
               VAR1 = Patient Identifier (Patient IEN)              
               VAR2 = PFSS Account Reference  
               VAR3 = Charge Type               
               VAR4 = Unique Charge ID (PFSS Charge ID)
               ARR1 = ARR1(4) Transaction Date (Fill Date), ARR1(7) Transaction
                        Code, ARR1(10) Transaction Quantity, ARR1(13) Department
      On/Off Switch, distributed with patch IB*2*260, is set to "ON".  The 
                        Code, ARR1(18) Patient Copay Status, ARR1(21) Ordered by
                        Code, ARR1(22) Unit Cost, ARR1(29) NDC_";"_Generic
                        Name, ARR1(31) Copay Transaction Type
               ARR3 = ARR3(n,3) Diagnoses Code, ARR3(n,6) Diagnosis Type
               ARR4 = ARR4(n,2) Type
               ARR5 = ARR5(1) Quantity_";;"_Days Supply, ARR5(17) Refills 
                        Dispensed (Fill Number), ARR5(18) Date of Most Recent
                        Fill (Release Date), ARR5(31) DEA, Special Handling
       
      4. There will be no return messaging from the COTS billing system to 
      ability for the local site to set the switch to "ON" will be provided at 
      Outpatient Pharmacy.  Note that IB will combine the data passed in the
      GETACCT and CHARGE APIs to form the charge message that will ultimately
      be passed to the COTS billing system via VDEF.
       
       
      CHARGE LOCATION additions:
       
      1. In the OUTPATIENT SITE file (#59), a new CHARGE LOCATION field 
      (#1007) was added, and this field is a pointer to HOSPITAL LOCATION file 
      (#44).
      the appropriate time with the release of a subsequent Integrated Billing 
       
      2. The Site Parameter Enter/Edit [PSO SITE PARAMETERS] option input
      template PSO SITE was modified to accommodate entry of the new CHARGE
      LOCATION field (#1007).
       
      3. If a CHARGE LOCATION is not defined for a particular division, the 
      system will loop through all divisions in the OUTPATIENT SITE file (#59) 
      and will use the first CHARGE LOCATION it finds.  When none of the
      divisions have a CHARGE LOCATION defined, the prescription will not be 
      passed to IB or the COTS billing system.  This issue will be addressed in
      System (PFSS) project.  PFSS patches are being released on various
      patch.
      a subsequent phase of the PFSS project.  Until that time, it is imperative
      that CHARGE LOCATION are defined for each division.
       
      The Integration Agreement (IA) #4732 was created to facilitate 
      modifications being made by IB for interfacility copay.  It will be used 
      in the background to return the pharmacist, person who last edited the 
      prescription fill, and the value of the IB SERVICE/SECTION field (#1003) 
      from the OUTPATIENT SITE file (#59).
       
      For more information about the PFSS project, review the documentation 
      accompanying this patch and refer to the following website: 
      http://vista.domain.ext/billreplace/.
       
      This Outpatient Pharmacy patch, PSO*7*201 provides the functionality
      needed to support the PFSS project.  Note that this patch depends on
      patches PSN*4*103 and PSS*1*92 to provide the new Charge Description
      Master (CDM) functionality.  The CDM provides Service Codes for each drug,
      schedules.  Some patch functionality will not be active until a new PFSS
      supply item, etc. to uniquely identify them to the new COTS billing
      system.  This information is passed via IB Application Program Interface
      (API) calls, which is explained in the Technical Description.
       
      Functional Description:
      =======================
       
      Outpatient Pharmacy was modified to check the status of the PFSS 
      switch.  If the PFSS switch is not activated, the current Integrated 
      Billing (IB) billing process will continue.  If the PFSS switch is
      switch is activated during final implementation. PFSS will initially be
      activated, prescription and copay information will be passed to the new
      COTS billing system for final copay assessments and billing via IB.
      As is currently the case with IB, the exchange of information will take
      place in the background with no user impact.
       
      Upon entering a new prescription order, copying, renewing, or editing 
      an order that causes a new order to be created, a PFSS Account Reference
      will be requested at finish from IB. This reference is used to uniquely
      identify the prescription in the COTS billing system.
       
      implemented at select pilot sites ONLY.
      At prescription release, a unique charge identifier will be requested 
      from IB, and it will serve to uniquely identify the fill in IB.  Next, a
      charge message will be sent to the COTS billing system via IB.  This
      includes the release of Consolidated Mail Outpatient Pharmacy (CMOP)
      prescriptions and prescriptions released by the Outpatient Pharmacy
      Automation Interface (OPAI) functionality.
       
      For return to stocks, and deletes that perform a return to stock, a charge
      credit message will be sent.  
       
       
      When Service Connection and/or Environmental Indicators are modified
      without a change in copay using the Reset Copay Status/Cancel Charges
      [PSOCP RESET COPAY STATUS] option, a charge update message will be sent.  
      A charge credit message will be sent when copay charges are cancelled.  
      When the fill is changed to copay, no message will be sent because this
      change is considered to be for the future fills.
       
      No messaging will take place for discontinued orders.  When a 
      discontinued order is reinstated, the previously obtained PFSS Account 
      Reference will be used.
      The purpose of the PFSS project is to prepare the Veterans Health 
       
      In order to maintain the display of the "$" sign on the Medication 
      Profile screen that indicates the prescription is eligible for copay, IB
      will continue to be utilized for the copay eligibility assessment that is
      performed at finish.  Also, the Outpatient Pharmacy and IB copay
      evaluations performed at release for Service Connection, Environmental 
      Indicators, Drug Enforcement Agency (DEA) special handling (supply items
      and investigational drugs), income exempt, and RX Patient Status checks
      have not changed and will continue to be used.  However, the final copay
      billing determination will be performed by the COTS billing system, and
      Information Systems and Technology Architecture (VistA) environment for
      the final decision is based on the above information, interfacility copay
      information, and current IB billing rules.  There will be no return
      messaging from the COTS billing system to Outpatient Pharmacy.
       
      When Days Supply is edited on a released prescription, a charge update
      message will be sent to the COTS billing system, and it is understood that
      the COTS billing system will pick up the latest charge update.
       
      Last, a new CHARGE LOCATION field (#1007) was added to the OUTPATIENT 
      SITE file (#59).  This field will be used by the COTS billing system 
      the implementation of a Commercial Off-The-Shelf (COTS) billing 
      to group charges by division.  Upon installation and before the PFSS 
      switch is turned on, the user will need to enter an Outpatient Pharmacy
      charge location in the HOSPITAL LOCATION file (#44), and afterward define
      this location in the new CHARGE LOCATION field (#1007) in the OUTPATIENT
      SITE file (#59).  The Site Parameter Enter/Edit [PSO SITE PARAMETERS]
      option may be used to define the CHARGE LOCATION in the OUTPATIENT 
      SITE file (#59).  A charge location should be defined for each division in
      the OUTPATIENT SITE file (#59). It is suggested that this field be
      coordinated with the Medical Center's billing office and the activation of
      the PFSS functionality.  If at least one division has a CHARGE LOCATION
      
    • 245 SEQ #222
      DATE APPLIED:   2006-11-22 23:44:29
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      This patch adds three new Outpatient Pharmacy Application Programming
      from the STATUS field (#100) from the PRESCRIPTION file (#52) is
      returned.  This API will invoke the FIELD^DID FileMan call and data will
      be returned to the calling application as specified in the FIELD^DID
      FileMan documentation.
       
      The third API (DIC) has three parameters and retrieves information 
      specific to the PRESCRIPTION file (#52).  This API will invoke the ^DIC 
      FileMan call and data will be returned to the calling application as 
      specified in the ^DIC FileMan documentation.
       
      Interfaces (APIs).
      For more information, please see Forum DBIA 4858, or the Pharmacy
      Re-Engineering (PRE) API Manual.
       
      This patch also corrects a problem with the PROF^PSO52API API.  The first
      node of data returned is meant to return both the PRESCRIPTION NUMBER and
      it's IEN.  Currently, the IEN is not returned.  This patch will correct
      the problem.
       
      This patch also corrects a problem with the PSO^PSO53 API.  Currently 
      there is an undefined error when the API is run.  This patch will correct 
       
      the problem and ensure the functionality of the PSO^PSO53 API call.
      The first API (DIQ) requires five parameters to be passed in and data
      from the PRESCRIPTION file (#52) will be returned.  This API will invoke
      the EN^DIQ1 FileMan call and data will be returned to the calling
      application as specified in the EN^DIQ1 FileMan documentation.
       
      The second API (STATUS) requires three parameters to be passed in and data
      
    • 253 SEQ #223
      DATE APPLIED:   2006-12-27 14:28:05
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      1) HD149502 - Patient instructions from the first patient will incorrectly
      display for the second patient when you are about to delete the patient
      instructions for the second patient.
       
      2) HD147655 - Reinstate Issue:
      When you have 2 Clozapine drugs ordered, one as active and one as 
      discontinued, you wish to reinstate the discontinued drug.  At this point 
      the active drug will incorrectly become discontinued when you have 
      decided to "^" out of the application.
      
    • 250 SEQ #224
      DATE APPLIED:   2006-12-27 14:41:15
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      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
      
    • 258 SEQ #225
      DATE APPLIED:   2006-12-27 14:46:39
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      This patch contains the first quarter enhancements for the Outpatient
            "Active/Susp". This change is also shared with the Application
            Program Interface (API) number 1281, provided to Computerized
            Patient Record System (CPRS) V. 1.0 to return "Active/Susp" instead
            of "Suspended".
         c. As a result of the installation of patch PSO*7*233, if a bad address
            is indicated, "BAD ADDRESS INDICATED-" followed by the reason
            ("UNDELIVERABLE", "HOMELESS", or "OTHER") was being printed. Once
            PSO*7*258 is installed, "**BAD ADDRESS INDICATED**" will be printed
            but will not be followed by the reason.
       
      Pharmacy V. 7.0 package. It provides the following updates to
      2. The Medication Profile [PSO P] option will now print the last 4 digits
      of the SSN instead of the full 9 digits.
       
      3. When finishing a pending order using the Patient Prescription
      Processing [PSO LM BACKDOOR ORDERS] option or using the Complete Orders
      from OERR [PSO LMOE FINISH] option, the following changes were
      made:
         a. The provider comments are displayed in the first screen. When the
            following prompt is displayed:
       
      functionality:
            Copy Provider Comments into the Patient Instructions? No//
       
            the user has to scroll the screen up to know what the provider
            comments are. To avoid this problem, the provider comments are
            displayed along with this prompt.
       
         b. A problem was reported with the calculated quantity for the drug
            Clozapine. A patient safety incident (PSI-06-146) was entered. The
            solution provided is as follows:
            If the drug has possible dosages defined, a quantity can be
       
            calculated. If this quantity is less than the quantity placed in
            CPRS, the calculated quantity will be displayed. Otherwise, the
            quantity placed in CPRS will be displayed. If there are no possible
            dosages defined then a quantity cannot be calculated and the message
            "Unable to calculate the quantity, enter a quantity" is displayed to
            the user in the ListMan message bar as a warning of a possible
            quantity issue. For Clozapine orders, since Outpatient Pharmacy
            might change the days supply and quantity placed in CPRS, the days
            supply and quantity have been added to the existing refill message.
            Here is an example of an order placed in CPRS with a days supply
      1. The Action Profile (132 COLUMN PRINTOUT) [PSO ACTION PROFILE] option is
            of 60 and a quantity of 60 for a patient eligible for 28 days
            supply:
       
            (6)     Issue Date: OCT 26,2006        (7) Fill Date: OCT 27,2006
           Patient Eligible for 28 Day Sup. or 14 Day with 1 refill or 7 Day
           with 3 refill
            (8)    Days Supply: 28                (9)   QTY (TAB): 28
                  Provider ordered 0 refills, days supply of 60 and a qty of 60
       
       
      modified to provide the following functionality:
      4. After the release of patch PSO*7*233 some issues were identified and
      are being corrected in this patch:
         a. If a hold reason of "8 (PER PATIENT REQUEST)" or "99 (OTHER--SEE
            COMMENTS)" was entered, some options were displaying reason "7 (BAD
            ADDRESS)" instead. This patch corrects that problem.
       
         b. The function call $$CHKRX^PSOBAI was missing a value on some quit
            statements. Although the affected lines of code should never be
            encountered, this patch corrects the problem.
         a. It will print only the last 4 digits of the Social Security Number
            (SSN) instead of the full 9 digits.
         b. The Prescription status of "Suspended" will now print as
      
    • 9 SEQ #22
      DATE APPLIED:   1999-06-02 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      1. This patch provides new functionality for the Return Medication to
      option. Previously, you would have needed to go to the Return Medication
      to Stock [PSO RETURNED STOCK] option, return the medication to stock, then
      go back to the Delete a Prescription [PSO RXDL] option to mark the
      prescription deleted.
       
      2. This patch fixes a problem of a possible incorrect FILL DATE default
      when entering a new prescription in the Patient Prescription Processing
      [PSO LM BACKDOOR ORDERS] option. If a past ISSUE DATE is entered, and
      based on the other information entered for the prescription the
      EXPIRATION DATE calculates to a past date, then the FILL DATE default
      Stock [PSO RETURNED STOCK] option and the Delete a Prescription [PSO RXDL]
      could be incorrect.
       
      3. This patch makes changes to the data returned from Outpatient
      Pharmacy detailed in DBIA 1878. Piece 16 of the zero node will contain the
      patient name. Also, the DFN input variable is now optional, but a null
      value must be passed in if the DFN is not defined.
       
      4. This patch makes a change to return Fill Date information to
      Computerized Patient Record System (CPRS) for display purposes.
       
      option. In the Return Medication to Stock [PSO RETURNED STOCK] option,
      5. This patch fixes an error that can occur when finishing an order
      entered through Computerized Patient Record System (CPRS), and that
      order was entered as a complex order with multiple sets of instructions.
       
      6. This patch fixes a problem of partial prescriptions not being released
      when that same prescription has a regular fill in suspense.
      prescriptions that have been filled and released at the Consolidated Mail
      Outpatient Pharmacy (CMOP) can now be returned to stock. In the Delete a
      Prescription [PSO RXDL] option, prescriptions that have been filled and
      released at the CMOP can now be marked for deletion. In addition, if a
      prescription has been released, you can now return that prescription to
      stock and mark it for deletion from the Delete a Prescription [PSO RXDL]
      
    • 255 SEQ #226
      DATE APPLIED:   2006-12-28 07:34:51
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      This patch will correct certain scenarios where bottle labels printed 
      through the OPAI External Dispense machines have a slightly different 
      drug name than when sent to CMOP or printed locally.  Two new drug name 
      fields, VA LABEL NAME & VA PRINT NAME, will be sent in the OPAI HL7 
      segments to the External Dispense Machines.
       
      Also will correct the Method of Pickup field in RXE.8 to send when all
      alpha characters.
      
    • 259 SEQ #227
      DATE APPLIED:   2006-12-28 07:36:25
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      This patch will correct 5 problems.
      Problem 5: Prevent OPAI from updating a refill node via Auto-Release
                 when the refill node was deleted.
       
      Problem 1: Users are able to delete released refills without returning to
                 stock.
      Problem 2: A released refill may still allow for deletion.
      Problem 3: Error occurs when deleting suspended refills using menu option
                 Change Suspense Date.
      Problem 4: The Return Medication to Stock option is not deleting the
                 refill.
      
    • 254 SEQ #228
      DATE APPLIED:   2007-06-27 23:26:09
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      For the Health Insurance Portability and Accountability Act (HIPAA)
             ...
       
             Select CPRS ORDERING INSTITUTION:
             RELATED INSTITUTION: ALBANY// 
             NPI INSTITUTION: ALBANY// 
         
             ...
        
      When this patch is installed, the information in this field will be 
      automatically populated through a post-install routine. The correct
      National Provider Identifier (NPI) project, this patch will create and
      institution will be identified using the existing NCPDP NUMBER field
      (#1008) in the OUTPATIENT SITE file (#59), along with a list of
      pre-defined NPI numbers, which should match to NPI numbers previously 
      assigned to each institution by the KERNEL V. 8.0 patch XU*8*410.
         
      The PSO SITE input template is being changed to include this new field.
      Therefore, the user will be able to manually add/edit/delete the NPI
      INSTITUTION field through the Site Parameter Enter/Edit [PSO SITE
      PARAMETERS] option.
        
      populate the new NPI INSTITUTION field (#101) in the OUTPATIENT SITE file
      **************************************************************************
      NOTE: All active outpatient sites MUST have an NPI INSTITUTION assigned.
      This is very important for sites currently performing third party
      electronic billing (ePharmacy) because the NPI number will replace the 
      previous NCPDP (National Council for Prescription Drug Programs) number 
      used to identify the dispensing pharmacy. 
      **************************************************************************
       
      For active sites that do not have an NPI INSTITUTION assigned after the
      installation of this patch, using the Site Parameter Enter/Edit [PSO SITE
      (#59). This patch will also change the Site Parameter Enter/Edi [PSO SITE
      PARAMETERS] option enter the correct institution for each site. In order
      to help you identify which sites have and which ones have not been 
      assigned an NPI INSTITUTION, the post-install routine will generate a 
      Mailman message which will be sent to the user installing the patch as 
      well as all the holders of the PSORPH security key. Below is an example
      of the Mailman message:
       
      Subj: NPI INSTITUTION POPULATION [#93686] 08/01/06@16:16  20 lines
      From: PATCH PSO*7*254  In 'IN' basket.   Page 1  *New*
      -----------------------------------------------------------------------
      PARAMETERS] option to allow the user to edit this new field as shown
      PSO*7*254 POST-INSTALL - POPULATES NPI INSTITUTION FIELD (#101)
                               IN THE OUTPATIENT SITE FILE (#59)
       
      Please, validate that the NPI INSTITUTION assignment below is correct for 
      each active DIVISION. If not, please use the Site Parameter Enter/Edit [PSO
      SITE PARAMETERS] option and assign the correct NPI INSTITUTION.
       
      ------------------------------------------------------------------------
      DIVISION(SITE#)        NPI#        NPI INSTITUTION
      ------------------------------------------------------------------------
      below:
      ALBANY(500)            9999854880  ALBANY
      LEAVENWORTH(686)       9999813538  LEAVENWORTH, KS
      SIDNEY CLINIC(442GC)               NO SITE# OR NCPDP# FOUND FOR DIVISION
      TROY(514)                          NO NPI# FOUND FOR THIS DIVISION
      GREELEY CLINIC(442GD)  9999591232  GREELEY CBOC
        
      TOTAL: 5 Division(s).
       
             NAME: ALBANY// 
       
      
    • 252 SEQ #229
      DATE APPLIED:   2007-06-29 21:06:24
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      This patch includes two new routines, PSO52EX and PSO52B.  It also
      ^TMP global.  Once these values are set by the user, EXTRACT will then
      extract all original fill information.  If a selected patient also has
      refill or partial fill information on record, that information will also
      be returned and subscripted accordingly.  The output is stored on the ^TMP
      global.  The second API is named REF.  REF also requires the same three
      parameters: SDATE, EDATE, and LIST.  It will retrieve information stored
      on the "AD" cross reference in the PRESCRIPTION file (#52) and return it
      to the ^TMP global. Refer to Forum DBIA 4902 for complete information.
       
      PSO52B is a new routine that contains a number of subroutines that have 
      enhances functionality and resolves two problems in PSO52API.
      been moved from PSO52API.  This was done to ensure that PSO52API will 
      continue to be within Programming Standards and Conventions (SAC) routine 
      size limits.  PSO52B also enhances the RX^PSO52API component by retrieving
      International Classification of Diseases (ICD) information from the
      PRESCRIPTION file (#52).  The user now has the option to pass in "ICD" in
      the NODE parameter of the RX^PSO52API call and retrieve information
      specific to the patient(s) concerning their ICD. Refer to the Application
      Programmer Interface (API) manual for further instruction on the use of
      this API.
       
       
      This patch also corrects two other issues within PSO52API.  Currently   if
      the user passes in only an end date, the API will error.  This patch will
      correct this problem.  Also, when "O" is passed in the NODE parameter to
      retrieve the ORDERABLE ITEM field (#39.2) from the PRESCRIPTION file
      (#52), the code will now return data as stated in the API manual without
      representing the field number in its ^TMP global subscript.
      PSO52EX is a new routine containing two Application Programmer Interfaces
      (APIs).  The first API is named EXTRACT.  EXTRACT retrieves data from the
      "AL" and "AM" cross references within the PRESCRIPTION file (#52).  
      EXTRACT requires three parameters: SDATE, EDATE, and LIST.  SDATE is the
      start date to retrieve data from.  EDATE is the end date to retrieve data
      from.  LIST is the name that is used to subscript the returned data into a
      
    • 243 SEQ #230
      DATE APPLIED:   2007-09-04 22:56:26
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      Remote Data Interoperability (RDI) functionality includes receiving data
       
       
      This patch contains the following changes for RDI order checking:
       
      1. Prescriptions with a status of "DELETED" in the STATUS field (#100) in
      the PRESCRIPTION file (#52) from a remote facility should not be included
      in order checks. This patch filters out DELETED remote prescriptions.
       
      2. Some older prescriptions do not have an expiration date in the 
      EXPIRATION DATE field (#26) of the PRESCRIPTION file (#52). This patch
      from the Health Data Repository (HDR) in order to perform order checking
      restricts prescriptions with a missing expiration date from being used in
      remote order checks unless the ISSUE DATE (#1) field of the PRESCRIPTION
      file (#52) is within the past year.
       
      3. Drugs not matched to the National Drug file were not performing remote 
      order checks. These drugs could have a drug class defined. This patch 
      adds the remote order check for drug class when orders are placed for 
      locally defined drugs.
       
      4. When Adverse Reaction Tracking (ART) patch GMRA*4*26 is installed at a
      against outpatient prescription and allergy data from remote VA or
      site, this patch adds the display of LOCAL, REMOTE SITE(S), or LOCAL AND
      REMOTE SITE(S) to allergy order checks to indicate whether the allergy
      entry originated at the local site or it came from a remote site. For
      backdoor outpatient pharmacy, currently only the drug class code and not
      the drug class name is displayed for an allergy drug class order check.
      This patch adds the display of the class name.
       
      Example:
       
      A Drug-Allergy Reaction exists for this medication and/or class!
      Department of Defense (DoD) facilities.
       
      Drug: AMOXICILLIN 250MG CAP
      Drug Class: AM110 PENICILLIN-G RELATED PENICILLINS (LOCAL)
       
       
      5. When the VUID field (#99.99) of the VA PRODUCT file (#50.68) of a
      remote prescription is inactive, every order being placed incorrectly
      displayed a duplicate drug order check. This patch corrects that problem.
       
      6. Remote order checking against remote discontinued or expired outpatient
       
      prescriptions is changed to perform the order check if the remote 
      prescription was expired or discontinued in the last 30 days instead of 
      within the last 120 days.
       
      7. During testing of RDI, a problem was discovered with the order checks
      involving remote allergy classes. Not all of the remote allergies were
      being retrieved from the HDR. A change was made to use a different
      Application Program Interface (API) to the allergy package that does 
      retrieve the remote data.
       
      When RDI is turned on (by the Computerized Patient Record System (CPRS)
      8. An issue with too many false positive order checks was discovered when 
      doing allergy order checks on certain drug classes. Analgesics, as a
      class, were performing order checks across all members. For example: class
      CN101 was generating an order check for class CN102. This patch corrects
      this problem by ensuring that allergy Analgesic class order checks only
      match against the specific 5-character class if the class begins with 
      "CN10".
       
      9. One feature of RDI is the notification to the user when processing 
      orders that only local data is being used if the remote data is 
      patch OR*3*238), the RDI order checking checks the current drug being 
      unavailable. Several sites reported issues with this mechanism. This 
      patch corrects this problem by performing the check for remote data 
      availability upon entering the patient's chart, rather than on each order.
       
      10. The list of remote allergies is added to allergy/adverse reaction 
      portion of the Medication Profile. If a patient has the same allergy
      information from several remote sites, it will only be listed once.
      ordered for duplicate drugs, duplicate drug classes, drug-drug
      interactions, and drug allergies.
      
    • 200 SEQ #231
      DATE APPLIED:   2007-09-04 23:08:55
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
       This patch contains the FY 2007 Quarter 2 Outpatient Pharmacy V. 7.0
       
            profile screen.
         g. While printing original labels (not reprint of the signature log), 
            if all of the fills have a routing of mail, the signature log will
            not be printed.
         h. The line "Relationship_________________ Counseled? _____" is changed
            to "Relation_____ Counseling Refused__ Accepted__".
       
       
      5. When a fill is released, if the BAI is no longer set or there is an 
      active temporary address, the "B" is removed from the status column of 
      If you are using automated dispensing equipment that relies on 
      the patient profile. (This is removed by making an additional entry in 
      the label log. The "B" comes from the "last" entry having a bad address 
      condition at the time the label printed).
       
       
       
      To address E3R 19820, the following code changes are included in this 
      patch:
       
      1. Add the capability to tie a ScripTalk printer to regular Pharmacy
      the data stream sent to the laser labels port, you have 2 options:
      label printer(s) to control where the ScripTalk labels print for
      multi-divisional sites. The new SCRIPTALK PRINT DEVICE MAPPING multiple
      (#47) in PHARMACY SYSTEM file (#59.7) has been created to store this
      information in Pharmacy Data Management patch PSS*1*122. The multiple
      contains PRINTER TO BE MAPPED field (#.01) and SCRIPTALK DEVICE field
      (#.02).
       
      The added functionality works in conjunction with the existing ScripTalk 
      divisional functionality, so a divisional ScripTalk device must be
      defined.  If no mapping is defined in the new fields, ScripTalk labels
        1. Implement the Outpatient Automation Interface (OPAI) (available with
      will continue to print on the printer defined for the division.  If
      a pharmacy printer is mapped to a ScripTalk printer, the ScripTalk label
      will automatically be printed on the mapped ScripTalk printer.
       
       
      2. Modify the ScripTalk Device Definition Enter/Edit [PSO SCRIPTALK
      DEVICE DEF'N] option to allow definition of printer mapping for 
      ScripTalk devices.  The user will be prompted to define the ScripTalk 
      printer by division or by printer mapping.  After selecting D for 
      division, the divisional definition has not changed.  After selecting 
           released patch PSO*7*156) or 
      P for printer mapping, the user will be prompted "LABEL PRINTER TO BE
      MAPPED". The device entered into this field corresponds to the label
      printer selected during Pharmacy login and/or the printer selected during
      print from suspense functions. Next, "SCRIPTALK DEVICE" will be prompted,
      and this field should contain the ScripTalk printer to be mapped to the
      regular label printer.
       
       
      MISCELLANEOUS ENHANCEMENTS:
      ---------------------------
        2. Contact your vendor to make adjustments based on the new data stream.
      1. A new field FINISH DATE/TIME field (#38.3) is added to the
      PRESCRIPTION file (#52).
       
      2. When using the Print from Suspense File [PSO PNDLBL] option, if the
      routing is not WINDOW and the BAD ADDRESS INDICATOR (#.121) field of the
      PATIENT file (#2) is set (value of 1=UNDELIVERABLE, 2=HOMELESS, 3=OTHER)
      and the patient does not have an active temporary address, the
      prescription fill will not be sent to automated filling equipment and/or
      to the label printer. Also, if the fill's routing is mail and the 
      patient's MAIL field (#.03) in the PHARMACY PATIENT file (#55) is set to
       
      "DO NOT MAIL" and the current date is before the MAIL STATUS EXPIRATION
      DATE field (#.05) in the PHARMACY PATIENT file (#55), the label will not
      print and the fill will not be sent to the automated filling equipment.
       
      The first time a prescription is not sent/label printed, a MailMan message
      will be generated to the user who queued the print from suspense and the
      members of the PSO EXTERNAL DISPENSE ALERTS mail group. An entry will also
      be set in the PRESCRIPTION file (#52) activity log.
       
      Example activity log entry:
       
      ---------------------------
      Activity Log:
      #   Date        Reason         Rx Ref           Initiator Of Activity
      =====================================================================
      1   02/19/07    SUSPENSE       ORIGINAL         OPPHARMACIST,ONE
      Comments: RX not printed from suspense due to BAD ADDRESS INDICATOR
       
      - or -
      Comments: RX not printed from suspense due to DO NOT MAIL
       
      Outpatient Pharmacy Automation Interface (OPAI) enhancements: 
      Example MailMan message:
      ------------------------
      Subj: 500 BAD ADDRESS SUSPENSE NOT PRINTED  [#169828] 02/26/07@07:30  11
      lines
      From: OUTPATIENT PHARMACY PACKAGE  In 'IN' basket.   Page 1
      --------------------------------------------------------------------------
      -----
      The following prescriptions with a routing of mail were not printed/sent 
      to
      external interface due to the BAD ADDRESS INDICATOR being set and no 
      -------------------------------------------------------------
      active
      temporary address or patient has an active MAIL status of DO NOT MAIL:
       
      OPPATIENT,ONE   000001234   (BAD ADDRESS INDICATOR)
        100002608  (1)  A AND Z OINTMENT
        100002609  (0)  ASPIRIN 325MG TABS
       
      OPPATIENT,FOUR   000004321   (DO NOT MAIL)
        100002654A  (0)  BACITRACIN OINTMENT 1OZ
       
      enhancements. 
      1. Modified to use the new commercial warning label source to send the
       
      3. Modify the report from the Bad Address Suspended List [PSO BAI 
      SUSPENDED] option to allow printing by more than one division and also 
      include prescriptions suspended for Consolidated Mail Outpatient Pharmacy 
      (CMOP). This report was also changed to not prompt for a start date.
       
      Example:
      --------
      Select OPTION NAME: PSO BAI SUSPENDED     Bad Address Suspended List
      Bad Address Suspended List
      warning label text to the automated filling equipment. The OPAI WARNING
       
      This option shows unprinted suspended prescriptions for patients who have 
      the
      BAD ADDRESS INDICATOR set in the PATIENT file and no active temporary 
      address.
       
       
      Ending suspense date: T+3  (MAR 01, 2007)
      Outpatient Pharmacy software - Version 7.0
       
      LABEL SOURCE field (#16.2) in the PHARMACY SYSTEM file (#59.7) must be set
      Division:    EXT  500  
       
                You are logged on under the EXT division.
       
      Select LABEL PRINTER: HOME//   GENERIC INCOMING TELNET
       
      OK to assume label alignment is correct? YES// 
       
      Bingo Board Display: OUTPATIENT//   
       
      to "N" for "New" to send the warning labels from the new commercial data
         You are logged in under the EXT division.
       
      Print only those Rx's suspended for this division? Yes// NO
      DEVICE: HOME//   GENERIC INCOMING TELNET
       
       
      Suspense bad address report - division = ALL                       PAGE: 1
      for suspense dates through MAR 01, 2007
      --------------------------------------------------------------------------
       
      source to OPAI. It can be set by using the Pharmacy System Parameters Edit
      OPPATIENT,TEN   (00-0187)      
      MAR 01, 2007    Rx#: 301054     CIMETIDINE 200MG TAB
      MAR 01, 2007    Rx#: 301055     COAL TAR 5% GEL 3 OZ TUBE
       
      OPPATIENT,FIVE   (00-0773)        
      FEB 27, 2007    Rx#: 100002655  BACITRACIN OINTMENT 1OZ
       
      End of Report.
      Press Return to continue: 
       
      [PSS SYS EDIT] option.
      4. As per the request of Computerized Patient Record System (CPRS)
      package the following were added to the Applications Program Interface
      (API) PSOHCSUM:
         a. PLACER ORDER # field (#39.3) of the PRESCRIPTION file (#52).
         b. Letter "R" when the original fill is returned to stock.
      For more details please see the IA (Integration Agreement) #330.
       Example:
       
      Select OPTION NAME: PSS SYS EDIT       Pharmacy System Parameters Edit
      Pharmacy System Parameters Edit
       
       
      PMIS PRINTER: L8150$PRT// 
      PMIS LANGUAGE: English// 
      WARNING LABEL SOURCE: NEW// 
      CMOP WARNING LABEL SOURCE: NEW//
      OPAI WARNING LABEL SOURCE: ?
           Enter "N" for NEW to use commercial data source for OPAI warning 
      labels.
           Choose from: 
             N        NEW
       
      OPAI WARNING LABEL SOURCE: N  NEW
       
         a. The warning text is sent as one record per warning.
         b. The text is sent in English or Spanish depending on the patient's
            other language settings. 
         c. If the DEA, SPECIAL HDLG field (#3) in the DRUG file (#50) begins
            with numbers 1,2,3,4, or 5, the NO TRANSFER warning text from the RX
            CONSULT file (#54) entry number 20 is automatically sent as one of
            the first 5 warnings when the OPAI WARNING LABEL SOURCE is set to 
            "New".
      ***** NOTE TO SITES USING AUTOMATED FILLING EQUIPMENT *****
       
       
      2. If the BAD ADDRESS INDICATOR (BAI) field (#.121) of the PATIENT file
      (#2) is set and the routing is WINDOW, the text "VAB" concatenated with
      the BAI code is sent in the Address field of the PID segment of the HL7
      message to the filling equipment.
       
      Here are some examples of this field:
       
      When the permanent address is active:
      Please ensure that your vendor is aware of the changes being made by this 
      PADD-1~PADD-2~SPRING~TX~77379~~P~PADD-3~201^~~""~""~~~N|""|||||||
      |
       
      When the temporary address is active:
      PADD-1~PADD-2~SPRING~TX~77379~~P~PADD-3~201^~~""~""~~~N^TADD-1~TADD-2 
      TADD-3~PLANO~TX~12345~~C~~""~~~
      ^HL(772,10388,"IN",2,0)=20070223&""|""|||||||||
       
      When the address is flagged as BAI:
      PADD-1~PADD-2~SPRING~TX~77379~~VAB1~PADD-3~201^~~""~""~~~N|""||||||
      patch. There are changes (described below) that affect both the HEALTH 
      |||
       
      "VAB1" - indicates Bad Address Indicator and 1 is for UNDELIVERABLE (2 for
      HOMELESS, 3 for OTHER)
       
       
      Laser Label enhancements:
      -------------------------
      1. Print the last 4 digits of the Social Security Number (SSN) instead of
      the last 6 digits.
      LEVEL SEVEN (HL7) messages (content of fields only - no new fields are
       
      2. Change the name on the mailing label back to Last name,First name
      format.
       
      3. On the Pharmacy Fill Card portion of the label, replace the text 
      "Mfr ___________________" with:
         a. NDC/MFR_______________ for non-ePharmacy sites
         b. NDC nnnnn-nnnn-nn for ePharmacy sites 
       
      4. Signature log enhancements:
      added) and the laser label stream.
         a. Print current date at top
         b. Do not print user name (if more than 1 prescription was included to
            be signed, the user name could be different for each one).
         c. Correct the spacing and continuation paging issues if one or more 
            of the prescriptions has been discontinued before printing the 
            signature log.
         d. Add a barcode to enable scanning to remove the patient's name from 
            the Bingo Board.
         e. Add as much of the drug name as will fit on the label.
         f. Add hidden action "RS" for Reprint Signature log to the prescription
      
    • 263 SEQ #232
      DATE APPLIED:   2007-09-04 23:50:04
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      This patch will correct the following issues.
      the EDIT PROVIDER option does not allow editing of SERVICE/SECTION or 
      PERSON CLASS for Fee Basis providers.
       
      Problem:  HD158732
      ------------------
      There is a discrepancy between fields in EDIT PROVIDER and VIEW PROVIDER.
       
      Problem:  HD15266
      ------------------
      An undefined error occurs when a single character is entered in the 
      PSO RESET COPAY option.
       
      Problem:  HD151887
      ------------------
      
    • 261 SEQ #233
      DATE APPLIED:   2007-09-05 00:10:28
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      This patch is part of the third quarter enhancements release for
      any functional changes.
       
      For more information on the addition of the thirteen new data fields,
      please refer to Appendix D of the Outpatient Pharmacy V. 7.0 Technical
      Manual / Security Guide that is being updated with this patch.
       
      This patch also corrects the problem of a VDEF message not being sent to
      the HDR when a refill is deleted from a prescription as a result of the
      refill being returned to stock.
       
      the Outpatient Pharmacy V. 7.0 package.
      **** VERY IMPORTANT ****
       
      You must suspend the VDEF Request Queue before installing this patch and
      then re-enable it after installation of the patch. Keep in mind that the
      suspension of the VDEF Request Queue will not prevent any new requests in
      Outpatient Pharmacy VDEF Domain application from being added to the VDEF
      Request Queue, it will only delay the building of these VDEF HL7 messages
      until the VDEF Request Queue is enabled again. The steps for doing that
      are outlined in the Installation Instructions section.
       
       
       
      MISCELLANEOUS FIXES:
      --------------------
      1. The hidden action "RS" for Reprint Signature log that was sent in
      patch PSO*7*200, was overwriting the action "OTH" for Other OP Actions,
      making the OTH action unavailable. The post-install routine PSOP261
      included in this patch (PSO*7*261) fixes this.
       
      2. An undefined error was identified by a site that went live with Remote
      Data Interoperability (RDI) patches. A common variable was being killed by
      As per the Health Data Repository (HDR) request, thirteen new data fields
      another package. The fix is to save the value of the variable before
      making the call to retrieve remote allergy data and to restore the
      variable to the saved value once control is returned to the calling
      routine.
      were added to the current Outpatient Pharmacy Vista Data Extraction
      Framework (VDEF) HEALTH LEVEL SEVEN (HL7) message that sends prescription
      information to the HDR.
       
      This patch affects the background HL7 processing only; users will not see
      
    • 265 SEQ #234
      DATE APPLIED:   2007-09-05 00:36:46
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      PSI-07-029 patch fix
       
      Corrects undefined filing errors for NON-VA Meds when an embedded
      semi-colon is entered in either the Dosag field or the Schedule field in
      CPRS as free form text.
      
    • 249 SEQ #235
      DATE APPLIED:   2007-09-05 00:46:24
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      Cancel date
      Scriptalk issue
      Fileman API
      
    • 23 SEQ #23
      DATE APPLIED:   1999-06-22 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      1. This patch contains new DEA requirements for Clozapine dispensing.  The
      will be one test within the CBC panel.
       
      After the installation of this patch the Drug Enter/Edit [PSS DRUG
      ENTER/EDIT] option in the Pharmacy Data Management (PDM) package should be
      used to add this second test to the drug(s) that are identified as being
      used for Clozapine/Clozaril dispensing.  For existing entries in the DRUG
      file (#50) the first test WBC should already be defined from previous setup
      of identifying drugs for Clozapine/Clozaril dispensing.  For new drugs added
      for Clozapine/Clozaril dispensing both the WBC and ANC test must be
      identified. If this second test is not added the user will get a message
      new requirements are that there will be two tests instead of one required
      when trying to dispense a Clozapine Rx, "Invalid Number of Tests (1) entered.
       
       Cannot dispense Clozapine Prescription. You must have TWO test identified
      for this drug.  Rx Deleted."
       
      Though this patch allows the dispensing of 14-day Clozapine/Clozaril Rxs,
      the eligibility of the patient is determined by the Mental Health package.
      There is no setup required by Outpatient Pharmacy.  If you have a
      question about a patient's eligibility, please contact The National
      Clozapine Center.
      for Clozapine dispensing.  The two tests are White Blood Count (WBC) and
       
      These two patches are required, Mental Health patch YS*5.01*47, and PDM
      patch PSS*1*19.
       
      2.  This patch corrects a problem where Rx's with controlled substances
      are being given a maximum expiration date of one year instead on six months.
        
      3.  This patch corrects a problem reported in MON-0199-51550.  The problem
      is that when using the Speed Refill action if the Rx's selected are all
      expired no message is given to the user that the Rx's selected are expired.
      Absolute Neutrophil Count (ANC). The ANC test at some sites is called the,
       
       
      %Neutrophil, %Neut, %Gran or something to this effect.  The exact name of
      this test should be coordinated with Lab Service.  The %Neutrophil results
      used in this order check are the result returned by the automated lab
      instruments and not the manual entry. The specimen collection sample must be
      identified as well, in most cases that will be blood.  The %Neutrophil test
      
    • 267 SEQ #236
      DATE APPLIED:   2007-09-05 00:51:08
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      This patch enhances the functionality of PSODI, PSO59, and PSO52EX.
         PSOFLAGS: CONTROLS THE PROCESSING OF DATA RETURNED [OPTIONAL] 
         PSOWORD: RETURN OF WORD PROCESSING FIELDS [REQUIRED only with word 
         processing fields]
       
      If a file access error is encountered, the calling application will have
      "0^FILE ACCESS ERROR" returned.  If a FileMan error has occurred, the
      calling application will have "0^FILEMAN UNABLE TO PROCESS REQUEST"
      returned.  A successful data retrieval will return in the format "1^(FIELD
      DATA)".  When retrieving data from a word processing field, an array name
      must be passed in to PSOWORD.  Once the word processing field is returned,
       
      it will then populate an array as defined by PSOWORD and the calling
      application will have "1^(PSOWORD)" returned.  If there is no data in the
      Word Processing field, the calling application will have "1^" returned,
      and the array defined by PSOWORD will be empty.
       
      Please see the VA FileMan Programmer Manual V. 22.0 for $$GET1^DIQ input
      definitions and DBIA 4858 for further description.
       
      PSO59 retrieves data from the OUTPATIENT SITE file (#59) and has three 
      parameters: PSOIEN (optional), PSOTXT (optional), and LIST (required).  
      PSODI contains a new Application Programmer Interface (API) named GET1.
      While PSOIEN and PSOTXT are both labeled as optional, PSO59 requires that 
      either parameter be passed in or no data will be returned.  PSOIEN is the 
      internal entry number (IEN) of a site, PSOTXT is a free text entry that 
      works as a search parameter, and LIST is the subscript name used in the 
      ^TMP global. The new functionality now allows the user to pass in "??" to 
      retrieve all divisions in the file and subscripts them accordingly.  If 
      both an IEN and "??" are passed in, PSO59 will ignore the "??" and return
      data specific to the IEN.  
       
      Please refer to DBIA 4827 for further description on PSO59.
      This API will invoke the $$GET1^DIQ FileMan Database Server (DBS) call and
       
      PSO52EX contains a new Application Programmer Interface (API) named 
      ARXREF. This API is to be used as an extrinsic function call and requires
      three parameters: PSODATE, PSOIEN, and PSOFILL.  PSODATE is the RELEASED 
      DATE/TIME field (#31) and PSOIEN is the internal entry number from the 
      PRESCRIPTION file (#52).  PSOFILL is the fill number of prescription (0 
      for Original Fill, 1 for Refill #1, 2 for Refill #2, etc.).  The user can
      set a local variable equal to the return value of ARXREF. If the return
      value equals:
       
      is to be used as an extrinsic function.  GET1 has five parameters:
         0 (zero) = Data does not exist in the "AR" cross reference, indicating
         the fill was not dispensed from the Consolidated Mail Outpatient
         Pharmacy (CMOP).
       
         1 (one) = Data does exist in the "AR" cross reference, indicating the
         fill was dispensed from the CMOP.
       
      Please refer to DBIA 4902 for further description on PSO52EX.
       
         PSOFILE: FILE OR SUBFILE NUMBER TO RETRIEVE DATA FROM [REQUIRED]
         PSOIEN: IEN TO RETRIEVE DATA FROM [REQUIRED] 
         PSOFIELD: FIELD TO RETRIEVE DATA FROM [REQUIRED] 
      
    • 268 SEQ #237
      DATE APPLIED:   2007-09-05 01:12:34
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      This patch is part of the third quarter enhancements release for the
         on a global node setting of ^DD("DILOCKTM")=3.
       
      Example 1 - Patient Prescription Processing:
      Select Action: Next Screen// NO   New Order
       
      Eligibility: SERVICE CONNECTED 50% to 100%     SC%: 60
      RX PATIENT STATUS: AUTH ABS -96//
       
      Example 2 - Complete Orders from OERR:
      Select By:  (PA/RT/PR/CL/E): PATIENT// ROUTE
      Route:  (W/M/C/E): WINDOW// MAIL
       
       
       
       
                OPPATIENT,ONE (666-00-0777)
           No Allergy Assessment!
       
      Eligibility: NSC
      RX PATIENT STATUS: OPT NSC//
       
      6. In the Patient Prescription Processing [PSO LM BACKDOOR ORDERS]
         In order to avoid the lock issue in Outpatient Pharmacy, this patch
         option, if the Patient Update "PU" action is chosen and the PATIENT
         STATUS is changed to a new one, when returning to the option and
         choosing "NO" for New Order, the default PATIENT STATUS displayed is
         the one before the PU change was done. This patch makes a correction
         to refresh the PATIENT STATUS before displaying the default.
       
      7. When selecting a patient in the Patient Prescription Processing [PSO
         LM BACKDOOR ORDERS] option or the Complete Orders from OERR [PSO LMOE
         FINISH] option, if Remote Data Interoperability (RDI) is turned on, a
         check has been added to check for the ability to access remote data.
         modifies all routines that currently use a lock timeout value of less
         If a problem has been detected with accessing remote data, the patient
         selection will display "Remote data not available - Only local order
         checks processed." once per patient rather than for each individual
         order.
       
      8. If the MAIL STATUS EXPIRATION DATE field (#.05) in the PHARMACY PATIENT
         file (#55) is less than today, the MAIL field (#.03) displays on
         the patient profile as if it is still active. This patch adds the
         display of the MAIL STATUS EXPIRATION DATE field next to the MAIL
         field on the patient profile for MAIL settings of Do Not Mail, Local -
         than 3 seconds to check for the node ^DD("DILOCKTM") and to use the
         Regular Mail and Local - Certified Mail if the mail status is expired.
       
      9. Following the installation of patch PSO*7*200, a site noticed that 6
         digits of the social security number were printing when using the new
         hidden "RS" action to reprint the signature log. This patch changes it
         to 4 digits to match the rest of the labels.
       
      10. In patch PSO*7*200, functionality was provided to use the new
          commercial warning label to send prescriptions to the automated
          filling equipment. One site reported a problem when using the old
         value defined there, otherwise the lock timeout value is set to a
          warning labels, that the HEALTH LEVEL SEVEN (HL7) message sent to
          Optifill was causing an error. This happens when the label text length
          is greater than 512 characters. To prevent this error, this patch
          ensures that the label text length sent does not exceed 245 
          characters. If the label text length exceeds 245 characters, then the
          additional text will be parsed and sent in additional messages.
         default value of 3 seconds.
       
      2. PSI-06-186  - Changing dispense drug and SIG
         When finishing a new order using the Patient Prescription Processing
      Outpatient Pharmacy V. 7.0 package.
         [PSO LM BACKDOOR ORDERS] option, and answering "NO" to the prompt
         "Is this correct? YES//", the software allows the option to edit
         the dispense drug. It allows you to select any active drug from the
         DRUG file (#50) and accept the order even though the entered SIG is
         incorrect. This patch will not list all the active drugs for selection
         during dispense drug edit, but will list only those drugs that are tied
         to that orderable item in the DRUG file (#50).
       
         When the dispense drug is changed the software prompts "Do You want to
         Edit the SIG?  NO//." To read the current SIG you may have to scroll
       
         the screen up. This patch will now display the current SIG along with
         the prompt "Do You want to Edit the SIG? YES//."
       
         A similar modification is also done in this patch for editing an
         existing prescription and the dispense drug is changed, to display the
         current SIG along with the prompt "Do You want to Edit the SIG? YES//."
       
         When finishing a pending order through the backdoor, the software
         allows the option to edit the orderable item and select a different
         dispense drug, but does not prompt you to change the SIG. This can
      1. With the deployment of Cache version 5, it was discovered that the
         lead to incorrect SIG. This patch will now prompt the question
         "Do You want to Edit the SIG? YES//."
       
      3. This patch adds SERVICE REJECT to the current list of selection for
         the Nature of Order prompt.
         Example:
       
         Nature of Order: WRITTEN// ?
         Choose from:
         1            WRITTEN     W
         short lock timeout values could generate a lock failure. Patch
         2            VERBAL     V
         3            TELEPHONED     P
         4            SERVICE CORRECTION     S
         5            POLICY     I
         6            DUPLICATE     D
         12           SERVICE REJECT     R
       
      4. PSI-06-184 - Enhancements for No Allergy Assessment
         The following changes are included to make the pharmacist aware/act on
         prescriptions if they're being entered/finished for a patient with no
         DI*22*147, which has already been released, provided a solution to
         allergy assessment:
         a. Within the profile information, display "No Allergy Assessment"
            next to the allergy header (like "NKA" currently shows)
       
         b. At the same spot where checking for bad address, add a check for
            no allergy assessment and provide a message to the user. (When the
            user continues on, he could choose EA to enter allergy information,
            stop with that patient, or continue on with ordering or finishing).
       
         c. On the profile header, on the right side of the line with patient
         resolve this issue and future lock issues.
            name where <A> currently shows in reverse video if the patient has
            any allergy/adverse reaction information on file, show  <NO ALLERGY
            ASSESSMENT> in reverse video if no assessment has been done.
       
         d. If the pharmacist proceeds with drug entry for a patient with no
            allergy assessment, prompt to intervene just as if there had been an
            allergy reaction and treat this like a critical interaction. (i.e.
            require them to choose to continue processing and if so, prompt for
            an intervention.
       
       
            Note: When flagging is available in backdoor Outpatient Pharmacy for
            pending orders, procedurally sites can choose to flag pending orders
            for patients awaiting an allergy assessment.
       
      5. The patient's eligibility will be displayed before prompting for
         patient status when finishing prescriptions or entering new orders (to
         ensure that the proper entry from the RX PATIENT STATUS file (#53) is
         being selected. This is stored in the PATIENT STATUS field (#3) of the
         PHARMACY PATIENT file (#55)):
         a. In the Patient Prescription Processing [PSO LM BACKDOOR ORDERS]
         This patch instituted a new default lock timeout of three seconds based
            option, redisplay the eligibility just before prompting for patient
            status.
       
         b. In the Complete Orders from OERR [PSO LMOE FINISH] option, after
            displaying patient name, display eligibility and prompt for patient
            status.
       
         c. In both options, use RX PATIENT STATUS: for the prompt instead of
            PATIENT STATUS:
       
      
    • 273 SEQ #238
      DATE APPLIED:   2007-12-12 20:16:04
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      This patch enhances the functionality of PSO59.
      INSTITUTION field (#101) and NCPDP NUMBER field (#1008) from the 
      OUTPATIENT SITE file (#59).
       
      Please refer to DBIA 4827 for further description on PSO59.
       
      PSO59 retrieves data from the OUTPATIENT SITE file (#59) and has three 
      parameters: PSOIEN (optional), PSOTXT (optional), and LIST (required).  
      While PSOIEN and PSOTXT are both labeled as optional, PSO59 requires that 
      either parameter be passed in or no data will be returned.  PSOIEN is the 
      internal entry number (IEN) of a site, PSOTXT is a free text entry that 
      works as a search parameter, and LIST is the subscript name used in the 
      ^TMP global.  This routine will now return field values for the NPI 
      
    • 278 SEQ #239
      DATE APPLIED:   2007-12-12 20:55:15
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      In backdoor pharmacy, when placing a new order, renewing an existing
      CV question will remain the same, i.e., the default answer will be set to
      either 'Yes' or 'No' depending on what is being marked by the provider.
      Order, or copying an order to a new order, if a patient is eligible for
      COMBAT VET (CV), the default answer to the prompt "Was treatment related
      to Combat" is currently presented as Null. This patch will change the
      default answer, currently Null, to 'Yes'.
       
      Note:
       
      When finishing a pending order the current functionality related to the
      
    • 260
      DATE APPLIED:   2007-12-12 21:49:01
      APPLIED BY:   USER,ONE
    • 264 SEQ #241
      DATE APPLIED:   2007-12-12 21:52:07
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      The FY07 Q4 Enhancement Release includes the following PSO enhancements:
            to holders of the PSOAUTRF key with details of Not-Filled refills,
          Example:
       
          Patient Information        Aug 10, 2007@10:04:09       Page: 1 of 2
          OPPATIENT,SEVEN
                                                                  <A>
          PID: 000-12-3456                        Ht(cm): _______ (______)
          DOB: DEC 1,1950 (56)                    Wt(kg): _______ (______)
          SEX: MALE
       
          Eligibility: NSC, VA PENSION
            unsuccessful runs, count of refills processed successfully, etc.
          RX PATIENT STATUS: OPT NSC
       
          Disabilities: POST-TRAUMATIC STRESS DISORDER-100% (SC),
       
          2222 CENTRAL AVE
                                                        HOME PHONE:
          ALBANY                                        CELL PHONE:
                                                        WORK PHONE:
          Prescription Mail Delivery: Regular Mail
          Cannot use safety caps.
       
       
          Allergies
              Verified: PENICILLIN,
          +         Enter ?? for more actions
          EA  Enter/Edit Allergy/ADR Data         PU  Patient Record Update
          DD  Detailed Allergy/ADR List           EX  Exit Patient List
          Select Action: Next Screen//
       
       b. Change the existing 'PHONE:' label to 'HOME PHONE:', and also display
          the PHONE NUMBER [CELLULAR] field (#.134) and the PHONE NUMBER [WORK]
            Note: The new PSOAUTRF security key is transported in this patch and
          field (#.132) of the PATIENT file (#2). The work and cell phone
          fields can be maintained via the PATIENT UPDATE (PU) action and the
          Update Patient Record [PSO PAT] option.
       
      8. Added a new hidden ListMan 'CM' action to the Medication Profile called
         Manual Queue to CMOP [PSO LM QUEUE TO CMOP] to the PSO HIDDEN ACTIONS
         #2 PROTOCOL, to manually queue selected prescriptions to CMOP.
       
      9. Added a new column showing the B/D/F (Bad Address Indicator/ Do Not
         Mail/ Foreign Address) to the Log of Suspended Rx's by Day (this
                  should be assigned to the appropriate personnel to setup the
         Division) [PSO PNDLOG] option.
       
      10. Modified Bad Address Suspended List [PSO BAI SUSPENDED] option to
          include the prompt either B/D/F or 'ALL' in the unprinted suspended
          prescriptions report.
       
       
      MISCELLANEOUS FIXES:
      -------------------
       
                  above job.
      1. With the release of PSO*7*260, a line of code was missing from the
         View Prescription [PSO VIEW] option that displays Dosage, Verb,
         Dispense Unit, Noun, Route, and Schedule. This patch restores this
         functionality.
       
      2. The field description of the REFILL INACTIVE DRUG RXS field (#.111) of
         the OUTPATIENT SITE file (#59) has a typo. It is corrected to
         'prescription'.
       
       
            Example: If the patient is marked as dead, the following message is
                     generated:
       
       
            Subj: ALBANY Internet Refills Not Processed List,  [#104161]
            08/10/07@09:12 11 lines
            From: POSTMASTER  In 'IN' basket.   Page 1  *New*
            ------------------------------------------------------------------
            Internet Refills Not Processed Report for the ALBANY Division.
       
            The following refill requests were not processed:
       
            Patient: OPPATIENT,SEVEN   SSN: 0000
      1. Internet Refill Automation and Reporting
       
            Rx #: 100002461  (REF #1)  Qty: 2
            Drug: ASPIRIN 650MG SUPPOSITORIES
            Reason: Patient Died on AUG 10, 2007
       
       
         b. Added two new fields, PROCESS AUTO REFILLS FOR INPAT field (#2030)
            and PROCESS AUTO REFILLS FOR CNH field (#2035), to the OUTPATIENT
            SITE file (#59) to allow the sites to process/not to process refills
            for inpatients and CNH patients for the scheduled job defined in
         a. Internet Refill Automation Job
            item 1.a above. It will process these refills only if the site has
            flagged these fields as YES.
       
            The Site Parameter Enter/Edit [PSO SITE PARAMETERS] option is also
            modified to include these two new fields.
       
         c. Added a new LOGIN DATE field (#11) to the PRESCRIPTION REFILL
            REQUEST file (#52.43) to capture the date and time the refill
            request was made.
       
            Added a new Automate Internet Refill [PSO AUTO REFILL INITIALIZE]
         d. Added a new Internet Refill Report [PSO INTERNET REFILL REPORT]
            option, to the Output Reports [PSO OUTPUTS] menu that generates
            reports by division, detail, or summary of internet refills sorted
            by Patient, Date, or Result.
       
      2. Modified the Barcode Batch Prescription Entry [PSO BATCH BARCODE] and
         Process Internet Refills [PSO INTERNET REFILLS] options to provide
         separate prompts to Allow refills for inpatient and Allow refills for
         Contract Nursing Home (CNH) instead of a single prompt that applies to
         both.
            option to the Maintenance (Outpatient Pharmacy) [PSO MAINTENANCE]
       
      3. If the REGISTRATION package V. 5.3 patch DG*5.3*688 that introduces the
         COUNTRY field to the PATIENT file (#2) is installed, then:
        a. for Local Mail-outs with foreign addresses, the address information
           on the laser label mailing label is replaced with
           *** FOREIGN ADDRESS ***.
       
        b. In print from suspense, if the address is foreign and the routing is
           not "window", the label will not print nor will the prescription be
           sent to automated filling equipment. The fill will remain on suspense
            menu that allows the sites to schedule/un-schedule a background job
           until it is pulled early, or the routing is changed to window, or the
           address is changed.
       
      4. Added a new Queue CMOP Prescription [PSO RX QUEUE CMOP] option to the
         Suspense Functions [PSO PND] menu, Pharmacist Menu [PSO USER1] and
         Pharmacy Technician's Menu [PSO USER2] menu, to manually queue
         prescription to Consolidated Mail Outpatient Pharmacy (CMOP).
       
      5. The software is modified to check if the Provider has a DEA number in
         the DEA# field (#53.2) or a VA number in the VA# field (#53.3) of the
            to automatically process refill requests placed via the Internet. It
         NEW PERSON file (#200) and the YSCL AUTHORIZED key to order clozapine
         drug. Previously, the check was only for the DEA#. If the ordering
         provider does not have the DEA# or the VA#, the order cannot be placed
         and user will see the message 'Provider must have a DEA# or VA# to
         write prescriptions for clozapine'. Also, if the provider does not hold
         the YSCL AUTHORIZED key, the message 'Provider must hold YSCL
         AUTHORIZED key to write prescriptions for clozapine' is displayed.
       
         Note: The YSCL AUTHORIZED key was transported in the MENTAL HEALTH V.
               5.01 patch YS*5.01*90 and should be assigned to the appropriate
            requires the PSOAUTRF key and generates MailMan messages by division
               provider to write prescriptions for clozapine.
       
      6. The View Provider [PSO PROVIDER INQUIRE] option is modified to display
         the NPI field (#41.99) of the NEW PERSON file (#200).
       
      7. Changes to the Patient Information (Profile) Screen
       a. The PATIENT STATUS field (#3) of the PHARMACY PATIENT file (#55) is
          added to the Patient Information screen. It will be displayed after
          the patient's eligibility.
       
      
    • 285 SEQ #242
      DATE APPLIED:   2007-12-12 22:53:06
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      This patch has enhancements which extend the capabilities of the Veterans
      for Print List is changed to PT for consistency with other Outpatient 
      Pharmacy options.  
       
      2.  The ePharmacy Medication Profile (View Only) [PSO PMP] option is 
      changed to display discontinued prescriptions that do not have a cancel 
      date defined.
      Health Information Systems and Technology Architecture (VistA) electronic
      pharmacy (ePharmacy) system.  
       
      This patch modifies the Outpatient Pharmacy (OP) V. 7.0 application in the
      following areas:
       
      1.  For the Reject Information screen under the Third Party Payer 
      Rejects - Worklist [PSO REJECTS WORKLIST] option, the hidden action PL 
      
    • 283 SEQ #243
      DATE APPLIED:   2008-02-03 22:05:37
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      Problems have been reported with the expiration date of prescriptions.
      prescriptions.
       
      Up-arrow ('^') separated values (patients WITHOUT ICN#):
      SITE NAME VAMC (999)^158^0^0^0^0^0^0^0^0^0^247^3585^6653607
       
      Run Log:
      --------------------------------------------------------------------------
      ----
      SEQ DATE/TIME         INITIATOR                  ACTION
      --------------------------------------------------------------------------
      -----
        
        1 10/21/07@12:01:25 USER1,TEST                 PATCH INSTALLATION
        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 tally 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 count of prescriptions with this problem will be broken down into five
      the
      following support personnel:
       
       
              NAME                     Role
              -----------------------------------------------
              Barron, LuAnne           EPS
              Mohamed, Anwer           Developer
              Rocha, Marcelo           Developer
              Ruzbacki, Ron            Developer
      different groups:
              Willette, Candice        Implementation Manager
              Williamson, Eric         Project Manager
       
      GROUP 1: Prescriptions with a null expiration date.
         
      GROUP 2: Expired prescriptions that are active in CPRS or with an 
               expiration date greater than 366 days.
       
      In some cases the date is not present and other cases have a wrong date.
      GROUP 3: Prescriptions past their expiration date that are active in
               Outpatient Pharmacy.
       
      GROUP 4: Deleted prescriptions. These prescriptions don't necessarily
               have a problem, however they will be resend to HDR.
       
      OTHER  : Prescriptions with database inconsistencies, such as NO PATIENT,
               NO DRUG or NO ISSUE DATE are being counted for informational 
               purpose only.
       
      Furthermore, most of the prescriptions with such problem are not in sync
      The process to count these prescriptions will start right after the patch
      is installed. If it is necessary to stop, restart the job or to know the
      status of the job, run the following command in programmer mode:
         
      >D ^PSO283PI              
        
      Expiration Date problem tally patch for Outpatient Pharmacy prescriptions
      =========================================================================
           Current status: RUNNING (Last Rx IEN: 2587430)
       
      with Computerized Patient Record System (CPRS) V. 3.0 and/or Health 
           Select one of the following:
       
                SP        STOP TALLY JOB
                VW        VIEW PARTIAL TALLY JOB RESULTS
                QT        QUIT
       
      (SP)Stop,(VW)View,(QT)Quit: VIEW//  VIEW PARTIAL TALLY JOB RESULTS
       
       
      Expiration Date clean up job for Outpatient Pharmacy prescriptions
      Data Repository (HDR) in regards to their status. This patch will 
      ==================================================================
      Current status: COMPLETED ON Nov 06, 2007@17:03:36
       
      1. Institution   : SITE NAME VAMC (999)
                                                                       PATIENT
                                                                WITH ICN#   
      W/NO ICN#
      Group 1: RX'S WITH NO EXPIRATION DATE                    ----------  
      ----------
      -------------------------------------
      identify 
      2.  Calc exp date > CUTOFF (update HDR)                         
      363         158
      3.  Calc exp date < CUTOFF,CPRS active (update HDR/CPRS)          
      0           0
      4.  Calc exp date < CUTOFF,CPRS non-active (update HDR)           
      0           0
      5.  No CPRS order# (Update HDR)                                   
      0           0
       
      Group 2: RX'S IN EXPIRED STATUS
      and report a tally of how many prescriptions have such problem. A 
      -------------------------------
      6.  CPRS active (update CPRS/HDR)                             
      5,400           0
      7.  Exp>366 days,reset date,CPRS order# (update CPRS/HDR)         
      0           0
      8.  Exp>366 days,reset date,no CPRS order# (update HDR)          
      18           0
       
      Group 3: RX'S PAST EXPIRATION DATE BUT STILL ACTIVE
      ---------------------------------------------------
      follow-up
      9.  CPRS active (update CPRS/HDR)                                 
      0           0
      10. CPRS DC'd or expired (update HDR)                             
      0           0
      11. No CPRS order# (HDR will run own update)                      
      0           0
       
      Group 4: RX's IN DELETED STATUS
      -------------------------------
      12. No CPRS order# (update HDR)                               
      patch (PSO*7*293) will subsequently be released to fix these 
      2,275         247
       
      OTHER
      -----
      13. BAD RX's: NO PATIENT,DRUG or ISSUE DT (NO UPDATES):              3,585
       
      14. TOTAL NUMBER OF PRESCRIPTIONS ANALYZED:  6,653,607
       
      Up-arrow ('^') separated values (patients WITH ICN#):
      SITE NAME VAMC (999)^363^0^0^0^5400^0^18^0^0^0^2275^3585^6653607
      
    • 280 SEQ #244
      DATE APPLIED:   2008-05-26 15:00:19
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      This patch corrects the following issues.
       
      HD204891 - trade name error (PSI-07-155)
      
    • 274 SEQ #245
      DATE APPLIED:   2008-05-26 15:07:34
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      This patch contains corrections for the following Issues
      HD94995   -  I have recieved a complaint from the Pharmacy that the 
                   Pharmacist field in the prescription file is being filled in
                   during the prescription entry process.
      HD176910  -  Outpatient Pharmacy Activity Log Problem
                   HD161861.
      HD176910  -  Outpatient Pharmacy Activity Log Problem.
      
    • 25 SEQ #24
      DATE APPLIED:   1999-07-19 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      This patch resolves several issues.  
      3. The site parameter EDIT PATIENT DATA is not working properly.
      When set to "YES", it should prohibit editing SSN and DOB. The input
      templates [PSO OUTPT] and [PSO OUTPTA] contained in the PATIENT
      file (#2) have been updated.  
       
      4. After archiving prescriptions, the archived prescription number may be 
      reused. This had created the potential to have two series of prescriptions 
      using the same number.  Added check for new prescriptions for existing
      numbers. 
       
       
       
      5. Two erroneous ^DD nodes are deleted from the PHARMACY PATIENT 
      file (#55).  They are ^DD(55,0,"P") and ^DD(55,0,"PS").  
       
       
      6. Updated the DD(52,0,"ID",6) with correct reference to new field location.  
      1. The routine PSOAMIS0 used the variable DFN to represent a value
      other than the internal file number in the PATIENT file (#2). This variable
      name was changed to PSODFN to comply with standards.  
       
      2. It fixes a potential error when running the nightly tasked job, Compile
      AMISData (NIGHT JOB) [PSO AMIS COMPILE].  
       
      
    • 269 SEQ #246
      DATE APPLIED:   2008-05-26 15:08:08
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      Site reported that the incorrect Orderable Item was selected when the
      entry was entered in "lowercase".  This caused the incorrect medication
      to be given.
      
    • 206 SEQ #247
      DATE APPLIED:   2008-05-26 15:09:06
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      PSO*7.0*206 
      HD68224  - DEA Code handling changes.
        HD68648- dup HD68224
        HD85385- dup HD68224
        HD179790- dup HD68224
      HD186713 - Label shows Certified after mail status.
      HD156961 - Medication status of renewed for meds past stop date.
      HD161968 - Max refill issue for monthly clozapine patient
      
    • 240 SEQ #248
      DATE APPLIED:   2008-05-26 15:33:18
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      This patch will correct the following issues:
       
      HD206713  Activity Log issues
      HD170652 - <UNDEFINED>PAT+1^PSOSD
      
    • 292 SEQ #249
      DATE APPLIED:   2008-05-26 15:34:36
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      PROBLEM:
      1. If expiring or discontinuing a prescription that also has a pending
      renewal, the "renewed from" CPRS order's status is changed to expired or
      discontinued instead of staying as "renewed".
       
      2. If cancel a pending renewal for a previously expired (or 
      discontinued) prescription that had been renewed after expired, the 
      "renewed from" CPRS order should go back to "expired" (or "discontinued")
      instead of remaining as "renewed".
       
      RESOLUTION:
      --------
      -----------
      1. PSOHLSN1 - If  expiring or discontinuing a prescription that also has a
      pending renewal, keep the "renewed from" CPRS order's status as "renewed".
       
      2. PSOHLSN: - If cancel a pending renewal for a previously expired (or 
      discontinued) prescription that had been renewed after expired (or 
      discontinued), set CPRS order's status back to expired (or discontinued).
      HD214867 - Renewed orders remaining active
       
       
      PSI-06-177 - RENEWED ORDERS REMAINING ACTIVE
      (Note: Other scenarios related to renewed orders are being corrected in
      patch PSO*7*257).
       
      
    • 275 SEQ #250
      DATE APPLIED:   2008-05-26 15:40:11
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      Patch PSO*7.0*275 will correct the following issues
      HD122245        Editing Provider Comments/patient instructions
              d-HD154492   Leading punctiation prevents editing Patient 
                           Instructions
      HD179234        Issue with selecting service related option.
      HD196315        Error - <UNDEFINED>SETNEW^PSOBINGO
      
    • 302 SEQ #251
      DATE APPLIED:   2008-05-26 15:49:59
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      Emergency patch to disable PSO SPEED RENEW PROTOCOL.
      
    • 257 SEQ #252
      DATE APPLIED:   2008-05-26 15:53:23
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      This patch addresses PSI-06-177 - MED STATUS RENEWED PAST STOP DATE
        DISCONTINUED
                  SPECIAL QUEUEING: 
      ________________________________________________________________________
      Exit     Save     Next Page     Refresh
       
      Enter a command or '^' followed by a caption to jump to a specific field.
       
      COMMAND: Save 
       
       
      End Capture ********** 
        CANCELLED
        DISCONTINUED/EDIT
        EXPIRED
       
      This patch corrects an additional issue with mis-calculating the default 
      value for the start date prompt for the Manual Auto Expire Rxs [PSO MANUAL
      AUTO EXPIRE] option. 
       
      This patch fixes an error received when running the Compile AMIS Data
       
      (NIGHT JOB) [PSO AMIS COMPILE].  When the Expire Prescriptions [PSO EXPIRE
      PRESCRIPTIONS] or Manual Auto Expire Rxs [PSO MANUAL AUTO EXPIRE] process
      runs at the same time the CMOP transmission is running bad data can be
      created.  The Expire Prescriptions and Manual Auto Expire Rxs processes
      will delete the last refill data if the refill does not have a label
      printed (CMOP fills do not have this) and does not have a Release
      Date/Time which they do not if CMOP has not yet released the refill.  The
      refill node is deleted and then when CMOP does release the refill it only
      sets the Released Date/Time and Dispensed Date so this will be the only
      data set for the refill which causes the error in the AMIS compile.
      This patch will modify the Manual Auto Expire Rxs [PSO MANUAL AUTO EXPIRE]
       
      ==================
      ** IMPORTANT!! **:
      ================== 
      Please check that the nightly expire - PSO EXPIRE PRESCRIPTIONS job is
      tasked to run on a 24 hour rescheduling frequency. This is very important,
      as it relates to the HDR, because this job sets the status of a
      prescription to Expired the day after the prescription expiration date,
      and also updates CPRS and the HDR with this information. If this job is
      not running, prescriptions could show as Active in the HDR, when the
      option and the Expire Prescriptions [PSO EXPIRE PRESCRIPTIONS] option to
      expiration date is in the past.
       
      The job in TaskMan would look something like this:
       
      2478948: PSO EXPIRE PRESCRIPTIONS - Expire Prescriptions.  No device.
               CHYSQA,ROU.  From Today at 1:11,  By you.        Scheduled for 
      Today at 23:00
        
       
       
      check for more values of the STATUS field (#5) in the ORDER file (#100) in
      Please check to see if this job is tasked to run on a 24 hour 
      rescheduling frequency. To access the set-up of this job in Outpatient 
      Pharmacy, follow these steps:
       
       
      Begin Capture **********
       
       
      Select OPTION NAME: PSO MANAGER       Outpatient Pharmacy Manager
      Outpatient Pharmacy software - Version 7.0
      the Computerized Patient Record System (CPRS) before deciding whether to 
       
      Division:    ALBANY  500 
       
                You are logged on under the ALBANY division.
       
      Select PROFILE PRINTER: HOME//   COMPUTER ROOM
       
      Select LABEL PRINTER: HOME//   COMPUTER ROOM
       
      OK to assume label alignment is correct? YES// 
      send the expire transaction. Before, the expire transaction was sent if 
       
      Bingo Board Display: OUTPATIENT//   
       
       
      Select Outpatient Pharmacy Manager Option: MAintenance (Outpatient 
      Pharmacy)
       
       
      Select Maintenance (Outpatient Pharmacy) Option: EXPire Prescriptions
       
      the STATUS field was "ACTIVE". This patch checks for the CPRS status not
      NOTE:
      (The only fields that need to be filled in are the  "QUEUED TO RUN AT 
      WHAT TIME" field to what time you want the job to run,  and the 
      "RESCHEDULING FREQUENCY" field, which should be set to 24H.)
       
                                Edit Option Schedule
          Option Name: PSO EXPIRE PRESCRIPTIONS      
          Menu Text: Expire Prescriptions                      TASK ID: 74539  
        _______________________________________________________________________
       
      being any of the following and if not, will send the expire transaction:
        QUEUED TO RUN AT WHAT TIME: MAR 23,2006@19:00             
       
      DEVICE FOR QUEUED JOB OUTPUT:
       
       QUEUED TO RUN ON VOLUME SET:
       
            RESCHEDULING FREQUENCY: 24H                           
       
                   TASK PARAMETERS:
       
      
    • 281 SEQ #253
      DATE APPLIED:   2008-05-26 16:13:54
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      This patch has enhancements which extend the capabilities of the Veterans 
      1.  EPHARMACY MEDICATION PROFILE (VIEW ONLY) [PSO PMP] option has been
      modified in the following manner:
       
          a.  Patients flagged with the Bad Address indicator will display the
              same warning messages as PATIENT PRESCRIPTION PROCESSING [PSO LM
              BACKDOOR ORDERS] option. If the user holds the PSO ADDRESS UPDATE
              key, a prompt to update the address/phone will be displayed.
       
          b.  The PU - Patient Record Update action has been added to the
              Patient Medication Profile screen.  To achieve this, the 
      Health Information Systems and Technology Architecture (VistA) electronic 
              PU action was added to the PATIENT MEDICATION PROFILE protocol
              menu [PSO PMP MENU].
       
              The following actions have been removed from the Patient 
              Medication Profile screen by removing them from the PATIENT
              MEDICATION PROFILE protocol menu [PSO PMP MENU]:
       
                   DR         Sort By Drug
                   ID         Sort By Issue Date
                   LF         Sort By Last Fill Date
      pharmacy (ePharmacy) system that supports the Electronic Claims 
                   RX         Sort By Prescription
       
          c.  The above removed actions have been added to the hidden actions
              menu by adding them to the ePharmacy Medication Profile Hidden 
              Actions [PSO PMP HIDDEN ACTIONS MENU] protocol.
       
          d.  The REJ View Reject action was added to the hidden menu on the Rx
              View screen.  The ePharmacy Hidden Actions Menu #2 [PSO PMP HIDDEN
              ACTIONS MENU #2] protocol was added to contain this new action,
              and this protocol is also used by the VIEW PRESCRIPTION option
      Management Engine (ECME).  It is the first of four stand alone patches
              [PSO VIEW].
       
       
      2.  The default answer of (I)gnore on the Reject Processing Screen has 
      been changed to (Q)uit which automatically sends the claim rejection  
      information to the Pharmacy Reject Worklist (i.e. re-instate discontinued 
      order, unhold, refill, PP - pull early from suspense, edit that doesn't 
      create a new order, and release with NDC edits). Due to conflicting patch
      release schedules and shared routines with another Pharmacy patch, the new
      order, copy, edits that create new orders, and renewal functions will
      that will fulfill the requirements of ePharmcy/ECME Enhancements Phase 4 
      remain with a default answer of (I)gnore for reject processing screens
      displayed prior to label print. These functions will be updated in a
      subsequent ePharmacy Iteration II patch when the conflict no longer
      exists.
       
      3.  The VIEW PRESCRIPTION [PSO VIEW] option has been modified to give 
      comprehensive help text for the VIEW PRESCRIPTION prompt.  The REJ View
      Reject action was added to the ePharmacy Hidden Actions Menu
      # 2 [PSO PMP HIDDEN ACTIONS MENU # 2].
       
      Iteration II.  It modifies the Outpatient Pharmacy V. 7.0 application as
      4.  The ECME LOG was recording the routing of WINDOW for all original 
      fills and refills.  A modification was made to correctly state the route 
      for each fill that is processed after this patch is installed.  The 
      PATIENT PRESCRIPTION PROCESSING [PSO LM BACKDOOR ORDERS] option,  VIEW
      PRESCRIPTION [PSO VIEW] option, and EPHARMACY MEDICATION PROFILE (VIEW 
      ONLY) [PSO PMP] option is affected by this change.
       
      5.  The ECME Log entry that is stored when a prescription is printed
      from suspense has been changed from stating ECME:SUSP LABEL PRINTED to 
      ECME:PRINTED FROM SUSPENSE.  This change will affect fills processed 
      described below:
      after this patch has been installed.  
       
      6.  A change was made to allow the user to edit Dispensed As Written (DAW)
      and National Drug Code (NDC) fields for expired and discontinued ePharmacy
      prescriptions and refills.
       
      7.  A modification was made to store the last used NDC for payable 
      prescriptions that were pulled early from suspense.  This change affects
      the PULL EARLY FROM SUSPENSE [PSO PNDRX] option and the PP Pull RX action
      of the Patient Prescription Processing [PSO LM BACKDOOR ORDERS] option.
       
       
      8.  A post intall routine (PSO260PI) from PSO*7.0*260 will be deleted 
      with this patch.
       
      
    • 291 SEQ #254
      DATE APPLIED:   2008-05-26 19:20:30
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
       
      next prompt for prescription, if an @ is entered, an undefined error 
      occurs. (HD210092)
       
      2. In the Prescription Cost Update [PSO RXCOST UPDATE] option, unless the 
      original fill date for the prescription is included in the requested date 
      range, the cost will not be updated in the PRESCRIPTION file (#52) for
      any of the fills. If the user selects to update refills and partials 
      also, it updates all fills on the prescription regardless of whether 
      they were within the requested date range. This patch makes a correction
      to update fills only within the requested range without having to 
      This patch corrects the following issues:
      include the original fill in that range. If the user selects an end fill
      date of today or in the future, this option will update the cost for all
      existing and suspended fills that have a fill date in the future. 
      (HD213587)
       
      3. Older data in the Health Data Repository (HDR) could contain
      non-numeric data in the quantity field for some prescriptions. The data
      definition was changed in patch PSO*7*29 to no longer allow alpha
      characters. The following was added to the technical description for
        1. QTY field (#7) in the PRESCRIPTION file (#52)
       
        2. QTY field (#1) in the PRESCRIPTION file REFILL multiple (#52.1)
        3. QTY field (#.04) in the PRESCRIPTION file PARTIAL multiple (#52.2)
       
       NOTE: QTY values that were on file prior to patch PSO*7*29 (released
       2/17/00) may contain alpha characters.
      (HD211759)
      1. In the Delete a Prescription [PSO RXDL] option:
        a. If entering a prescription number that has previously been deleted 
      and then pressing enter when prompted for a prescription again, an
      undefined error occurs. (HD212690)
        b. If enter a character like ! at the prescription prompt, 2 question
      marks are displayed because it is an invalid prescription. Then at the
      
    • 246 SEQ #255
      DATE APPLIED:   2008-05-26 19:30:49
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      MODIFY PSO COST TO IGNORE BAD XREFS IN FILE 52
       
      An Undefined error occurs when editing a large number of prescriptions.
       
      Correct OPAI option 4 in file #59 field #28 (send marked drugs and
      print labels)
       
      Locking Issue
      
    • 26 SEQ #25
      DATE APPLIED:   1999-09-14 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      1. This patch fixes the problem of the allergy warning label document
      Copayment [PSOCP EXEMPTION] option. When setting a status from No to
      Yes, a warning will now be given, and a mail message will be sent to
      all PSORPH key holders informing them of this change.
       
      4. This patch fixes a problem of messages not being exchanged successfully
      between Outpatient Pharmacy and an external application. This problem
      would occur for sites that have the EXTERNAL INTERFACE site parameter set
      to 1 (SEND ALL ORDERS AND PRINT LABEL), 2 (SEND ALL ORDERS AND DON'T PRINT
      LABEL), or 3 (SEND MARKED ORDERS AND DON'T PRINT). Also fixed some
      formatting problems with reports related to the external interface
      possibly printing prior to the filling label for a prescription,
      functions.
       
      5. This patch fixes a problem of an invalid Initiator of Activity being
      stored and displayed in the ACTIVITY LOG REASON (#53.3) file for an edit
      of a prescription.
       
      6. This patch fixes an undefined error that could occur if an invalid
      barcode is entered while in the Change Suspense Date [PSO PNDCHG] option.
       
      7.  This patch corrects a problem that can occur when entering a refill
      when there is no allergy entered to that drug for the patient.
      date for a refillable controlled substance prescription. The date range
      displayed should be the issue date to the expiration date, normally
      followed by a default of Today. The date range ending date will sometimes
      show beyond six months, which is invalid for a refillable controlled
      substance prescription. This patch corrects this problem.
       
      2. Currently, when entering a new prescription, a non-numeric entry can
      be entered for the quantity. This patch makes a leading numeric required
      for the quantity.
       
      3. This patch makes a change to the Exempt Rx Patient Status from
      
    • 293 SEQ #256
      DATE APPLIED:   2008-05-26 19:32:11
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      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:
      -------
      
    • 294 SEQ #257
      DATE APPLIED:   2008-07-22 08:09:29
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      This patch introduces the components necessary to build four tools
      orders that need to be changed.
       
      Tool 2 is a Medication Chart health summary component.  This report
      provides a grid-formatted list of active and pending medications suitable
      for giving to a patient at a clinic visit or upon discharge from the hospital.
       
      Tool 3 is a TIU data object provided as an alternative to the Medication
      Chart health summary process.  The unique aspect of this object is that
      the list, generated for the patient,includes recently expired
      medications but not recently discontinued medications.
      useful for medication reconciliation.
       
      Tool 4 is a series of TIU data objects and health summary components that
      retrieve remote active medications and remote allergy/ADR data.
       
       
      Tool 1 is a Medication Reconciliation Profile health summary component.
      This report creates an alphabetical list of outpatient prescriptions,
      unit dose medications, documented non-VA medications, and remote VA
      medications.  This summary can be used at transition points in a patient's
      care, (admission, discharge, etc.) to identify medications that need to
      be continued, new items to be ordered, old items to be discontinued, or
      
    • 288 SEQ #258
      DATE APPLIED:   2008-07-22 14:34:53
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      SUBSCRIPT ERROR WHEN RUNNING THE HEALTH SUMMARY
      
    • 279 SEQ #260
      DATE APPLIED:   2009-04-20 15:52:14
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      This patch will correct the following
       
      HD216000 - PSOAUTRF Key
      HD226478 - Field missing in NTE segment of HL7 for PMI
      HD214848 - Incorrect wording:  Division used to describe Institution
      
    • 225
      DATE APPLIED:   2009-04-21 15:51:14
      APPLIED BY:   USER,SEVENTEEN
      DESCRIPTION:   
      The Enrollment VistA Changes (EVC) project is being undertaken to support
      This patch provides the functionality changes to determine, process and
          VIEW 2 - This provides the medication list sorted by prescription
                   Status Group, Status, and Drug Name.
                  Active group:
                    Active
                    Hold
                  Pending group
                    Non-Verified
                    Pending
                  Discontinued
                    Discontinued by Provider
      disseminate the newly added Environmental Indicator (EI) called Project
                    Discontinued (Edit)
       
          VIEW 3 - This provides the medication list sorted by Drug Name,
                 active/suspended and Stop Date/Expiration Date.
       
       c. Flag/Un-Flag functionality (PSI-06-041)
          It was requested in the Remedy ticket #133716 that the flagging
          capability that is available in CPRS be made available for
          Outpatient Pharmacy use. This patch provides the flagging
          functionality for Pending orders only.
      112/SHAD Exposure (a.k.a SHAD), where applicable.
       
       d. As per the E3R numbers 19973 and 19876, to improve communication
          between the provider and the pharmacist, Outpatient Pharmacy will now
          send the actual comments made by the pharmacist to CPRS when a
          prescription is put on Hold, Discontinued, and Returned to Stock
          replacing the generic "per pharmacy request" text.
       
       e. When the DC-Discontinue ListMan option is used to discontinue a
          pending "renewal" order, the software will now check for an active
          prescription for the same drug. If found it will prompt the following:
       
          "There is an active Rx for this pending order, Discontinue both
          (Y/N)".
          This will provide the user with the option to discontinue both pending
          and the active order.
       
       f. A problem was reported in one of the error messages displayed on CPRS
          side when a provider tries to discontinue an Outpatient Pharmacy
          order from the Orders Tab and that order for some reason is
          not found in the PRESCRIPTION file (#52). The solution provided is to
          replace the error message "Unable to locate order" with "Invalid
      This patch also changed the EI, "Environmental Contaminant" to read
          Pharmacy order number" to be in consistent with the Inpatient
          Medications V. 5.0 error messages.
       
       g. At the request of CPRS active calls to obsolete routine OR3CONV have
          been removed from Outpatient Pharmacy V. 7.0.
       
       h. When finishing a pending order placed in CPRS, it was reported that
          the patient instructions sent across to CPRS was getting truncated.
          This patch fixes the problem.
       
      as "Southwest Asia Conditions".
       i. PSI-07-057 - Potential of inappropriate or misleading provider
          comments to be automatically included on new medication orders.
          To fix this problem CPRS is dropping (will not carry over) the
          original provider comments during renewals of Outpatient Pharmacy
          medications.
          To follow suit with CPRS, Outpatient Pharmacy is also dropping the
          original provider comments from all backdoor renewals.
       
       1. For the following options, when creating a new order, renewing an
          existing order, copying an existing order to a new order, or editing
          an existing order that results in a new order, the copay status of the
      technology and business changes that are occurring with the implementation
          prescription needs to be determined for billing purposes.
       
          a. Patient Prescription Processing [PSO LM BACKDOOR ORDERS]
          b. Barcode Batch Prescription Entry [PSO BATCH BARCODE]
          c. Complete Orders from OERR [PSO LMOE FINISH]
       
         If a patient is found eligible for SHAD then the prompt
         "Was treatment related to PROJ 112/SHAD?" will be presented to the
         pharmacist.
       
      of the Health Eligibility Center (HEC) Enrollment System Redesign (ESR)
         A "YES" or "NO" response will be stored in the new fields, PROJ
         112/SHAD field (#122.01) of the PRESCRIPTION file (#52) and in the PROJ
         112/SHAD field (#8) of the ICD DIAGNOSIS sub-file (#52.052311) of the
         PRESCRIPTION file (#52).
       
       2. The Integration Control Registration (ICR) #2534, provides
          Computerized Patient Record System V. 3.0 (CPRS) with all the eligible
          EI questions that will be prompted during the pharmacy order entry
          process. This ICR is modified to include the SHAD prompt.
       
      project. Some modified and new business functionality is being included in
       3. When a verbal or telephone order is placed in backdoor pharmacy, it
          requires an electronic signature from the provider. During the
          signature entry process in CPRS, the provider may update the SC, EI,
          or the ICD diagnosis information. This updated information is passed
          back to pharmacy via the ICR #4666, which is modified to include the
          SHAD changes.
       
       4. The PENDING OUTPATIENT ORDERS file (#52.41) that stores the pharmacy
          orders entered via CPRS is modified to include the provider's response
          to the SHAD question. The provider's response will be stored in the
      the new system and corresponding changes are necessary in VistA for
          new fields, PROJ 112/SHAD field (#110.2) of the PENDING OUTPATIENT
          ORDERS file (#52.41) and the PROJ 112/SHAD field (#8) of the DIAGNOSIS
          sub-file (#52.41311) of the PENDING OUTPATIENT ORDERS file (#52.41).
       
       5. During the release of a prescription, if the SHAD question applies and
          is unanswered, the MailMan message that is sent to the finishing
          pharmacist, ordering provider, and holders of the PSO COPAY key, to
          get answers to the EI questions will have the SHAD question if
          applicable.
       
      preliminary determination of veterans Enrollment and Eligibility status.
       6. The Reset Copay Status/Cancel Charges [PSOCP RESET COPAY STATUS]
          option is modified to include the SHAD question wherever applicable.
       
       7. During label printing, if the prescription is flagged as SHAD then the
          text "NO COPAY" will be printed in the label.
       
      Unrelated to the Enrollment VistA Changes (EVC) features, this patch also
      provides the following changes to support CPRS v27.
       
       a. To add the proper escape sequences to the standard HEALTH LEVEL
      The EVC project has been rolled out in three phases. This release
          SEVEN (HL7) encoding characters to messages sent to CPRS / remove
          escape sequences received from CPRS and replace them with standard HL7
          encoding characters. This will help avoid errors that can occur if
          special delimiting characters are encountered during parsing of the
          HL7 messages.
       
       b. Integration Control Registration (ICR) #2400, will be modified to
          provide new sorting sequences of the patient medication profile that
          is viewed under the CPRS-Meds Tab including the Non-VA medications.
       
      represents the third and last phase called EVC Release 2.
          VIEW 0 or null - This provides the medication list as it was prior to
                   GUI 27 so that other applications calling this API will not
                   see any changes.
          VIEW 1 - This provides the medication list sorted by prescription
                   Status Group and Stop Date/Expiration Date. Following is the
                   order:
                  Pending group
                    Non-Verified
                    Pending
                  Active group:
       
                    Active
                    Hold
                    Suspended (Active/Susp)
                    Provider Hold
                  Expired group
                    Expired
                  Discontinued/Deleted group
                    Discontinued by Provider
                    Discontinued (Edit)
       
      
    • 304 SEQ #263
      DATE APPLIED:   2009-04-21 16:18:56
      APPLIED BY:   USER,SEVENTEEN
      DESCRIPTION:   
      Order checks are not generated when editing the dose of a prescription.
      
    • 287 SEQ #264
      DATE APPLIED:   2009-04-21 16:22:20
      APPLIED BY:   USER,SEVENTEEN
      DESCRIPTION:   
      This patch is one of four patches that enhance the ePharmacy software to 
       
       
       
      3.  (Dormant except for item C.) - The Third Party Payer Rejects -
      Worklist [PSO REJECTS WORKLIST] option and the Third Party Payer Rejects -
      View/Process [PSO REJECTS VIEW/PROCESS] options have been modified in the
      following manner:
       
           A. Non-DUR/RTS Tricare rejections will be segregated at the end of
              the displayed information. They will be denoted with a "TRICARE -
              Non-DUR/RTS" header.  This header will remain regardless of
             APPLICATION/VERSION                                  PATCH
              whether the GI - Group by Insurance action is toggled on or off.  
              The Tricare section will sort in the same manner as the main sort
              for non-Tricare prescriptions (i.e. by Rx, drug, patient, etc.).
        
           B. Tricare DUR/RTS rejects will be displayed with all other DUR/RTS
              rejects.  When GI - Group by Insurance action is toggled on, the
              header "TRICARE" will be displayed, and this "TRICARE" section
              will sort alphabetically within the other insurances.  This
              Tricare section is separate from the Non-DUR/RTS section that
              displays at the end of the listing.  When GI is toggled off, these
           --------------------------------------------------------------
              rejects will sorted in the same section as all other DUR/RTS
              rejects.
       
           C. (Not dormant) - The new TRI - Show/Hide Tricare toggle action has
              been added to the hidden menu on the Insurance Rejects screen.  
              When toggled to Show, Tricare Non-DUR/RTS reject will be
              automatically displayed at the end of the listing.  Toggling the
              TRI action to Hide will remove them from the screen.
       
           D. The Reject Information screen has been modified to display TRICARE
       1.  CONSOLIDATED MAIL OUTPATIENT PHARMCY (CMOP) V. 2.0   PSX*2*66
              in the header for the Reject Information section.  For DUR/RTS
              Tricare rejects, the IGN - Ignore Reject action will be shown but
              will not be selectable. For Non-DUR/RTS Tricare rejects, the FIL -
              Fill Rx action will be displayed. If the prescription is payable,
              the user will be allowed to fill the prescription and print the
              label.  If not payable, a message will be displayed stating that
              the prescription must have a payable status to be filled.
       
           E. For rejects that remain in suspense, the user will be allowed to
              process the rejection as indicated above, however no labels will
       2.  OUTPATIENT PHARMACY (OP) V. 7.0                      PSO*7*287
              be printed until the prescription is pulled early or printed from
              suspense.  Upon resolving the reject, the user will be notified
              of this information.  CMOP prescriptions will function in the same
              manner.
       
      4.  In preparation for a future ePharmacy patch the following fields are 
      being added to PRESCRIPTION file (#52) for original fills and refills:
      DATE NDC VALIDATED field (#83) and NDC VALIDATED BY field (#84).  
       
      5.  For ePharmacy prescriptions, the price per dispense unit for the
       3.  ELECTRONIC CLAIMS MANAGEMENT ENGINE (ECME) V. 1.0    BPS*1*6
      NDC will be saved in PRESCRIPTION file (#52).  For original fills, the  
      UNIT PRICE OF DRUG field (#17) will be updated.  For refills, the CURRENT
      UNIT PRICE OF DRUG field (#1.2) of REFILL multiple (#52.1) will be
      updated. If the NDC chosen is the default NDC, the value stored will be
      taken from PRICE PER DISPENSE UNIT field (#16) of DRUG file (#50).  If the
      NDC selected is a synonym, the PRICE PER DISPENSE UNIT field (#404) of
      SYNONYM multiple (#9) of DRUG file (#50) will be saved. In the case of
      CMOP fills, only the default NDC price will be stored which is taken from
      PRICE PER DISPENSE UNIT field (#16) of DRUG file (#50).
       
       4.  INTEGRATED BILLING (IB) V. 2.0                       IB*2*383
      6.  (Dormant) - If ECME's status on the claim remains in an "In Progress"
      state past the processing time out during finish of the prescription,
      Tricare prescriptions will not be allowed to be filled and must be
      discontinued.
       
      7.  (Dormant) - If the pharmacy is active for ePharmacy processing but the
      insurance plan is not linked or not active, Tricare prescription will be
      allowed to be filled normally.  The phrase "Inactive ECME Tricare" will be
      displayed during Finish.
       
      All four patches are being released separately with a requirement that 
      they be installed in the order outlined above.  There are no other 
      provide the framework to support Tricare and Active Duty outpatient
      dependencies between these patches, except that Tricare/Active Duty 
      billing will not be supported by ePharmacy until all 4 patches are 
      installed.
       
      All sites should install these patches regardless of whether or not they 
      have been activated for ePharmacy by the CBO or are providing outpatient
      pharmacy services to Tricare or Active Duty patients.  After the
      installation of these patches, the activation status of the site will not
      be impacted.  As before, activation of the ePharmacy product will require
      instructions provided by the CBO, and sites are not to activate ePharmacy
      pharmacy billing.  The Tricare/Active Duty portions of this software
      unless instructed specifically by the CBO.  Also, sites should not start
      to provide outpatient pharmacy services to Tricare patients without
      discussions with the CBO.
       
      This patch modifies the Outpatient Pharmacy v7.0 application as described
      below.  The modifications labeled dormant in the software and will remain
      inactive until the future Tricare patch is released.
       
      1.  (Dormant) - Prescriptions where the patient is Tricare eligible will
      be submitted to ECME for third party insurance processing in the same
      enhancement will not be active until a future patch is released.  The
      manner as all other insurance types.  Tricare eligibility is determined by
      Integrated Billing (IB). An indicator is returned to Outpatient Pharmacy
      PRESCRIPTION file (#52) and REFILL multiple (#52.1) to be stored in the
      new BILLING ELIGIBILITY INDICATOR field (#85).  Because this is a set of
      codes field, the internal value will be T, V or C. These values will be
      displayed respectively to the user as TRICARE, VETERAN, or CHAMPVA. Note
      that CHAMPVA will not be addressed in this patch.  Prescriptions with only
      a 'VETERAN' eligibility flag are what is currently processed through ECME.
       
      2.  (Dormant) - When a Tricare prescription has a third party rejection,
      release of the additional patch is pending Central Business Office (CBO)
      the same reject notification screen will be displayed to the user as is
      currently done for the Veteran eligibility.  Tricare Rejections will be
      stored in the same manner as Drug Utilization Review (DUR) and
      Refill-too-soon (RTS) prescription reject are currently stored.
       
      The following exceptions will apply for Tricare prescriptions:
       
          A.  All Tricare rejections will be denoted as Tricare in the REJECT 
              Information header on the Reject Information screen.
       
      contracting with the Tricare Fiscal Intermediary.
          B.  Where DUR or RTS are one of the reject codes, the user will be
              able to select from (D)iscontinue the prescription, submit 
              (O)verride codes, or (Q)uit which sends the rejection to the Third
              Party Payer Rejects - Worklist.  Tricare rejection may not be
              (I)gnored.
       
          C.  For prescription rejections that have non-DUR/RTS rejects, the
              user will be able to select from (D)iscontinue the prescription or
              (Q)uit which sends it to the Third Party Payer Rejects - Worklist.
       
       
          D.  For non-billable Tricare prescriptions, an abbreviated version of
              the reject notification screen will be displayed.  Because the
              prescriptions is non-billable, the insurance and ECME information
              that's currently provided for DUR/RTS rejects will not be
              displayed (i.e. insurance, group name, group #, ECME #, contact,
              cardholder ID).  In this case, the user will only be able to
              (D)iscontinue the prescription due to the business rule that OP
              cannot fill Tricare prescriptions that are non-billable.
       
          E.  Labels will not print for discontinued Tricare prescriptions.
      Below is a list of all the applications involved in this project along 
              Reprint labels will not be allowed to be printed for Tricare
              rejected prescriptions.  The reject notification screen will be
              displayed during reprint in the same manner as non-Tricare
              prescription currently are displayed with the exception of the
              available actions listed above for Tricare prescriptions.
       
          F.  Suspended prescriptions will remain on suspense when a reject
              occurs, when the Rx is non-billable, or when the third party claim
              remains in an 'IN PROGRESS' status in ECME.  Labels will not
              print.  Once the reject is resolved, the user may pull the Rx 
      with their associated patch number:
              early from suspense or wait for the next scheduled print from
              suspense runs at which time labels will print accordingly. This
              includes CMOP and local suspense.
       
          G.  Rejected Tricare prescription may not have a partial fill ordered 
              until the reject is resolved.
       
          H.  When the  Pull Early from Suspense [PSO PNDRX] option is used, 
              Tricare prescriptions will be processed in the foreground and
              rejections will be displayed for user intervention.
      
    • 297 SEQ #265
      DATE APPLIED:   2009-04-21 16:25:07
      APPLIED BY:   USER,SEVENTEEN
      DESCRIPTION:   
      SCRIPTALK DISPLAYING LAST 6 OF SSN
      
    • 315 SEQ #266
      DATE APPLIED:   2009-04-21 16:32:27
      APPLIED BY:   USER,SEVENTEEN
      DESCRIPTION:   
      CPRS GUI V27 FOLLOW UP ISSUES: 
       
       
                   .D PP S ORD=0 D @PSRT S PAT(PAT)=PAT
                                   ^
                   <NOLINE>PRI+15^PSOORFI5
       
      This patch will correct this issue.
      =============================
       
      The Complete Orders From OERR option [PSO LMOE FINISH] breaks when the
      user selects to process pending orders via Priority status and when they
      answer "NO"  to the prompt "Do you want to see Medication Profile? Yes//"
      NO. 
       
      Below is a screen capture of the hard error:
      
    • 299 SEQ #267
      DATE APPLIED:   2009-04-22 12:21:47
      APPLIED BY:   USER,SEVENTEEN
      DESCRIPTION:   
      This patch contains two APIs for extracting data from the PRESCRIPTION
      (#52) file. The APIs are in the routine PSOCLINR, the APIs are:
       
      STAT(PSO) ;Returns Status (#100) external format from Prescription (#52)
                 file
      NEPSRX()  ;Returns the number of prescriptions in the file
      
    • 27 SEQ #26
      DATE APPLIED:   1999-09-14 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      1) This patch, in conjunction with patches from Inpatient Medications and
      patient. Additionally, CPRS users will no longer be locked out of entering
      orders for a patient, when orders for that patient are being finished in
      the Outpatient Pharmacy package.
       
      2) A change has been made in the messaging that takes place when
      prescriptions are released or returned to stock. This change will not
      effect the Outpatient Pharmacy user.
       
      3) This patch fixes a problem when a prescription is Renewed, and the
      provider renewing the prescription required a cosigner when the
      Computerized Patient Record System (CPRS), will enhance the way that
      prescription that is being renewed was originally entered, but no longer
      requires a cosigner. The cosigning physician was being carried over to the
      new prescription, and printing on the Action Profile, even though the
      provider no longer required a cosigner. This patch will fix this problem.
       
      4) A problem was reported that involves the prescription numbering
      sequence. If a prescription is entered for a controlled substance, then
      the drug is edited to a non-controlled substance after answering "No" to
      the "Is this Correct" prompt, then the prescription will still be assigned
      a number from the controlled substance sequence of prescription numbers.
      locking is done at the order level and at the patient level among these
      This patch corrects this problem.
       
      5) This patch corrects a problem of the Non-Formulary warning printing
      next to the dispense drug on the order screen in Outpatient Pharmacy, at
      times when it is not appropriate to print. This can result from an order
      being entered with a dispense drug that has a valid Non-Formulary status,
      then that drug is edited to a drug that should not have a Non-Formulary
      status, but the Non-Formulary indicator still prints next to the dispense
      drug.
       
      packages. Anytime an order is acted upon in the Outpatient Pharmacy
      6) This patch corrects a problem of a user in CPRS being able to enter a
      refill request that comes to the Outpatient Pharmacy package, even if the
      refill request is beyond the expiration date of the prescription.
       
      7) This patch corrects a problem that can occur in the Complete Orders
      from OERR [PSO LMOE FINISH] option for sites with multiple CPRS ordering
      institutions. At the "Select CPRS ORDERING INSTITUTION" prompt, sometimes
      the default will not be accepted if the user enters return. The user is
      forced to type in the institution name. This patch corrects the problem.
       
      package, locks will now take place within the Outpatient Pharmacy package
      8) This patch will bring back the functionality of doing drug interaction
      checks on Renewals.
       
      9) This patch fixes a problem encountered when finishing orders in
      Outpatient Pharmacy that were entered through CPRS before the day the
      order is finished. These orders were being treated as future fills and
      being suspended, since the order had been entered on a previous day
      through CPRS. This patch makes a change where these will no longer
      be seen as future fills, as long as the order is being filled for today.
       
      at that order level, and the order will also be locked in CPRS. A Pharmacy
      10) This patch addresses an issue that occurs when removing
      a prescription from a pharmacy hold status. Prior to this patch, this
      action would always generate a label request, regardless of whether or not
      the last fill of the prescription had been released. This patch makes a
      change to not print a label when removing a prescription from hold if the
      last fill of the prescription has been released.
       
      11) When editing the Drug of a prescription, if the new Drug is matched
      to the same Pharmacy Orderable Item, and there are synonyms in the
      Pharmacy Orderable Item file (#50.7) that contain numbers in the
      Patient lock has also been created. When actions on orders take place in
      synonym name, it is possible that after editing the Drug, the
      Pharmacy Orderable Item will change to an incorrect Pharmacy Orderable
      Item. This patch corrects the problem.
       
      12) Currently, a prescription that is on Provider Hold should not be
      acted upon through the Outpatient Pharmacy package. If you are entering a
      new prescription and get a duplicate drug or duplicate class check on
      a prescription that is on provider hold, you are currently able
      to discontinue the prescription that is on provider hold. This patch will
      prevent that prescription on provider hold from being discontinued, so the
      Outpatient Pharmacy that could result in a change in the order, all other
      new prescription entry will not be allowed, since the discontinue action
      is not allowed.
      Pharmacy users will be locked out of acting on any orders for that same
      
    • 317 SEQ #268
      DATE APPLIED:   2009-04-22 15:19:35
      APPLIED BY:   USER,SEVENTEEN
      DESCRIPTION:   
      This patch modifies the Outpatient Pharmacy v7.0 application as described
      below:
       
       
      1. After release of an ePharmacy Phase 4 patch (PSO*7*287), it was found
      that the PSOORED6 routine was erring or causing a DIE error due to a
      variable being killed in a called routine.  This patch corrects this
      error.
      
    • 296 SEQ #269
      DATE APPLIED:   2009-04-22 15:26:22
      APPLIED BY:   USER,SEVENTEEN
      DESCRIPTION:   
      The "stop date" for complex Outpatient prescriptions do not display in 
      the Computerized Patient Record System (CPRS). This patch resolves this 
      issue.  The resolution implemented by this patch is not retroactive.  
      Only Outpatient prescriptions entered after patch installation will 
      display the "stop date" in CPRS.
      
    • 303 SEQ #270
      DATE APPLIED:   2009-04-22 15:52:24
      APPLIED BY:   USER,SEVENTEEN
      DESCRIPTION:   
      This patch has enhancements which extend the capabilities of the Veterans 
      activate unless instructed specifically by the CBO.
       
      This patch is being released along with PSS*1*139 and IB*2*405.  These
      patches can be installed in any order but the full functionality 
      for Nutritional Supplement additions contained within these patches will
      not be available until all 3 patches are installed.
       
      This patch modifies the Outpatient Pharmacy v7.0 application as described
      below:
          
      Health Information Systems and Technology Architecture (VistA) electronic 
      1.  Modifications to change the default answer of (I)gnore on the Reject 
      Processing Screen to (Q)uit which automatically sends the claim rejection 
      information to the Pharmacy Reject Worklist for new orders, copies, edits 
      that create new orders, and renewal functions.  This patch, PSO*7*303,  
      includes the modifications for these functions.
       
      2.  Additional software to handle the new "N  for Nutritional Supplement
      DEA special handling code added in patch PSS*1*139.  This new "N" code
      will be treated the same as supply items and investigational drugs in
      Outpatient Pharmacy.  Copay will not be charged, and third party billing 
      pharmacy (ePharmacy) billing system.
      for these type drugs will only occur when the drug is also marked with 
      "E" for Electronically Billable.  When the drug is not defined to be 
      electronically billable, the ECME Log will reflect drug not billable.  
      For prescriptions where the eligibility changed since the last refill, a 
      "PRESCRIPTION QUESTIONS REVIEW NEEDED" MailMan message is sent.  The last 
      paragraph of this message will be changed to include nutritional drugs:
       
           Supply, nutritional and investigational drugs are not charged a VA
           copay but could be reimbursable by third party insurance.
       
       
      3.  For the ePharmacy Medication Profile (VIEW ONLY) [PSO PMP] option,
      flagged pending orders will be notated on the medication profile screen by
      highlighting the sequence number shown on the left side of the screen.  
      Note that the "Flagged by..." information shown once the prescription is
      selected is already present with the PSO*7*225 release.
       
      4.  For Tricare Reversal/Resubmit actions sent to ECME with NDC changes,
      the text for the ECME activity log was too large to fit in the field
      without being truncated.  The log entry text "Reversal/Re-submit sent"
      has been abbreviated to "Rev/Resubmit" to ensure the entire NDC is 
      All sites should install this patches regardless of whether or not they 
      viewable in the log entry.
      have been activated for ePharmacy by the Central Business Office (CBO).  
      After the installation of these patches, the activation status of the 
      site will not be impacted.  As before, activation of the ePharmacy 
      product will require instructions provided by the CBO.  Sites are not to 
      
    • 319 SEQ #271
      DATE APPLIED:   2009-04-23 11:28:39
      APPLIED BY:   USER,SEVENTEEN
      DESCRIPTION:   
      This patch will fix the issue where the incorrect patient is 
      printed on the label. 
      
    • 300 SEQ #272
      DATE APPLIED:   2009-04-23 11:32:40
      APPLIED BY:   USER,SEVENTEEN
      DESCRIPTION:   
      The Pharmacy Prescription Practices V.1.0 package is being retired per
      PSI-07-114. Therefore, calls to the PPP package within Outpatient
      Pharmacy V.7.0 need to be removed.
      
    • 323 SEQ #273
      DATE APPLIED:   2009-04-23 12:45:56
      APPLIED BY:   USER,SEVENTEEN
      DESCRIPTION:   
       
       
       
      This patch addresses a subscript error in routine: PSOHLSN
      HD0000000291680 - <SUBSCRIPT>SEGPARX+4^PSOHLSN
      
    • 301 SEQ #274
      DATE APPLIED:   2009-04-23 14:09:58
      APPLIED BY:   USER,SEVENTEEN
      DESCRIPTION:   
      ASSOCIATED REMEDY:
      ==================
      HD220858 - PSI-07-227 - Error Filling Prescriptions in Outpatient Pharmacy
      d HD231034 - Wrong script information
      d HD237297 - HL7 prescription issue
      
    • 305 SEQ #275
      DATE APPLIED:   2009-06-03 11:36:56
      APPLIED BY:   USER,SEVENTEEN
      DESCRIPTION:   
      The FY08 Q4 Enhancement Release includes the following enhancements.
      This patch adds a new NTE8 segment that has the VA Notice of Privacy
      Practices, IB 10-163 narrative to the content of the laser labels print
      stream.  If you are using automated dispensing equipment that relies on
      the data stream sent to the laser labels port, you have to contact your
      vendor to make adjustments to the trailer page as defined in item #4
      below.
       
      1. Automate CPRS Refill Processing
      ==================================
      This patch provides functionality to automatically process refills placed
       
      by the provider via CPRS.  A new system parameter, AUTOMATE CPRS REFILLS
      field (#40.16), has been added to the PHARMACY SYSTEM file (#59.7) by the
      Pharmacy Data Management V. 1.0, patch PSS*1*137 to support this
      functionality.
       
      Please refer to patch PSS*1*137 for more details.
       
      The auto refill process will occur only if the new AUTOMATE CPRS REFILLS
      field (#40.16) of the PHARMACY SYSTEM file (#59.7) is set to YES and the
      security key, PSOAUTRF, has been assigned to at least one user; otherwise
      1. Automate Computerized Patient Record System V. 1.0 (CPRS) Refill
      the current process will continue where the orders have to be finished
      manually. Orders processed automatically will have the refill date
      calculated by the refill process to the next possible fill date and the
      routing will be set to Mail.
       
      During the auto refill process, if the criteria for refilling fails, then
      the order will not be processed but will be stored in the PENDING
      OUTPATIENT ORDERS file (#52.41) for manual processing. Also, a MailMan
      message, with the reason for not filling the auto refill, will be sent to
      holders of the PSOAUTRF security key. This should be very rare since CPRS
         Processing.
      will allow refills only if they are refillable.
       
      2. Display of both the Fill Date and the Release Date
      =====================================================
      On the Patient Medication Profile screen, new functionality was
      implemented to allow users to have the option of viewing either the FILL
      DATE or the RELEASE DATE information. This is done by using a hidden
      ListMan action called RDD to invoke the RELEASE DATE display and will
      remain for that session. Using the RDD action again will display the FILL
      DATE.
      2. Display of both the Fill Date and the Release Date.
       
      3. Duplicate Drugs Message Enhancements
      =======================================
      This enhancement is related to patient safety issue PSI-07-236 and remedy
      ticket RT223633. When a duplicate drug message is displayed, the heading
      "CMOP Status" is currently shown for CMOP drugs only. This heading is
      being renamed to "Processing Status" and it will appear on every duplicate
      drug message along with the release status.
       
      4. Notice of Privacy Practice Reminder on Laser Labels
      3. Duplicate Drugs Message Enhancements.
      ======================================================
      When the labels are printed for a patient's prescriptions, the
      following narrative will be printed on the trailer page in either English
      or Spanish, depending on the patient's language preference.
       
      The English version reads as follows.
       
        The VA Notice of Privacy Practices, IB 10-163, which outlines your
        privacy rights, is available online at http://www1.domain.ext/Health/ or you
        may obtain a copy by writing the VHA Privacy Office (19F2), 810 Vermont
      4. Notice of Privacy Practice Reminder on Laser Labels.
        Avenue NW, Washington DC 20420.
       
      The Spanish language translation for the Privacy Notification reads as
      follows.
       
        La Notificacion relacionada con las Politicas de Privacidad del
        Departamento de Asuntos del Veterano, IB-10-163, contiene los
        detalles acerca de sus derechos de privacidad y esta disponible
        electronicamente en la siguiente direccion:
        http://www1.domain.ext/Health/. Usted tambien puede conseguir una copia
       
        escribiendo a la Oficina de Privacidad del Departamento de Asuntos de
        Salud del Veterano, (19F2), 810 Vermont Avenue NW, Washington, DC 20420.
      ***** NOTE TO SITES USING AUTOMATED FILLING EQUIPMENT *****
      
    • 289
      DATE APPLIED:   2009-07-14 09:12:33
      APPLIED BY:   USER,SEVENTEEN
      DESCRIPTION:   
      DThis patch has enhancements which extend the capabilities of the Veterans
         OUTPATIENT PHARMACY (OP) V. 7.0                      PSO*7*289
      The system will not hold a prescription for 3/4 days supply when:
       
          -   the previous fill was not ECME billable
          -   the Rx is flagged for SC or EI
          -   the DEA special Handling code is non billable (i.e. has M or 0 
                   (zero) or  (I, S, N, and/or 9)) without and E.
          -   the Rx is a zero fill on a renewal
          -   the patient does not currently have insurance
       
      6. A modification was made to PRESCRIPTION file (#52), REJECT INFO 
         INTEGRATED BILLING (IB) V. 2.0                       IB*2*384
      sub-file (#52.25), CLARIFICATION CODE field (#24). This was a set of codes
      field.  It is now a pointer to file #9002313.25 (BPS NCPDP CLARIFICATION
      CODE).  A post install routine will go through the reject info subfile and
      convert the old set of code values to the appropriate new pointer values.
      The post install will send a mail message to the person installing the
      build which details the affected rejected prescriptions.  The 'Submit
      Clarif. Code' protocol [PSO REJECT DISPLAY CLARIFICATION CODE] has been
      altered to use the new pointer value.
       
      7. The 'Edit NDC and DAW Code of Discontinued/Expired Prescriptions' 
         ELECTRONIC CLAIMS MANAGEMENT ENGINE (ECME) V. 1.0    BPS*1*7
      functionality introduced in PSO*7.0*281 has been extended to also allow 
      edits of prescriptions with a status of DISCONTINUED BY PROVIDER and 
      DISCONTINUED (EDIT).
       
      8. New functionality was added to create a nightly background mail 
      message regarding open/unresolved rejects on the reject worklist.  The 
      'Third Party Payer Rejects - Nightly Message' option [PSO REJECTS 
      BACKGROUND MESSAGE] will be queued to run every 24 hours by the post 
      install routine.  This option is intended to be a stand alone option and 
      should not be placed on any menu.  The message will be delivered to the 
       
      'PSO REJECTS BACKGROUND MESSAGE' mailgroup; this mailgroup should be 
      populated with appropriate ePharmacy users to receive the information.  
      Mail messages are generated for each division. Sites may alter EPHARMACY
      SITE PARAMETERS file (#52.86) REJECT WORKLIST DAYS field (#4) for each 
      division using the ePharmacy Site Parameters option [PSO EPHARM SITE 
      PARAMETERS] of the ePharmacy Menu.  If no sites are defined in the 
      EPHARMACY SITE PARAMETERS file (#52.86), no message will be generated.  
      This parameter may be defined to be 1 to 30 days that an uncommented
      reject can remain on the reject worklist without being included in the
      nightly reject worklist alert mail message.  The following are the
      The last three patches (PSO*7*289, IB*2*384 and BPS*1*7) will be released 
      criteria for a reject to be included in the mail message:
       
          a. The prescription is active, suspensed, expired, or on hold.
          b. The prescription is unreleased.
          c. The claim has been on the Reject Worklist for more days than the
             value in the REJECT WORKLIST DAYS field for the division.
          d. The claim has no comments added within the date range.
       
      9. New functionality was added to allow NDC validation of third party
      payable prescriptions by pharmacy technicians.  Current functionality
      in the Kernel Installation and Distribution System (KIDS) multi-build 
      requires a pharmacist to perform this task.  In addition, for the
      PRESCRIPTION file(#52) and the REFILL sub-file (#52.1), the DATE NDC
      VALIDATED field (#83) and NDC VALIDATED BY field (#84) will be captured
      when the NDC is validated for a prescription or refill; this validation
      information will be displayed when prescriptions are released; if the NDCs
      have not been validated, that information will be displayed instead.  The
      'NDC Validation' option [PSO NDC VALIDATE] has been added to the ePharmacy
      Menu for use by technicians.  The option will work as follows:
       
          a. The technician will be prompted to scan or enter a prescription 
      distribution BPS PSO IB BUNDLE 3.0.  Patches PSX*2*65 and PSS*1*131 will 
             number.  An '^' may be entered to halt the option.
          b. The system will evaluate the Rx.  If the Rx NDC has already been 
             validated, the technician will be prompted if they wish to
             revalidate. If the answer is yes, the technician will be allowed to
             proceed.  If the answer is no, the technician will be returned to
             the select a prescription prompt.
          c. If the Rx is CMOP, external interface or released, the user will
             not be allowed to verify the Rx.
          d. The system will display information about the Rx, notate that the
             Rx has not been previously verified and will prompt for PRODUCT 
      be released as stand-alone patches.  Since there is an implementation 
             NDC. A valid PRODUCT NDC must be entered for this prompt.  Valid
             PRODUCT NDC's are those defined for the drug in Drug file (#50) as
             an NDC of a synonym or the default NDC.
          e. The system will compare the Rx NDC to the PRODUCT NDC submitted on
             the ePharmacy claim.  If the NDCs do not match, the system will
             reverse and resubmit a third party claim with the new NDC and 
             store the new NDC on the fill.
          f. If the prescription is defined as TRICARE and is not payable, the 
             system will display an appropriate message and the technician will 
             be returned to the select a prescription prompt.
      dependency between the multi-build distribution and the stand-alone 
          g. If the prescription is defined as TRICARE and the reversed claim 
             returns not payable, the system will display an appropriate 
             message and the technician will be returned to the select a
             prescription prompt.
          h. Otherwise, the system will update the NDC validation fields for the
             Rx/Fill, and the technician will be returned to the select a
             prescription prompt.
       
      10.  The RES - Resubmit Claim action was added to the Reject Information
      (TRICARE) screen of the Third Party Payer Rejects - Worklist [PSO REJECTS
      patches, PSX*2*65 and PSS*1*131 must be installed prior to the 
      WORKLIST] option.
       
      11.  The following functionality will work only if the REGISTRATION
      package V.5.3 patch DG*5.3*688 that introduces the COUNTRY field to the
      PATIENT file (#2) is installed:
       
         When using the Print from Suspense File [PSO PNDLBL] option, if the
         routing is MAIL and the address is Foreign, it will be treated just
         like the BAD ADDRESS INDICATOR or DO NOT MAIL order where:
       
      Health Information Systems and Technology Architecture (VistA) electronic 
      installation of the multi-build.  For more specific instructions please 
         a. The prescription will not be sent to the automated filling equipment
            and/or to the label printer. The fill will remain on suspense until
            it is pulled early, the routing is changed to window, or the address
            is changed.
       
         b. For the first time attempt to print from suspense, an entry will be
            added to the activity log and a MailMan message will be generated to
            the user who queued the job to print from suspense and the members
            of the PSO EXTERNAL DISPENSE ALERTS mail group.
       
      refer to the installation steps provided in each of the patches.
      12.  When the NDC changes during auto-release of the prescription for CMOP
      or OPAI fills, the fill date on the fill be updated to become the same as
      the release date.  An entry will be made in the activity log for the fill 
      to denote the changed date.
       
      This patch modifies the Outpatient Pharmacy v7.0 application as described
      below:
       
      1.  A modification was made to prevent users from entering a suspense date
      that is greater than the fill date plus 90 days.  Dates where the fill
      date plus 90 days is greater than the expiration date will not be allowed.
       
      pharmacy (ePharmacy) billing system.  Below is a list of all the 
      2.  Functionality to allow non-DUR/RTS reject to be placed on Third Party 
      Payer Rejects - Worklist [PSO REJECTS WORKLIST] option was added.  To 
      accomplish this the following additions were made:
       
          a.  A new EPHARMACY SITE PARAMETERS FILE (#52.86) was added to store
              ePharmacy specific parameters by division.  Along with this file, 
              a new EPHARMACY SITE PARAMETERS [PSO ePHARM SITE PARAMATERS]
              option was added for entry/edit of parameters.  Regardless of any
              parameters defined in this new file, Refill-Too-Soon (RTS), Drug
              Utilization Review(DUR) and Tricare rejects will always be placed
      applications involved in this project along with their patch number:
              on the Pharmacy Reject Worklist.
       
              Sites will have the ability to select to allow all third party 
              rejects to pass to the the Third Party Payer Rejects - Worklist
              which is also referred to as the Pharmacy Reject Worklist or they
              can choose to specify individual reject codes. Individual third
              party reject codes can be defined to be automatically placed on
              the worklist or defined to require OPECC intervention. If the site
              chooses to allow all rejects to be placed on the worklist,
              individual codes are overridden but not deleted from the file.
       
       
           b. For display of non-DUR/RTS rejects for the Third Party Payer
              Rejects - Worklist [PSO REJECTS WORKLIST] option, rejects passed
              via OPECC manual intervention will be denoted in the comment
              section of the Reject Information screen as:
       
              - JUN 09, 2008@14:04:18 - Transferred by OPECC. (user,name)
       
          
              Rejects passed automatically will be denoted in the comments 
         APPLICATION/VERSION                                  PATCH
              section of  the Reject Information Screen as 
       
             - JUN 09, 2008@16:00:09 - Automatically transferred due to override
               for reject code. (user,name)
       
              All rejects other than Refill-Too-Soon, DUR, and Tricare will be 
              displayed at the end of the listing under "OTHER REJECTS"
              header. The "OTHER REJECTS" header will be displayed regardless of
              whether the GI - Group Insurance action is toggled on or off.  
              
         --------------------------------------------------------------
              Non-DUR/RTS rejections will be resolved with the existing
              functionality and will be resubmitted to ECME in the same manner
              as DUR/RTS rejections.
       
      3.  A modification was made to not allow a claim to be reversed through 
      ECME for an unreleased CMOP fill when the prescription/fill is 
      discontinued. If the fill is either a CMOP released or Non-CMOP released 
      fill the reversal will be performed.  Because the software already 
      performs a reversal for unsuccessful/not dispensed claims, no changes are 
      needed for reversing discontinued non-dispensed fills.  Also, no changes 
         CONSOLIDATED MAIL OUTPATIENT PHARMACY (CMOP) V. 2.0  PSX*2*65
      are needed when the NDC from CMOP differs from the NDC on the claim 
      because this function is already performed by existing software.
       
      4. New functionality was added to prevent prescriptions from being 
      filled/sent to CMOP when a host processing error occurs when a claim is 
      submitted through ECME. The host processing errors are identified by 
      reject codes M6, M8, NN, and 99. The following conditions apply when this 
      scenario occurs.
       
          a. The transmission of the Rx/fill will be delayed 1 day in hopes
         PHARMACY DATA MANAGEMENT (PDM) V. 1.0                PSS*1*131
             that the host processing issues will be resolved.
          b. An activity log entry will be defined to state the date/time 
             along with a comment stating that the Rx/fill was left in suspense
             hold due to a host processing error.
          c. This added functionality does not include the Pull Early from 
             Suspense function.
       
      5. New functionality was added to the Print from Suspense File [PSO 
      PNDLBL] option to prevent ePharmacy prescriptions from being pulled early
      from suspense until 3/4 of the days supply of the Rx/fill has elapsed.  
      
    • 311 SEQ #277
      DATE APPLIED:   2009-07-14 09:13:36
      APPLIED BY:   USER,SEVENTEEN
      DESCRIPTION:   
      REMOVE TEMPORARY MENU OPTIONS
      
    • 30 SEQ #27
      DATE APPLIED:   1999-12-10 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      1. This patch fixes a problem that can occur when editing a prescription
      Mfg______Exp______ will print on the labels after the quantity and
      dispense unit. The patch makes a change to also look at the COMMUNITY
      NURSING HOME field (#40) of the PHARMACY PATIENT file (#55), so if a
      patient is flagged as YES in either of these 2 fields, the text
      Mfg_____Exp_____, will print on the labels.
       
      3. This patch fixes a problem that can occur when a pending renewal order
      from Computerized Patient Record System (CPRS) is discontinued by Pharmacy
      without renewing the original order. If this occurs, and that same
      original order is renewed again in CPRS, the user in CPRS will receive a
      that is suspended for local filling. If the patient is flagged as DO NOT
      message saying that it is a duplicate renewal request, and will not be
      allowed to process the renewal, even though the original renewal was
      discontinued. This patch will allow that subsequent renewal to be sent to
      pharmacy for completion. A post-init routine in this build will run that
      will kill an invalid cross reference in the PENDING OUTPATIENT ORDERS file
      (#52.41). This will allow for the functionality to be in place for all
      previous orders.
       
      4. This patch fixes a problem of "NKA" sometimes printing when it
      shouldn't in the Allergy section of the labels, and in the HL7 message to
      MAIL in the MAIL field (#.03) of the PHARMACY PATIENT file (#55), and
      external applications.
       
      5. A renewal problem can occur when renewing a prescription that has been
      canceled by the Autocancel Rx's on Admission [PSO AUTOCANCEL1] option. If
      that canceled prescription was never filled, then the new prescription
      could be suspended too far in the future. This patch corrects the problem.
       
      6. This patch fixes an undefined error that can occur in the Patient
      Prescription Processing [PSO LM BACKDOOR ORDERS] option, when viewing
      the medication profile. The error would only occur for a drug name that
      that suspended prescription is edited, it can possibly be removed from
      is greater than 40 characters in length, which is prohibited by the
      nationally exported data dictionaries.
       
      7. This patch fixes a problem of a prescription label printing for a
      refill when it should not print. If a refill is processed for a
      prescription and the label is queued to print, and that refill is
      deleted before the label prints, a label will print for the
      last fill documented in the prescription. This patch changes the
      functionality to not print a label for a prescription if the refill
      associated with the label request is deleted before the label prints.
      local suspense and suspended for Consolidated Mail Outpatient Pharmacy
      (CMOP), even though the patient is flagged as DO NOT MAIL.
       
      2. On Outpatient Pharmacy labels, if a patient is flagged as YES in
      the CNH CURRENT field (#148) of the PATIENT file (#2), then the text
      
    • 170
      DATE APPLIED:   2009-07-14 15:21:31
      APPLIED BY:   USER,SEVENTEEN
      DESCRIPTION:   
      The following issues are addressed in this patch:
      is updated for a patient, an entry is queued for retransmission.
       
       
      2. During internal testing, it was discovered that the FIRST SERVICE DATE
      field (#.07) and the ACTUAL/HISTORICAL FLAG field (#.08) were not being
      set appropriately when the user exited out of label print. This patch
      corrects this problem.
      1. This patch addresses a request which support the Pharmacy Benefits
      Management (PBM) Extracts Enhancement #3 project. In order to allow the
      retransmission of only those patients who have had demographic updates,
      Outpatient Pharmacy V. 7.0, Inpatient Medications V. 5.0, Registration
      V. 5.3 and Pharmacy Data Management V. 1.0 were modified to build an entry
      for re-transmission in PBM PATIENT DEMOGRAPHICS File #59.9.
       
      When the FIRST SERVICE DATE field (#.07) in the PHARMACY PATIENT file #55
      
    • 266 SEQ #279
      DATE APPLIED:   2009-07-29 11:05:47
      APPLIED BY:   USER,SEVENTEEN
      DESCRIPTION:   
      PSO*7*266 will correct the following remedy tickets
      HD153822   90 day supply with 11 refills allowed.
          Dupe: HD186337     Drug Change And No Refills.
      HD129050   Allowable Refills
      HD198754   BINGO BOARD DISPLAYING INCORRECT RX #
      HD120910   Incorrect Suspend Date 
      
    • 306 SEQ #280
      DATE APPLIED:   2009-08-05 17:19:04
      APPLIED BY:   USER,SEVENTEEN
      DESCRIPTION:   
      This patch will fix the issue where the Lot # is carried over
      is set to Today instead of the same date as the original refill.
      to the new prescription during a renewal.
      It will also fix an issue with the Refill Date when a prescription
      is suspended.
      If a user creates a prescription with a Fill Date of Today and then a 
      refill is requested for Today, the prescription is put into suspense for
      a future date.
      If the refill is deleted and then re-added without exiting the OP
      Medication screen, the suspense date for the newly requested refill
      
    • 320 SEQ #281
      DATE APPLIED:   2009-08-06 14:28:05
      APPLIED BY:   USER,SEVENTEEN
      DESCRIPTION:   
      The FY09 Q2 Enhancement Release includes the following.
         if a patient has remote prescription(s), then the user will be prompted
                          FOR PATTESTING FOR PATIENT TESTING FOR PATTESTING
                          FOR PATIENTENT INTRUCT ION ON SIG1 TESTING FOR
                          PATIENT INTRUCTION ON SIG1 TESTING FOR PATIENT
                          REPLACE IENT WITH IENT TESTING FOR PATIENT
                          INTRUCTION ON SIG1 TESTING FOR PATI
                     PROVIDER: PSOPROVIDER,ONE
       
      5. In the Pull Early from Suspense [PSO PNDRX] and Print from Suspense
         File [PSO PNDLBL] options, if the patient has remote prescriptions, then
         the text "THIS PATIENT HAS PRESCRIPTIONS AT OTHER FACILITIES" will be
         with the following question.
         displayed on the report as shown in the following example.
       
                           PRESCRIPTION PROFILE AS OF 12/30/2008
       
                              NAME: PSOPATIENT,ONE
                              ID# : 000-00-0000
       
         THIS PATIENT HAS PRESCRIPTIONS AT OTHER FACILITIES
       
                              PHARMACIST: __________________  DATE: ________
       
       
       
       
      6. Three new protocols were added: PSO RDI VISITS MENU, PSO RDI BOTH, and
         PSO RDI REMOTE.
       
      7. Two new list templates were added: PSO RDI VISITS and PSO RDI VISITS
         DETAIL.
      
      
                REMOTE PRESCRIPTIONS AVAILABLE!
      
                Display Remote Data? N//
       
         If the response is "No", then there are no changes to the existing
         functionality. If the response is "Yes" then it provides a new screen
         to view the remote data as shown in the following example.
       
       
      Remote Facilities Visited     Dec 30, 2008@17:26:47          Page: 1 of 1
       
      Patient: PSOPATIENT,ONE            (000-00-0000)      DOB: 01/02/1967
       
        Station
        HDR CHEYENNE
       
       
       
                Enter ?? for more actions
      This patch provides the ability to view a patient's remote prescription
      DR  Display Remote Pharmacy Data        DB  Display Both Pharmacy Data
      Action:Quit//DR
       
      Medication Profile - Remote   Dec 30, 2008@17:29:43       Page: 1 of 2
       
      Patient: PSOPATIENT,ONE             (000-00-0000)      DOB: 01/02/1967
       
        RX#         DRUG                              ST QTY ISSUED  LAST FILLED
      HDR CHEYENNE
      712885        AMOXICILLIN TRIHYDRATE 250MG CAP   A  90 11/06/08  11/06/08
      data within Outpatient Pharmacy V. 7.0 using the Remote Data
                    SIG: TAKE ONE CAPSULE BY MOUTH THREE TIMES A DAY
                    PROVIDER: PSOPROVIDER,TEN
      712886        DILTIAZEM (INWOOD) 240MG CAP,SA    A  30 11/28/08  11/28/08
                    SIG: TAKE ONE CAPSULE BY MOUTH EVERY DAY
                    PROVIDER: PSOPROVIDER,TEN
      712888        LABETALOL HCL 200MG TAB            A  60 12/30/08  12/30/08
                    SIG: TAKE ONE TABLET BY MOUTH TWICE A DAY
                    PROVIDER: PSOPROVIDER,TEN
      712887        SIMVASTATIN 20MG TAB               A  15 12/09/08  12/09/08
                    SIG: TAKE ONE-HALF TABLET BY MOUTH EVERY EVENING TESTING
      Interoperability (RDI) interface to retrieve data from the Health Data
                         FOR PATTESTING FOR PATIENT TESTING FOR PATTESTING
                         FOR PATIENTENT INTRUCTION ON SIG1 TESTING FOR
                         PATIENT INTRUCTION ON SIG1 TESTING FOR PATIENT
                         REPLACE IENT WITH IENT TESTING FOR PATIENT
      +         Enter ?? for more actions
       
      Select Action:Next Screen//
       
      2. In the Patient Prescription Processing [PSO LM BACKDOOR ORDERS] option,
         on the Patient Medication Profile screen, a new hidden ListMan action
      Repository (HDR).
         called DR [DISPLAY REMOTE] was added to display a patient's remote
         prescriptions.
       
      3. In the Complete Orders from OERR [PSO LMOE FINISH] option, if a user
         answer "Yes" to the prompt 'Do you want to see Medication Profile?',
         then if a patient has remote prescription(s), the user will be
         prompted with the following question.
       
                REMOTE PRESCRIPTIONS AVAILABLE!
                Display Remote Data? N//
       
       
         If the response is "No", then there are no changes to the existing
         functionality. If the response is "Yes", then it provides a new screen
         as shown in item #1.
       
      4. In the Action Profile (132 COLUMN PRINTOUT) [PSO ACTION PROFILE] COLUMN
         option, if a patient has remote prescription(s) then they are printed
         at the end of the report as shown in the following example.
       
                           MEDICATION PROFILE FROM OTHER VAMC(s)          Page: 4
      The following changes were made.
                                  Date Printed: 12/22/2008
       
      Patient: PSOPATIENT,ONE                                      DOB: 05/01/1955
      ===============================================================================
       
         RX #        DRUG                               ST  QTY  ISSUED   LAST
      FILLED
      ===============================================================================
      HDR CHEYENNE
       
      1. In the Patient Prescription Processing [PSO LM BACKDOOR ORDERS] option,
      712885         AMOXICILLIN TRIHYDRATE 250MG CAP   A    90  11/06/08   11/06/08
                     SIG: TAKE ONE CAPSULE BY MOUTH THREE TIMES A DAY
                     PROVIDER: PSOPROVIDER,ONE
       
      712886         DILTIAZEM (INWOOD) 240MG CAP,SA    A    30  11/28/08   11/28/08
                     SIG: TAKE ONE CAPSULE BY MOUTH EVERY DAY
                     PROVIDER: PSOPROVIDER,ONE
       
      712887         SIMVASTATIN 20MG TAB               A    15  12/09/08   12/09/08
                     SIG: TAKE ONE-HALF TABLET BY MOUTH EVERY EVENING TESTING
      
    • 322 SEQ #282
      DATE APPLIED:   2009-09-24 10:48:37
      APPLIED BY:   USER,SEVENTEEN
      DESCRIPTION:   
      1. Undefined error in routine PSOATRF.
      2. DUZ variable being reset.
      3. Replace direct call to data dictionary with Pharmacy API
      
    • 326 SEQ #283
      DATE APPLIED:   2009-11-30 13:59:47
      APPLIED BY:   USER,SEVENTEEN
      DESCRIPTION:   
      The FY09 Q1 Enhancement Release is related to PSI-07-090 (PSPO #543) and
                                          (addressed in patch PSN*4*181)
          Complete Orders from OERR [PSO LMOE FINISH]
          Pull Early from Suspense [PSO PNDRX]
          Print from Suspense File [PSO PNDLBL]
           - 5 Standard Print from Suspense
          Reprint a non-voided Outpatient Rx Label [PSO SCRIPTALK REPRINT
                                                    VISTA LB]    
          Queue ScripTalk Label by Barcode [PSO SCRIPTALK MANUAL INTERNAL]
          Queue ScripTalk Label by Rx# [PSO SCRIPTALK MANUAL EXTERNAL] 
       
      Remedy Ticket #189923. The Social Security Number (SSN) was removed from
      Additionally, the ability to lookup by prescription number or wand a
      barcode with the prescription was added to the patient lookup prompt on
      the following options.
        Patient Prescription Processing [PSO LM BACKDOOR ORDERS]
        Medication Profile [PSO P]
        Rx (Prescriptions) [PSO RX]
        Update Patient Record [PSO PAT]
        Manual Print of Multi-Rx Forms [PSO LM MULTI-RX PRINT]
        ScripTalk Patient Enter/Edit [PSO SCRIPTALK PATIENT ENROLL]
        Patient Address Changes Report [PSO ADDRESS CHANGE REPORT]
      the print out given to the patient from the following options.
        List Prescriptions Not Mailed [PSO BAI NOT MAILED]
        Non-VA Meds Usage Report [PSO NON-VA MEDS USAGE REPORT]
        Enter New Patient [PSO BINGO NEW PATIENT]
        Action Profile (132 COLUMN PRINTOUT) [PSO ACTION PROFILE]
        Poly Pharmacy Report [PSOPOLY].
       
      The help text for patient lookup was modified and will display the
      following.
        Enter the prescription number prefixed by a # (ex. #XXXXXXX) or
        Wand the barcode of the prescription. The format of the barcode is
        Action Profile (132 COLUMN PRINTOUT) [PSO ACTION PROFILE]
        NNN-NNNNNNN where the first 3 digits are your station number.
                  - OR -
        Answer with PATIENT NAME, or SOCIAL SECURITY NUMBER, or last 4 digits
        of SOCIAL SECURITY NUMBER, or first initial of last name with last 4
        digits of SOCIAL SECURITY NUMBER
        Do you want the entire NNNNNNNN-Entry PATIENT List?
        Medication Profile [PSO P]
        Printing/Reprinting prescription labels using these options:
          Patient Prescription Processing [PSO LM BACKDOOR ORDERS]
           - ListMan hidden action (RP)  - Reprint (OP)
           - ListMan hidden action (OTH) - MI Print Medication Instructions
      
    • 308 SEQ #284
      DATE APPLIED:   2009-12-03 09:07:20
      APPLIED BY:   USER,SEVENTEEN
      DESCRIPTION:   
      This patch will fix an error that is caused by a long provider comment 
      (more than 32 characters with no spaces) that is entered in CPRS and
      copied when the pending order is processed in Outpatient Pharmacy.
      
    • 321 SEQ #285
      DATE APPLIED:   2010-01-21 17:12:06
      APPLIED BY:   USER,SEVENTEEN
      DESCRIPTION:   
      This patch will resolve the issue where another patient's 
      prescription is printing on the label log.
      
    • 327 SEQ #286
      DATE APPLIED:   2010-01-28 14:48:10
      APPLIED BY:   USER,SEVENTEEN
      DESCRIPTION:   
      CARRIAGE RETURNS IN HL7 MESSAGES SENT TO HDR
      
    • 324 SEQ #288
      DATE APPLIED:   2010-02-17 10:48:21
      APPLIED BY:   USER,SEVENTEEN
      DESCRIPTION:   
      The FY09 Q3 Enhancement Release includes the following.
      "No Allergy Assessment - Do you want to duplicate Intervention? Yes//"
       
      If the answer is "No," then it will prompt for a new intervention.
       
      If the answer is "Yes," then it will display the last intervention
      entered. The following is an example.
       
      INTERVENTION DATE: DEC 11, 2008       PATIENT: PSOPAT,NAME
      PROVIDER: PSOPROV, NAME               PHARMACIST: PSOPHARM, NAME
      DRUG: "current order drug name"       INSTITUTED BY: PHARMACY
       
      INTERVENTION: ALLERGY                 RECOMMENDATION: OTHER
      ORIGINATING PACKAGE: OUTPATIENT       DIVISION: OKLAHOMA CITY VAMC
       
      Would you like to edit this Intervention? No//
       
      If "No," then the system accepts the intervention and continues.
      If "Yes," then the system allows editing of the intervention.
       
       
      2. PSI-07-181 (PSPO# 865) - Remedy Ticket # HD208961
      1. PSI-07-134 (PSPO #771) - Remedy Ticket # HD200301/HD217962
       
      A prescription's strength was changed in Computerized Patient Record
      System V. 1.0 (CPRS) creating a new Rx. The original Rx had been
      transmitted to Consolidated Mail Outpatient Pharmacy (CMOP) on the
      previous day. When finishing, the pharmacist missed the previous day's
      transmission to CMOP of the original prescription. Both Rxs were mailed
      to the patient in the same package from the CMOP.
       
      When a CMOP prescription with a status of Transmitted or Retransmitted is
      discontinued by a background process to the Outpatient Pharmacy options,
       
      e.g. CPRS or Registration V. 5.3 packages, then an email notifying that a
      prescription was just discontinued for that Rx will be sent to the new PSX
      EXTERNAL DISPENSE ALERTS mail group created by patch PSX*2*68 (see
      PSX*2*68 patch description for details). If no recipients are defined in
      the new mail group, then it will be sent to PSXCMOPMGR key holders. The
      email alert will inform the group that the CMOP status for the Rx just
      discontinued was either Transmitted or Retransmitted as seen in the
      example below.
       
        Subj: TROY - DC Alert on CMOP Rx 123456789 TRANSMITTED  [#90494]
      In Outpatient Pharmacy during order entry when there is no allergy
        03/03/09@17:37 8 lines
        From: POSTMASTER  In 'IN' basket.   Page 1  *New*
        ------------------------------------------------------------------------
                     Rx #: 123456789   Fill: 0
                  Patient: OUTPATIENT,DCONE (6660)
                     Drug: TAMOXIFEN CITRATE 10MG TABS
                Rx Status: DISCONTINUED BY PROVIDER
        Processing Status: TRANSMITTED to CMOP on 02/27/09
                 Provider: OPPROVIDER, PROV
       
      assessment on file for a patient, the user will be given the ability to
        ********    Please contact CMOP or take appropriate action    ********
       
        Enter message action (in IN basket): Ignore//
        ------------------------------------------------------------------------
       
      When a CMOP prescription with a status of Transmitted or Retransmitted is
      discontinued by a foreground Pharmacy process due to a duplicate drug
      scenario that would trigger the duplicate to be discontinued, then the
      Processing Status field of the duplicate drug message is highlighted to
      alert the user. Below is an example.
      duplicate the allergy intervention data filed for the last drug.
       
        ------------------------------------------------------------------------
        Duplicate Drug A AND Z OINTMENT in Prescription: 123456789
       
                          Status: Active                       Issued: 03/03/09
      <<BOLD>> Processing Status: Transmitted to CMOP on 03/04/09 <<BOLD>>
                             SIG: APPLY 1 TUBE TO AFFECTED AREA TWICE A DAY
                             QTY: 1                         # of refills: 5
                        Provider: OPPROVIDER, PROV     Refills remaining: 5
                                                      Last filled on: 03/04/09
      In order to provide this functionality, during subsequent allergy
                                                         Days Supply: 5
        ------------------------------------------------------------------------
       
      Discontinue RX # 123456789?
      intervention, this patch will now prompt
      
    • 32 SEQ #28
      DATE APPLIED:   2000-02-29 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      1) E3R #12579: If an edit is done on a pending order, which results in the
      pharmacist.  If the Verification field (#.12) is set to no the pharmacy tech
      will not be able to finish medication orders from CPRS.  
       
      3) E3R #10287:  This E3R request was to move the actual discontinuation of a
      prescription when a duplicate drug or class order check occurs.
      Prescriptions will no longer be discontinued when the user says yes to
      discontinue duplicate drugs or drug classes during new order entry but when
      the user answers yes to the prescription is correct.  
       
      4) Modified software to allow medication orders put on hold through CPRS to
      creation of a new order, the following text will be automatically entered in
      be discontinued by Outpatient Pharmacy.  
       
      5) E3R #11810: The name of the printer device shall be displayed at the
      label prompt along with an additional action of 'CHANGE PRINTER'. The same 
      functionality as provided by the Change Label Printer [PSO CHANGE PRINTER] 
      option will be used.  
       
      6) E3R #11658: The existence of a release date shall be used to determine 
      whether the fill date for the original or refill is deleted or retained.  If
      the original fill for a prescription has been released, the fill date will
      the REMARKS field (#12) of the PRESCRIPTION file (#52), "CPRS Order #nnnn
      not be deleted when put on hold. The fill date will be shown as the last
      fill date. If the original fill has not been released the current
      functionality will be retained and the fill date deleted. The same will hold
      true for refills.  If the last refill has been released when a prescription
      is placed on hold, that fill shall be retained as the last fill. If the last
      refill has not been released, the prior fill date will be used.  
       
      7) E3R #11294: The speed renewing functionality will be modified to: 
       a. Remove the DAYS SUPPLY and # of Refill prompts from the speed renew 
      process.  
      Edited." 
       b. The original Rx days supply, # of refills and quantity values will be
      used as defaults for the prescriptions renewed through the SPEED RENEW
      actions.  
       
      8) This patch corrects a problem where provider comment from a finished 
      prescription medication order could be carried over to a subsequent 
      prescription medication order.  
       
      9) E3R # 11309: There is a future development project that involves both 
      Pharmacy and CPRS medication ordering that should address the inaccurate 
       
      calculation of the days supply. In the meantime, in order to help determine
      the appropriate value for the DAYS SUPPLY field (#8) and to somewhat help 
      distinguish what was entered by the provider versus pharmacy software
      defaults, pharmacy software will be modified to show the number of refills
      entered by the provider. Below the number of refills prompt displayed on the
      screen when finishing an order a statement such as (11 refills ordered by
      provider) will be also displayed.  
       
      10) A problem was reported when finishing orders by Clinic or Clinic Sort
      Group in the Complete Orders from OERR [PSO LMOE FINISH] option. If a
      2) This patch corrects a problem that allows pharmacy technicians to finish
      patient has a pending order for the Clinic or Clinic Sort Group chosen, and
      that order is discontinued, the Patient Information screen would still
      appear for that patient, even though there are no orders to finish. This
      patch resolves the problem.
        
      11) This patch corrects a potential problem of duplicate prescriptions. The 
      problem can occur when variables are not cleaned up preventing duplicate
      order checks from occurring.  
       
      12)  Corrected a problem when a duplicate drug class has been entered and
      prescription medication orders from Computerize Patient Record System (CPRS).
      the other duplicate has been put on provider hold. User is not prompted to
      discontinue provider held prescription.  
       
      13)  E3R #12827:  This E3R request that only numeric quantities be allowed
      when finishing orders from CPRS.  
       
      14)  E3R 12850:  This E3R requests that functionality be added to allow the
      inactivation of outpatient divisions.  A new field, INACTIVE DATE (#2004),
      will be used to inactive outpatient divisions in the OUTPATIENT SITE file
      (#59).  
      The problem was that if a site did not have the site parameter Verification
       
      15)  A new field, DAYS TO PULL SUSPENDED CS CMOP field (#3.1), in the
      OUTPATIENT SITE file (#59) will be installed with patch.  This field will be
      used with future CMOP functionality.  
       
      16)  This patch corrects a possible null subscript error when marking
      non-verified prescriptions as deleted.
       
      17) This patch corrects a possible subscript error when finishing orders
      from CPRS.
      field (#.12) set to yes, the prescription label printed without review by a
      
    • 337 SEQ #289
      DATE APPLIED:   2010-02-23 16:25:06
      APPLIED BY:   USER,SEVENTEEN
      DESCRIPTION:   
      In the Batch Barcode option a non-pharmacist can renew a prescription 
      without a pharmacist review.  
      The Refill option works fine.
      
    • 335 SEQ #290
      DATE APPLIED:   2010-03-31 10:56:41
      APPLIED BY:   USER,SEVENTEEN
      DESCRIPTION:   
      PROBLEMS WITH PSO INTERNET REFILL REPORT
      
    • 338 SEQ #291
      DATE APPLIED:   2010-04-05 14:37:44
      APPLIED BY:   USER,SEVENTEEN
      DESCRIPTION:   
      The FY10 Q1 Enhancement Release includes the following.
         b. At the prompt, "Select By:  (PA/RT/PR/CL/FL/E): PATIENT//", the help
            text "FL FLAG" was changed to "FL FLAGGED".
       
      2. PSPO #1101 - Remedy Ticket #275487
         The following enhancements were made to the prescription laser label.
         a. The current title "Additional Warning Labels" that is printed at
            the top of the PMI section was renamed to "Additional Warnings".
       
         b. If the warning label is lengthy, requiring more than the four
            provided lines, the label is truncated so the text "... See printed
       
            Additional Warnings." can be added to the end of the fourth line.
       
         c. The truncated warning label and its code are printed in their
            entirety at the top of the PMI section under the "Additional
            Warnings" section.
       
      3. Remedy Ticket #345084
         The warning message "<There are ## flagged orders for INSTITUTION>" is not
         displayed when there is only one associated CPRS ordering institution
         with an outpatient site. Routine PSOORFI2 was corrected to fix this
      1. PSPO #1167
         problem.
      
         The following enhancements were made for the Flagged Pending Orders.
         a. When using the Complete Orders from OERR [PSO LMOE FINISH] option,
            the message "<There are ## flagged orders for INSTITUTION>" is
            displayed in reverse video to alert the user that there are
            flagged pending orders.
       
      
    • 312 SEQ #292
      DATE APPLIED:   2010-05-05 09:52:01
      APPLIED BY:   USER,SEVENTEEN
      DESCRIPTION:   
      This patch will modify the dispensing machine releasing so 
      the Message Server ID field (#10) of the Pharmacy External 
      Interface file (#52.51) does not get overwritten for previous 
      fills with the latest Message Server Id.
      
    • 298 SEQ #293
      DATE APPLIED:   2010-05-18 15:23:25
      APPLIED BY:   USER,SEVENTEEN
      DESCRIPTION:   
      This patch will correct the following issues
       
       
      HD0000000206768 - Activity Log - Sig Edits
      HD0000000219618 - Rx Fill Date Missing
      HD0000000303117 - 2 "Sorry  bout that.  $ZERROR=" error message
      
    • 345 SEQ #294
      DATE APPLIED:   2010-05-20 10:30:13
      APPLIED BY:   USER,SEVENTEEN
      DESCRIPTION:   
      This patch will resolve the issue where the pharmacist is kicked out of 
      the system after they flag pending orders from a list of orders.  Added 
      to this is a fix for the Ignored Rejects Report [PSO IGNORED REJECTS 
      REPORT], where an error occurs if only one patient is selected in the 
      sorting option.
      
    • 347 SEQ #295
      DATE APPLIED:   2010-05-26 10:01:29
      APPLIED BY:   USER,SEVENTEEN
      DESCRIPTION:   
      This patch will resolve the Patient Safety issue (PSPO-1424)
      where CMOP prescriptions are not suspending.
      
    • 336 SEQ #296
      DATE APPLIED:   2010-05-26 11:26:45
      APPLIED BY:   USER,SEVENTEEN
      DESCRIPTION:   
      A duplicate NTE 8 was inadvertently created via patch  PSO*7.0*305 to add 
      the VA Notice of Privacy Practices.
      If the patient has other language preference then the Spanish patient 
      instructions are already being sent in the
      NTE 8 segment.
      
    • 341 SEQ #297
      DATE APPLIED:   2010-06-02 10:51:09
      APPLIED BY:   USER,SEVENTEEN
      DESCRIPTION:   
      This patch resolves an UNDEFINED error in routine PSO52PAI.  
      This error occurred while users were loading IB patch IB*2*400.
      The error resulted from processing invalid ePharmacy data in
      the Pharmacy file (#52).
      
    • 334 SEQ #298
      DATE APPLIED:   2010-06-15 10:11:41
      APPLIED BY:   USER,SEVENTEEN
      DESCRIPTION:   
      This patch will fix the issue where multiple labels are printed.
      
    • 28 SEQ #29
      DATE APPLIED:   2000-02-29 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
       1. This patch corrects the problems with the Cost Management Cost compile
       patch as the print template is modified to accommodate this new piece.
       
       3. This patch fixes a possible undefined variable error that may occur
       during Bingo Board Display.
       
       4. This patch fixes a possible stack overflow error of a local variable
       array by using the ^TMP global.
       
       5. This patch fixes a problem where patients were not being registered
       completely into the Clozapine program.
       that was enhanced in PSO*7*20. The nightly cost compile job was
       
       6. In the Monthly Rx Cost Compilation [PSO COSTMONTH] option, "the AL"
       cross reference node is used for accumulating cost related information.
       There are times this node has more than one record logged for the same
       date and time. This patch ensures that the cost compile routine does not
       skip any of the logged records.
       
       7. In the Print Bingo Board Wait Time [PSO BINGO REPORT WAIT TIME]
       option, it was reported that the wait time for prescriptions filled at
       10:00am or released at 10:00am were showing very high wait time. This
       calculating the averages incorrectly.
       patch corrects this problem by fixing the trailing zeroes to the
       canonical value that is returned from the Fileman API call NOW^%DTC.
       
       8. In the Print Bingo Board Statistics [PSO BINGO REPORT PRINT] option,
       it was reported that the divisions total page is generated when one or a
       range of divisions are selected, but does not generate the total page
       when all divisions are selected. This patch fixes this problem.
       
       2. In Drug Costs by Division [PSO COST BY DIVISION], this patch fixes the
       REQUESTS column that was showing the same figure for all divisions (which
       was the total patient count of the pharmacy), instead of breakdown by
       divisions by introducing a new piece in File# 50.9006.
       The sort and print templates PSO COST STAT, are also sent out with this
      
    • 344 SEQ #299
      DATE APPLIED:   2010-07-13 12:37:58
      APPLIED BY:   USER,SEVENTEEN
      DESCRIPTION:   
      The Clinical Reminders Order Check project will introduce the
        ARRAY("ISSUE DATE")=ISSUE DATE field (#1)
        ARRAY("PROVIDER")=PROVIDER field (#4) (internal and external format)
        ARRAY("CLINIC")=CLINIC field (#5) (internal and external format)
        ARRAY("DISPENSE DRUG")=DRUG field (#6) (internal and external format)
        ARRAY("PHARMACIST")=PHARMACIST field (#23) (added external format)
        ARRAY("LAST DISPENSED DATE")=LAST DISPENSED DATE field (#101)
        ARRAY("QTY")=QTY field (#7)
       
      From the REFILL sub-file (#52.1):
        ARRAY("PHARMACIST")=PHARMACIST NAME field (#4) (added external format)
      functionality for a site to create order checks using Clinical Reminder
        ARRAY("QTY")=QTY field (#1)
       
      From the PARTIAL DATE sub-file (#52.2):
        ARRAY("PHARMACIST")=PHARMACIST NAME field (#.05) (added external format)
        ARRAY("QTY")=QTY field (#.04)
       
      From the DRUG file (#50):
        ARRAY("DEA SPECIAL HDLG")=DEA, SPECIAL HDLG field (#3)
      Terms and Definitions. Additional data elements to be used in conditional
      evaluation of those terms/definitions can only be provided by changes to
      the Outpatient Pharmacy Application Program Interface (API), PSOPXRM1.
      This patch will add the following data elements to the array returned
      by the API.
       
      From the PRESCRIPTION file (#52):
      
    • 348 SEQ #300
      DATE APPLIED:   2010-07-16 09:24:13
      APPLIED BY:   USER,SEVENTEEN
      DESCRIPTION:   
      The FY10 Q2 Enhancement Release includes the following two enhancements.
       
       
      VA Generic Name: PREDNISONE  
       
        Dispense Drugs
        ---------------
         1 - PREDNISONE 1MG TAB
         2 - PREDNISONE 5MG TAB
         3 - PREDNISONE 20MG S.T.
       
      Enter a list or range of numbers (1-3): 1-3
      This new option has been placed under the Output Reports [PSO OUTPUTS]
       
      VA Generic Name: 
       
      Exclude Deceased Patients? YES// NO
       
       
              **  To avoid undesired wrapping of the output data,    **
              **  please enter '0;256;999' at the 'DEVICE:' prompt.  **
       
       
      menu and uses a sort template PSO DRUG WARNINGS.
       
      DEVICE: HOME// ;0;256;999  GENERIC INCOMING TELNET
       
       
           Before continuing, please set up your terminal to capture the
           detailed report data. On some terminals, this can be done by
           clicking on the 'Tools' menu above, then click on 'Capture
           Incoming Data' to save to Desktop. This report may take a
           while to run.
       
       
       
      Press Return to Continue: 
       
      The output of this report is in a delimited output format suitable for 
      export to MS Excel and includes data from original prescription fills,
      refills and partial fills. The report output is sorted primarily by
      patient name and secondarily by prescription number.
       
      Each fill of the prescription is printed on a separate line. Each 
      prescription detail line starts with a double backslash followed by an
       
      identifier to denote the type of fill (ORIGINAL, REFILL, PARTIAL). 
      Each line contains 38 fields separated by up-arrow ("^") as described 
      below:
       
         1. FILL TYPE (e.g.,\\ORIGINAL\)    2. RX #
         3. DRUG NAME                       4. PATIENT NAME
         5. SSN                             6. ADDRESS 1
         7. ADDRESS 2                       8. ADDRESS 3
         9. CITY                           10. STATE
        11. ZIP                            12. PHONE (HOME)
      Example of Input Prompts:
        13. PHONE (WORK)                   14. PHONE (CELL)
        15. DECEASED?                      16. FILL #
        17. ISSUE DATE                     18. FILL DATE
        19. RELEASED DATE/TIME             20. EXPIRATION DATE
        21. LOT #                          22. NDC
        23. DIVISION                       24. PHARMACIST
        25. PROVIDER                       26. PATIENT STATUS
        27. QTY                            28. DAYS SUPPLY
        29. # OF REFILLS                   30. MAIL/WINDOW
        31. CMOP?                          32. PARTIAL REMARKS
       
        33. TRANSMISSION NUMBER            34. SEQUENCE #
        35. CMOP NDC                       36. DATE SHIPPED
        37. CARRIER                        38. PACKAGE ID
        
      Example of Output:
       
      \\FILL TYPE\^RX #^DRUG NAME^PATIENT NAME^SSN^ADDRESS 1^ADDRESS 2^
      ADDRESS 3^CITY^STATE^ZIP^PHONE (HOME)^PHONE (WORK)^PHONE (CELL)^
      DECEASED?^FILL #^ISSUE DATE^FILL DATE^RELEASED DATE/TIME^EXPIRATION
      DATE^LOT #^NDC^DIVISION^PHARMACIST^PROVIDER^PATIENT STATUS^QTY^DAYS
              **  To avoid undesired wrapping of the output data,   **
      SUPPLY^# OF REFILLS^MAIL/WINDOW^CMOP?^PARTIAL REMARKS^TRANSMISSION
      NUMBER^SEQUENCE #^CMOP NDC^DATE SHIPPED^CARRIER^PACKAGE ID
      \\ORIGINAL\^100002236A^AMPICILLIN 250MG^WHIPATNM,PATIENT^666-00-0248^
      164 FRIENDSHIP DRIVE^^^TROY^NEW YORK^12180^271-1112^^^Y^0^8/22/03^
      8/22/03^12/23/03 13:36:40^2/22/04^^839-5087-06^EXT (500)^RPH,NAME^
      DOCTOR,NAME^SC LESS THAN 50%^1^30^5^MAIL^N^^^^^^^
      \\REFILL\^100001423^IBUPROFEN 600MG^WILPATNM,TEST3^000-00-3333^HERE
      ^^^TROY^NEW YORK^10000^^^^N^1^4/1/96^2/5/97^2/5/97 14:40:41^4/2/97^
      123123123^00615-2526-05^EXT (500)^TEST,PHARM F^TEST,PROVIDER L^
      ^SC LESS THAN 50%^90^30^5^MAIL^N^^^^^^^
              **  please enter '0;256;999' at the 'DEVICE:' prompt. **
      \\PARTIAL\^100002236A^AMPICILLIN 250MG^TEST2,PATIENT^666-00-0248^
      164 FRIENDSHIP DRIVE^^^TROY^NEW YORK^12180^271-1112^^^Y^1^8/22/03^
      12/4/03^12/23/03 13:36:42^2/22/04^^00839-5087-06^TROY (514)^RPH,NAME^
      DOCTOR,NAME^SC LESS THAN 50%^1^1^5^WINDOW^N^PARTIAL REMARKS TEST^^^^^^
        
      MISCELLANEOUS FIX:
      ------------------
       
      The recently released patch PSO*7*326 provided the enhanced functionality
      to look up patient by prescription number in backdoor pharmacy. After
       
      installing this patch, four sites reported that they were unable to
      retrieve patient information by swiping the Veterans Identity Card (VIC),
      which had not been a problem before patch 326 installation. 
       
      The output of this particular card reader is in the format:
      "%99999999^XXXXXXXXXXXXXXXX^99999999^^^^N^9999999999?"
       
      The code change that was made to retrieve patient by prescription number 
      in patch 326 was not allowing the use of up-arrow ("^") characters as 
      part of the input data, hence the failure. This patch 348 addresses the 
       
       
      issue.
      EXCLUDE DECEASED PATIENTS (Y/N) Y// ES
      START WITH DIVISION: FIRST//
          START WITH DRUG: FIRST//
            * Previous selection: FINISH DATE/TIME from Oct 25,2009 to Oct 
            27,2009@24:00
            START WITH FINISH DATE/TIME: Oct 25,2009//   (OCT 25, 2009)
            GO TO FINISH DATE/TIME: Oct 27,2009//   (OCT 27, 2009)
      DEVICE:   GENERIC INCOMING TELNET
       
      1. Canned Report for Outpatient Prescription Activity (NSR #20081114)
       
           Before continuing, please set up your terminal to capture the
           detailed report data. On some terminals, this can be done by
           clicking on the 'Tools' menu above, then click on 'Capture
           Incoming Data' to save to Desktop. This report may take a
           while to run.
       
      Press Return to Continue:
       
      The report output will be generated by print templates PSO DRUG WARNINGS
       
      and PSO DRUG WARNINGS HEADER in a delimited output format suitable for
      export to Microsoft (MS) Excel. The report will contain patient
      demographic and prescription information.
       
      Output Example:
       
      \\^PATIENT^SSN^ADDRESS 1^ADDRESS 2^ADDRESS 3^CITY^STATE^ZIP^PHONE 
      (HOME)^PHONE (WORK)^PHONE (CELL)^DECEASED?^RX #^DRUG^FINISH D/T^QTY PER 
      DAY^STATUS^REF REM^PRO VIDER^LAST DISPENSED DATE^RETURNED TO STOCK?
      \\^OUTPATNM,BARRY^666000198^1 SPRING ST^BLDG 2^APT 3^SPRINGFIELD^MO^65801^
      A new option named Prescription List for Drug Warnings [PSO RX LIST]
      456-6789^^^^301129^DOXEPIN 25MG CAP^03/22/07^1^DISCONTINUED^10^PHARMA,
      OUTPT^04/12/07^
      \\^TESTPATNM,MICHELLE^666000770^MAIN ST^^^CLEARWATER^FLORIDA^33762^
      444-5532^345-1234^^^800024A^DOXEPIN 25MG CAP^02/14/07^2^DISCONTINUED^5^
      ^PHARMA,INPT^02/18/07^
       
       
      2. Reports to Identify Patients/Prescriptions for Recall Notices 
      (NSR #20081115)
       
      provides a report capable of identifying all patients that have 
      A new option called List of Patients/Prescriptions for Recall Notice [PSO
      RECALL LIST] has been provided to identify prescriptions containing
      medications associated with specific recall criteria, such as lot numbers
      and/or National Drug Code (NDC) numbers.
       
      This new option has been placed under the Output Reports [PSO OUTPUTS]
      menu and prompts the user for the following criteria: 
          Division  
          Prescription Release Date Range
          Medication Identifier 
      been dispensed a particular medication(s). This report was developed by
          Inclusion/Exclusion of Deceased Patients
       
      One of the following four medication identifiers may be selected:
        1-NDC code
        2-Dispense Drug and Lot #
        3-Dispense Drug only
        4-VA Generic Name
        5-Orderable Item
       
       
      converting Class III functionality to a standardized, nationally released
      Example of input prompts:
       
      You may select a single or multiple Divisions,
      or enter ^ALL to select all Divisions.
       
      Division: ^ALL
       
      From Release Date: T-90//  (JAN 20, 2010)
       
      To Release Date: T//  (APR 20, 2010)
      report.
       
           Select one of the following:
       
                1         NDC
                2         DISPENSE DRUG AND LOT NUMBER
                3         DISPENSE DRUG
                4         VA GENERIC NAME
                5         ORDERABLE ITEM
       
      Select 1-5 : 4  VA GENERIC NAME
      
    • 276 SEQ #301
      DATE APPLIED:   2010-07-16 09:24:21
      APPLIED BY:   USER,SEVENTEEN
      DESCRIPTION:   
      1. When a non-suspended refill is deleted there is no entry added into the
         Activity Log to reflect this.
      2. ePharmacy Medication Profile (View Only) shows a prescription as copay
         even after the copay has been removed.
      3. Undefined error when printing Medication Instructions.
      4. UNDEFINED error at h+7^IBCSCU
      
    • 340 SEQ #303
      DATE APPLIED:   2010-08-19 14:38:12
      APPLIED BY:   USER,SEVENTEEN
      DESCRIPTION:   
      This patch will correct the following issues.
       
      HD0000000344080   2 CMOP is getting wrong refill text (3 of 2) and the 
                        refill # is a negative
      
    • 290
      DATE APPLIED:   2010-09-15 09:21:44
      APPLIED BY:   USER,SEVENTEEN
      DESCRIPTION:   
      1. A modification was made to the Reject Information screen under the 
         INSURANCE Information
         Insurance      : OPP INSURANCE            Coord. Of Benefits: PRIMARY
         Contact        :
         Group Name     : D-GROUP1
         Group Number   : D00001
         Cardholder ID  :
       
      2. A COB field(#27) was added to the PRESCRIPTION file (#52),
      REJECT INFO sub-file (#52.25) to store the COB for the Third Party 
      Insurance Rejects for the fill. The Set of Codes will be stored as "1" for
      Third Party Payer Rejects - Worklist [PSO REJECTS WORKLIST] option and the
      Primary, "2" for Secondary, and "3" for Tertiary. Tertiary billing will 
      not be implemented with this patch group, but is included for future use.
       
      DATA          NAME                  GLOBAL        DATA
      ELEMENT       TITLE                 LOCATION      TYPE
      --------------------------------------------------------------------------
      52.25,27      COB                    2;7          SET
       
                                      '1' FOR PRIMARY; 
                                      '2' FOR SECONDARY; 
      Third Party Payer Rejects - View/Process [PSO REJECTS VIEW/PROCESS] option
                                      '3' FOR TERTIARY; 
                    LAST EDITED:      JAN 20, 2009 
                    DESCRIPTION:      This field contains the Coordination of 
                                      Benefits indicator for the third party 
                                      insurance rejection for the fill. This 
                                      field can contain 1 for Primary, 2 for
                                      Secondary, or 3 for Tertiary.
       
      3. A modification was made to the Patient Medication Profile screen 
      under the ePharmacy Medication Profile (View Only) [PSO PMP] option to
      to incorporate the Coordination of Benefits (COB) indicator to be 
      modify the ECME LOG section to change the "Comments:" preface from
      "Submitted to ECME:" to "ECME:" for non reversals. Second modification was
      made to add the COB indicator with insurance provider to the suffix of the
      "Comments:." The COB indicator will be denoted with a lower case "p" for
      Primary, "s" for Secondary and a "t" for Tertiary, which will be followed
      by the name of the insurance provider in capital letters.
       
      Example: 
         
         ECME Log:
      displayed in the insurance section. The indicator will be displayed as
       
         #   Date/Time           Rx Ref          Initiator Of Activity
      ==========================================================================
         1   1/28/09@11:37:56    ORIGINAL        OPUSER,ONE
         Comments:  ECME:WINDOW FILL(NDC:00046-1066-05)-E PAYABLE-pOPP INSURANCE
      "Coord. Of Benefits:" followed by either PRIMARY, SECONDARY, or TERTIARY.
       
      Example:
       
      
    • 330 SEQ #305
      DATE APPLIED:   2010-12-07 17:07:23
      APPLIED BY:   USER,SEVENTEEN
      DESCRIPTION:   
       1. The Drug Transaction History [PSA DRUG DISPLAY] menu option is not   
          showing the outpatient prescriptions that are dispensed for all
          pharmacy locations when the prescription is dispensed through
          the Outpatient Pharmacy Automation Interface (OPAI).
       
       2. The mailman message that gets generated when the release of a
          discontinued prescription is attempted does not make the distinction
          between a regular and a partial fill.                              
      
    • 358
      DATE APPLIED:   2010-12-16 16:42:31
      APPLIED BY:   USER,SEVENTEEN
    • 331 SEQ #307
      DATE APPLIED:   2011-01-11 10:57:54
      APPLIED BY:   USER,SEVENTEEN
      DESCRIPTION:   
      This patch will resolve the 3 issues.
      should always display.
      1. If a prescription has only a date, no time, for Released Date.Timeme
      it will not show up on the Hi Cost Report.
      2. When selecting the 'Sort by Drug (alphabetically), status active,
      status recent expired' view on the Meds Tab, prescriptions that have
      a status of Hold or Provider Hold are not displayed.
      3. Non-VA med orders, that have been Discontinued, are showing up in
      the Meds tab in CPRS.  Active Non-VA meds, if they have a start date
      older than the ORCH CONTEXT MEDS date are not displayed.  Active meds 
      
    • 352 SEQ #308
      DATE APPLIED:   2011-03-31 16:51:32
      APPLIED BY:   USER,SEVENTEEN
      DESCRIPTION:   
      This patch will resolve the issue where the Ignored Rejects Report [PSO 
      IGNORED REJECTS REPORT] abends when sorting on PATIENT and only one
      patient is selected.
      
    • 366 SEQ #309
      DATE APPLIED:   2011-04-28 15:56:18
      APPLIED BY:   USER,SEVENTEEN
      DESCRIPTION:   
      A VAMC has requested both a date and time stamp for prescription activity
      log entries displayed by FileMan.
      
    • 4
      DATE APPLIED:   1999-04-16 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      1. Fixed errors reported in Tuscaloosa, local NOIS PHA-0198-N0089 and
       
      3. Added a check to screen out pending refill order when doing order checks.
      Routine PSODRDU1
       
      4. Made Site parameters required in the Delete Rx option. NOIS: PUG-0198-52050
      Routine PSORXDL
       
      5. Fixed an error that occurred in Tuscaloosa on a Health Summary. It came upon
      a prescription with missing data, (No drug, provider, or patient pointer).
      A check was added to look for missing data. Routine PSOHCSUM
      PHA-0198-N0076. An undefined error occurred if the user selected to edit
       
      6. Fixed error that occurred in Tuscaloosa in PSOORRL routine, returning
      a Med profile to CPRS. The error occurred because of an invalid provider
      entry in a prescription. Modified code to check for invalid and
      missing data in the provider field and the drug field. Routine PSOORRL
      both the Pharmacy Orderable Item and the Dispense Drug, and entered a
      Duplicate Drug of another Rx for that patient, and did not Discontinue
      that duplicate Rx when prompted to Discontinue. Routine: PSOOREDT
       
      2. Corrected a problem where a possible invalid cross reference existed.  Which
      could cause an undefined error when cost data is being compiled.
      Routine: PSOCSTM, PSOCSTD
      
    • 29 SEQ #30
      DATE APPLIED:   2000-02-29 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      1. For a drug marked for lab monitor, if text is entered for the results
      3. Fixed a possible undefined variable error that may occur during the
      renewal of certain drugs in certain sites. (START+15^PSORENW1:2,
      %DSM-E-UNDEF, undefined variable PSODRUG("DEA"))
       
      4. For clinics that had inactive sites, one particular management report
      was giving empty pages even though there were other active sites with
      data. This patch fixes this problem.
       
      5. Made data dictionary changes to the following fields in PRESCRIPTION
      file (#52):
      instead of a numeric value, the Action Profile reports the result as zero
          a. UNIT PRICE OF DRUG field (#17)
          b. CURRENT UNIT PRICE OF DRUG field (#1.2) of REFILL sub-file (#52.1),
          c. CURRENT UNIT PRICE OF DRUG field (#.042) of PARTIAL DATE sub-file
             (#52.2).
       
      These fields currently set to the 99.999 format, need to be changed to the
      999.9999 format, in order to maintain the same format as that of PRICE PER
      DISPENSE UNIT field (#16) of the DRUG file (#50) which is of the format
      999.9999. During an original/refill/partial fill an exact unit cost will
      be maintained in the respective fields without getting truncated. This
      rather than displaying the text. This problem is fixed in this patch.
      change will also eliminate the possibility of reporting zero cost for
      certain low cost dispensed items as reported in numerous NOISs.
       
      This patch also makes a Data Dictionary change to the NDC field (#11), an 
      unused field by Outpatient Pharmacy V. 7.0 package in REFILL sub-file
      (#52.1) from piece 13 of node 0 to piece 3 of node 1. There is an optional
      background job that will move the data from its old location to its new
      location. The date/time is site selectable and can be queued to run during
      the installation of the patch or at another time by using the entry point
      NDCQ^PSOPOST1. 
       
       
      6. Fixed a possible undefined variable error (%DSM-I-ATLABEL,
      START+2^PSOCST5:7) that may arise while using the OPTION: Provider by Drug
      Costs [PSO COST PROVIDER BY DRUG] on exiting using "^" in response to the
      "(Enter ^ to Halt)" during viewing of the report on the screen.
       
      7. When a medication information sheet is printed using the Rx
      (Prescriptions) [PSO RX] option, under the Patient Prescription
      Processing [PSO LM BACKDOOR ORDERS] option, Medication Profile, the
      patient's name does not print on the medication sheet. (This fix is in
      2. When  UNITS field (#6) of SITE/SPECIMEN sub-file (#100) of
      reference to an E3R# 12659).
       
      8. A change has been made to the input transforms of the quantity fields
      of the PRESCRIPTION file (#52). The change will prevent alpha characters
      from being entered for quantity through the pharmacy options.
      LABORATORY TEST file (#60) is not defined, the Display Lab Tests and
      Results [PSOLAB LIST] option displays "Specimen data missing !!". This
      patch fixes the problem.
       
      
    • 251
      DATE APPLIED:   2011-04-28 16:06:59
      APPLIED BY:   USER,SEVENTEEN
      DESCRIPTION:   
      This patch is part of a combined build, made up of the following three 
      Drug Information Framework (DIF) interfaces and database. The VistA Drug 
      Interaction module will be replaced by the FDB Drug-Drug Interaction 
      Module (DDIM). The VistA Duplicate Class module will be replaced by the 
      FDB Enhanced Therapeutic Classification (ETC) System.
       
      In addition, the following three order checks that use VistA data have
      been added to Inpatient Medications and Outpatient Pharmacy. These checks
      currently occur in Computerized Patient Record System (CPRS), but will be
      new to Pharmacy with the installation of these patches:
           Aminoglycoside Ordered
      patches:
           Dangerous Meds for Patients > 64
           Glucophage - Lab Results
       
      A new Graphical User Interface (GUI) module is also being introduced 
      called Pharmacy Enterprise Customization System (PECS), to be used only 
      by members of Pharmacy Benefits Management (PBM). It will allow PBM to 
      customize the data provided by FDB for use in VistA.
       
      The following three patient safety issues have also been addressed in 
      these patches:
             OR*3.0*272           (Computerized Patient Record System)
             Order Checks on PreMix IV Solutions (PSI-06-012)
             Order Check display sequence changes (PSI-07-080)
             Eliminating confusion in Inpatient Medications Order Check display 
             and processing (PSI-07-080)
             PSJ*5.0*181           (Inpatient Medications)
             PSO*7.0*251          (Outpatient Pharmacy)
       
      These patches will replace most of current VistA medication order 
      checking system with version 1.0 of the new Medication Order Check 
      Healthcare Application (MOCHA) system that uses the First DataBank (FDB) 
      
    • 375 SEQ #311
      DATE APPLIED:   2011-04-28 16:07:12
      APPLIED BY:   USER,SEVENTEEN
      DESCRIPTION:   
      1. This patch corrects a problem when a tech/clerk reinstates a prescription
      discontinued did not display when it should have displayed.
       
      3. This patch corrects a problem where the SIG for med orders did not
      format and display correctly (ccr3803).
       
      4. Corrects a problem when Ctopying an Rx and the duplicate therapy Rx list
      selected for deletion does not re-displays the complete list of Rxs to be
      deleted as a duplicate therapy.
       
      5. OP Intervention Hidden Action When viewing interventions via the View
      from previously being discontinued.  The problem occurs when the site
      Intervention prompt data does not display correctly. Data is displayed until
      screen has filled and then overlaps on bottom few lines. The user cannot
      view the intervention due to scrolling issue. 
       
      6. Corrected order check sequence. (ccr 3832). 
       
      7. IP REQ 3.8.10.28 Failing - no TD messages for OP TD Discontinued Meds
      (ccr 3837).
       
      8. Hard error during clerk reinstate of an rx with a duplicate drug non-va
      parameter VERIFICATION (FILE #59; Field #.12) is set to 'No' and a user
      med (ccr 3851).
       
      9. IP Remote Rx display in Therapeutic Duplication warning does not match
      the SRS and FR 3.8.10.16 (ccr 3853).
       
      10. Hard error during clerk reinstate of an rx with a duplicate drug non-va
      med (ccr 3551).
      does not hold the PSORPH key and reinstates a prescription, the prescription
      gets put into a 'NON-VERIFIED' status.  In this situation the prescription
      should have a status of 'ACTIVE'.
       
      2. This patch corrects a problem when a tech/clerk enters a new duplicate
      drug and the confirmation message that the duplicate drug order was
      
    • 343 SEQ #312
      DATE APPLIED:   2011-04-28 16:14:44
      APPLIED BY:   USER,SEVENTEEN
      DESCRIPTION:   
      This patch contains software modifications to the Outpatient Pharmacy (OP)
       . Patient decision-making should be advised by information about a known
       
            Please wait... 
          
            The system is unable to display FDA Med Guide automatically.
        
            Please, contact your local technical support for assistance to
            resolve this problem. In the meantime, you can copy/paste the
            link above into your browser's address bar to retrieve the
            FDA Medication Guide.
       
         serious side effect with a product, or 
            Enter RETURN to continue, '?' for HELP, or '^' to exit:    
       
        
        If a user tries to use this option for a medication that does not have
        an FDA Medication Guide on file, the following message will display:
       
       
            Select Item(s): MG   Display FDA Medication Guide  
           
            There is no FDA Medication Guide associated with this medication.
       . Patient adherence to directions for the use of a product is essential
       
            Press RETURN to continue
        
        
        Note: This option requires a Java software component to be installed on
        ----  the user's computer. This software will be released as part of this
              project. Please, refer to the project Release Notes and Installation
              Guide documentation for further information.
         to its effectiveness. 
       
      The features in the FDA Medication Guides project are being delivered in
      incremental releases. This patch is part of the Increment 2 release. The 
      features included in this release are:
       
       . Establishment of a Server Repository for FDA Medication Guides within 
      V. 7.0 application to support the FDA Medication Guides project. The 
         the VA network.
       
       . Updates to 900+ entries in the VA PRODUCT file (#50.68) to store the 
         corresponding FDA Medication Guide document name will be provided via
         the NDF Monthly Data Update patches.
       
       . Introduction of a PC based Java software component to enable the
         automatic retrieval of an FDA Medication Guide from within VistA. The
         software does not require any direct user interaction. It works as a 
         bridge between VistA and the PC where it is installed. The software 
      project objective is to allow pharmacy staff to retrieve the FDA Medication 
         identifies a request from VistA for a specific FDA Medication Guide and
         automatically retrieves it from the Server Repository and displays to the
         user via the Internet Explorer browser. 
        
       . Introduction of a new option called Display FDA Medication Guide [PSN MED
         GUIDE] to the National Drug File V. 4.0 application for retrieving and 
         displaying the FDA Medication Guide for a specific VA Product.
       
       . Introduction of new functionality to the Patient Prescription Processing
         [PSO LM BACKDOOR] option in the Outpatient Pharmacy V. 7.0 application
      Guide for prescriptions that contain FDA approved information that can help
         for retrieving and displaying the FDA Medication Guide for a specific 
         prescription.
         
      Below is a list of all the applications involved in this release along
      with their patch number:
        
         APPLICATION/VERSION                                  PATCH
         -----------------------------------------------------------------
         OUTPATIENT PHARMACY (OP) V. 7.0                      PSO*7*343
         NATIONAL DRUG FILE (NDF) V. 4.0                      PSN*4*263
      patients avoid serious adverse events. The FDA requires that Medication
         PHARMACY DATA MANAGEMENT (PDM) V. 1.0                PSS*1*158
         
      The FDA Medication Guides project is expected to complete in three 
      increments. Among other features, the next Increment will automate the 
      printing of FDA Medication Guides for prescriptions dispensed by the VA
      via Outpatient Pharmacy application when the prescription label is printed.
         
      The following modification is inclued in this patch (PSO*7*343):
        
      Patient Prescription Processing [PSO LM BACKDOOR ORDERS] option
      Guides be included with certain prescribed drugs and biological products 
       
        Pharmacists will be able to retrieve an FDA Medication Guide for a 
        specific prescription by selecting the prescription and invoking the OTH
        (Other OP Actions) hidden action and choosing the new item MG Display FDA
        Medication Guide. A Java software component running at the user's PC will 
        then display the FDA Medication Guide Adobe Acrobat document (.pdf) by 
        automatically opening it via the user's default web browser, which will
        allow the users to print it to any printer available to them, as seen 
        below:
             
      when the Agency determines that: 
                             --- Other OP Actions ---
            PN   Progress Note (OP)
            AP   Action Profile (OP)
            MI   Print Medication Instructions
            DO   Display Orders' Statuses
            MG   Display FDA Medication Guide
       
            Select Item(s): MG   Display FDA Medication Guide  
        
            The following URL provides the link to the FDA Medication Guide 
       
            associated with this medication.
       
            vaww.national.cmop.domain.ext/FDAMedGuides/Lindane_(Generic)_(2008).pdf
       
            Please wait... 
       
              [FDA Medication Guide .pdf document opens on the web browser]
       
            Enter RETURN to continue, '?' for HELP, or '^' to exit:    
       
       . Certain information is necessary to prevent serious adverse effects 
       If a user tries to use this option from a computer which does not have the 
       required Java software component installed, the following message will 
       display:
       
            Select Item(s): MG   Display FDA Medication Guide  
       
            The following URL provides the link to the FDA Medication Guide 
            associated with this medication.
       
            vaww.national.cmop.domain.ext/FDAMedGuides/Lindane_(Generic)_(2008).pdf
      
    • 316 SEQ #313
      DATE APPLIED:   2011-04-28 16:15:19
      APPLIED BY:   USER,SEVENTEEN
      DESCRIPTION:   
      Patches PSO*7*316 and GMTS*2.7*92 correct issues reported with the 
      --------
      Routine PSS^PSO59 returns data about the demographics of outpatient 
      pharmacy divisions, such as site name and address.  The existing API did 
      not return the division's assigned area code and phone number, which are 
      present in the format of Tool #2: Medication Worksheet.
       
      Resolution:
      -----------
      This patch modifies routine PSO59 to return the AREA CODE field (#.03)
      and PHONE NUMBER field (#.04) as part of the target array.
      Tool #2: Medication Worksheet. The Health Summary patch GMTS*2.7*92
       
      2.  Routine PSOQUAP distributed with patch PSO*7*294 is not used.
       
      Problem:
      --------
      During testing of patch PSO*7*294, changes were made that resulted in 
      routine PSOQUAP being no longer required.  The routine was left in the 
      patch at the time in order to reduce the remaining testing time required.
       
      Resolution:
      will require patch PSO*7*316 and will create a national entry in the
      -----------
      This patch removes routine PSOQUAP.  There are no known programs that 
      call this routine.
       
      3.  PSO*7*294 was noncompliant with Programming Standards and 
          Conventions (SAC) for VistA applications.
       
      Problem:
      --------
      During the internal review of some of the routines distributed with 
      HEALTH SUMMARY COMPONENT file (#142.1) for Tool #2: Medication Worksheet.
      PSO*7*294 findings uncovered some SAC standard violations.
       
      Resolution:
      -----------
      Routines PSOQ0186 and PSOQMCAL are being replaced with GMTSPST2.  
      Corresponding Health Summary patch GMTS*2.7*92 creates a national Health
      Summary component for Tool #2: Medication Worksheet to utilize the
      replacement routines.
       
      1. The existing Application Program Interface (API) #4827 did not
         return fields required by Tool #2: Medication Worksheet.
       
      Problem:
      
    • 365 SEQ #314
      DATE APPLIED:   2011-05-18 14:56:24
      APPLIED BY:   USER,SEVENTEEN
      DESCRIPTION:   
      This patch will resolve the issue where the incorrect message is displayed
      to the user.  This is PSPO1744.
      
    • 355 SEQ #315
      DATE APPLIED:   2011-05-19 12:48:53
      APPLIED BY:   USER,SEVENTEEN
      DESCRIPTION:   
      User receives an undefined error when accessing the Non VA Meds Report.
      
    • 387 SEQ #316
      DATE APPLIED:   2011-08-12 13:59:41
      APPLIED BY:   USER,SEVENTEEN
      DESCRIPTION:   
      This patch is a follow-up to MEDICATION ORDER CHECK HEALTHCARE 
      Application Program Interface (API) that retrieves order check
      information.  This API returns a value of -1 for error of some type
      occurred, 0 (zero) for order checks complete with no issues found, or 1
      for interactions found.  Outpatient Pharmacy was not checking for -1.  
      This patch adds the check for -1, and displays a message when -1 is
      returned.
       
      2.  A misspelling of the word "Interoperability" was corrected in the 
      first line of routine PSOORRD2.
       
      APPLICATION (MOCHA) 1.0 group of patches.
      3.  An undefined error was corrected.  Using the Rx Verification by Clerk 
      option, a subscript error occurs after an unsuccessful request to First 
      Data Bank (FDB) is recieved.  The variable DFN is undefined and the error
      is displayed around the "Verify for" prompt.  The error can present itself
      in the following ways:
       
          a. When a page feed occurs just prior to the "Verify for" prompt: 
             <UNDEFINED> VERIFY+2^PSOVER1 *DFN. 
       
          b. During the order check process just before the PDM API is called: 
       
             <UNDEFINED> OBX+3^PSODDPRE ^TMP(547819387,"PSOPEPS","OUT",0). 
       
      4. For a technician entered order, the message "Remote data not available
      - Only local order checks processed" was rolling off the screen.  This 
      message is displayed in when remote data isn't available just before
      therapeutic duplications during the prescription order process.  This has 
      been corrected by adding an "Enter to continue" prompt after the message 
      is displayed when the user is a technician.
      1.  A correction was made to address an occurrence reported in a
      test account where Order Checks did not occur and no message was
      displayed to the user.  
       
      After the message "Now Processing Enhanced Order Checks!  Please wait..."
      is displayed, the system calls a Pharmacy Data Management (PDM) 
      
    • 371 SEQ #317
      DATE APPLIED:   2011-08-22 11:22:06
      APPLIED BY:   USER,SEVENTEEN
      DESCRIPTION:   
      This patch will resolve two issues with the List of Patients/Prescriptions
      for Recall Notices.
       
      1)  List of Patients/Prescriptions for Recall Notices is wrapping
          incorrectly.
       
      2)  PSO RECALL LIST Report needs End-of-Record Identifier.
      
    • 353 SEQ #318
      DATE APPLIED:   2011-08-22 11:22:15
      APPLIED BY:   USER,SEVENTEEN
      DESCRIPTION:   
       
       
      This patch will resolve the issue where the REFILL DATE shows a past date 
      when the Rx is taken off hold.
      
    • 382 SEQ #319
      DATE APPLIED:   2011-09-30 13:20:30
      APPLIED BY:   USER,SEVENTEEN
      DESCRIPTION:   
      This patch addresses a request made by the Health Resource Center (HRC) 
      1. The calculation of remaining refills on the medication profile screen. 
         Routine PSOPMP1 was modified to fix the issue.
       
      2. When selecting multiple items to be displayed from the medication 
         profile list, only the first selection is displayed. Routine PSOPMP0
         was modified so that all selected items are displayed.
       
      Integration Control Registration #4595 was modified to grant the CAPRI 
      package access to the Medication Profile and Refill [PSO HRC PROFILE/
      REFILL] option.
      to Outpatient Pharmacy V. 7.0 to provide a new standalone option similar
      to that of ePharmacy Medication Profile (View Only) [PSO PMP] option for
      the Compensation and Record Interchange (CAPRI) system. The Medication
      Profile and Refill [PSO HRC PROFILE/REFILL] option will allow users both
      to view a patient's medication profile and to refill prescriptions.
       
      The patch also corrects the following two issues found in ePharmacy 
      Medication Profile (View Only) [PSO PMP] option.
      
    • 34 SEQ #31
      DATE APPLIED:   2000-02-29 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      1) This patch fixes a problem that can occur when processing refills
      Listman action, a problem can occur with the METHOD OF PICK-UP field
      (#35). If the routing is WINDOW, and no METHOD OF PICK-UP is entered, and
      the prescription has a previous METHOD OF PICK-UP entered, the previous
      METHOD OF PICK-UP will print on the label, even though a METHOD OF PICK-UP
      was not entered when pulling from suspense. This patch makes the change to
      print whatever was entered when pulling from suspense, and if the prompt
      was bypassed, the METHOD OF PICK-UP will be deleted from the prescription,
      and will not appear on the label.
       
      3) When pulling a prescription from suspense, the fill date or refill
      in the Barcode Batch Prescription Entry [PSO BATCH BARCODE] option. The
      date field is updated with the date that the pull action occurs. Then
      when that prescription is refilled, the next possible fill date is
      calculated based on that last fill date. The problem occurs when the
      label that is pulled from suspense is a reprint label. This patch makes
      the change to only update the fill date or refill date if the label
      being pulled from suspense is not a reprint label.
       
      4) A problem can occur in the Patient Prescription Processing [PSO LM
      BACKDOOR ORDERS] option when a reprint request is made for a prescription
      that cannot be reprinted, such as an expired or discontinued prescription.
      patient record is sometimes getting locked during this process, and not
      If other valid labels are also requested for the patient, the valid
      labels will sometimes not print. This patch resolves the problem.
       
      5) This patch will modify the call that returns prescription information
      to Computerized Patient Record System (CPRS). The release date of the
      original fill is being added for display purposes in CPRS.
       
      6) When processing refills through the Barcode Batch Prescription
      Entry [PSO BATCH BARCODE] option, and when processing refills phoned
      in through the MUMPS AudioFax software, the patient name and last four
      always getting unlocked. This patch makes the change to only lock at the
      digits of the SSN will display if the refills can't be processed because
      "Yes" was the response for the "Allow fills for inpatient and CNH?"
      prompt, and the patient is an inpatient or is CNH Current.
      order level when processing refills in this option. When processing
      renewals through this option, the lock will remain for the patient record,
      and will also remain at the order level.
       
      2) When pulling a prescription from suspense using the Pull Rx (OP)
      
    • 357 SEQ #320
      DATE APPLIED:   2011-10-19 10:38:38
      APPLIED BY:   USER,SEVENTEEN
      DESCRIPTION:   
      User received an error while completing an order enterd via CPRS
      
    • 368 SEQ #321
      DATE APPLIED:   2011-10-26 16:45:02
      APPLIED BY:   USER,SEVENTEEN
      DESCRIPTION:   
      Pharmacy inventory not updated when medication is returned to stock.
      
    • 359
      DATE APPLIED:   2011-11-02 12:02:44
      APPLIED BY:   USER,SEVENTEEN
      DESCRIPTION:   
      ePharmacy Phase 5 - NCPDP D.0
      
    • 350 SEQ #323
      DATE APPLIED:   2011-11-08 13:58:43
      APPLIED BY:   USER,SEVENTEEN
      DESCRIPTION:   
      When running menu option Signature Log Reprint [PSO SIGLOG REPRINT] or 
      the Speed option RS Reprint Sig Log no output is printed.
      It will also resolve an issue where a label that should print does not 
      and a label that should not be printed does.
      
    • 381 SEQ #324
      DATE APPLIED:   2011-11-15 17:34:24
      APPLIED BY:   USER,SEVENTEEN
      DESCRIPTION:   
      This patch will resolve the issue where Active Non-VA meds with a 
      Start Date do no display on the Meds Tab when no Stop Date is defined in
      the ORCH CONTEXT MEDS parameter.
       
      parameter.
      
    • 373 SEQ #325
      DATE APPLIED:   2011-12-07 15:19:13
      APPLIED BY:   USER,SEVENTEEN
      DESCRIPTION:   
      This patch will resolve the issue where the incorrect Pharmacist is 
      appearing on prescription.
      
    • 384 SEQ #326
      DATE APPLIED:   2012-02-06 14:48:51
      APPLIED BY:   USER,SEVENTEEN
      DESCRIPTION:   
      This patch will resolve the issue where the ROUTE from the previous 
      prescription is displayed on the screen for the next prescription when 
      there is no ROUTE associated with it.
      
    • 379 SEQ #327
      DATE APPLIED:   2012-02-06 14:48:58
      APPLIED BY:   USER,SEVENTEEN
    • 385
      DATE APPLIED:   2012-02-16 14:00:23
      APPLIED BY:   USER,SEVENTEEN
      DESCRIPTION:   
      ePharmacy Phase 6
      
    • 354 SEQ #329
      DATE APPLIED:   2012-03-07 10:50:21
      APPLIED BY:   USER,SEVENTEEN
      DESCRIPTION:   
      This patch is being released as part of Pharmacy Legacy Enhancements 
      one division to have more than one Automated Dispensing Device (ADD)
      communicating with Veterans Health Information Systems and Technology
      Architecture (VistA) through the OPAI.
        
      1.  A new file named PHARMACY AUTOMATED DISPENSING DEVICES file (#52.53)
          was created. Entries in this file are required only if the site wants 
          to utilize the multiple dispensing functionality. The new file 
          contains the following fields:
         
          NAME - A free-text field that is between 3-30 characters in length. 
      Fiscal Year 2011 to address the Outpatient Pharmacy Automation Interface
                 It is the name given to the automated dispensing device.
          DNS  - A free-text field that is between 1-50 characters in length. It
                 stores the DNS name or IP address of the automated dispensing 
                 device.
          PORT - This field is a numeric between 1 and 65535 with no decimal 
                 places. It stores the port associated with the automated
                 dispensing device.
          INACTIVE 
          DATE - This is a date field, not required, but is used to inactivate 
                 the OPAI connection to an automated dispensing device.
      (OPAI) Enhancements. The Pharmacy Data Management patch PSS*1*156 is also
       
      2.  A new menu option named Enter/Edit Automated Dispensing Devices [PSO 
          AUTO DISPENSING DEVICE] was created to maintain the PHARMACY 
          AUTOMATED DISPENSING DEVICES file (#52.53). The option is located
          under the Maintenance (Outpatient Pharmacy) [PSO MAINTENANCE] menu.
          Only sites planning to use the multiple automated dispensing devices
          for an outpatient division should use this option.
       
      3.  A new sub-file (#59.20081) multiple named OPAI was added to the 
          DISPENSING SYSTEM PRINTER sub-file (#59.02008) in the OUTPATIENT SITE 
      being released as part of this enhancement.
          file (#59). The sub-file contains the following new fields:
        
          DNS NAME      - This field is a pointer to the PHARMACY AUTOMATED 
                          DISPENSING DEVICES file (#52.53).
          CATEGORY      - Categories provide the flexibility of routing RXs to
                          different ADDs. This field contains the following set
                          of codes:
                          MCS    MAIL - CS
                          MNCS   MAIL - NCS
                          MAIL   MAIL
        
                          WCS    WINDOW - CS
                          WNCS   WINDOW - NCS
                          WIND   WINDOW
                          CS     CONTROLLED SUBSTANCE
                          NCS    NONCONTROLLED SUBSTANCE
                          A      ANY
                          S      STORAGE
         
      4.  The Site Parameter Enter/Edit [PSO SITE PARAMETERS] option was   
          modified for addition of the new fields in the OPAI multiple
      Veterans Affairs Medical Center (VAMC) facilities have moved to using 
          (#59.20081) in the OUTPATIENT SITE file (#59).
        
      5.  During prescription processing, if the label printer selected has 
          ADDs defined then Rx will be routed to the appropriate ADDs. A message
          will be displayed indicating the ADDs where the Rx will be routed.
          Below is an example of the routing message.
       
            PRESCRIPTIONS SENT TO:
              OPTIFILL1
                100002815      ACETAMINOPHEN 325MG C.T.
      multiple vendors for automated medication dispensing systems to improve
                100002816      AMOXICILLIN 250MG CAP
                100002824      AMOXAPINE 50MG TAB
         
              SCRIPTPRO1
                100002844      CIMETIDINE 200MG TAB
         
      6.  During testing a problem was discovered in the Print from Suspense
          File [PSO PNDLBL] and Reprint Batches from Suspense [PSO PNDRPT] 
          options. The ZTIO variable, which stores the label printer, was being
          reset to null after processing each patient prescription. As a result 
      the efficiency of outpatient pharmacy operations. The following
          a printer defined with multiple ADDs was not routing prescriptions 
          properly. Routines PSOSULBL and PSOSUSRP were modified to address this
          problem.
       
      7.  A new Integration Control Registration (ICR) #5579 was created to 
          grant the Pharmacy Data Management package read access to the PHARMACY
          AUTOMATED DISPENSING DEVICES file (#52.53).
       
      8.  As per the User Group request, when a dispense complete message is 
          received by VistA from the external dispensing interface and if the 
      enhancements were made to the Outpatient Pharmacy software to allow any
          mail tracking information is included in the 13th piece of the RXD 
          segment, then the activity log will be updated with this information.
      
    • 35 SEQ #32
      DATE APPLIED:   2000-04-05 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      1. This patch corrects a problem when compiling the Health Summary component
      to be acted upon (renew, refill, etc.).  
        
      A new option, Backfill Prescriptions to CPRS [PSO BACKFILL PRESCRIPTIONS]
      will be distributed as a stand alone option and may be given to the user(s) 
      responsible for backfilling prescriptions to CPRS.  
       
      3. This patch updates the View Prescriptions [PSO VIEW] option to include
      the provider comments and instructions from CPRS entered orders.  
       
      for Outpatient Pharmacy data.  With the new prescription statuses added for 
      version 7 discontinued prescriptions were printing when they should not
      have.  
        
      2. The CPRS Workgroup members requested that the Outpatient Pharmacy package
      provide the capability to backfill prescriptions for a date range into CPRS 
      (only 18 months of prescriptions are backfilled upon installation of CPRS). 
      This will be an optional tool for sites and none of the orders will be able
      
    • 377 SEQ #330
      DATE APPLIED:   2012-03-19 11:07:51
      APPLIED BY:   USER,SEVENTEEN
      DESCRIPTION:   
      This patch will resolve the following issues:
      1) The message 'There is no refill data to be edited' incorrectly
         displays when editing a prescription that does have refills
       
      2) Due to a change in system printing a modification needs to be made to
         the device setup for the Daily Amis Report [PSO DAILY AMIS].
      
    • 351 SEQ #331
      DATE APPLIED:   2012-03-29 18:31:24
      APPLIED BY:   USER,SEVENTEEN
      DESCRIPTION:   
      The RXD-3 segment for a "partial" in Outpatient Pharmacy has a date missing.
      
    • 367 SEQ #332
      DATE APPLIED:   2012-03-29 18:35:53
      APPLIED BY:   USER,SEVENTEEN
      DESCRIPTION:   
      his patch contains software modifications to the Outpatient Pharmacy (OP)
       . Patient decision-making should be advised by information about a known
         however the user will be able to select other printers as well. The
         HOME and NULL DEVICE are selectable at this point.
       
         Select OPTION NAME: PSO MANAGER       Outpatient Pharmacy Manager
         Outpatient Pharmacy software - Version 
       
         Division:    DIVISION 999 
       
                You are logged on under the DIVISION division.
       
         serious side effect with a product, or 
         Select PROFILE PRINTER: HOME//   GENERIC INCOMING TELNET
       
         Select LABEL PRINTER: HOME//   GENERIC INCOMING TELNET
       
         OK to assume label alignment is correct? YES// 
       
         DIVISIONS's FDA Medication Guide Printer(s) on file:
       
           FDA MED GUIDE PRINTER (Default)
       
       . Patient adherence to directions for the use of a product is essential
         Select FDA MED GUIDE PRINTER: FDA MED GUIDE PRINTER//
        
      3. Complete Orders from [OERR PSO LMOE FINISH] option
         Patient Prescription Processing [PSO LM BACKDOOR ORDERS] option
         ---------------------------------------------------------------
         There are a few enhancements being added to the prescription processing
         options regarding the printing of FDA Medication Guides. Among them:
        
         a) The FDA Medication Guide document will print automatically for
            prescriptions, if there is one available.
         to its effectiveness. 
       
         b) Users will have the ability to change the FDA Medication Guide 
            printer in the same way they change the label and profile printers
            today.
       
         c) When queuing labels to print, if there is at least one prescription
            with an FDA Medication Guide associated, it will require a valid FDA
            Medication Guide printer to be entered. This is similar to requiring
            a valid printer for the label printer.
       
       
         d) The actual label document will contain a note under the barcode,
            before the PMI document, that says "Read FDA MED Guide". Such note
            should indicate to the pharmacist that an FDA Medication Guide
            document has been printed for the prescription and should be handed
            to the patient.
       
         e) The Label Log and CMOP Event Log will both list the FDA Medication
            Guide document name (.pdf) associated with each fill.
         
         f) Users will have the ability to reprint the FDA Medication Guide for
      The features in the FDA Medication Guides project are being delivered in
            past prescription fills or the latest FDA Medication Guide available
            for the prescription via a new action RM - Reprint FDA Medication
            Guide under the OTH - Other OP Actions menu.
             
      4. Print from Suspense File [PSO PNDLBL] option
         --------------------------------------------
         In order to run this option users will be required to enter a valid FDA
         Medication Guide printer. All prescriptions that prints a label via
         this option and that have an FDA Medication Guide associated will have
         the documente printed as well in the designated printer.
      incremental releases. This patch is part of the Increment 3 release, which
       
      5. Pull Early from Suspense [PSO PNDRX] option
         -------------------------------------------
         If the prescription being pulled from suspense has an FDA Medication
         Guide associated the user will be required to enter a valid FDA
         Medication Guide printer to where the document will be printed for
         the prescription.
       
      6. Change Label Printer [PSO CHANGE PRINTER] option
         ------------------------------------------------
      is the last planned release. The features included in this release are:
         This option is used by users to change the profile and label printers
         after having logged on to a pharmacy division. It is being modified to
         allow users to change the FDA Medication Guide printer as well.
         
      7. Reprint an Outpatient Rx Label [PSO RXRPT] option
         -------------------------------------------------
         If the prescription selected to reprinted the label has an FDA 
         Medication Guide associated, this option will ask whether the user also
         wants to reprint the FDA Medication Guide. If they answer YES, a valid
         FDA Medication Guide printer will be required for the user to proceed
       
         with the reprinting of the label and FDA Medication Guide.
       
      8. Label/Profile Monitor Reprint [PSO B] option
         Reprint External Batches [PSO INTERFACE REPRINT] option
         Reprint Batches from Suspense [PSO PNDRPT] option
         -------------------------------------------------------
         These options are used for reprinting batches of labels that may have 
         jammed on the printer. When reprinting labels via one of these options
         users will be prompted if they also want to reprint the FDA Medication
         Guide. If they answer YES, a valid FDA Medication Guide printer will be
       . Ability to create and maintain a list of FDA Medication Guide printers
         required for the user to proceed with the reprinting of the label and
         FDA Medication Guide, if one is available.
       
      9. The background process that calculates suspense days now rounds any
         partial day to the next full day. This modification was moved from 
         patch PSO*7*385 into this patch due to routine overlap and to avoid
         patch dependency.
      V. 7.0 application to support the Food and Drug Administration (FDA) 
         for a specific pharmacy division.
       
       . Automatic printing of FDA Medication Guide along with prescription 
         labels.
       
       . Ability to reprint the FDA Medication Guide when reprinting a 
         prescription label.
       
       . Ability to change the FDA Medication Guide printer at any point of the
         dispensing process, similar to changing the label printer.
      Medication Guides - Increment 3 project. The project objective is to allow
       
       . Ability to reprint the FDA Medication Guide for any given prescription
         fill or the latest FDA Mediation Guide available for the medication on
         the prescription.
        
       . Identification on the label document that an FDA Medication Guide was
         printed as well and needs to be collated to the documentation before
         being handed over to the patient.
       
       . Changes to the prescription label activity logs showing which specific
      pharmacy staff to retrieve the FDA Medication Guide for prescription items
         FDA Medication Guide document printed along with the label.
       
       . Changes to the Consolidated Mail Outpatient Pharmacy (CMOP) Event log
         showing which specific FDA Medication Guide document was available 
         for the medication when the prescription fill was transmitted to CMOP.
       
       . Introduction of a PC based Java software component to enable the
         automatic printing of an FDA Medication Guide from within VistA. The
         software does not require any direct user interaction. The software 
         identifies a request from VistA for a specific FDA Medication Guide
      that contain FDA approved information that can help patients avoid adverse
         and automatically sends it to the FDA Medication Guide printer
         selected by the user within VistA when dispensing the medication.
       
       . Ability to update the Windows network printer name for a specific
         device through the Kernel application. Once the pharmacist selects a
         printer to print the FDA Medication Guide Vista will retrieve the 
         Windows name for the printer and will pass it on to the Java
         application responsible for printing the document.
          
      Below is a list of all the applications involved in this release along
      events. The FDA requires that Medication Guides be included with certain
      with their patch number:
        
         APPLICATION/VERSION                                    PATCH
         -----------------------------------------------------------------
         CONSOLIDATED MAIL OUTPATIENT PHARMACY (CMOP) V. 2.0    PSX*2*70
         NATIONAL DRUG FILE (NDF) V. 4.0                        PSN*4*264
         OUTPATIENT PHARMACY (OP) V. 7.0                        PSO*7*367
         KERNEL V. 8.0                                          XU*8*566
         
      The following modifications are included in this patch (PSO*7*367):
      prescribed drugs and biological products when the Agency determines that:
       
      1. Site Parameter Enter/Edit [PSO SITE PARAMETERS] option
         ------------------------------------------------------
         Two new parameters are being introduced in this option: 
         a) FDA MED GUIDE PRINT SERVER URL: this field is used to store the
            Uniform Resource Locator (URL) for the Print Server where the Java
            application responsible for automatically printing of the FDA
            Medication Guides for the division was installed 
            (e.g.,'http://127.0.0.1/'). This field is required for the FDA
            Medication Guide functionality to work properly.
       
         b) FDA MED GUIDE PRINTER: This is a multiple field used to store a
            list of printers used for printing FDA Medication Guide document 
            for the division. There are two fields in the multiple: 1) FDA
            MED GUIDE PRINTER, which is a pointer to the DEVICE file (#3.5).
            Only devices with a content in the WINDOWS NETWORK PRINTER NAME
            field (#75) are selectable, and 2) DEFAULT PRINTER, which 
            indicates whether the printer selected is to be used as the 
            default printer for the division. Only one printer can be set as
            default printer for each division. This field is not required.
            The printers in this multiple will be displayed for selection
       . Certain information is necessary to prevent serious adverse effects 
            when the user logs into a division. If there is a printer set as
            the default printer, it will be set as the default printer.
         
        
      2. Outpatient Pharmacy Manager [PSO MANAGER] option
         ------------------------------------------------
         When logging into a division, after selecting the Profile and Label
         printers, the user will be prompt to select an FDA Medication Guide
         printer for the current session. If the division selected has a list
         of FDA Medication Guide printers they will be displayed (see below),
      
    • 360 SEQ #333
      DATE APPLIED:   2012-03-29 18:37:00
      APPLIED BY:   USER,SEVENTEEN
      DESCRIPTION:   
      This patch will fix an issue that was discovered in PSOSD1 
      where the variable LINE is not being renewed.
      
    • 403 SEQ #334
      DATE APPLIED:   2012-04-18 11:51:06
      APPLIED BY:   USER,SEVENTEEN
      DESCRIPTION:   
      HIPAA 5010 MAINTENANCE
      
    • 388 SEQ #335
      DATE APPLIED:   2012-08-29 10:38:53
      APPLIED BY:   USER,SEVENTEEN
      DESCRIPTION:   
      This patch resolves the following two issues:
       
      1) Provide users a more accurate description as to as to why a refill is 
      not allowed.
       
                                                                         
       
      2) Correct a misspelling of the word "prescription" in a CPRS pop-up 
      box.
      
    • 332 SEQ #336
      DATE APPLIED:   2012-08-29 10:59:47
      APPLIED BY:   USER,SEVENTEEN
      DESCRIPTION:   
      When the Date of Death is deleted from a patient, a mailman message is 
      generated that contains the patient's full name and last four digits of 
      their Social Security Number in the subject line.
      Return to Stock for the original fill and partials do not trigger a VDEF
      call to update the HDR.
      When a prescription is auto-DC'ed, if the pharmacist reinstates the 
      prescription, the Last Fill Date gets set to today's date rather than 
      reverting back to the actual Last Fill Date.
      
    • 398 SEQ #337
      DATE APPLIED:   2012-08-29 12:01:52
      APPLIED BY:   USER,SEVENTEEN
      DESCRIPTION:   
      This patch addresses the following two issues.
      1 - Presciptions re-instated in error.
      2 - The EXCLUSIONARY CHECKED BY field is not getting updated.
      3 - The PSO HI COST report is not exiting when the "^" is used.
      
    • 404 SEQ #338
      DATE APPLIED:   2012-08-29 12:32:38
      APPLIED BY:   USER,SEVENTEEN
      DESCRIPTION:   
      Need to replace the direct global read for the Major Diagnostic Category
      of the ICD Diagnosis file (#80) with the API $$ICDDX^ICDCODE and the 
      Description of the ICD Diagnosis file (#80) with the API $$ICDD^ICDCODE.
      
    • 361 SEQ #339
      DATE APPLIED:   2012-08-29 12:53:14
      APPLIED BY:   USER,SEVENTEEN
      DESCRIPTION:   
      CMOP MESSAGE IN ACTIVITY LOG IS CUT-OFF.
      VIEW PRESCRIPTIONS MENU OPTION DOES NOT SHOW CONJUNCTION OF EXCEPT FOR 
      COMPLEX ORDERS.
      
    • 31 SEQ #33
      DATE APPLIED:   2000-04-05 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
       1. When using the following cost related report options:
            Provider Costs [PSO COST PER PROVIDER]
       
       it was reported that when a period was specified in different date
       formats (i.e., MMYY or MMDDYY) of any past months then differing reports
       were being produced. This patch fixes this problem. This patch also
       enhances the routines to use common calls, improves the output formats,
       and enhances the user interactive help messages. A new routine named
       PSOCSTX contains all the common calls.
       
       2. This patch fixes the High Cost Rx Report [PSO HI COST] order sequence
            Clinic Costs [PSO CLINIC COSTS]
       so that it generates reports based on the release date order sequence.
            Division Costs by Drug [PSO DIV COSTS BY DRUG]
            Drug Costs [PSO DRUG COSTS]
            Drug Costs by Division [PSO COST BY DIVISION]
            Drug Costs by Division by Provider [PSO COST DIVISION BY PROVIDER]
            Drug Costs by Provider [PSO COST BY PROVIDER]
            Patient Status Costs [PSO COST BY PATIENT STATUS]
            Provider by Drug Costs [PSO COST PROVIDER BY DRUG]
      
    • 401 SEQ #340
      DATE APPLIED:   2012-08-30 16:29:13
      APPLIED BY:   USER,SEVENTEEN
      DESCRIPTION:   
      Error occurs when the Drug Class is not defined in the VA DRUG CLASS 
      file (#50.605).
      
    • 396 SEQ #341
      DATE APPLIED:   2012-09-13 15:35:27
      APPLIED BY:   USER,SEVENTEEN
      DESCRIPTION:   
      This patch will resolve the following 3 tickets:
      HD0000000498138 - Date of Death cancelled prescriptions reinstated does not
                        show correct Last Fill dates.
       
      HD0000000601013 - Print issues with TRICARE prescriptions
       
      HD0000000586028 - Refills are clogging CPRS
                        (CPRS refills were not processing automatically)
      
    • 386 SEQ #342
      DATE APPLIED:   2012-09-24 15:26:17
      APPLIED BY:   USER,SEVENTEEN
      DESCRIPTION:   
      The Pharmacy Legacy Enhancements (PLE) Increment 9 Release includes the 
             '1 INSUFFICIENT QTY IN STOCK'
      +---------------------------------------------------------------------+
       
       
      2. Flagging/Unflagging of a pending renewal order
         ----------------------------------------------
         The flagging/unflagging functionality was limited to new pending orders
         only from Computerized Patient Record System (CPRS) V. 3.0. Changes
         were made to extend this functionality to pending renewal orders from
         CPRS as well.
         Note: Flagging/Unflagging is a functionality for the pharmacist (PSORPH
             '2 DRUG-DRUG INTERACTION'
               key holders) only.
       
      3. Non-holders of PSORPH key were able to unflag pending orders
         ------------------------------------------------------------
         The action FL (Flag/Unflag) is blocked for users without the PSORPH
         key when finishing a new pending order. However, if the user selected 
         FN (Finish) to finish a new flagged pending order the software was
         allowing the user to unflag the pending order. This has been changed
         to no longer allow non-holders of the PSORPH key to unflag pending 
         orders.
             '3 PATIENT REACTION'
       
      4. Non PSORPH key holder access to Edit/DC actions
         -----------------------------------------------
         When processing pending new/renewal orders from CPRS, a non PSORPH key
         holder could use the actions 'Edit' or 'Discontinue' on the order, 
         which should not be allowed. This functionality has been disabled.
       
      5. COMMENT field (#.05) in the ACTIVITY LOG sub-file (#52.3) of the 
         PRESCRIPTION file (#52)
         ----------------------------------------------------------------
             '4 PHYSICIAN TO BE CONTACTED'
         The length of this field has been increased from 75 to 100 characters
         long to accommodate HOLD and UNHOLD comments.
        
      6. PSO52API API (Application Programming Interface)
         ------------------------------------------------
         This API was modified to check if the prescription's expiration date 
         is in the past. If it is and the current prescription status is not
         DISCONTINUED, DELETED, or EXPIRED, the API will update the prescription
         status to EXPIRED. The API will also send updates to CPRS and Health
         Data Repository (HDR) of the status change.
             '5 ALLERGY REACTIONS'
             '6 DRUG REACTION'
             '7 BAD ADDRESS'
             '8 PER PATIENT REQUEST'
             '99 OTHER--SEE COMMENTS'
        
      following modifications to the Outpatient Pharmacy V. 7.0 application:
              As per the recommendation of the Pharmacy User Group the 
              following changes were made to the set of codes:
       
              The following new codes were added:
              '9 CONSULT/PRIOR APPROVAL NEEDED'
              '98 OTHER/TECH (NON-CLINICAL)'
              
              The following code descriptions were modified:
              '4 PHYSICIAN TO BE CONTACTED' to '4 PROVIDER TO BE CONTACTED'
              '6 DRUG REACTION' to '6 ADVERSE DRUG REACTION'
       
              '99 OTHER--SEE COMMENTS' to 'OTHER/RPH (CLINICAL)'
       
              The following codes were removed as they were redundant and code
              '6 ADVERSE DRUG REACTION' to be used in its place:
              '3 PATIENT REACTION' 
              '5 ALLERGY REACTIONS' 
       
              Note:
              A post-install routine has been included in this patch that will
              convert the historical data of codes '3' and '5' to code '6'. 
      1. Prescription HOLD/UNHOLD Functionality
       
              On complete installation of this patch, the HOLD REASON field 
              (#99) of the PRESCRIPTION file (#52) will have the following set
              of codes:
              '1 INSUFFICIENT QTY IN STOCK'
              '2 DRUG-DRUG INTERACTION'
              '4 PROVIDER TO BE CONTACTED'
              '6 ADVERSE DRUG REACTION'
              '7 BAD ADDRESS'
              '8 PER PATIENT REQUEST'
         --------------------------------------
              '9 CONSULT/PRIOR APPROVAL NEEDED'
              '98 OTHER/TECH (NON-CLINICAL)'
              '99 OTHER/RPH (CLINICAL)'
       
         b. New Security Key PSO TECH ADV for pharmacy technicians
            A new security key called PSO TECH ADV has been created, which 
            will allow a user to HOLD a prescription using one of the following
            HOLD reasons, which are a subset of the hold reasons that are
            available to the PSORPH key holders in item (a) above:
       
         a.  The HOLD REASON field (#99) of the PRESCRIPTION file (#52) has the
            '1 INSUFFICIENT QTY IN STOCK'
            '7 BAD ADDRESS'
            '8 PER PATIENT REQUEST'
            '98 OTHER/TECH (NON-CLINICAL)'
       
            The PSO TECH ADV key holders will be able to remove a prescription
            from HOLD only for the above hold reasons whether they were put 
            on HOLD by the PSORPH key holder or by the PSO TECH ADV key holder.
       
         c. UNHOLD Comments
             following set of codes, which is presented to the PSORPH key holder
            The UNHOLD action has been modified to display the original hold 
            reason along with the hold comments (if any) as seen in the example
            below:
            
      +---------------------------------------------------------------------+
      | Select Action: Next Screen// UH   UH  UNHOLD                        |
      | Nature of Order: WRITTEN//        W                                 |
      |                                                                     |
      | HOLD COMMENTS: HOLD COMMENTS ENTERED BY THE USER MANUALLY. (REASON: |
      |                BAD ADDRESS) on MAY 10, 2012                         |
             during prescription 'HOLD' process:
      |                                                                     |
      | UNHOLD COMMENTS:                                                    |
      +---------------------------------------------------------------------+
       
         d. Rx Activity Log
            All activities related to HOLD/UNHOLD action on a prescription will
            be captured in the activity log as seen below:
       
           
      +---------------------------------------------------------------------+
       
      | Activity Log:                                                       |
      | #   Date        Reason         Rx Ref         Initiator Of Activity |
      | ...                                                                 |
      | 8   05/10/12    HOLD           REFILL 1       USER,PHARMACY         |
      | Comments: Rx placed on HOLD (Reason: BAD ADDRESS) and removed from  |
      |           SUSPENSE - HOLD COMMENTS ENTERED BY THE USER MANUALLY.    |
      | ...                                                                 |
      | 9   05/10/12    UNHOLD         REFILL 1       USER,PHARMACY         |
      | Comments: Rx Removed from HOLD - UNHOLD COMMENTS ENTERED BY THE USER|
      |           WHEN REMOVING THE RX FROM HOLD.                           |
      
    • 400 SEQ #343
      DATE APPLIED:   2012-10-24 10:03:25
      APPLIED BY:   USER,SEVENTEEN
      DESCRIPTION:   
      This patch resolves the following issue:
       
      Users receive a message in error while entering the dosage in Patient
      Prescription Processing.
      
    • 405 SEQ #344
      DATE APPLIED:   2013-01-31 15:06:27
      APPLIED BY:   USER,SEVENTEEN
      DESCRIPTION:   
      The same last 4 digits of the SSN prints for every patient with Non-VA 
      meds and no prescriptions when running the Poly Pharmacy Report for ALL 
      patients.
      An undefined error occurs when running the Poly Pharmacy Report for one 
      patient that has Non-VA Meds and no prescriptions.
      The display of the CMOP suspense date is truncated on a reinstate.
      
    • 390 SEQ #345
      DATE APPLIED:   2013-02-12 10:38:40
      APPLIED BY:   USER,SEVENTEEN
    • 417 SEQ #346
      DATE APPLIED:   2013-02-12 10:38:46
      APPLIED BY:   USER,SEVENTEEN
      DESCRIPTION:   
      This build is to be installed immediately after PSO*7.0*390 to
      3. Corrected a potential SUBSCRIPT error reported by test site (Boston) 
       (CCR6212).  
      correct a potential undefined error when renewing prescriptions
      without drug allergies.  CCR6153.
       
      2. Updated the second lines of the following routines: 
        a. Added patch number 388 to 2nd line of PSORENW and fixed typo. 
        b. Added patch number 387 to 2nd line PSORXI (no code changes needed).  
        (CCR6213).  
       
      
    • 409 SEQ #347
      DATE APPLIED:   2013-02-27 17:39:56
      APPLIED BY:   USER,SEVENTEEN
      DESCRIPTION:   
      An incorrect message diplays in the message box while viewing a prescription
      in the following option: PSO VIEW.
      
    • 364 SEQ #348
      DATE APPLIED:   2013-03-05 15:08:55
      APPLIED BY:   USER,SEVENTEEN
      DESCRIPTION:   
      This patch will resolve the issue where the LAST LOCAL NDC code is being 
      stored in the NDC BY OUTPATIENT SITE sub-file of the DRUG file for non
      E-PAYABLE drugs.
      
    • 333 SEQ #349
      DATE APPLIED:   2013-03-19 11:20:19
      APPLIED BY:   USER,SEVENTEEN
      DESCRIPTION:   
      This patch contains a fix for the issues summarized below:
       1. Undefined error during OPAI HL7 generation for Other Language Sig.
       2. Noun missing from sig on label when Print from Suspense
      
    • 36 SEQ #34
      DATE APPLIED:   2000-05-01 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
       
      ensures that in this case, the second user will get the duplicate drug
      check, and will only be allowed to continue if the first prescription
      is discontinued.
       
      2) This patch fixes a problem that can occur when using the Pull Early
      from Suspense [PSO PNDRX] option. If a specific prescription is pulled,
      and the prescription number entered is also the same internal entry
      number for another prescription that is also suspended, the entry
      that matched the internal number will be pulled from suspense, instead
      of the entry that matched the external number. This patch fixes the
       
      problem.
       
      3) A problem has been reported with the Queue Background Jobs [PSO
      AUTOQUEUE JOBS] option. There are times when some of the options that
      this option presents for scheduling or re-scheduling will not appear. This
      patch fixes the problem, so now all of the options will appear for
      scheduling or re-scheduling.
       
      4) This patch addresses some problems that can occur when processing
      two or more refills for the same prescription in the same ListMan
      1) This patch fixes a problem of a patient possibly having two active
      session while using the Patient Prescription Processing [PSO LM
      BACKDOOR ORDERS] option.
       
       a) If two or more refills are requested for the same prescription and
          none of the fills are auto-suspended, and the labels are queued to
          print, all of the labels will indicate that it is a label for the
          last fill, and that last fill information will print on the label.
          This patch will fix this problem by printing the appropriate fill
          information on the labels.
       
      prescriptions for the same drug. If two Outpatient Pharmacy users have
       b) If two or more refills are requested for the same prescription, and
          the last fill is auto-suspended prior to exiting the session, then
          "S" for Suspend is entered at the label prompt, the fill that is
          currently suspended will be overwritten in suspense, and only that
          last fill will print from Suspense. With this patch, a warning will
          be given after "S" is entered at the label prompt for each duplicate
          request, and the user will be given the opportunity to print each of
          those fills locally.
       
       c) If the first fill of a prescription is requested, and it does not
      the same patient profile on the screen in the Patient Prescription
          get auto-suspended at the time of the request, but eventually will
          be auto-suspended for Consolidated Mail Outpatient Pharmacy
          (CMOP) upon exiting the session for that patient,
          and then another fill is requested and it is auto-suspended for CMOP,
          then upon exiting the session, the first fill request will then be
          auto-suspended for CMOP, overwriting the second request, and a
          fill will be bypassed. With this patch, the second fill will
          not be allowed, since the first fill will be auto-suspended for
          CMOP upon exiting the session.
       
      Processing [PSO LM BACKDOOR ORDERS] option, the first user can enter a
      5) When a prescription is renewed through Pharmacy, if the prescription
      that is being renewed has a suspended refill that has not yet printed
      from suspense, in addition to that prescription being marked discontinued,
      that refill also gets deleted. If that same prescription would have been
      renewed through Computerized Patient Record System (CPRS), when that
      renewal is finished in Pharmacy, the renewed prescription would be
      marked discontinued, but the refill would not be deleted. This patch
      provides the functionality to delete the refill in this case, which
      makes it consistent with renewals initiated through Pharmacy.
       
      prescription then exit the option, then the second user can enter a
      6) When a prescription is discontinued, if that prescription was never
      filled locally, but filled only through CMOP, it's possible that when
      viewing that discontinued prescription, the Last Fill Date is incorrect.
      This patch resolves the problem.
      prescription for the same drug and not get the duplicate drug check,
      thereby creating two active prescriptions for the same drug. This patch
      
    • 374 SEQ #350
      DATE APPLIED:   2013-03-26 11:09:37
      APPLIED BY:   USER,SEVENTEEN
      DESCRIPTION:   
      This patch deals the following issue:
      CS vault updates more than once if the user fails to enter a
      reason for removing the Rx copay
      
    • 415 SEQ #351
      DATE APPLIED:   2013-04-16 10:25:58
      APPLIED BY:   USER,SEVENTEEN
      DESCRIPTION:   
      Users get an "end of file" error after running the TRICARE CHAMPVA
       Bypass/Override Report
      
    • 410 SEQ #352
      DATE APPLIED:   2013-04-29 14:15:35
      APPLIED BY:   USER,SEVENTEEN
      DESCRIPTION:   
      When processing Pending Orders in Outpatient Pharmacy, the system hangs
      if any word in the Provider Comments is longer than 60 characters and
      has a special delimiter (;,=:) after character position 57. If this 
      process continues to run, a <FILEFULL> error will occur.
      
    • 413 SEQ #353
      DATE APPLIED:   2013-05-07 15:29:09
      APPLIED BY:   USER,SEVENTEEN
      DESCRIPTION:   
      The DISCONTINUE PRESCRIPTION(S) option aborts when a prescription is   
      processed on a deceased patient.
                                                 
      User is able to discontinue a prescription that has been "marked for 
      deletion".  This should not be allowed.
      
    • 378 SEQ #354
      DATE APPLIED:   2013-05-16 17:44:25
      APPLIED BY:   USER,SEVENTEEN
      DESCRIPTION:   
      This patch will resolve the issue when a user edits the first ROUTE of a 
      complex prescription from ORAL to SUBLINGUAL, prior to accepting, the 
      UNDER THE TOUGUE will echo to the second occurrence.
      
    • 391
      DATE APPLIED:   2013-06-14 09:02:25
      APPLIED BY:   USER,SEVENTEEN
      DESCRIPTION:   
      This patch is being released as part of the DEA e-Prescribing of
         -----------------------------------------------------------------
       
        Data Name           CPRS File         Pharmacy Pending File
        ---------           ---------         ---------------------
        QTY PRESCRIBED      15                30
       
               
        If the error code is related to 'certificate expired', the pending 
        order will be processed (will not be auto discontinued) and a 
        notification will be sent to the provider with the message, "DEA
        certificate expired. Renew your certificate."
         KERNEL V. 8.0                                          XU*8*580
       
      2. When finishing a pending CS order, if the user does not hold the new 
         PSDRPH security key, the order will be marked as 'Non-Verified'.
       
      3. To verify a 'Non-Verified' CS order, PSDRPH security key is now
         required.
       
      4. To discontinue a pending CS order, PSDRPH security key is now required.
       
      5. The pending order screen will now display the provider's DEA/VA #, the 
         PHARMACY DATA MANAGEMENT (PDM) V. 1.0                  PSS*1*166
         DETOX# (if available) and the site address.
       
      6. When finishing a new pending CS order, the orderable item, dosage, 
         provider name, or the number of refills will not be allowed to be 
         edited. Also, if the changes to the dispense drug would result in
         a new order being created, this will not be allowed for digitally 
         signed orders. The user WILL be allowed to select other dispense drugs 
         for the same Orderable Item as long as it does not change the 
         prescribed dosage.
       
         COMPUTERIZED PATIENT RECORD SYSTEM (CPRS) V. 3.0       OR*3*306
      7. When finishing a new pending CS order, the days supply or the quantity
         will not be allowed to increase, but can be decreased. If the days
         supply is decreased, the number of refills will also be adjusted 
         accordingly depending on the drug setup (maximum refills, not 
         refillable etc).
       
      8. In patch PSO*7*99, a change was made for pending orders not to 
         recalculate the quantity for CS drugs on selecting a different strength
         of the same drug and resulting in the same prescribed dosage. This
         change is removed in this patch.
         CONTROLLED SUBSTANCES (CS) V. 3.0                      PSD*3*73
       
      9. When finishing a pending CS order or verifying a CS order by the PSDRPH
         key holder, any edit to some of the key fields like dispense drug,
         dosage, dispense units, issue date, day's supply, quantity or number of
         refills, will now be captured and stored in the activity log.
       
      10. In the Complete Orders From OERR [PSO LMOE FINISH] option, a new sort 
          selection, 'CS' is included to select digitally signed CS orders 
          separately.
       
         OUTPATIENT PHARMACY (OP) V. 7.0                        PSO*7*391
      11. A new field BACKDOOR SIGNATURE STATUS (#311) is being added to the 
          PRESCRIPTION file (#52) and will be set to '1' to indicate that the CS
          order was entered via pharmacy backdoor and was not digitally signed.
       
      12. A new field, DIRECTIONS FOR USE (#120) is being added to the PENDING
          OUTPATIENT ORDERS file (#52.41) to store the raw HEALTH LEVEL SEVEN
          (HL7) dosage data as sent from CPRS. This will be used to validate the
          integrity (hash count) against the CPRS digitally signed orders.
       
      13. Currently, the pending order screen displays only the number of 
       
          refills ordered by the provider. For digitally signed orders, this
          is modified to include the days supply and the quantity. Here is a
          screen capture:
          (6)    Issue Date: SEP 17,2012        (7) Fill Date: SEP 17,2012
          (8)    Days Supply: 45                (9)   QTY (  ): 45
         Provider ordered: days supply 45, quantity 45 & refills 1    
         (10)   # of Refills: 1                (11)  Routing: WINDOW
       
      14. The protocols PSO LM ACCEPT and PSO LM RENEW MENU are being modified
          to add code to the SCREEN field (#24) and the HEADER field (#26) of
      Note:
          the PROTOCOL file (#101) to ensure users are limited to ListMan
          actions based on their security key.
       
      15. As part of this project, Kernel patch XU*8*580 introduced the 
          following new fields to the NEW PERSON file (#200). Apart from the 
          DEA#/VA# requirement, DEA further classifies what CS schedule a
          provider is authorized to write. 
       
          55.1      SCHEDULE II NARCOTIC (S), [PS3;1]
          55.2      SCHEDULE II NON-NARCOTIC (S), [PS3;2]
      1. A new security key named "PSDRPH", has been sent out in the Controlled
          55.3      SCHEDULE III NARCOTIC (S), [PS3;3]
          55.4      SCHEDULE III NON-NARCOTIC (S), [PS3;4]
          55.5      SCHEDULE IV (S), [PS3;5]
          55.6      SCHEDULE V (S), [PS3;6]
       
          If any one of the above fields are populated for a provider then when
          placing a new order in backdoor pharmacy, the software will now check
          for the drug schedule with the provider privileges. If the provider
          does not have the credentials to write such orders then the software
          will display a message (as shown below) and will not allow the 
         Substances patch PSD*3*76, which is a required patch for this patch.
          selection that provider.
          Example: When the provider does not have schedule 2 privileges, this
          message is displayed: 
          "Provider not authorized to write Federal Schedule 2 prescriptions."
       
      16. When placing an order for a CS Detoxification drug, the software will 
          now check for a valid Detoxification number for the provider. If the 
          provider does not have a Detoxification number then the software will 
          display a message "Provider must have a DETOX# to order this drug."
       
      Controlled Substances (CS) project using Public Key Infrastructure (PKI)
         This key authorizes pharmacists to finish/verify a digitally signed
      17. The Released and Unreleased Prescription Report [PSO RELEASE REPORT] 
          is being modified to include CS as a selection to the input. The drug
          name and CS schedule is being added to the output. Here are the
          changes:                         
       
      You are currently logged in under the CHEYENNE VAM&ROC division.
      Do you want to select a different division? NO// 
       
      Do you want ONLY Unreleased Prescriptions? NO// 
      Include (C)S Rx only, (N)on CS Rx only, or (B)oth (C/N/B): B// Controlled 
         Schedule II-V CS orders placed via CPRS and should be assigned to
      Substances Rxs Only
       
      Select controlled substance schedules
       
           Select one of the following:
       
                1         SCHEDULES I - II
                2         SCHEDULES III - V
                3         SCHEDULES I - V
       
         registered pharmacists working with Schedule II-V drugs.
      Select Schedule(s): 3// 
       
      The report currently shows the count of unreleased and copay
      prescriptions, but not the count of released prescriptions. The report is
      modified with this patch to include the count of released prescriptions.
       
      18. The following options are being modified to include the
          DETOX/MAINTENANCE ID NUMBER field (#53.11) and the DEA EXPIRATION DATE
          field (#747.44) of the NEW PERSON file (#200) as part of the screen. 
          The DEA EXPIRATION DATE field will be prompted only if the PROVIDER
       
          TYPE field (#53.6) of the NEW PERSON file (#200) is marked as "FEE 
          BASIS".
       
          Add New Providers [PSO PROVIDER ADD]
          Edit Provider [PSO PROVIDER EDIT]
          View Provider [PSO PROVIDER INQUIRE]
       
      19. Currently, the default days supply for all drugs is set from the DAYS 
          SUPPLY field (#3) of the RX PATIENT STATUS file (#53) up to a maximum
          of 90. With this project, the default for CS schedule II-V drugs will
      2. Patches PSO*7*391 and PSD*3*73 are being released in the Kernel 
          be set to 30 or from the DAYS SUPPLY field (#3) of the RX PATIENT
          STATUS file (#53) if it is less than 30. Also, the Integration Control
          Registration #3278 that returns days supply (DSUP^PSOSIGDS) to CPRS is
          modified to return 30 or from the DAYS SUPPLY field (#3) of the RX
          PATIENT STATUS file (#53) if it is less than 30 for CS schedule II-V
          drugs.
       
      20. The pharmacy release slip portion of the Laser Label is being 
          modified to include the text "(DSIG)" or "(NOT DSIG)" after the
          patient's name to indicate that the prescription is digitally signed
         Installation and Distribution System (KIDS) multi-build distribution
          or not digitally signed.
       
      21. This patch addresses the issue reported in REMEDY ticket #595795, to
          ensure that when editing an orderable item/dispensed drug, the 
          instruction field is displayed only when editing the pending order 
          and not when editing an active or non-verified order.
       
      22. The Expire Prescriptions [PSO EXPIRE PRESCRIPTIONS] option that 
          currently runs as a nightly job is being modified to check for the
          Institutional DEA 'expiration date'. If the expiration date is within
         CPRSV29_PSO_PSD. 
          30 calendar days or past expiration then a mail message will be
          generated and sent to PSDMGR key holders. Here is an example when the
          expiration date is within 30 days:
       
      Subj: 500:Institutional DEA Expiration Date is about to expire  [#140331]
      03/20/12@11:57  3 lines
      From: POSTMASTER  In 'IN' basket.   Page 1  *New*
      -----------------------------------------------------------------------
       
      Please update Institutional DEA Certification Date. Will expire on 
       
      3/24/12.
       
      ******************************
       
      Here is an example when the DEA Expiration Date is past expiration date:
       
       
      Subj: 500:Institutional DEA Expiration Date has expired  [#140333]
      03/20/12@12:08  3 lines
      From: POSTMASTER  In 'IN' basket.   Page 1  *New*
      The following modifications and enhancements are included in this patch 
      ----------------------------------------------------------------------
       
      Please update Institutional DEA Certification Date. Expired on 2/19/12.
       
      **********************************
      (PSO*7*391):
      to satisfy requirements requested by the Drug Enforcement Administration
       
      1. When processing a digitally signed pending order, the integrity of the 
      original order placed in CPRS is now being checked to ensure that the data
      fields listed below are not altered from the time the order is signed in
      CPRS and later selected for processing in backdoor pharmacy. This is done
      by passing the data elements listed below to a Kernel Application
      Programming Interface (API), Integration Control Registration (ICR) #3539,
      along with the CPRS hash count, provided by ICR #5709. The Kernel API
      compares these two hash values and returns an "OK" if the pending order is
      unaltered or otherwise, returns a "-1^error code^error message."
      (DEA).
       
      Example: "-1^89802016^Mismatched digital signature hash values."
       
      These are the fields used in the hash check:
              Date of Issuance
              Full Name and Address of the Patient
              Drug Name
              Quantity Prescribed  
              Directions for Use
              Prescriber Name   
      The applications involved in this project along with their patch numbers 
              Prescriber Address (site address) 
              Prescriber DEA / VA Registration Number
              Order Number (CPRS)
       
      The Kernel API will also check for the validity of the DEA certificate. If
      the certificate is revoked or expired then the API will return the
      appropriate error code.
      If the error code is related to hash mismatch or the DEA certificate is
      revoked then the following events will be triggered during pending order
      processing:
      are listed below and the same order should be followed when installing 
        The order will be auto discontinued.
        First line of the pending order screen will have the message "Digital
        Signature Failed: Corrupted (Hash mismatch)" or "Certificate revoked"
        concatenated with "Order Auto Discontinued", and the message will be
        highlighted in reverse video.
        The status bar of the screen will have the message "Signature Failed: 
        Corrupted (Hash mismatch)" or Certificate revoked."
        A mail message will be generated to the holders of the PSDMGR key 
        notifying that the order has been auto discontinued (similar to the 
        example listed below).
      the patches.
        If the discontinuation is due to a hash mismatch as a result of altering
        one of the fields listed above then the mail message will show the
        altered fields with the discrepancies. Here is an example:
       
        Subj: DIGITALLY SIGNED NEW ORDER AUTO DISCONTINUED  [#196353] 
              03/20/12@17:1024 lines
        From: POSTMASTER  In 'IN' basket.   Page 1  *New*
               
        -----------------------------------------------------------------------
       
       
        Following order was auto discontinued when finishing a pending order   
        due to Corrupted (Hash mismatch) - 89802016
       
        Division      : GREELEY CLINIC
        CPRS Order #  : 5587651
        Issue Date    : MAR 7,2012
        Patient       : TEST,PATIENT (0908)
        Address       : P.O. BOX 31
                        LAPORTE, CA  95981
        Drug          : CODEINE SULFATE 60MG TAB
         APPLICATION                                            PATCH
        Dosage Ordered: 120(MG)
        Dosage Form   : TABLETS
        Quantity      : 54
        Provider      : TEST,PROVIDER
        DEA#          : TA1234563
        Site Address  : 2360 E PERSHING BLVD
                        2360 East Pershing Boulevard
                        CHEYENNE
       
        Differences in CPRS and Pharmacy Pending File
      
    • 426
      DATE APPLIED:   2013-06-14 09:04:25
      APPLIED BY:   USER,SEVENTEEN
      DESCRIPTION:   
      This is a follow-up patch for PSO*7*391 that was part of Computerized 
      "L" as "M" when "L" is found in the duration field.
      Patient Record System (CPRS) Graphic User Interface (GUI) v29. CPRS GUI 
      v29 will be a phased implementation and therefore, this patch, PSO*7*426,
      should be installed after CPRS GUI v29 bundle is installed.
       
      Hines reported that when finishing a complex pending order if 'month' is
      part of duration then the order is discontinued due to hash mismatch. This
      is due to pharmacy storing 'month' as "L" and CPRS storing as "M". This
      patch resolves this problem by tweaking the hash check code to represent
      
    • 424 SEQ #357
      DATE APPLIED:   2013-06-18 11:30:07
      APPLIED BY:   USER,SEVENTEEN
      DESCRIPTION:   
      1. This build is to be installed immediately after PSO*7.0*390 to 
         correct an issue where allergy labels are printing each time an allergy
         order check occurs.  The allergy label should only print when a user
         has not been assigned the PSORPH key. (CCR6452). 
      
    • 383 SEQ #358
      DATE APPLIED:   2013-07-10 16:15:36
      APPLIED BY:   USER,SEVENTEEN
      DESCRIPTION:   
      This patch will resolve the following issues: 
      1)  DUZ is printing on the label instead of co-signer.
      2)  To change the USPS forwarding terminology on labels in Vista.
      3)  Remove "REGULAR MAIL" from the shipping portion of laser labels in
          VistA.
      
    • 421
      DATE APPLIED:   2014-01-06 16:16:56
      APPLIED BY:   USER,SEVENTEEN
      DESCRIPTION:   
      EPHARMACY OPERATING RULES
      
    • 33 SEQ #35
      DATE APPLIED:   2000-05-16 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      This patch is part of the CMOP - Controlled Substance Rxs enhancements.
      The Installation Guide for the CMOP - Controlled Substance Rxs project can
      be obtained on the VISTA Consolidated Mail Outpatient   
      Pharmacy web page.  The address is http://vista2.domain.ext/cmop/.
       
      The Installation Guide is also available on the ANONYMOUS.SOFTWARE
      directory at one of the following Office ofInformation (OI) Field Offices.
      The file name is CMOPCS_IG.PDF.
        
       OI FIELD OFFICE                FTP ADDRESS             DIRECTORY
       ===============                ===========             =========
      It modifies functions within the Outpatient Pharmacy application to
       Albany                         152.127.1.5             anonymous.software
       Hines                          152.129.1.110           anonymous.software
       Salt Lake City                 152.131.2.1             anonymous.software
       
      NOTE: Since future patches may be dependent on this patch, it should be
      installed even if you are not using the CMOP software or planning to
      transmit controlled substances to the CMOP facilities.  The installation
      instructions will provide further guidance for this situation.
       
       
      support the transmission of controlled substance prescriptions to the
      1. This patch adds Controlled Substance functionality to the Released and
      Unreleased Prescription Report[PSO RELEASE REPORT]. The user is now also
      presented with sorting criteria to sort by:
       
      'C'     'Controlled Substance Rxs Only'
      'N'     'Non Controlled Substance Rxs only'
      'B'     'Both Controlled Substance and Non Controlled Substance Rxs'
       
      2. This patch adds a new menu option  CMOP Controlled Substance Rx
      Dispense Report[PSO CMOP CS RX DISPENSE REPORT] as a part of the Output
      Consolidated Mail Outpatient Pharmacy facilities.
      Reports [PSO OUTPUTS] menu of Outpatient Pharmacy. The user is prompted
      for criteria concerning:
       
       
      [Single division sites will not see the following question.]
      Print for (A)ll or a (S)ingle division? (A/S) S//
       
      Select one of the following: 1//
      1. Sort by Release Date
      2. Sort by Drug
        
      Start Date:
      End Date:
       
      The new report sorts by division and prints out the following fields:
      Release date, RX #, Fill #, Drug, Patient with SSN(last four), CMOP
      Status, and CMOP Facility.
       
      PRESCRIPTION File (#52)
       
      Release Date            RELEASED DATE/TIME (#31)        for Original RX
      This patch will be installed in conjunction with three other patches
                              or
                              REFILL multiple (#52)           for Refills
                              RELEASED DATE/TIME (#17)
       
      RX #                    RX # (.01)
       
      FILL #                  0                               for Original RX
                              IEN                             of refill for
      Refills
       
      (PSX*2*23, PSD*3*21, and PSS*1*28). Refer to the CMOP - Controlled
      DRUG                    DRUG (#6)
       
      Patient with SSN        PATIENT (#2)
       
      CMOP Status             CMOP EVENT multiple (#400)
                              STATUS (#3)
       
      CMOP Facility           CMOP EVENT multiple (#400)
                              TRANSMISSION NUMBER (#01) :
                              CMOP TRANSMISSION FILE #550.2
      Substance Rxs Installation Guide for installation instructions. 
                              CMOP SYSTEM (#3)
       
       
      3. This patch adds the display of the PRESCRIPTION file (#52) CMOP EVENT
      multiple (#400) fields CARRIER (#10) and PACKAGE ID (#11) to the View
      Prescriptions [PSO VIEW] option of Outpatient Pharmacy.
       
      4. This patch also corrects the following problem reported.
       
      Problem:        The CMOP Event Log in the View Prescriptions [PSO VIEW]
       
      option displays the release of a previous event when the current even has
      no release date.
       
      Resolution:     The code has been changed to clear the previous value and
      display "Not Released"  when the prescription is yet to be released.
      
    • 429 SEQ #360
      DATE APPLIED:   2014-02-26 10:08:32
      APPLIED BY:   USER,SEVENTEEN
      DESCRIPTION:   
      The Causative Agent showing in the Allergy Order check in Outpatient
      Pharmacy is not correct.
      
    • 434 SEQ #361
      DATE APPLIED:   2014-02-27 15:04:24
      APPLIED BY:   USER,SEVENTEEN
      DESCRIPTION:   
      VIC CARD ENHANCEMENT
      Refer to patch PSO*7*434 in the FORUM Patch Module for a complete
      description.
      
    • 372
      DATE APPLIED:   2014-04-07 17:23:32
      APPLIED BY:   USER,SEVENTEEN
      DESCRIPTION:   
      This patch is part of a combined build that makes up the release of 
      functionality, the Single Dose information will be displayed to
      the user.  The following scenarios describe the types of messaging added: 
       
        1. If the dosage entered passes the dosing checks, no message will be
           displayed.
        2. If the dosage entered is too high or too low, the Single Dose warning
           message will be displayed.
        3. If the dose checks were not able to be performed, a generic message
           will be displayed notifying the user that a manual check needs to be
           completed to verify appropriate dosing.
      MEDICATION ORDER CHECK HEALTHCARE APPLICATION (MOCHA) 2.0.
       
      MOCHA 2.0 encompasses Pharmacy Data Management (PDM) patch PSS*1*160
      and a combined build for Outpatient Pharmacy patch PSO*7*372 and 
      Inpatient Medications patch PSJ*5*252.
       
      This patch group adds dosing checks that implements a new system that uses
      data from First DataBank (FDB).  In this initial phase of dosing
      
    • 416
      DATE APPLIED:   2014-04-07 17:24:03
      APPLIED BY:   USER,SEVENTEEN
    • 431
      DATE APPLIED:   2014-04-07 17:24:41
      APPLIED BY:   USER,SEVENTEEN
      DESCRIPTION:   
       
      Outpatient Pharmacy for a pending order scrolls off the screen.  Examples
      of the message would be "FDB dosing information is not available for this
      drug" or "Drug not matched to NDF".
       
      For Max Single Dose messages, the pharmacist is correctly required to sign
      the order and enter an intervention.  Pharmacists do have the opportunity
      to see the CPRS dosing message when the pending order is first opened in
      Outpatient Pharmacy.  The CPRS message is the same message the scrolls off
      the screen.
       
      This patch is a MOCHA 2.0 fast track release patch to correct an issue 
      To correct this, an "Enter to continue" will be displayed to keep the 
      dose message from scrolling off the screen when the number of 
      disabilities to be displayed exceeds the screen length.
      found late in IOC testing process for MOCHA 2.0.  The following is the 
      needed modification:
       
       
      1. For order level dosing order check messages that do not require the
      pharmacist to enter a signature code on the order and where there are more
      than three disabilities defined for the patient, the dose message in
      
    • 362 SEQ #365
      DATE APPLIED:   2014-04-24 10:30:05
      APPLIED BY:   USER,SEVENTEEN
      DESCRIPTION:   
      This patch resolves the following issues:
      Prevent labels for patients whose mail is routed from being marked as a
      foreign address.
       
      A patient's prescription is changing from Co-pay to No Co-pay when
      it is released.
       
      The Sig does not match between the prescription and the order.
      
    • 318 SEQ #367
      DATE APPLIED:   2014-07-30 17:10:53
      APPLIED BY:   USER,SEVENTEEN
      DESCRIPTION:   
      This patch resolves the following 3 issues:
      1. Detailed display in CPRS for an IV shows data from another
         prescription.
                                                                 
      2. The algorithm used to determine the # of refills for a pending order
         does not take into account the "Rx patient status".
         
                                                                 
      3. Label is incorrectly designated a REPRINT after printing from suspense.
      
    • 313 SEQ #368
      DATE APPLIED:   2014-09-02 12:55:10
      APPLIED BY:   USER,SEVENTEEN
      DESCRIPTION:   
      This patch PSO*7*313 includes the following enhancements:
      The Outpatient Pharmacy application currently allows the entry of a 
         have the letter 't' postfix to the RX # as seen below (entry #1): 
       
                 :                   :                            :
                                                         ISSUE  LAST REF DAY 
         #  RX #       DRUG                       QTY ST  DATE  FILL REM SUP 
        -------------------------------ACTIVE------------------------------- 
         1 100005024t  AMOXAPINE 50MG TAB          30 S  09-26 09-26   2  30 
         2 100005022   AMOXICILLIN 250MG CAP       30 A  08-18 08-18  11  30 
         3 100005035   KALETRA                      3 A  09-29 09-29   0   3 
                 :                   :                            :
      complex order, which contains a "THEN" conjunction. This type of order is
       
         Note: A prescription can be unmarked as Titration/Maintenance by 
               invoking the same TM action on an already marked prescription.  
       
        
      b. A new hidden action is being introduced in the Patient Prescription 
         Processing [LM BACKDOOR ORDERS] option called TR (Convert 
         Titration Rx). This action will populate the new field MAINTENANCE 
         DOSE RX (#45.2) in the PRESCRIPTION File (#52).  
         When a titration to maintenance prescription needs to be 
      allowed to leave the Duration field preceding the "THEN" conjunction 
         refilled so the patient can continue on the Maintenance Dose 
         this option will allow the users to create a new prescription with 
         the maintenance dose only. The process works similar to copying an 
         existing prescription, however it can only be used on prescriptions 
         with the following characteristics: 
         
           - Rx is a complex order with a THEN conjunction
           - Rx was not digitally signed
           - Rx is released 
           - Rx status is ACTIVE 
      as null. This null duration field is causing issues when the Outpatient
           - Rx does not have refills previously ordered 
           - Rx # Of Refills is greater than 0 (zero) 
         
         Before the new Maintenance Rx can be accepted the Pharmacist is 
         prompted to validate the QTY field for the new Rx, which may or may not
         be automatically re-calculated. Only the last dose from the original
         prescription is carried over to the new Maintenance Rx and the # of 
         Refills field is decreased by 1 because the new Maintenance Rx counts 
         as a fill. The Fill Date for the new Maintenance prescription is 
         automatically set with the next possible fill date from the existing
      Pharmacy order was being transferred to an Inpatient Medication Order(s).
         prescription, which can be changed by the pharmacist.
         Once the pharmacist verifies the information for the Maintenance Rx is 
         accurate they can accept the Maintenance Rx. This action will trigger 
         a Duplicate Drug check against the original complex order, which must 
         be discontinued before the new Maintenance Rx can be accepted. 
         After the new Maintenance Rx is accepted it will have the new 
         indicator 'm' on the right side of the Rx # in the patient's Medication
         Profile as seen below (entry #1):
       
                 :                   :                            :
      The default stop dates were for thirty (30) days for the two (2) new
                                                         ISSUE  LAST REF DAY 
         #  RX #       DRUG                       QTY ST  DATE  FILL REM SUP 
        -------------------------------ACTIVE------------------------------- 
         1 100005436m  AMOXAPINE 50MG TAB          30 S  09-26 09-26   1  30 
         2 100005022   AMOXICILLIN 250MG CAP       30 A  08-18 08-18  11  30 
         3 100005035   KALETRA                      3 A  09-29 09-29   0   3 
                 :                   :                            :
       
      c. The new Titration/Maintenance indicator (t/m) will be included in the 
         following menu options where the prescription number is displayed: 
      inpatient orders created and the Start/Stop dates in the sequence were
       
         View Prescriptions                       [PSO VIEW] 
         Patient Prescription Processing          [PSO LM BACKDOOR ORDERS]    
         Complete Orders from OERR                [PSO LMOE FINISH] 
         ePharmacy Medication Profile (View Only) [PSO PMP] 
         Medication Profile                       [PSO P] 
        
      d. External refill requests such as from AudioFax and Internet will not 
         be processed for Titration/Maintenance marked prescriptions. 
       
      incorrect. The pharmacist did not notice the incorrect dates and finished
         Subj: ALBANY External Application Refills: Not processed List  
               [#101509] 01/28/09@13:52  11 lines
         From: POSTMASTER  In 'IN' basket.   Page 1 
         
      -------------------------------------------------------------------------
         Refills Not Processed Report for the ALBANY Division.  
       
         The following refill requests were not processed:  
       
         Patient: OPPATIENT,TWO (9999) 
      off the orders. Upon transfer of a complex order from Outpatient Pharmacy
       
           Rx #: 100005122  (REF #1)  Qty: 55 
           Drug: ZINC SULFATE 66MG TAB 
           Reason: 'Titration/Maintenance Rx' cannot be refilled.  
       
      e. CPRS refill requests will not be automatically processed for
         Titration/Maintenance marked prescriptions. The refill request will
         remain in the patient's Medication Profile as PENDING and the mailman
         message above (item d) will also be sent to PSOAUTRF security key
         holders.  
      to Inpatient Medication order(s), the resulting order will start at the
        
      f. The activity logs for both Titration and Maintenance Rx's will record 
         the corresponding Titration and Maintenance Rx # if they exist as seen 
         below: 
        
      Titration Rx: 
      ------------
      #   Date        Reason         Rx Ref         Initiator of Activity  
      ====================================================================== 
      1   09/29/08    EDIT           ORIGINAL       OPUSER,ONE Comments: 
        1. Complex Orders Duration Field 
      first step rather than continue at the step the patient was at as an
      Maintenance
      Dose Rx: 100005130 
       
       
      Maintenance Rx: 
      --------------
      #   Date        Reason         Rx Ref         Initiator of Activity  
      ====================================================================== 
      1   09/29/08    EDIT           ORIGINAL       OPUSER,TWO Comments: 
      Titration Dose Rx: 100005392
      Outpatient. It looks like a new complex order to the finishing pharmacist,
          
       
      g. The VistA Integration Control Registration (ICR) #2398 provided to 
         Computerized Patient Record System V. 1.0 (CPRS) was modified to 
         prevent the renewal of a Titration dose order with the following 
         message: 
       
        "Prescription was marked as Titration to Maintenance Dose  by Pharmacy 
        and cannot be renewed. To repeat the titration, enter a new prescription
        or copy the prior titration order. To continue the maintenance dose, 
      since the Start date is populated with the date of finishing so that the
        refill this prescription if refills are available or enter a new
        prescription for the maintenance dose."
       
       
      h. When using the Barcode Batch Prescription Entry option 
         [PSO BATCH BARCODE], if the prescription has been marked 
         as a Titration/Maintenance Rx, and the user attempts to 
         renew or refill the prescription, the following message 
         will display: 
       
      patient would be started on the first step, which may not be correct.
         For a renewal: 
         "Rx# XXXXXX is marked as Titration Rx and cannot be renewed." 
       
         For a refill: 
         "Rx# XXXXXX is marked as Titration Rx and cannot be refilled." 
       
       
      i. The PSO HIDDEN ACTIONS Protocol in the PROTOCOL File (#101) 
         will be modified to include the two new Hidden Actions 
         introduced by this enhancement.  PSO LM BACKDOOR MARK AS 
      This would pertain to complex orders that taper or titrate doses up or
         TITRATION and PSO LM BACKDOOR TITRATION RX REFILL are both 
         new protocols added to the PROTOCOL File (#101). 
       
       
       
       ******************************  IMPORTANT  ******************************
       The enhancements related to Titration/Maintenance dose Rx are made only 
       for Outpatient Pharmacy package. The corresponding changes to CPRS 
       package are not included at this time. Therefore, the CPRS Order Copy and
       Order Change functionalities will continue to function as is. 
      down and potentially impacts patients by receiving too much or too little
       Furthermore, there will be no indication of a Titration/Maintenance order
       in the CPRS application.
       *************************************************************************
       
      3. Remedy Ticket #1022059 
         This patch fixes an issue that could create duplicate prescriptions on 
         a patient profile. When a complex order is copied and the duration 
         field is edited, upon accepting the order, the message to discontinue
         the original order is not triggered. This causes duplicate 
         prescriptions to appear on the patient profile. This patch corrects
      medication.  
         this problem by prompting the user to discontinue the original order.
       
      The Outpatient Pharmacy is being modified to require the entry of a 
      duration for a dose preceding a THEN conjunction if the schedule for such
        2. Titration/Maintenance Rx 
      dose is not a ONE-TIME type schedule. If the dose preceding the THEN
      conjunction is a ONE-TIME type schedule the software will continue to
      allow the Duration field to be left blank (optional). The corresponding
      change to CPRS will be done in a future CPRS patch.
       
      Example of an acceptable SIG ('NOW' is ONE-TIME type schedule): 
      --------------------------------------------------------------
      TAKE ONE TABLET BY MOUTH NOW THEN TAKE TWO TABLETS EVERY 8 HOURS 
       
      No longer acceptable SIG ('Q4H' is not ONE-TIME type schedule): 
          
      --------------------------------------------------------------
      TAKE ONE TABLET BY MOUTH EVERY 4 HOURS THEN TAKE TWO TABLETS EVERY 8 
      HOURS 
       
      Note: The SIG above is not acceptable because it does not have a 
            Duration for the first dose. In order to be acceptable the 
            SIG above would have to have a duration like the one below: 
             
            TAKE ONE TABLET BY MOUTH EVERY 4 HOURS FOR 3 DAYS THEN TAKE TWO 
            TABLETS EVERY 8 HOURS 
      1. Complex Orders Duration Field 
         
      The Duration field is not required for the dose following the last "THEN"
      conjunction.  
        
      Below is an example of a complex order being entered via Patient 
      Prescription
      Processing [PSO LM BACKDOOR ORDERS] 
        
          :       :
        VERB: APPLY 
      ================================
        ROUTE: PO// PO   ORAL 
        Schedule: QD (EVERY DAY) 
           
        LIMITED DURATION (IN DAYS, HOURS OR MINUTES): 
        CONJUNCTION: THEN 
         
       Duration field required for the dosage entered prior to this THEN 
       conjunction. 
       
        
      This Enhancement is related to Patient Safety Issue PSI-07-167 and Remedy 
        LIMITED DURATION (IN DAYS, HOURS OR MINUTES): 
          :       :
       
      2. Titration/Maintenance Rx 
      ===========================
      This Enhancement is related to PSI-06-176 and Remedy Ticket #168928.  
       
      The Outpatient Pharmacy (OP) application was modified to accommodate 
      Titration/Maintenance prescription functionality. The existing software 
      presented patient safety risks when prescriptions dispensed with a 
      Ticket # 203088. 
      titrating dose followed by a maintenance dose were being copied, renewed
      or refilled. The issue was that refills as well as the new prescriptions
      (derived from copy, renewals or edits) automatically carried over the
      initial titrating dose into the new fill/prescription, which was not
      always the user's intention.  
       
      The new functionality provides two steps for processing Titration/ 
      Maintenance prescriptions.
       
      a. First, the user will have the ability to mark prescriptions as 
       
         'Titration to Maintenance' when finishing prescriptions from CPRS as 
         well as via the Patient Prescription Processing [PSO LM BACKDOOR 
         ORDERS] option by invoking the new hidden action 'TM' - Mark Rx 
         as Titration. This action will result in preventing the following 
         actions to be taken on the prescription: Refill, Renewal (including 
         via CPRS), Copy and editing of any field that requires a new Rx to be 
         created. This action will also set the new field TITRATION RX FLAG 
         (#45.3) in the PRESCRIPTION File (#52) as well as the new field 
         TITRATION DOSE RX (#45.1) in the PRESCRIPTION File (#52).  
         Prescriptions that are marked as Titration/Maintenance will 
      
    • 408 SEQ #369
      DATE APPLIED:   2014-09-02 12:55:21
      APPLIED BY:   USER,SEVENTEEN
      DESCRIPTION:   
      The Safety Updates for the Medication Prescription Management (SUMPM)
      information for purposes of their profession. The information must be
      9. Queue Background Jobs [PSO AUTOQUEUE JOBS]
         ------------------------------------------
         The Scheduled Batch Export [PSO SPMP SCHEDUED EXPORT] option mentioned
         above will be added to the list of options that can be edited via this
         option.
      reported using the American Society for Automation in Pharmacy (ASAP) data
      format, which was developed by the Alliance of States with Prescription
      Monitoring Programs and the National Association of State Controlled
      Substances Authorities.
        
      The new menu called State Prescription Monitoring Program Menu [PSO SPMP
      MENU] can be found under the Supervisor Functions [PSO SUPERVISOR]
      menu option. The following options will be available under this new menu:
       
      project adds a new module to the Outpatient Pharmacy V. 7.0 application,
      1. View/Edit SPMP State Parameters [PSO SPMP STATE PARAMETERS]  
         -----------------------------------------------------------
         This option is used for viewing or editing the SPMP parameters for a 
         specific state. The following fields can be updated via this option:
       
            ASAP VERSION
            TRANSMIT RETURN TO STOCK*
            INCLUDE NON-VETERAN PATIENTS
            REPORTING FREQUENCY IN DAYS
            VMS LOCAL DIRECTORY
      which will be used for enabling the Veterans Health Administration (VHA)
            UNIX/LINUX LOCAL DIRECTORY
            WINDOWS/NT LOCAL DIRECTORY
            FILE NAME PREFIX
            FILE EXTENSION
            STATE FTP SERVER IP ADDRESS
            STATE FTP SERVER USERNAME
            STATE FTP SERVER PORT #
            STATE FTP SERVER PASSWORD
            STATE FTP SERVER DIRECTORY
            SFTP TRANSMISSION MODE
      pharmacies to comply with Mandatory Reporting to State Controlled
            SFTP PRIVATE KEY TEXT**
            SFTP PUBLIC KEY TEXT**
       
         *  Visible only if ASAP VERSION is 1995
         ** Visible only if SFTP TRANSMISSION MODE is set to A - AUTOMATIC 
        
      2. View ASAP Definitions [PSO SPMP VIEW ASAP DEFINITIONS]
         ------------------------------------------------------
         This option allows the user to visualize the ASAP data format and the
         data elements reported to the states. It provides detailed information
      Substance Rx Databases required by Consolidated Appropriations Act, 2012,
         about each segment and field for the ASAP format versions 4.0, 4.1 and
         4.2.
          
      3. View/Export Single Prescription [PSO SPMP SINGLE RX VIEW/EXPORT]
         ----------------------------------------------------------------
         This option is used for visualizing a specific prescription and the
         data related to a specific fill that is transmitted to the state in the
         ASAP format.
        
      4. View Export Batch [PSO SPMP BATCH VIEW/EXPORT]
      PL 112-74. Also known as State Prescription Monitoring Program (SPMP), the
         ----------------------------------------------
         The information reported to the states are first compiled into a batch,
         which can be for a single prescription or a collection of prescriptions
         for a determined date range. This option allows the user to visualize 
         information contained in one batch as well as the list of prescriptions
         in the batch. This option also allows the user to manually export the
         batch to the state.
       
      5. Export Batch Processing [PSO SPMP BATCH PROCESSING]
         ---------------------------------------------------
      program is a state electronic database which collects designated data on
         This option is used to monitor all the batches used to transmit data to
         the states. The user selects a date range and a list of batches is
         presented where the user can select to perform different actions on a
         specific batch.
         
      6. Scheduled Batch Export [PSO SPMP SCHEDULED EXPORT]
         --------------------------------------------------
         This option is used for running the automatic transmission to the
         states and should not be executed by the end-user directly. It will be
         automatically scheduled to run nightly and it will decide when to
      controlled substances dispensed. The states then distribute data from the
         transmit the data to the state based on the REPORTING FREQUENCY IN DAYS
         field (#3) of the SPMP STATE PARAMETERS file (#58.41) value for the
         state, which can be updated via the View/Edit SPMP State Parameters
         [PSO SPMP STATE PARAMETERS] option.
       
      7. Accounting Of Disclosures Report [PSO SPMP DISCLOSURE REPORT]
         -------------------------------------------------------------
         This option is used for generating a list of prescriptions transmitted
         to states. This option allows for a date range selection as well as
         one, multiple or all states and one, multiple or all patients. The list
      database to individuals who are authorized under state law to receive the
         is sorted by state and then by patient. 
       
      8. Unmark Rx Fill as Administered In Clinic [PSO SPMP UNMARK ADMIN CLINIC]
         -----------------------------------------------------------------------
         This option is used to unmark prescriptions as 'Administered In
         Clinic'. Administered in clinic prescription fills are not transmitted
         to the states. This option enables the user to unmark fills that have
         been mistakenly marked as 'Administered In Clinic' and subsequently
         transmit them to the state.
       
      
    • 436
      DATE APPLIED:   2014-10-31 15:56:10
      APPLIED BY:   USER,SEVENTEEN
    • 37 SEQ #36
      DATE APPLIED:   2000-05-16 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
       1. Site reports that inactive orderable items are showing up as a choice for 
       
      3. This patch corrects a problem where pharmacists without the PSOLOCKCLOZ key
      are not allowed to override Clozapine medication orders from CPRS when there
      are no recent lab data available.  
       
      4. This patch corrects a problem when renewing prescriptions with cosigning 
      providers and the cosigning provider has changed from the previous renewed 
      prescription.  
       
      5. This patch corrects a problem where the Nature of Order retains an incorrect
      the pharmacist when editing of verified or pending prescriptions.  It does not
      default  when discontinuing active orders while using the Copy (OP) [PSO LM BACKDOOR
      COPY] action.  
       
      6. This patch adds an order check for valid providers when the Copy (OP) [PSO
      LM BACKDOOR COPY] action.  
       
      7. This patch corrects a problem when using the Discontinue Prescription(s) 
      [PSO C] option to discontinue individual prescriptions.  
       
      8. This patch corrects a possible %DSM-E-NUMBER, ILLEGAL NUMBER error.  
      even distinguish active/inactive.  This is creating confusion because the
       
      pharmacist does not know which to choose.  
       
      2. In the Clozapine ordering software an invalid check is done to determine if
      the site is registered with the National Clozapine Center.  The fields, *SITE
      DEA NUMBER (#1) and *SITE (NATIONAL NAME) (#2), in the OUTPATIENT SITE file
      (#59) are marked for deletion and should not be used.  
      
    • 437 SEQ #371
      DATE APPLIED:   2014-11-12 12:44:56
      APPLIED BY:   USER,SEVENTEEN
      DESCRIPTION:   
      This patch addresses the following:
      2. Patch PSO*7*313, had this verbiage:
         "The Outpatient Pharmacy is being modified to require the entry of a 
         duration for a dose preceding a THEN conjunction if the schedule for
         such dose is not a ONE-TIME type schedule. If the dose preceding the
         THEN conjunction is a ONE-TIME type schedule the software will continue
         to allow the Duration field to be left blank (optional)".
       
         It was supposed to allow a ONE-TIME type schedule to proceed without
         the duration, but it did not. This patch corrects this issue.
       
      1. New Jersey had an issue with the setup after the installation of
         patch PSO*7*408. When they tried to transmit Controlled Substances
         prescriptions to the State Prescription Monitoring Program (SPMP),
         there was an issue with the VMS local directory, "USER$:[EXTRACT.SPMP]"
         conversion to the Unix/Linux format, "/USER$/EXTRACT/SPMP". This patch
         fixes this issue.
       
      
    • 438 SEQ #373
      DATE APPLIED:   2015-03-20 11:18:09
      APPLIED BY:   USER,SEVENTEEN
      DESCRIPTION:   
      The new universal member ID# is not included in the description of
      acceptable criteria to select a patient at the VistA Outpatient
      selection prompt.
      Drug-Drug Interaction is not occurring with Non-VA Meds
      
    • 282
      DATE APPLIED:   2015-09-16 14:22:23
      APPLIED BY:   USER,SEVENTEEN
    • 370
      DATE APPLIED:   2015-12-01 17:51:23
      APPLIED BY:   USER,FIFTYFOUR
      DESCRIPTION:   
      This patch will resolve the following issues.
      A foreign address is triggered for the Philippines when printing
      suspense labels with a Routing of Mail.
      The Help Prompt for the Label Date/Time in the Prescription file is 
      incorrect.
      When editing the Refill Date on a prescription, the internal Fileman
      date is stored in the Activity Log entry.
      User without PSORPH key can put rx on hold using pharmacist reasons.
      The finishing pharmacist's name appears in the released pharmacist's entry
      
    • 427
      DATE APPLIED:   2016-02-11 17:16:38
      APPLIED BY:   USER,FIFTYFOUR
    • 443 SEQ #378
      DATE APPLIED:   2016-03-04 13:24:35
      APPLIED BY:   USER,FIFTYFOUR
      DESCRIPTION:   
      A prescription that has been transmitted to the CMOP can be put on HOld.
      
    • 456 SEQ #379
      DATE APPLIED:   2016-03-10 17:08:53
      APPLIED BY:   USER,FIFTYFOUR
    • 411
      DATE APPLIED:   2016-05-26 15:49:17
      APPLIED BY:   USER,FIFTYFOUR
    • 444 SEQ #381
      DATE APPLIED:   2016-07-13 12:57:20
      APPLIED BY:   USER,FIFTYFOUR
      DESCRIPTION:   
      This patch is part of the Pharmacy Safety Updates project which was 
         APPLICATION/VERSION                                  PATCH
         SUPPLY field based on the limit set by the MAXIMUM DAYS SUPPLY field (#66)
         in the DRUG file (#50) or the MAXIMUM DAYS SUPPLY field (#32) in the VA
         PRODUCT (#50.68) file. If alternate maximum values exist, the current
         limits will remain the same.
       
      3. Edit Prescriptions [PSO RXEDIT] option
         This option was also modified to accept the new maximum value for the DAYS
         SUPPLY field based on the limit set by the MAXIMUM DAYS SUPPLY field (#66)
         in the DRUG file (#50) or the MAXIMUM DAYS SUPPLY field (#32) in the VA
         PRODUCT (#50.68) file. If alternate maximum values exist, the current 
         -----------------------------------------------------------------
         limits will remain the same.
       
      4. Barcode Batch Prescription Entry [PSO BATCH BARCODE] option
         The renewal functionality within this option was also modified to accept
         the new maximum value for the DAYS SUPPLY field based on the limit set by
         the MAXIMUM DAYS SUPPLY field (#66) in the DRUG file (#50) or the MAXIMUM
         DAYS SUPPLY field (#32) in the VA PRODUCT (#50.68) file. If alternate
         maximum values exist, the current limits will remain the same.
        
      5. Prescription Management Data Compilation   
         OUTPATIENT PHARMACY (OP) V. 7.0                      PSO*7*444
         The algorithm used to compile prescription management data was modified to
         account for prescriptions with greater than 90 days supply. The OVER 90
         DAYS (#8) field in the OUTPATIENT PHARMACY MANAGEMENT DATA file (#59.12), 
         which is used as a counter for the number of prescription fills with DAYS
         SUPPLY value greater than 90, will now be populated.
        
      6. Count of Prescriptions [PSO MGMT REPORT RX COUNTS] option &
         Count of Prescriptions [PSO MGMT MONTHLY RX COUNTS] option
         These daily and monthly reports have been modified to include a new column
         called ">90 DAY", as seen below. This column will display the total number
         INTEGRATED BILLING (IB) V. 2.0                       IB*2*545
         of prescription fills with a DAYS SUPPLY value greater than 90, as shown
         below.
       
                30      60      90     >90      EQ             TOT     TOT
               DAY     DAY     DAY     DAY     FLS    METH      RX   EQ FL
            ...===========================================================...
                 1       3       0       1      11       0       5      11
                 0       0       1       2      14       0       3      14
                 0       0       0       0       0       0       0       0
                 0       0       0       0       0       0       0       0
         PHARMACY DATA MANAGEMENT (PDM) V. 1.0                PSS*1*189
            ...=== ======= ======= ======= ======= ======= ======= =======...
                 1       3       1       3      25       3       8      25
         NATIONAL DRUG FILE (NDF) V. 4.0                      PSN*4*429
         INPATIENT MEDICATIONS (IM) V.5.0                     PSJ*5*313
       
       
      The following New service Requests (NSRs), Remedy Ticket and Patient Safety
      established to address specific New Service Requests (NSRs) as well as a
      Issue (PSI) are being addressed by this patch:
       
       NSRs 20060601/20111206 Allow Dispensing of Greater Than 90 Day Supply
       ---------------------------------------------------------------------------
       The Outpatient Pharmacy and supporting VistA applications are being modified
       to allow dispensing of more than 90 day supply fill for outpatient 
       prescriptions. The new limit will be 365 days and will be set for each drug
       individually. See below for more information on specific menu 
       options related to this enhancement.  
       
      Remedy Ticket and a Patient Safety Issue (PSI) related to the VistA Pharmacy
       PSI PSPO00002793 Patient Prescription Processing error, truncating the 
                        second character of the Days Supply
       Remedy 387051 Patient Medication Profile Bad Address Indicator display
       ----------------------------------------------------------------------------
       The Outpatient Pharmacy Medication Profile has a display problem for a
       prescription with the following characteristics: 2-letter status (e.g., DC), 
       drug marked for Consolidated Mailout Outpatient Pharmacy (CMOP) and Bad
       Address Indicator. When a prescription with all three features is displayed
       the DAY SUP column value is being truncated as illustrated below where the
       Day Supply value is actually 90 and it displays as 9.
      applications as approved by the Health Systems Enterprise Systems Manager
       
                                                                ISSUE  LAST REF DAY
       #  RX #         DRUG                              QTY ST  DATE  FILL REM SUP
       --------------------------------DISCONTINUED--------------------------------
       1 100005604$    TOBRAMYCIN 80MG/2ML INJ           100 DC>B01-21 01-21   0  9
        
       
      This patch modifies the Outpatient Pharmacy application regarding the
      enhancements and issues listed above:
       
      (ESM).
      1. Patient Prescription Processing [PSO LM BACKDOOR ORDERS] option 
         a) The backdoor pharmacy was modified to accept the new maximum value for
            the DAYS SUPPLY field based on the limit set by the MAXIMUM DAYS SUPPLY
            field (#66) in the DRUG file (#50) or the MAXIMUM DAYS SUPPLY field (#32)
            in the VA PRODUCT (#50.68) file. If alternate maximum values do not
            exist, the current limits will remain the same.
       
            Note: The MAXIMUM DAYS SUPPLY field (#32) added to the VA PRODUCT file
                  (#50.68) is being introduced by patch PSN*4*429, however it will
                  not be populated initially by the Pharmacy Product System -
       
                  National (PPS-N) as changes will be required to that application to
                  edit and export this new field. 
        
         b) The medication profile was modified to display the Bad Address Indicator
            in a different line in order to address the Remedy Ticket 387051 and 
            Patient Safety Issue PSPO00002793 mentioned above. The indicator will be
            placed in the next line, as seen below.
       
          ----------------------------------ACTIVE---------------------------------
          1 100005598   ALSEROXYLON 2MG TAB              400 A> 12-11 03-01   2  90
      This project is comprised of patches from five different applications, as
                                                            **Bad Address**   
          2 100005596   DESIPRAMINE 25MG TAB              90 DC 11-01 11-01  11  30
                                                            **Bad Address**   
          3 100005601A  NAPROXEN 250MG S.T.              170 HP>12-17 12-17   5  30
                                                            **Bad Address**   
          4 100005595   TIMOLOL 0.25% OPTH SOL 10ML       90 S> 11-01 11-21  10  30
        
       
        c) The calculation of the number of refills for a prescription was modified 
           to take into account the new maximum value allowed for the DAYS SUPPLY
      shown below:
           field. The current calculation (up to 90 days supply) will remain the
           same and a new formula will be introduced to calculate the number of
           refills for days supply values of 91 up to 365. The table below shows
           the number of refills allowed based on the days supply value:
       
           ---------------------------------+------------------------------------
              NON-CONTROLLED SUBSTANCES     | CONTROLLED SUBSTANCES (NO CHANGE)
           ---------------+-----------------+------------------+-----------------
            DAYS SUPPLY   |   # OF REFILLS  |   DAYS SUPPLY    |   # OF REFILLS    
           ---------------+-----------------+------------------+-----------------
        
               1 - 59     |        11       |       1 - 59     |        5
              60 - 89     |         5       |      60 - 89     |        2
              90 - 91     |         3       |        90        |        1
              92 - 121    |         2       |                  |        
             122 - 182    |         1       |                  | 
             183 - 365    |         0       |                  |
           ---------------+-----------------+------------------+----------------
       
      2. Complete Orders From OERR [PSO LMOE FINISH] option
         This option was modified to accept the new maximum value for the DAYS
      
    • 458 SEQ #382
      DATE APPLIED:   2016-07-13 14:28:31
      APPLIED BY:   USER,FIFTYFOUR
      DESCRIPTION:   
      ME2 Follow Up build for known minor defects.
      
    • 39 SEQ #38
      DATE APPLIED:   2000-06-12 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      1) This patch will add  functionality to the drug/class orders check to
      was suspended locally instead of transmission to CMOP.  PSO*7*39.  
       
      'List of Rxs with CMOP Drugs Printed From Suspense'
           Option name: PSO SUCMOP 
      PRINT REPORT
      This utility will print a report of everything that has printed 
      locally that has a CMOP drug.  This report is by start and end dates.  The
      report will list the Rx#, patient name, date printed from suspense, and the
      drug.  This report is printed by the division you have signed in under. 
            
      display the CMOP status of an Rx when entering new Rxs.  
           PSO*7*39.
       
      'Re-Suspend Printed Rxs with CMOP Drugs'
           Option name: PSO SUCMOP RE-SUSLOCALCMOPPRI
      This utility will allow sites to re-suspend those Rxs that list on the 
      List of Rxs with CMOP Drugs Printed From Suspense report [PSO SUCMOP
      PRINT REPORT].  This utility will re-suspend to the date that it was originally
      suspended to.  It should not be necessary to edit the suspended date  
      because all Rxs queued for CMOP transmission will be transmitted.
            
       
           PSO*7*39
       
      'Unprinted/Non-Transmitted Rxs Re-Suspend'
           Option name: PSO SUCMOP RESUSPENDNOTPRI
      This utility will allow sites to re-suspend everything that has not printed
      and not already queued for CMOP.  This utility can be queued to run in the
      background or while you wait. 
            
           PSO*7*39
      2) This patch corrects a problem where an incorrect CMOP status is displayed
      next to the Release date on the order display screen. 
       
      CMOP Utilities      Option name:  PSO SUCMOP MENU 
       
      This menu will contain utilities to help the sites re-suspend those Rxs that
      
    • 450 SEQ #383
      DATE APPLIED:   2016-08-15 12:40:46
      APPLIED BY:   USER,FIFTYFOUR
      DESCRIPTION:   
      This patch addresses 3 issues.
       
              3) When editing a RX and allow to time out at Noun Prompt, nothing
                 will be saved prior to the prompt.
       
              1) When adding a new order via PSO LM BACKDOOR, if a user edits
                 the data for the new order and then enters "^" to exit editing,
                 the system cancels the order
       
              2) In PSO PROVIDER EDIT, the user sometimes accesses fields which 
                 they should not be accessing.  Additionally, using UP-ARROW
                 jump does not always work.
      
    • 451 SEQ #384
      DATE APPLIED:   2016-08-15 12:41:13
      APPLIED BY:   USER,FIFTYFOUR
      DESCRIPTION:   
      The State Prescription Monitoring Program (SPMP) Enhancement project was
      After PSO*7*408 was released it was identified during the implementation
         also to delete an existing SSH key pair. In addition, this new option will
         provide an extensive help text on how the SSH keys are used in the 
         transmission process, which is shown below:
         
           Select one of the following:
       
                V         View Public SSH Key
                N         Create New SSH Key Pair
                D         Delete SSH Key Pair
                H         Help with SSH Keys
      phase that some states PDMPs had unique requirements that could not be
       
           Action: V// H  Help with SSH Keys
        
         Secure SHell (SSH) Encryption Keys are used to automate the data 
         transmission to the State Prescription Monitoring Programs (SPMPs). Follow
         the steps below to successfully setup SPMP transmissions from VistA to the
         state/vendor server:
       
         Step 1: Select the 'N' (Create New SSH Key Pair) Action and follow the
                 prompts to create a new pair of SSH keys. If you already have an
      fulfilled by the functionality released in PSO*7*408 which caused the SPMP
                 existing SSH Key Pair you can skip this step. You can check
                 whether you already have an existing SSH Key Pair through the 'V'
                 (View Public SSH Key) Action.
       
              Encryption Type: DSA or RSA?
              ----------------------------
              Digital Signature Algorithm (DSA) and Rivest, Shamir & Adleman (RSA)
              are two of the most common encryption algorithms used by the IT
              industry for securely sharing data. The majority of SPMP servers can
              handle either type; however there are vendors that accept only one
      transmissions from sites in such states to be rejected. This patch
              specific type. You will need to contact the SPMP vendor support to
              determine which type to select.
       
         Step 2: Share the Public SSH Key content with the state/vendor. In order
                 to successfully establish SPMP transmissions the state/vendor will
                 have to install/configure the new SSH Key created in step 1 for
                 the user id they assigned to your site. Use the 'V' (View Public
                 SSH Key) Action to retrieve the content of the Public SSH key. The
                 Public SSH Key should not contain line-feed characters, therefore
                 after you copy & paste it from the terminal emulator into an email
      (PSO*7*451) will enhance the SPMP functionality to allow VHA to fulfill
                 or text editor make sure it contains only one line of text (no 
                 wrapping).
        
      4. View/Export Single Prescription [PSO SPMP SINGLE RX VIEW/EXPORT] option
         -----------------------------------------------------------------------
         This option was modified to highlight custom Data Elements and Segments
         by changing the font color as well as by adding an '*' (asterisk) to the
         right of the Data Element or Segment ID.
       
      5. View/Export Batch [PSO SPMP BATCH VIEW/EXPORT] and Export Batch Processing
      specific state requirements and successfully transmit data to those states
         [PSO SPMP BATCH PROCESSING] options
         --------------------------------------------------------------------------
         When exporting a batch through one of these two options the users will now
         have three different choices to execute the transmission: 'B' for 
         Background (via TaskMan), which queues the transmission to be performed in
         the background through TaskMan; 'F' for Foreground, which executes the
         transmission in the foreground as it did before this patch and 'D' for
         Debug Mode (Foreground), which will execute the transmission in the
         foreground however it will display the sFTP debug steps, which can be very
         helpful for troubleshooting transmission problems. 
      PDMPs. This patch also enhances the security of Secure SHell (SSH) Keys 
         Before this patch the transmission was always executed in the foreground
         which made it difficult to troubleshoot issues with the transmissions, 
         especially the scheduled transmissions, which are always executed in the
         background. Below is a screen capture of the prompt for choosing the
         transmission execution mode:
        
         Select Item(s): Quit// EXP   Export Batch  
        
         Indicate whether the transmission should be queued to run on the
         Background via TaskMan, on the Foreground (Terminal Screen) or in Debug
      management by streamlining the SSH Key creating and restricting user access
         Mode (Foreground)
       
            Select one of the following:
       
                B         Background
                F         Foreground
                D         Debug Mode (Foreground)
       
         Running Mode: F// 
       
      to the Private SSH Key content. In addition, a few smaller miscellaneous
      6. PSO SPMP NOTIFICATIONS Mail Group
         ---------------------------------
         The existing mail group PSO SPMP NOTIFICATIONS released by PSO*7*408 will
         be modified from type PRIVATE to PUBLIC.
       
      7. SPMP Transmission Failed MailMan Message
         ----------------------------------------
         The Mailman message generated by the SPMP Scheduled Background Job as well
         as by the (B)ackground option mentioned above for exporting a batch to the
         state was modified to include Operating System sFTP Log Information, as in
      issues have also been addressed, which are described below.
         this example from an OpenVMS environment:
       
         Subj: NEW YORK Prescription Monitoring Program Transmission Failed [#99999]
         02/29/16@12:44  26 lines
         From: SPMP TRANSMISSION  In 'IN' basket.   Page 1
         --------------------------------------------------------------------------
         There was a problem with the transmission of information about Controlled
         Substance prescriptions to the NEW YORK State Prescription Monitoring
         Program (SPMP).
       
      established to further enhance the VistA SPMP functionality released by patch
       
         Batch #: 41
         Period : 02/29/16 thru 02/29/16
         Error  : Secure FTP Transmission failed.
       
         Please, use the option Export Batch Processing [PSO SPMP BATCH PROCESSING]
         to manually transmit this batch to the state.
         
         sFTP Log:
         ========
         $ SET VERIFY=(PROCEDURE,IMAGE)
      All the changes introduced by this patch were related to the options under
         $ SET DEFAULT USER$:[SPMP]
         $ sftp -"D3" -oIdentityFile="/USER$/SPMP/VMSSSHID." -"B" SPMP_FTP_201606021
         6.INP -oUser=VATEST 54.175.203.159
         debug( 2-JUN-2016 17:37:28.02): Ssh2/SSH2.C:1896: CRTL version (SYS$SHARE:D
         SHR.EXE ident) is V8.3-01
         debug( 2-JUN-2016 17:37:28.04): SshAppCommon/SSHAPPCOMMON.C:313: Allocating
         bal SshRegex context.
         debug( 2-JUN-2016 17:37:28.05): SshConfig/SSHCONFIG.C:3482: Metaconfig pars
         stopped at line 4.
         debug( 2-JUN-2016 17:37:28.05): SshConfig/SSHCONFIG.C:890: Setting variable
      the State Prescription Monitoring Program (SPMP) Menu [PSO SPMP MENU] which
         rboseMode' to 'FALSE'.
         debug( 2-JUN-2016 17:37:28.06): SshConfig/SSHCONFIG.C:3390: Unable to open 
         /ssh2_config
         debug( 2-JUN-2016 17:37:28.07): Connecting to 54.175.203.159, port 22... 
          not used)
         debug( 2-JUN-2016 17:37:28.07): Ssh2/SSH2.C:2881: Entering event loop.
         debug( 2-JUN-2016 17:37:28.12): Ssh2Client/SSHCLIENT.C:1655: Creating tra
          protocol
         debug( 2-JUN-2016 17:37:28.12): SshAuthMethodClient/SSHAUTHMETHODC.C:104:
         "publickey" to usable methods. 
      is located under the Supervisor Functions [PSO SUPERVISOR] menu option. 
         %TCPIP-E-SSH_FC_ERR_DEST, destination is not directory or does not exist
        
         ...
       
         debug( 2-JUN-2016 17:37:35.66): Ssh2/SSH2.C:327: locally_generated = TRUE
         Disconnected; no more authentication methods available (No further authent
         on methods available.).
         debug( 2-JUN-2016 17:37:35.66): Ssh2Client/SSHCLIENT.C:1731: Destroying 
         debug( 2-JUN-2016 17:37:35.66): SshConfig/SSHCONFIG.C:2888: Freeing pki. 
         pki != NULL, user_pki = NULL)
       
         debug( 2-JUN-2016 17:37:35.66): SshConnection/SSHCONN.C:2636: Destroying
         debug( 2-JUN-2016 17:37:35.66): Ssh2Client/SSHCLIENT.C:1799: Destroying 
         completed.
         debug( 2-JUN-2016 17:37:35.66): SshAuthMethodClient/SSHAUTHMETHODC.C:109: 
         oying authentication method array.
         %TCPIP-F-SSH_FATAL, non-specific fatal error condition 
       
      8. PSO SPMP ADMIN Security Key
         ---------------------------
         A new security key was created to restrict access to the following SPMP
      The following functionality enhancements will be delivered by this patch:
         functionalities:
       
            - ASAP Definition Customization updates through the option View/Edit
              ASAP Definitions [PSO SPMP ASAP DEFINITIONS]. Visualization of the
              current ASAP Definition is not restricted.
       
            - SPMP Parameters value updates through the option View/Edit SPMP State
              Parameters [PSO SPMP STATE PARAMETERS]. Visualization of the current
              SPMP parameters is not restricted.
        
       
            - SSH Key generation or replacement through the option Manage Secure
              SHell (SSH) Keys [PSO SPMP SSH KEY MANAGEMENT]. Visualization of the
              current public key is not restricted.
       
      9. Misleading "File Successfully Transmitted" message for Linux OS
         ---------------------------------------------------------------
         The previous algorithm used to identify whether the SPMP sFTP data
         transmission was successful was not 100% accurate for Linux Operating
         Systems. A new algorithm has been created and it should reflect the
         transmission status with much greater accuracy when transmitting data
      1. View/Edit ASAP Definitions [PSO SPMP ASAP DEFINITIONS] option
         from a Linux based environment.
       
      10.SPMP Files Access Restrictions
         ------------------------------
         The FILE ACCESS setting for the SPMP files below will be opened up so
         users can use FileMan to view and search their content. The files were
         unintentionally released in PSO*7*408 as restricted.
       
          - SPMP ASAP RECORD DEFINITION (#58.4)
          - SPMP EXPORT BATCH (#58.42)
         -------------------------------------------------------------
       
      11. Pharmacy DEA Number (ASAP Data Element PHA03)
          ---------------------------------------------
          The Pharmacy DEA# was previously retrieved from the INSTITUTION file
          (#4) through the RELATED INSTITUTION field (#100) in the OUTPATIENT
          SITE file (#59). Now, the software will look for a DEA# for the
          institution in NPI INSTITUTION field (#101) in the OUTPATIENT SITE
          file (#59). If the DEA# for the NPI Institution is blank the software
          will retrieve the DEA# for the Related Institution, like it was doing
          before this patch.
         Some extensive enhancements have been made to this option to allow full 
      PSO*7*408 back in September 2014. The SPMP VistA functionality is used to
         user customization of the American Society for Automation in Pharmacy
         (ASAP) data definition format (protocol) used to report outpatient
         controlled substance prescription data to the states.
       
         a) The term '/Edit' has been added to the external name of this option
            and the term 'VIEW' was removed from the internal option name.
        
         b) This option has been modified to include full customization capability 
            for the ASAP definitions 3.0 and later versions, which will allow sites 
            to fulfill states PDMPs' specific requirements. Moreover, sites will be
      identify prescriptions for controlled substance drugs, Schedule 2 through 5,
            able to create new ASAP versions by copying an existing one, which
            will hopefully allow them to continue transmissions well into the
            future as new ASAP versions are released and adopted by the states
            PDMPs.
            
            Below is a list of actions that have been added to this option:
             
            CV  Copy ASAP Version  CE  Customize Element     ED  Edit Delimiters
            CS  Customize Segment  DC  Delete Customization  
        
      dispensed by the Veterans Health Administration (VHA) Outpatient Pharmacy
            For more information on these new actions see the Outpatient Pharmacy
            Manager's User Manual in the State Prescription Monitoring Program
            (SPMP) section.
       
         c) Customized Data Elements and Segments will be identified by an '*' 
            (asterisk) displayed to the right of the Data Element or Segment ID.
       
      2. View/Edit SPMP State Parameters [PSO SPMP STATE PARAMETERS] option
         ------------------------------------------------------------------
         A few modifications have been made to this option to support the new 
      facilities and to create and transmit an export file containing this
         functionality released by this patch.
       
         a) The parameter WINDOWS/NT LOCAL DIRECTORY was removed from this option
            because this module no longer supports this operating system  due to
            the increase in the complexity for handling SSH Keys and the fact that 
            VHA does not use WINDOWS/NT operating system for VistA database at any
            of its sites.
       
         b) The parameter REPORTING FREQUENCY IN DAYS was modified to allow a
            maximum value of 30 days. Before this field allowed a maximum value of
      information to the Prescription Drug Monitoring Program (PDMP) of each state
            99 days.
              
         c) A new parameter called RENAME FILE AFTER UPLOAD was added right after
            the 'FILE EXTENSION' parameter. The current transmission creates and
            sends the data file with the ".UP" file extension (for "upload"); once
            the file is transmitted a command within sFTP (Secure File Transfer 
            Protocol) is issued to rename the file to ".DAT" (or ".TXT") file
            extension. This new parameter will allow the site to control whether
            they want to keep the existing functionality by setting this parameter
            to 'YES' or if they would like to create and transmit the file without
      on a daily basis.
            renaming it by setting this parameter to 'NO'. The parameter will be
            initially exported with a default value of 'YES', which is consistent
            with the existing released functionality.
       
         d) The parameters STATE SFTP SERVER IP ADDRESS and STATE SFTP SERVER
            USERNAME had their maximum value lengths increased from 30 to 60 and
            50 characters respectively to accommodate longer PDMP's DNS (Domain
            Name System) names and the usernames they assign to VHA sites.
       
         e) For security reasons the parameters SFTP PRIVATE KEY TEXT and SFTP
       
            PUBLIC KEY TEXT have been removed from this option as the SSH
            encryption keys content will be handled by a new option called Manage
            Secure SHell (SSH) Keys [PSO SPMP SSH KEY MANAGEMENT], which is
            described below.
        
      3. Manage Secure SHell (SSH) Keys [PSO SPMP SSH KEY MANAGEMENT] option 
         -------------------------------------------------------------------
         This new option was created to automate the management of SSH encryption
         keys and to improve the security regarding their content. This new option
         will allow sites to view the public SSH key, create a new SSH key pair and
      
    • 448
      DATE APPLIED:   2016-08-29 12:56:25
      APPLIED BY:   USER,FIFTYFOUR
      DESCRIPTION:   
      MCCF ePharmacy Compliance Phase 3
      
    • 469 SEQ #386
      DATE APPLIED:   2016-09-23 15:22:19
      APPLIED BY:   USER,FIFTYFOUR
      DESCRIPTION:   
       This patch is part of the Pharmacy Safety Updates project and will 
       
       CA Service Desk I10102695FY16
       -----------------------------
       Pharmacy Technician not able to edit # of refills data field.
       address Patient Safety Issue (PSI) #PSPO00003291 and CA Service 
       Desk ticket I10102695FY16.
       
       PSI PSPO00003291 is CA Service Desk Ticket I10020812FY16
       --------------------------------------------------------
       When processing outpatient medication orders, and no dispense drug 
       is selected, the range values for the # of refills prompt is
       defaulting to zero.
      
    • 455 SEQ #387
      DATE APPLIED:   2016-10-28 15:15:40
      APPLIED BY:   USER,FIFTYFOUR
      DESCRIPTION:   
      This patch addresses five issues:
      medications that have a sig longer than 3 words will not display in the 
      meds tab.
       
              4. If a Health Level 7 (HL7) delimiter character is inserted
      into the comment field for Non-VA meds, the escape character is 
      incorrectly stored in the global.
       
              5. Non-VA meds do not display on the Meds Tab in CPRS if the
      Start Date is set to NOW when creating the Non-VA med.
               1. The calculation of the dosage of a prescription will not 
      populate when creating an order and entering the schedule in all lower 
      case. 
              2. Schedules are not expanding to SPANISH. The labels aren't 
      printing in Spanish translated from English as necessary when creating a 
      prescription in outpatient pharmacy. 
       
              3. In the Computerized Patient Record System (CPRS) Non-VA 
      
    • 454 SEQ #388
      DATE APPLIED:   2016-12-01 15:51:17
      APPLIED BY:   USER,FIFTYFOUR
      DESCRIPTION:   
      One VA Pharmacy remote prescription enhancements.
      
    • 460
      DATE APPLIED:   2016-12-20 15:22:51
      APPLIED BY:   USER,FIFTYFOUR
      DESCRIPTION:   
      FIXED MEDICATION COPAYMENT TIER (FMCT)
      
    • 475 SEQ #390
      DATE APPLIED:   2017-01-23 13:50:16
      APPLIED BY:   USER,FIFTYFOUR
      DESCRIPTION:   
      This patch resolves a problem where a pharmacy user is not prompted for a 
      label device. This occurs when the host site does not generate label data 
      for a remote refill or partial fill request.
      
    • 476 SEQ #391
      DATE APPLIED:   2017-02-03 15:27:50
      APPLIED BY:   USER,FIFTYFOUR
      DESCRIPTION:   
      FIXED MEDICATION COPAYMENT TIER (FMCT)
      
    • 459 SEQ #392
      DATE APPLIED:   2017-02-24 17:03:53
      APPLIED BY:   USER,FIFTYFOUR
      DESCRIPTION:   
      This patch will fix the issue where a suspended prescription
      is being transmitted to CMOP too soon.
      
    • 40 SEQ #39
      DATE APPLIED:   2000-07-11 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      1) In V. 6.0 of Outpatient Pharmacy when a medication was returned to stock 
      prescription is returned to stock.  This functionality becomes fully
      functional when PSD*3*24 is installed.  
       
      2) With the release of PSO*7*32, functionality was added to allow the 
      inactivating of Outpatient Pharmacy divisions in the OUTPATIENT SITE file 
      (#59).  The DIC("S") that was added prevented these inactive divisions from 
      selection when processing Audiofax prescriptions.  This patch will allow 
      inactive divisions to be selected when processing Audiofax fill requests. 
       
      For this part of the patch to be completely functional the latest version 
      for a refill (nothing has really changed for original fill), the patient 
      of VEXREX must be installed.  Please see PSO*7*38 for details.
       
      3) With the installation of V. 7.0 of the Outpatient Pharmacy package, the
      background utility, Expire Prescriptions [PSO EXPIRE PRESCRIPTIONS], that
      automatically expires prescriptions daily was not queued to run at many
      sites. Because this utility was not queued, prescriptions with a status
      of active were showing on the Orders tab in CPRS option and on some
      printouts when they should actually show as expired. A new option Manual
      Auto Expire Rxs [PSO MANUAL AUTO EXPIRE] is added to the Maintenance 
      (Outpatient Pharmacy) [PSO MAINTENANCE] menu option. This new option
      essentially lost that refill. In v. 7.0 this was fixed for refills, so that 
      allows sites to back expire all prescriptions from the date Outpatient
      Pharmacy package V. 7.0 was installed until the current date minus one day
      (T-1).
       
      4) When printng the Action Profile (132 COLUMN PRINTOUT) [PSO ACTION
      PROFILE], to the screen the screen pauses and breaks do not work
      correctly. This patch corrects this problem.
       
      5) When printing the Action Profile (132 COLUMN PRINTOUT) [PSO ACTION
      PROFILE] using the entry point DFN^PSOSD1 the header text states that the
      when a refill is returned to stock, the refill is deleted.  The problem is 
      profile is printing for the last 45 days when it is actually printing for
      120 days. This patch corrects the header text to 120 days which is the
      correct number of days that the profile is being printed for.
      the Controlled Substances package is not aware of the deletion.  
       
      A patch is to be released by both the Outpatient Pharmacy and Controlled 
      Substance (PSD*3*24) packages. The Outpatient Pharmacy portion of the patch 
      will send notification to the Controlled Substances package each time an 
      
    • 480 SEQ #393
      DATE APPLIED:   2017-04-03 15:46:09
      APPLIED BY:   USER,FIFTYFOUR
      DESCRIPTION:   
      There are multiple variables used for determining whether a patient will 
      be billed copay in Outpatient Pharmacy (i.e. Supply Item, Investigational 
      Drug, Nutritional Supplement, service connection, environment indicators, 
      IB billable flags, etc.).  They are used separately or in conjunction 
      with one another to determine if the prescription is billable.  For the 
      Domiciliary patients, IB has a specific check for Domiciliary and returns 
      the exempt status; however, OP did not have one of three flags defined 
      correctly to exempt prescriptions from copay.
      
    • 468 SEQ #394
      DATE APPLIED:   2017-04-03 15:57:28
      APPLIED BY:   USER,FIFTYFOUR
      DESCRIPTION:   
       The patch addresses (2) issues:
       1. Duplicate orders are erroneously allowed and duplicate warning 
          messages do not appear after patient status is updated from 
          "authorized absence" to another status.
       2. Duplicate warning messages are absent when copying an order if the 
          previous order attempt was terminated in the same session.
      
    • 465 SEQ #395
      DATE APPLIED:   2017-04-27 16:31:27
      APPLIED BY:   USER,FIFTYFOUR
      DESCRIPTION:   
      This patch will fix the following issues:
      1. The CMOP transmission stopped due to an Undefined
         error
      2. Update the Technical Manual/Security Guide for
         the HL7 record sent to the dispensing machines
      
    • 440 SEQ #396
      DATE APPLIED:   2017-04-27 17:50:13
      APPLIED BY:   USER,FIFTYFOUR
      DESCRIPTION:   
      The patch addresses three (3) issues:
              division on the retransmission from the correct division to the 
              division the user is signed on to at the time the option is run.
              This really affects integrated sites.
                            
      1) INC000000954036 - SUSPEND HOLD ISSUE
              When a Rx on suspense goes on hold, it should be restored to the 
              suspended status when unhold.
      2) INC000000736122 - RX renewal date
              Renewed script date becomes "ISSUE" date
      3) INC000001180597 - Division Change with Transmission 
              The option Unprinted/Non-Transmitted Rxs Re-Suspend, changes the 
      
    • 485 SEQ #399
      DATE APPLIED:   2017-06-01 17:40:37
      APPLIED BY:   USER,FIFTYFOUR
      DESCRIPTION:   
      This is a follow-up patch for Fixed Medication Copayment Tier (FMCT) 
      patch PSO*7*460, where the mail message, "PRESCRIPTION QUESTIONS REVIEW 
      NEEDED" was not generating.
      
    • 479 SEQ #400
      DATE APPLIED:   2017-06-29 15:19:05
      APPLIED BY:   USER,FIFTYFOUR
      DESCRIPTION:   
      This patch will fix the following issue:
      User attempts to '^' at the Device prompts, the fill is still processed
      
    • 484
      DATE APPLIED:   2017-06-29 16:13:27
      APPLIED BY:   USER,FIFTYFOUR
      DESCRIPTION:   
      This patch will fix the following issue:
      1. Drug Interaction Order Checks
      
    • 486 SEQ #403
      DATE APPLIED:   2017-08-30 15:12:26
      APPLIED BY:   USER,FIFTYFOUR
      DESCRIPTION:   
      The patch addresses two (3) issues:
         Outpatient Rx, the Rx Expiration Date is reset to an incorrect date.
         Rx #100001973 STERI-STRIPS^401962 will be discontinued after the
         acceptance of the new order.  
        
         Now doing allergy checks.  Please wait...
       
         Now processing Clinical Reminder Order Checks. Please wait ...
         Now Processing Enhanced Order Checks!  Please wait...
          
          
         Press return to continue: ^ <<< [This up (^) character causes the problem]    
       
       
         Rx # 100001977         06/26/17
         TESTATNM,CLETUS               #8
         APPLY 1 BANDAGE OVER AFFECTED AREA THREE TIMES A DAY
       
         ACER BANDAGE
         ROCHA,MARCELO            ROCHA,MARCELO
         # of Refills: 0
        
                SC Percent: 30%
      3. R15046343FY17 - A drug with same tab strength did NOT discontinue after
              Disabilities: 
       
         Was treatment for Service Connected condition? NO// 
         
         Are you sure you want to Accept this Order? NO// YES
         ...
        
      Resolution:
      --------
      Changed PSOORNEW routine to initialize the array variable PSORX("DFLG") 
         duplicate (new order) processing. This created a duplicate active order in
      right before the call to file the new order and subsequent DC of the existing
      duplicate order. This initialization will cause the code responsible for 
      discontinuing the existing order (DCORD^PSONEW2) to perform the DCing of the
      existing order without skipping it, like it was doing before this fix.
         the patient's profile.
       
      Associated NSR(s):
      =================
      N/A
       
       
      Associated CA SDM Ticket(s):
      ============================
      1. R10380204FY16 - When entering a new outpatient Rx, the Rx is Deleted on
         editing the dosage and entering an up (^) character to exit.
      2. R9361753FY16 - When editing/modifying the Issue Date or Fill Date of an
         Outpatient Rx, the Rx expires on an incorrect date.
      3. R15046343FY17 - A drug with same tab strength did NOT discontinue after
         duplicate (new order) processing.
       
      Participating Test Sites:
      1. R10380204FY16 - when entering a new Rx using the Patient Prescription 
      ========================
      OKLAHOMA CITY
      TAMPA BAY
       
      Ticket Overview:
      ===============
      1. R10380204FY16- When entering a new RX using LM BACKDOOR ORDERS, the RX
         is Deleted on editing the dosage and entering an up (^) character to 
         exit. 
       
         Processing [PSO LM BACKDOOR ORDERS], and then editing the dosage and 
      Problem:
      --------
      When user enters a new Outpatient prescription and answers "NO" to the prompt
      "Is this correct? YES//" and then user edits the dosage and enter an up (^)
      character to exit the prompt "Dosage:" and accepts Rx then new Rx will be
      deleted. 
       
      Resolution:
      --------
      Correct routine code ASK^PSOORED5 to call line tag EXE instead EX to escape 
         entering an up (^) character to exit, the Rx will be deleted as user
      killing required data before saving.
       
        
      2. R9361753FY16 - Outpatient Rx expired on an incorrect date, when Issue Date
         or Fill Date is modified.
       
      Problem:
      --------
      When editing/modifying the Issue Date or Fill Date of an Outpatient Rx using
      the backdoor pharmacy, the Rx expiration date is reset to an incorrect Date.
         accepts the Rx.
        
      Resolution:
      --------
      Corrected A^PSOEXDT to set up expiration date for prescription without
      refills not less than 30 days after issue date unless it is a Clozapine
      prescription. In addition, if the newly calculated Rx Expiration Date is
      earlier than the Rx Fill Date the Rx Expiration Date will be re-calculated
      to be the Rx Fill Date plus the Days Supply value.
       
        
       
      3. R15046343FY17 - A drug with same tab strength did NOT discontinue after
         duplicate (new order) processing. This created a duplicate active order
         in patient's profile.
        
      Problem: 
      --------
      When using the options Patient Prescription Processing [PSO LM BACKDOOR
      ORDERS] or Complete Orders from OERR [PSO LMOE FINISH] for finishing 
      pending orders there was a scenario where duplicate active orders could
      remain on the patient profile as ACTIVE. The screen capture example below
      2. R9361753FY16 - Using the Patient Prescription Processing [PSO LM BACKDOOR
      shows the prompt "Press return to continue:" where if the user entered an
      up (^) character at this prompt, the duplicate existing order would not be
      DC'd.
       
         ...
         --------------------------------------------------------------------------
         Duplicate Drug in Local Rx:
       
                          Rx: 100001973
                        Drug: ACER BANDAGE
         ORDERS] option, when users edit/modify the Issue Date or Fill Date of an
                         SIG: APPLY 1 BANDAGE OVER AFFECTED AREA THREE TIMES A DAY
                         QTY: 9                      Refills remaining: 1
                    Provider: ROCHA,MARCELO                     Issued: 06/25/17
                      Status: Active                       Last filled: 06/26/17
           Processing Status: Not released locally (Window)
                                                           Days Supply: 9
         --------------------------------------------------------------------------
       
         Discontinue RX # 100001973 STERI-STRIPS Y/N? YES  
        
      
    • 466 SEQ #404
      DATE APPLIED:   2017-08-30 17:12:30
      APPLIED BY:   USER,FIFTYFOUR
      DESCRIPTION:   
      This patch will correct the following issues: 
       
      3) The option Print from Suspense File might erroneously skip printing
         some labels for orders which previously had labels printed but were put
         back on suspense and do need new labels.
       
      1) When invoking the CK action in the Outpatient Pharmacy Medication 
         Profile screen, Non-VA and pending orders which do not contain dispense
         drugs do not receive allergy checks.
       
      2) When invoking the CK action in the Outpatient Pharmacy Medication 
         Profile screen, the business rule for performing allergy checks on
         discontinued orders is not being followed.
      
    • 473 SEQ #405
      DATE APPLIED:   2017-09-28 17:15:53
      APPLIED BY:   USER,FIFTYFOUR
      DESCRIPTION:   
      The patch addresses three (3) issues:
                         Fill Date issue 
       
       
       ROUTINE:
       =======
       Added new code to DT+1^PSON52 to check if the patient is not a clozapine 
       patient, # of Refills is zero and the Expiration Date is < Filled Date,
       then to set the expiration date.
       The Expiration Date will normally be set to (Fill Date + Day Supply). 
       However, it will be adjusted to comply with the following restrictions:
        - For controlled substances, the maximum Expiration Date allowable is 
       
          (Issue Date + 184 days)
        - For non-controlled substances, the maximum Expiration Date allowable 
          is (Issue Date + 366 days)
        - If the Expiration Date is less than the Fill Date, it will be set to 
          the same as the Fill Date
       Associated PSPO(s):
       ===================
       N/A
          
       Associated NSR(s):
       =================
       N/A 
        
       
       Participating Test Sites:
       ========================
       TBD
       
       Ticket Overview:
       ================
       1. I8924763FY16 - When a Maintenance Rx was created as the result of
          converting a Titration marked Rx instead of retaining the Expiration Date
          from the Titration Rx it was wrongly being assigned a new Expiration
          Date.
       Associated CA ticket(s):
       
       Problem:
       =======
       When using the Patient Prescription Processing [PSO LM BACKDOOR] option
       and using the hidden action Convert Titration Rx (TR) to create a new
       Maintenance dose prescription from a Titration Rx the user noticed that the
       Expiration Date associated with the new Maintenance Rx was calculated 366
       days in the future instead of being assigned the exact same Expiration Data
       from the Titration Rx.
        
       ========================
       Resolution:
       =========
       Changed the routine PSON52 responsible for creating the new Maintenance Rx
       to overwrite the calculated Expiration Date with the Expiration Date from
       the original Titration Rx.
       
       ROUTINE:
       =======
       Added code at DT+1^PSON52 to set the array variable PSOX("STOP DATE") with 
       the Titration Rx Expiration, if a Titration Rx To Maintenance Rx conversion
       1. I8924763FY16 - Expiration date changed for prescription marked as a
       is taking place.
       
       
       2. I9667491FY16 -The site would like to use the PSO BATCH BARCODE option to
          renew prescriptions. When this is attempted the renewal appears to
          succeed and there is a prompt to edit the renewal. If yes is selected the
          session will crash with an undefined variable (hard error).
       
       Problem:
       =======
                         titration script.
       When using the Barcode Batch Prescription Entry [PSO BATCH BARCODE] option
       for renewals the users received a hard error and were logged out of the
       system when they answered YES to the "Edit renewed Rx ?" prompt (before
       accepting it).
        
       Resolution:
       =========
       The root cause of this problem was due to the fact that the PSOACT variable
       that controls which action a specific user can perform on an order, based on
       the user security keys as well as whether the order was digitally signed or
       2. I9667491FY16 - Renewing a script using PSO BATCH BARCODE causes crash
       not. The routine PSOBBC was modified to initialize the PSOACT variable,
       which will prevent the hard error.
        
       ROUTINE:
       =======
       Added code at NEW+9^PSOBBC to initialized the PSOACT variable according to 
       the type of order, user's security keys and system parameters.
       
       
       3. We would like to request for assistance in the identification and 
          
          deployment of the VistA patch used at VHA station #663 (Seattle
          division) that enables pharmacy staff resolves the Fill Date issue and
          generates the error message described below
       
          "The earliest fill date allowed is determined by the Issue Date, the
          Fill Date cannot be before the Issue Date or past the Expiration
          Date. Both the month and day are required."
       
       Problem:
       =======
       3. R8247671FY16 - VistA patch used at VHA station #663 that resolves the 
       When using the speed renewal hidden action in Patient Prescription 
       Processing [PSO LM BACKDOOR] option, it was reported that when the # of 
       refills is zero, there are times the expiration date is set to a date
       earlier than the filled date.
        
       Resolution:
       ==========
       In a situation where the # of refill is zero, patient is not a clozapine 
       patient and the expiration date is < fill date, added new logic to 
       calculate the most appropriate expiration date.
      
    • 47 SEQ #41
      DATE APPLIED:   2000-08-24 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      1. It was reported that patient instruction information is appearing
      prescription is filled and the user enters "^" at the label prompt thus
      terminating the label print process. This patch resolves these issues by
      creating new activity logs in the respective prescription entry.
       
      3. With the release of PSO*7*40 an interface was added for the Controlled
      Substance package (PSD*3*24).  This interface sends notification to the
      Controlled Substance package when a fill, refill or partial is returned
      to stock.  It was discovered that the interface was done incorrectly and
      caused an undefined error.  The interface was added to the routine
      PSORESK. This patch corrects the problem.
      randomly on prescriptions that were created through the back door. This
       
      4. Selecting 'HOLD' at the label prompt for a mail prescription with a
      CMOP drug receives a reply of "HAS BEEN SUSPENDED FOR CMOP UNTIL xxxx".
      This patch ensures that the 'HOLD' process prevents the Rx going into
      CMOP.
      was found to be due to some of the variables not getting killed prior to
      using the option Patient Prescription Processing [PSO LM BACKDOOR ORDERS].
      This patch fixes this problem.
       
      2. When a prescription label is requested, and if between the time it was
      requested and the time the label actually prints it got discontinued or
      it was put on hold, the label does not get printed.  Also when a new
      
    • 488 SEQ #406
      DATE APPLIED:   2017-10-05 12:23:59
      APPLIED BY:   USER,FIFTYFOUR
      DESCRIPTION:   
      This patch will resolve the following issues.
      1.    I9899883FY16  Drug Enter/edit option issue
      2.    I6126024FY16  Patient name does not come up on the Bingo Board
      
    • 422 SEQ #407
      DATE APPLIED:   2017-10-05 12:29:01
      APPLIED BY:   USER,FIFTYFOUR
      DESCRIPTION:   
      This patch will resolve the following issues:
      1.      If patient has Other Language Preference set to Yes and medication
      instructions are entered into Other Patient Instructions, this
      information will not print on the pharmacy fill part of the label.
      2.      Duplicate Prescriptions are active on a patients profile
      3.      Pharmacy staff can process their own prescriptions
      4.      When editing the Drug on a Prescription and answering NO to Edit 
      the SIG prompt, the Dosage is not updated to match the Drug and SIG.
      
    • 442 SEQ #408
      DATE APPLIED:   2017-11-02 14:49:41
      APPLIED BY:   USER,FIFTYFOUR
      DESCRIPTION:   
       
      active  prescription containing the duplicate class drug but does not 
      discontinue the drug when "Y" is entered at the prompt.
      3.      The Outpatient Pharmacy ScripTalk label process is using %ZTIO 
      variable to write to the Prescription file's Device field. The ZTIO 
      variable is used to hold the Scrip Talk device not %ZTIO. 
       
      The patch addresses the following issues:
       
      1.      Users report that when a Window Partial is filled, the Patient 
      Notification (Rx Ready) file entry (52.11) is showing the Fill Type as 
      full instead of partial.
      2.      The PSO RX Discontinue Prescription(s) reinstate process displays 
      a Therapeutic Duplication warning message then prompts to discontinue the 
      
    • 446 SEQ #409
      DATE APPLIED:   2017-11-27 12:22:39
      APPLIED BY:   USER,FIFTYFOUR
      DESCRIPTION:   
      This patch will resolve the following issues.  
      4. When editing day supply for controlled orders calculating (PSPO 
      the prescriber would be carried over to the next pending orders for that
      same patient.
        
      Resolution: 
      -----------
      The array variable PSORX("PROVIDER NAME") that stores information about 
      the provider was not being properly initialized between the processing
      each of the patient's pending orders. The code was modified to kill the
      array variable PSORX before processing each of the patient's pending
      order.  
         #2580) supply incorrect.
       
      Technical Resolution: 
      ---------------------
      Modified the routine PSOORFIN at tags SUCC+4 and PSOORFIN+19 to kill 
      array variable PSORX("PROVIDER NAME")
       
       
      3. I9898461FY16 - Comment placed in "REMARKS" prompt is not visible if Rx 
                        is on HOLD 
       
       
      Problem: 
      --------
      Comments entered into the REMARKS field (#15) were not being displayed
      when a prescription was put on hold. Once the prescription was removed
      from hold, the remarks would become visible again.
        
      Resolution: 
      -----------
      Modified routine PSOORNE2 so the comments entered into the REMARKS field 
      (#15) display when the prescription is put on hold. 
      5. When editing the field QTY (#9) of a Pending Order the system will auto
       
      Technical Resolution: 
      ---------------------
      Modified the routine ACT+2^PSOORNE2 to set just $P(RX3,"^") instead of 
      the entire RX3 variable, as shown below:
       
      I 'RX3 S RX3=$P(RX2,"^",2),$P(^PSRX(RXN,3),"^")=$P(RX2,"^",2) 
       
       
      4. I10167818FY16 - Editing day's supply incorrect
         calculate if Schedule not marked PRN
       
      PSPO #2580 
        
      Problem: 
      --------
      For pending orders with a dispense drug where the quantity can be
      automatically calculated based on the dosage and days supply there was a
      problem for certain situations where the automatic calculation was not
      desirable. For example, the prescriber would order 10 tablets of a 
      controlled substance medication with a 30 days supply PRN (As Needed) to
       
      be taken no more than twice a day. When the Outpatient Pharmacy user
      edited the DAYS SUPPLY field (#8) for such order and changed it from 30 to
      28, as an example, the software would automatically update the quantity
      from 10 to 56, which is clearly inconsistent with the prescriber's initial
      intention.  
        
      Resolution: 
      -----------
      A new logic has been introduced related to the editing the DAYS SUPPLY 
      field (#8) of a pending order:
       
       
       1. For single dose order the software will not automatically recalculate 
          the Quantity field if the current Quantity value on the order is not
          the result of a calculation based on the current Day Supply value
          (before the edit), which suggests the Quantity was previously manually
          entered (not calculated).
       2. The software will not take into account whether the Schedule is marked
          PRN (As Needed) or not when deciding to automatically recalculate the
          QTY field (#9).
       3. For a Controlled Substance pending order the system will not 
      Associated NSR(s): 
          automatically recalculate the Quantity field (#9) if it will cause the
          current Quantity value to be increased.
       4. For a Complex Controlled Substance pending order the system will not 
          automatically recalculate the Quantity field (#9).
       5. For a pending order that qualify for a Quantity recalculation that did
          not happen because of one of the rules above (1, 3 and 4), the system
          will display the following message to the user editing the DAYS SUPPLY
          field (#8): 
          
                The QTY (99) has not been changed.  
      ==================
                Please, review and update it if necessary.  
       
      Additionally, a modification was introduced to prevent any automatic
      calculation/update of the QTY field (#9) for a new, pending or existing
      order when the user selects to specifically edit the QTY field (#9)
      itself.
       
      Technical Resolution: 
      ---------------------
      Modified routines PSODIR1, PSOSIG, PSOSIGCX and PSOSIGTX to implement the 
      N/A 
      new rules above.
        
      5. I14933412FY17 - When editing the QTY field (#9) of a Pending Order the 
                         system will auto calculate if Schedule not marked PRN
         
      Problem: 
      --------
      When using the options Patient Prescription Processing [PSO LM BACKDOOR
      ORDERS] or Complete Orders from OERR [PSO LMOE FINISH] if the user tries 
      to edit the QTY field (#9) of the pending order and if the quantity can be
       
       
      automatically calculated and the current value does not match the 
      calculated value the software will automatically replace the current value
      with the calculated value before prompting the user for the QTY field (#9)
      for the order.
       
      As seen on the example below:
        
          Pending OP Orders (ROUTINE)   Jun 06, 2017@15:13:57      Page: 2 of 3 
           TESPATNM,ROB                                          <A> 
             PID: 666-00-0258                          Ht(cm): _______ (______) 
      Patient Safety Issues (PSIs):
             DOB: JUL 21,1963 (53)                     Wt(kg): _______ (______) 
          +---------------------------------------------------------------------
             (4)   Pat Instruct:                                         
              Provider Comments:                                         
                   Instructions: TAKE ONE TABLET PO QDAY                 
                            SIG: TAKE ONE TABLET BY BY MOUTH EVERY DAY  
             (5) Patient Status: SC                                   
             (6)     Issue Date: JUN 6,2017        (7) Fill Date: JUN 6,2017 
             (8)    Days Supply: 30                (9)   QTY (TAB): 10       
               Provider ordered: days supply 30, quantity 10 & refills 0   
      =============================
            (10)   # of Refills: 0                (11)   Routing: MAIL     
            (12)         Clinic: NHCU                                      
            (13)       Provider: ROCHA,MARCELO                             
            (14)         Copies: 1                                         
            (15)        Remarks:                                           
               Entry By: ROCHA,MARCELO            Entry Date: 06/06/17 12:07:24 
          -------Digitally Signed Order---------------------------------------- 
          BY  Bypass                DC  Discontinue           FL  Flag/Unflag 
          ED  Edit                  FN  Finish 
          Select Item(s): Quit// 9     
      PSPO #2696 - When finishing pending orders from CPRS using the Complete 
        
           Quantity has been changed from 10 to 30 
        
           Press Return to Continue: 
        
           QTY ( TAB ) : 30// 
        
      Resolution: 
      -----------
      A change was introduced to the code responsible for handling the editing 
      Orders from OERR[PSO LMOE FINISH] option, if the user selects not to 
      of the QTY field (#9) of a pending order to prevent any automatic
      recalculation and update of the quantity value from happening before the
      user is prompted for the QTY prompt. Also, when entering a new order the
      software will not try to auto update the QTY value if a value already is
      defined and the user is chooses to edit the QTY field (#9).
         
      Technical Resolution: 
      ---------------------
      Modified the routine PSODIR1 at the QTY line tag that handles the QTY 
      editing logic to not call QTY^PSOSIG (responsible for recalculating the
      display the patient profile and start processing pending orders a problem 
      quantity) when a quantity already exists for the order.
      would occur for patients with orders issued by more than one single 
      provider.
       
      PSPO #2580 - For pending orders with a dispense drug where the quantity 
      1. Messages from PSO EXTERNAL DISPENSE do not specify site location 
      can be automatically calculated based on the dosage and day's supply 
      there was a problem for certain situations where the automatic calculation
      was not desirable.
       
      Test Sites: 
      ===========
      Orlando VAMC
      Erie VAMC
       
      Associated CA SDM Ticket(s):
       
      ============================
      1.I9896500FY16 - Request for site ID in subject line/PSO EXTERNAL 
                       DISPENSE Message
       
      2.I9897580FY16 - Wrong authorization provider is listed on prescription 
                       in CPRS and Outpatient Pharmacy
       
      3.I9898461FY16 - Comment placed in "REMARKS" prompt is not visible if Rx 
                       is on hold
       
      2. Wrong authorization provider is listed on prescription in (PSPO 
      4.I10167818FY16 - Editing day's supply incorrect
       
      5 I14933412FY17 - When editing the QTY field (#9) of a Pending Order the 
                        system will auto calculate if Schedule not marked PRN
       
      Defect Tracking System Ticket(s) Overview:
      ==========================================
      1. I9896500FY16 - Request for site ID in subject line/PSO EXTERNAL 
                        DISPENSE Message
        
         #2696) CPRS and Outpatient Pharmacy
      Problem: 
      --------
      When OPAI (Outpatient Pharmacy Automated Interface) tries to release a 
      prescription and it is unable to match the release information with a 
      prescription fill on file it will create a Mailman message alerting users
      about the issue. The problem for integrated sites with multiple sites 
      using OPAI is that the Mailman message does not identify which site the
      release information was for, prompting all the sites to lookup the Rx
      record to find out whether it belongs to them or not.
       
       
      Current message subject: "External Dispense - Rx Release Attempted" 
       
      Resolution: 
      -----------
      The Mailman message subject was modified to include the Site Number at the
      beginning. This will be consistent with other mailman messages that 
      already identify the Rx site in the message subject.
        
      New message subject: "500 External Dispense - Rx Release Attempted" 
        
      3. Remarks entered do not display when prescription is placed on Hold 
      Technical Resolution: 
      ---------------------
      Modify routine PSOHLDI1 at tag MAIL+13: add the following code: 
       
      S XMSUB=$S($G(PSOSITE):$$GET1^DIQ(59,PSOSITE,.06)_" ",1:"")_"External 
      Dispense - Rx Release Attempted"
       
        
      2. I9897580FY16 - The Wrong authorization provider is listed on 
                        prescription in CPRS and Outpatient Pharmacy
       
       
      PSPO #2696
       
      Problem: 
      --------
      When finishing pending orders from CPRS using the Complete Orders from 
      OERR [PSO LMOE FINISH] option, if the user selects not to display the
      patient profile and start processing pending orders a problem would occur
      for patients with orders issued by more than one single provider. If the
      user selected the Provider field (#13) and merely confirmed it,
      
    • 478
      DATE APPLIED:   2017-11-27 13:48:55
      APPLIED BY:   USER,FIFTYFOUR
      DESCRIPTION:   
      MCCF EDI TAS EPHARMACY BUILD 2
      
    • 495 SEQ #411
      DATE APPLIED:   2017-11-28 12:47:17
      APPLIED BY:   USER,FIFTYFOUR
      DESCRIPTION:   
      This patch will resolve the following issues.
       
       Defect Tracking System Ticket(s) & Overview: 
       ===========================================
       
       1. I8213786FY16 -  Using Option RESET COPAY STATUS/CANCEL displays
                          ALL copay exemption flags after edit.
       
       Problem:
       =======
       While using option RESET COPAY STATUS/CANCEL to edit copay exemption
       
       flags, when a person is automatically Exempt from Copay (such as Service
       Connected 70%) the output displays ALL copay exemption flag end states 
       rather than only those copay exemptions that have changed. 
       
       Resolution:
       ==========
       The logic that determined whether the new exemption value was different
       from the old was based off a node in the prescription file that may not 
       exist. The routine for this option now compares the user's response to
       the value stored in the prescription file to determine if the value has
       1. I8213786FY16  - Using Option RESET COPAY STATUS/CANCEL displays 
       changed.
       
       2. I15627556FY17 - HARD ERROR DURING VERIFYING A DIGITALLY SIGNED 
                          PENDING ORDER 
       
       Problem:
       =======
       When processing a digitally signed pending order, if that order is 
       auto discontinued due to an address mismatch, there is a possibility of
       getting a hard error while generating the auto discontinued mail message.
                          ALL copay exemption flags after edit.
       This can happen for a patient who has a non verified allergy and if the
       patient address was changed using the PU Patient Record Update ListMan
       action prior to processing the pending order.
       
       Resolution:
       ==========
       When the PU Patient Record Update ListMan action is used, it kills the 
       DFN variable. Modified routine PSOPKIV2 to reset variable DFN if found 
       missing and to make a call to VADPT.
       
       2. I15627556FY17 - HARD ERROR DURING VERIFYING A DIGITALLY SIGNED 
       ROUTINE:
       =======
       At line tag ADCMAIL+1, added code,
       S:'$G(DFN) DFN=PSODFN D ^VADPT,ADD^VADPT
       At line tag PADAD+1, removed the call VADPT and ADD^VADPT as it's moved
       to ADCMAIL+1
       
       3. I11377620FY17 - Controlled substance prescription hash mismatch.
       
       Problem:
                          PENDING ORDER 
       =======
       Site reports that when a controlled substance prescription hash 
       mismatch status the vista email that is generated has the incorrect 
       last four the the ssn. 
       
       Resolution:
       ==========
       When generating the auto discontinued mail message, variable VA("BID") 
       that has the last 4 of the SSN is being used, which in this case happens 
       to be from a previous patient.  
       3. I11377620FY17 - Controlled substance prescription hash mismatch. 
       Modified routine PSOPKIV2 to ensure that the variable VA("BID") is for 
       that patient by making a call to VADPT.
       
       4. I9662455FY16 - Corrupted hash mismatch has a patient's last 4 
                         of SSN incorrect.
       
       Problem:
       =======
       Site reports that a corrupted hash mismatch has a patient's last 4 
       of SSN incorrect.
       4. I9662455FY16 - Corrupted hash mismatch has a patient's last 4 
       
       Resolution:
       ==========
       When generating the auto discontinued mail message, variable VA("BID") 
       that has the last 4 of the SSN is being used, which in this case happens 
       to be from a previous patient.  
       Modified routine PSOPKIV2 to ensure that the variable VA("BID") is for
                         of SSN incorrect. 
      
    • 490 SEQ #412
      DATE APPLIED:   2017-12-01 12:45:16
      APPLIED BY:   USER,FIFTYFOUR
      DESCRIPTION:   
      This patch will fix the following issue.
        I9914094FY16  OTH, PRO, OP screen flashes by within seconds
      
    • 462 SEQ #413
      DATE APPLIED:   2017-12-27 14:42:29
      APPLIED BY:   USER,FIFTYFOUR
      DESCRIPTION:   
      ===========
      The patch addresses (2) issues:
      1. Other than CMOP prescription not printed when used manual mail-out CM
      2. Controlled substance auto-discontinued when signed and released days 
         are different.
      
    • 467 SEQ #414
      DATE APPLIED:   2017-12-27 16:22:09
      APPLIED BY:   USER,FIFTYFOUR
      DESCRIPTION:   
      Inbound electronic prescribing enhancements.
      
    • 501 SEQ #415
      DATE APPLIED:   2018-01-03 13:39:07
      APPLIED BY:   USER,FIFTYFOUR
      DESCRIPTION:   
      This patch will resolve the following issues.
       
       1. Speed refill message displays too quickly to be read. 
       2. Pharmacist Enter/Edit option display issue.
      
    • 5
      DATE APPLIED:   1999-04-16 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
       
      changed to delete the entry when an up-arrow is entered at the prompt.
      The software will now display a message indicating that the "Bingo
      record is incomplete!" and "Bingo record removed. Routine: PSOBING1
       
      3. Fixed error reported by Puget Sound in NOIS PUG-0198-51767. An undefined
      error occurred when editing a prescription that created a new
      prescription, and there were no numbers left in the numbering sequence
      for prescriptions. Errors could also occur if a site was manually
      assigning the prescription numbers, and nothing was entered at the
      "Select New Rx #" prompt when creating a new prescription due to an Edit.
      1. Made change to Allergy/Adverse Reaction display on labels and screen
      Routines: PSONRXN, PSOORED1
       
      4. Fixed an error reported by San Francisco, NOIS SFC-0298-60681. The
      error occurred in the daily cost compilation background job. 
      When the patient is accessed during the compilation routine, an error could
      occur if that patient has both Outpatient and Inpatient orders to be
      backfilled. After the backfilling, upon returning to the cost compilation
      routine, an undefined error could occur. Routine: PSOHLUP
       
       
      profiles. The software was referencing an incorrect piece of data, which
      caused us to possibly display an Allergy under the Adverse Reaction heading,
      when it really should be displayed under the Allergy heading.
      Routines: PSODEM, PSOLBLN1, PSOLBLS, PSOORUT3
       
      2. Fix a problem reported in NOIS SFC-0298-60679. Entering an up-arrow (^)
      at the Ticket # prompt could cause an undefined error.  The software was
      
    • 48 SEQ #42
      DATE APPLIED:   2000-09-05 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      1) When the Print a PMI Sheet [PSNPMIS PRINT] option is selected
      Prescription Processing [PSO LM BACKDOOR ORDERS] option, it was erring out
      due to an 'Undefined PSOID' error. This patch carries a fix for this
      problem.
       
      3) The INACTIVATION DATE field (#7) of DRUG INTERACTION file (#56) is
      being populated by Pharmacy Data Management module, Enter/Edit Local Drug
      Interaction [PSS INTERACTION LOCAL ADD] option, to inactivate a
      particular set of drugs that was once set up as interactive. During the
      order entry process when using Patient Prescription Processing [PSO LM
      BACKDOOR ORDERS] option, currently the drug-drug interaction by routine
      immediately after using the Patient Prescription Processing
      PSODGDGI does not check for this inactivation date. This patch ensures
      that the inactivation date is now being checked.
      [PSO LM BACKDOOR ORDERS] option, the patient medication sheet that is
      printed for a particular drug also has the name of the patient that was
      previously accessed under the Patient Prescription Processing [PSO LM
      BACKDOOR ORDERS] option. This patch fixes this problem.
       
      2) While selecting a certain patient related title during the progress
      notes entry when placing a medication order using the Patient
      
    • 498 SEQ #416
      DATE APPLIED:   2018-01-03 17:30:37
      APPLIED BY:   USER,FIFTYFOUR
      DESCRIPTION:   
      This patch will fix the following issue.
      1.      I9914421FY16  all prescription information is not displayed
              on the Pharmacy verification screen
      
    • 506 SEQ #417
      DATE APPLIED:   2018-01-30 14:47:52
      APPLIED BY:   USER,FIFTYFOUR
      DESCRIPTION:   
      Emergency patch to resolve hard error during drug validation.
      
    • 497 SEQ #418
      DATE APPLIED:   2018-01-30 15:34:58
      APPLIED BY:   USER,FIFTYFOUR
    • 499 SEQ #419
      DATE APPLIED:   2018-02-27 14:06:51
      APPLIED BY:   USER,FIFTYFOUR
      DESCRIPTION:   
      This patch will resolve the following issues.
       
      1.      I12011023FY17 - One-VA partial functionality does not restrict
                              quantity
      2.      I12010975FY17 - One-VA displaying inconsistent information
                              in VistA options
      3.      I12150112FY17 - OneVA Pharmacy Selection of Drugs by the
                              Dispensing Site
      
    • 509 SEQ #420
      DATE APPLIED:   2018-02-28 16:51:58
      APPLIED BY:   USER,FIFTYFOUR
      DESCRIPTION:   
      This patch will resolve the following issues.
       
      1. I17894075FY18 - Pharmacist not showing up for renewal in 
                         View Prescription; typo in HELP-PROMPT
       
      2. I18165455FY18 - OneVA issue for Refill and Partial
      
    • 496 SEQ #421
      DATE APPLIED:   2018-03-01 15:09:36
      APPLIED BY:   USER,FIFTYFOUR
      DESCRIPTION:   
      This patch will resolve the following issues.
       
      Information Processing Standard (FIPS) code for Canada is "CA", however the
      SPMP standard requires "CN" for Canada. 
        
      Resolution:
      -----------
      Changed the retrieval of the patient's state and postal code fields to
      first check for the country. For foreign countries (non-US) it will
      retrieve the Province and Postal Codes values returned in the VAPA(23)
      and VAPA(24) return array from the ADD^VADPT API. Also changed it to send
      "CN" for PAT22 (Country of Non-US Resident) for Canada.
      Associated NSR(s)
         
      Technical Resolution:
      ---------------------
      Modified the routines PSOASAP and PSOASAP0 to check whether the country is
      non-US (foreign). If so, it will use the value in VAPA(24) and VAPA(23) for
      the fields PAT15 and PAT16 respectively. Also, changed the line tag PAT22 
      on the PSOASAP0 routine to return "CN" instead of "CA" for Canada.
      =================
       N/A 
       
      Test Sites:
      ==========
       
      Associated CA SDM Ticket(s):
      ============================
       
      1. I10127879FY16 - It is possible to suspend a script past the expiration
                         date. 
      2. I16514233FY17 - Vista transmits two instances of the same prescription
                         to the external interface. 
         R14795402FY17(d) - Vista is sending over prescription data twice for 
                            SOME prescriptions, resulting in duplicates showing
                            up in ScriptPro
      3. I11517650FY17 - Need assistance with SPMP Patient Address errors 
       
        
      1. It is possible to suspend a script past the expiration date.
      Defect Tracking System Ticket(s) & Overview:
      ============================================
      1. I10127879FY16 - It is possible to suspend a script past the expiration
                         date.  
      Problem:
      --------
      Currently in Outpatient Pharmacy the users are able to enter a REFILL DATE 
      that is past the Rx EXPIRATION DATE. The software should not allow a refill
      date that is past the expiration date because it is an invalid date and the
      prescription will be expired before it can be dispensed.
       
       
      Resolution:
      -----------
      The Data Dictionary for the PRESCRIPTION file (#52) was modified to include 
      restrictions on the following fields: FILL DATE (#22) and REFILL DATE (#.01)
      in the REFILL sub-file (#52.1). The restrictions will require that the value
      entered for either one of these two fields cannot be before the Rx ISSUE
      DATE or after the Rx EXPIRATION DATE.
       
      Technical Resolution:
      2. Vista transmits two instances of the same prescription to the external
      ---------------------
      Created new INPUT TRANSFORM code (FLDTINTR^PSOUTLA(Fill_Type)) and new 
      EXECUTABLE HELP code (FLDTHELP^PSOUTLA(Fill_Type)) and modified the fields
      mentioned above to replace the current M code with calls to these two new
      entry points in the PSOUTLA routine.
       
      Files & Fields Associated:
      ------------------------- 
      File Name (#)      Field Name (#)                         New/Modified/Deleted
      -----------------  -------------------------------------- --------------------
         interface. 
      PRESCRIPTION(#52)  FILL DATE (#22)                        Modified 
                         REFILL (#52.1)
                         -REFILL DATE (#.01)                    Modified
        
       
      2. I16514233FY17 - Vista transmits two instances of the same prescription
                         to the external interface. 
         R14795402FY17(d) - Vista is sending over prescription data twice for SOME
                            prescriptions, resulting in duplicates showing up in
                            ScriptPro
          
        
      Problem: 
      --------
      There is at least one scenario in Outpatient Pharmacy that will cause a 
      prescription fill to be sent twice to the external interface. This happens
      because sometimes when the user pulls a CMOP prescription from suspense to 
      print locally it will be sent to the print queue twice and consequently it
      was also being sent to the external interface twice.
        
      Resolution:
      3.  Need assistance with SPMP Patient Address errors  
      -----------
      Added a check in the routine that handles the pull from suspense to prevent
      it from adding a prescription to the print queue if the prescription is
      already on the queue.
        
      Technical Resolution:
      ---------------------
      Modified the routine PSOSUPOE to prevent it from setting the variable PPL
      with the same prescription twice.
       
       
       
      3. I11517650FY17 - Need assistance with SPMP Patient Address errors    
       
      Problem: 
      --------
      The State Prescription Monitoring Program (SPMP) module did not retrieve the
      correct State/Province (SPMP field PAT15 - State Address) and Postal Code 
      (SPMP field PAT16 - ZIP Code Address) for patients that have a foreign
      address on file. The software was retrieving the US state and Zip Code 
      fields, which were both blank for such patients. In addition, the Federal
      
    • 402
      DATE APPLIED:   2018-03-02 14:08:20
      APPLIED BY:   USER,FIFTYFOUR
      DESCRIPTION:   
      Mocha 2.1, dosing only scope.
      
    • 500
      DATE APPLIED:   2018-03-02 14:10:34
      APPLIED BY:   USER,FIFTYFOUR
      DESCRIPTION:   
      THIS IS A FOLLOW UP PATCH.
       
      This patch incorporates routine changes introduced into PSOORED5 in 
      PSO*7.0*486 and merges them with routine changes in PSO*7.0*402.
       
      Refer to the install guide for installation instructions.
      
    • 515 SEQ #424
      DATE APPLIED:   2018-03-02 15:20:42
      APPLIED BY:   USER,FIFTYFOUR
      DESCRIPTION:   
      This patch will correct 2 hard errors that are present in PSO*7.0*500, 
      The functions where the errors occur are:
      - Editing the Schedule while finishing a Pending order from CPRS
      - Editing a Schedule of an existing prescription
      - Editing a Schedule while Verifying a Non-verified Prescription using 
        either the ListMan verification action or the  'Rx Verification by 
        Clerk' option
      - Editing a Schedule while using the 'Process Order Checks' option
       
      This patch will also correct an issue presented with the release version 
      of PSO*7.0*500 where multiple word schedule expansions are not echoed to 
      which is part of the MOCHA 2.1B COMBINED BUILD and is due for national 
      the screen.  This defect does not affect the patient sig section were 
      multiple word schedules continue to be expanded appropriately, only the 
      immediate echo response functionality at the time of entry.
      release.
       
      The following two errors have been addressed in this patch:
       
      <UNDEFINED>SCH+3^PSOORED3 *SCHEX
      <UNDEFINED>SCH+3^PSOORED4 *SCHEX
       
      
    • 504 SEQ #425
      DATE APPLIED:   2018-04-03 17:40:03
      APPLIED BY:   USER,FIFTYFOUR
      DESCRIPTION:   
      This patch will resolve the following issues:
      4. I17185111FY18 - Error when changing routing from Window to Mail
       
      1. I15848129FY17 - Buprenorphine/naloxone prescription went through when
                         the DEA expiration date was in the past 
       
      2. R16854127FY18 - FILL DATE prompt range incorrect
       
      3. I5855290FY15  - CK Hidden Option and Remote Order Checks
          
      
    • 44 SEQ #43
      DATE APPLIED:   2000-09-05 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      1) When using the Detailed Allergy/ADR List action under the Patient
      of the patient who was last accessed prior to this patient using the
      option Complete Orders from OERR [PSO LMOE FINISH]. This could result in
      dispensing the wrong drug to the patient. This problem was found to be
      due to some of the variables not being cleaned up properly. This patch
      ensures that all such variables are killed appropriately.
      NOISs SLC-0200-50488, NJH-0600-21694 and PRO-0700-10326
       
      3) When a new prescription was created using the option Patient
      Prescription Processing [PSO LM BACKDOOR ORDERS], it was reported that the
      patient instruction was appearing randomly. This was the patient
      Prescription Processing [PSO LM BACKDOOR ORDERS] option, there is a
      instruction of the patient who was last accessed prior to this patient
      using the option Complete Orders from OERR [PSO LMOE FINISH]. This again
      was due to some of the variables not being killed properly. This patch
      ensures that all such variables are killed. NOISs MAR-0500-21140 and
      BIL-0700-31212
      possibility of getting a <STRLEN> (string too long) error when displaying
      the comments from the Adverse Reaction Tracking package. This patch fixes
      this problem.
       
      2) If the option Edit Prescriptions [PSO RXEDIT] is used to edit the SIG,
      this function generates a new order. It was reported that the new order
      created had changed the dispensed drug totally. It had picked up the drug
      
    • 513
      DATE APPLIED:   2018-04-03 17:43:42
      APPLIED BY:   USER,FIFTYFOUR
    • 502 SEQ #427
      DATE APPLIED:   2018-04-24 16:16:10
      APPLIED BY:   USER,FIFTYFOUR
    • 519 SEQ #428
      DATE APPLIED:   2018-04-25 17:29:34
      APPLIED BY:   USER,FIFTYFOUR
      DESCRIPTION:   
      This patch will resolve the following issues.
       
      1. I18715588FY18 - Undefined error when ^ out of prompt
      2. INC0023405 - Set prompt default to NO instead of YES
      
    • 520 SEQ #430
      DATE APPLIED:   2018-05-01 14:43:33
      APPLIED BY:   USER,FIFTYFOUR
    • 463 SEQ #431
      DATE APPLIED:   2018-06-01 16:19:58
      APPLIED BY:   USER,FIFTYFOUR
      DESCRIPTION:   
      IMPORTANT INSTALLATION NOTE:
      -----------
      RESET COPAY STATUS LM     ROUTINE       NEW
        
      Protocols Associated:
       
      Protocol Name                   New/Modified/Deleted    Action
      -------------                   --------------------    ------
      PSO PATIENT MED ACC PRO         NEW
      PSO PATIENT MED BILL PRO        NEW
      PSO PATIENT MED CANCEL          NEW
      PSO PATIENT MED EXPORT          NEW
      The Chief Business Office (CBO) is requesting system enhancements to
      PSO PATIENT MED PAT INQ         NEW
      PSO PATIENT MED RESET           NEW
      PSO PATIENT MED TPJI            NEW
      PSO PATIENT MEDICATION MENU     MODIFIED
       
      Templates Associated:
       
      Template Name                 Type   File Name (Number)      
      New/Mod/Del-------------                 ----   ------------------      
      -----------
      The Veterans Health Information Systems and Technology Architecture
      PSO PATIENT MEDICATION LIST   LIST   N/A                     NEW
       
      New Service Requests (NSRs):----------------------------
      20150505 - Revenue Reporting Enhancements
      20150506 - Revenue Eligibility Enhancements
      20150507 - Revenue Operations Enhancements
       
       
      Patient Safety Issues (PSIs):
      ------------------------------N/A
      (VistA) Integrated Billing (IB), Accounts Receivable (AR), and
       
       
      Remedy Ticket(s) & Overviews:
      -----------------------------
      N/A
       
      Test Sites:----------
      Durham VAMC
       
       
      Outpatient Pharmacy (PSO) software modules.
      Software and Documentation Retrieval Instructions:
      ----------------------------------------------------
      Patches for this installation are combined in host file
      IB_2_568_PRCA_PSO_BUNDLE_T1.KID
       
      Installation of this host file should be coordinated among the packages
      affected since only one installation is necessary.
       
      The patches are:
       
       
           IB*2.0*568
           PRCA*4.5*315
           PSO*7.0*463
       
       Software and Documentation Retrieval Instructions
      -------------------------------------------------
      Software being released as a host file and/or documentation describingthe 
      new functionality introduced by these patches are available.
       The preferred method is to retrieve files from 
      download.vista.domain.ext.
      The mission of the Department of Veterans Affairs (VA), Office of
      This transmits the files from the first available server. Sites may 
      also elect to retrieve files directly from a specific server. 
      
      Sites may retrieve the software and/or documentation directly using 
      Secure File Transfer Protocol (SFTP) from the ANONYMOUS.SOFTWARE 
      directory at the following OI Field Offices:
       
      OI FIELD OFFICE FTP ADDRESS DIRECTORY 
      --------------- -------------------- ------------------ 
      Albany: fo-albany.domain.ext  anonymous.software
      Information & Technology (OI&T), is to provide benefits and services to
      Hines: fo-hines.domain.ext  anonymous.software 
      Salt Lake City: fo-slc.domain.ext anonymous.software
       The host file is located in the anonymous.software directory.
       Use ASCII Mode when downloading the file.
       
      Documentation can also be found on the VA Software Documentation Library 
      at: http://www4.domain.ext/vdl/
       
      --------------------------------------------------------------------------
      Title File Name FTP    Mode
      veterans of the United States Armed Forces. In meeting these goals,
      -------------------------------------------------------------------------
      Outpatient Pharmacy Technical
       Manual/Security Guide pso_7_ TM_R0417.PDF binary
      Outpatient Pharmacy  
      Back-out, and Rollback Guide 
       FY16RevenuePSOVIP_Deployment_Installation_Guide
        binary
       
       Sites may retrieve documentation directly using Secure File 
      TransferProtocol (SFTP) from the ANONYMOUS.SOFTWARE directory at the 
      OIT strives to provide high quality, effective, and efficient
      following
      OI Field Offices:
       
      Albany:          fo-albany.domain.ext
      Hines:           fo-hines.domain.ext
      Salt Lake City:  fo-slc.domain.ext
       
      Documentation can also be found on the VA Software Documentation Library
      at:
      http://www4.domain.ext/vdl/
      ----------------------------
      Information Technology (IT) services to those responsible for providing
       
      Title                                             File Name  FTP Mode
      ---------------------------------------------------------------------
      Outpatient Pharmacy Technical Manual/Security 
      Guide                                                  pso_7_tm.doc Binary
      Outpatient Pharmacy Deployment, Installation,
           Back-Out, and Rollback Guide
                    FY16RevenuePSOVIP_Deployment_Installation_Guide.doc
                                                                     Binary
       
      care to the veterans at the point-of-care, as well as throughout all
       
       
      Patch Installation:
       
      Pre/Post Installation Overview:
      -------------------------------
      N/A
       
      Pre-Installation Instructions:
      ------------------------------
      the points of the veterans' health care. The VA depends on 
      N/A
       
      Installation Instructions:
      --------------------------
      This process will install new and updated routines and other
      components listed above. There is a post-install routine that will add
      entries to a number of files.
       
      The patch will be released in conjunction with Integrated Billing
      patch, IB*4.5*568, and Accounts Receivable, PRCA*4.5*315.
      InformationManagement/Information Technology (IM/IT) systems to meet 
       
        ************************ NOTE ************************
        IF A USER IS ON THE SYSTEM AND USING THESE PROGRAMS
        AN EDITED ERROR WILL OCCUR.
        The patch should be installed when NO Outpatient
        Pharmacy users are on the system.
        ******************************************************
       
       Installation will take less than 1 minute.
       
      mission
       Suggested time to install: non-peak requirement hours.
       
       
        1. Obtain the host file IB_2_568_PRCA_PSO_BUNDLE.KIDS which contains
           the following patches:
               IB*4.5*568
               PRCA*4.5*315
               PSO*7.0*463
       
        2. Startup KIDS
      goals.
           -------------     Start up the Kernel Installation and Distribution 
      System Menu option
           [XPD MAIN]:
        
               Edits and Distribution ...
               Utilities ...
               Installation ...
        
           Select Kernel Installation & Distribution System Option: 
      INStallation                                                              
       
      ---
               Load a Distribution
               Print Transport Global
               Compare Transport Global to Current System
               Verify Checksums in Transport Global
               Install Package(s)
               Restart Install of Package(s)
               Unload a Distribution
               Backup a Transport Global
        
      The overall FY16 HAPE Revenue Enhancement project has been further
           Select Installation Option: 
       
        3. LOAD TRANSPORT GLOBAL FOR MULTI-BUILD IB_2_568_PRCA_PSO_BUNDLE.KID
           -------------------------------------------------------------
           From the Installation menu, select the Load a Distribution option.
        
           When prompted for "Enter a Host File:", enter the full directory path
           where you saved the host file IB_2_568_PRCA_PSO_BUNDLE.KID (e.g.,
           SYS$SYSDEVICE:[ANONYMOUS] IB_2_568_PRCA_PSO_BUNDLE.KID).
        
      divided into three sub-projects:
           When prompted for "OK to continue with Load? NO//", enter "YES."  
           The following will display:
       
           Loading Distribution...
        
               IB*2.0*568
               PRCA*4.5*315
               PSO*7.0*463
        
               Use INSTALL NAME: IB*2.0*568to install this
       
               IB_2_568_PRCA_PSO_BUNDLE.KID distribution. 
       
        4. From this menu, you may select to use the following options
           (when prompted for INSTALL NAME, enter IB*2.0*568):
               a.  Verify Checksums in Transport Global - This option will
                   allow you to ensure the integrity of the routines that
                   are in the transport global.
               b.  Print Transport Global - This option will allow you to
                   view the components of the KIDS build.
               c.  Compare Transport Global to Current System - This 
      This patch is part of a multi-package build. There are three patches
      NSR #20150506
      option             will allow you to view all changes that will be made 
      when
                   this patch is installed.  It compares all components of
                   this patch (routines, DD's, templates, etc.).
               d.  Backup a Transport Global - This option will create a
                   backup message of any routines exported with this patch.
                   It will not backup any other changes such as DD's or
                   templates.
       
        5. When prompted "Want KIDS to INHIBIT LOGONs during the install?
      The Revenue Eligibility Enhancements Project effort for the Chief
           NO//" respond NO.
       
        6. When prompted "Want to DISABLE Scheduled Options, Menu Options,
           and Protocols? NO//" respond NO.
       
       
       
      Post-Installation Instructions:
      -------------------------------
      There are no special tasks to perform after this patch installation.
      Business Office (CBO), bundles several NSRs with similar business
      needs into a single requirements document.  Successfully addressing
      the requirements contained within this document will enable the
      Department of Veterans Affairs (VA) to appropriately bill certain
      subsets of billable events by correcting, automating, or enhancing
      current Veterans Health Information Systems and Technology
      Architecture (VistA) systems.
       
      associated with the FY16 HAPE Revenue Enhancement project - IB*2.0*568,
      NSR #20150507
      The Revenue Operations Enhancements Project combines several NSRs, as
      well. This effort enables the Department of Veterans Affairs (VA) to
      improve revenue operation functionality related to repayment plans,
      late charge capture, bill suspension reasons, the billing of
      deactivated providers, and the display of appeal rights and
      responsibilities on the Veterans Beneficiary travel Bill of 
      Collectionsform.  Implementation of the proposed enhancements will make a
      significant positive impact on stakeholders and target users.
       
      PRCA*4.5*315 and PSO*7.0*463. All three patches are to be installed
      NSR #20150505
      The Revenue Reporting Enhancements Project will enable the VA to
      improve tracking and reporting of revenue, and will support 
      revenuereporting business rules and guidelines.
       
       
      PSO*7.0*463 patch enhancements, pertinent to the above NSRs, include:
       
      1.) In the event of a Prescription Reset Status/Cancel Charges action,
      all automatic prepayment generation shall be
      together as a bundle, IB_2_568_PRCA_PSO_BUNDLE_T1.KID
      eliminated.
       
      2.) All "credit balances" that are automatically generated in the event
      of a Prescription Reset Status/Cancel Charges action exemption to stop.
       
      3.) A new on-demand List Manager report will be made available for
      identification of Prescription resets.
       4.) The new on-demand report for processing Prescription Resets 
      willprovide an option to generate a Summary Report and/or Detailed Report.
       
       
       
       
      Associated Patches:
      -------------------
      IB*2.0*568
      PRCA*4.5*315
       
      Concurrent Development / Dependencies:
      --------------------------------------
      N/A
       
       
      Category
      --------
      Routine
      Template
      Other
       
       
      Patch Components:
      ----------------- 
      Description
      Files & Fields Associated:
       
      File Name (Number)    Field Name (Number)     New/Modified/Deleted
      ------------------    -------------------     --------------------
      N/A
       
      Options Associated:
       
      Option Name                     Type          New/Modified/Deleted
      -----------                     ----          --------------------PSOCP 
      
    • 518
      DATE APPLIED:   2018-07-06 15:43:55
      APPLIED BY:   USER,FIFTYFOUR
    • 526 SEQ #433
      DATE APPLIED:   2018-08-03 15:13:37
      APPLIED BY:   USER,FIFTYFOUR
      DESCRIPTION:   
      This patch will resolve the following issues.
       
      INC0105896 - <SYNTAX> error
      INC0320678 - <UNDEFINED> Error
      
    • 505 SEQ #434
      DATE APPLIED:   2018-09-04 15:34:23
      APPLIED BY:   USER,FIFTYFOUR
      DESCRIPTION:   
      Medication Prescribing and Dispensing Updates.
      
    • 482
      DATE APPLIED:   2018-09-07 12:24:14
      APPLIED BY:   USER,FIFTYFOUR
      DESCRIPTION:   
      MCCF EDI TAS EPHARMACY BUILDS 3 & 4
      
    • 527 SEQ #436
      DATE APPLIED:   2018-09-07 12:25:18
      APPLIED BY:   USER,FIFTYFOUR
    • 45
      DATE APPLIED:   2000-09-05 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      PSO*7*45 provides an API for the Clinical Reminders package.  The API
      provides patient and prescription information, based on a specified date
      range and a specified list of medications, as it relates to the Hepatitis
      C Initiative. This patch will not affect users of the Outpatient Pharmacy
      package. The PSOORAPI routine in patch PSO*7*45 provides an entry point
      that returns patient and prescription information in a ^TMP global to the
      Clinical Reminders package, based on the criteria passed into the call. 
      
    • 314
      DATE APPLIED:   2018-09-25 15:39:30
      APPLIED BY:   USER,FIFTYFOUR
      DESCRIPTION:   
      *************
        At the bottom of the report there is a section that displays other 
      outpatient prescriptions dispensed in the previous year.  The combination 
      of long drug names and the status "DISCONTINUED/EDIT" would cause the 
      report to lose data at the right margin when printed.  This patch 
      reformats lines in the affected section to maintain spacing within the 
      printed margins.
       
      Tool #1 - Medication Reconciliation
        Inpatient orders that do not have additional order text (such as large 
      volume IVs) are inadvertently skipping the BCMA LAST ACTION line.  This 
      THIS ENTIRE PATCH DESCRIPTION NEEDS TO BE REVISED.  RMS 3-12-12
      patch will include that line more consistently on all inpatient orders.
       
      Tool #1 - Medication Reconciliation
        The display of previously expired and discontinued orders at the bottom 
      of the report was selecting the LAST RELEASED DATE based on the 
      prescription that had the latest expiration date.  This patch corrects 
      that selection to display the proper release date that is most recent for 
      a given medication.
       
      Tool #1 - Medication Reconciliation
      *************
        The listing of medications entered as "clinic medications" through the 
      Inpatient Medications for Outpatient (IMO) process was incorrectly labeled
      as an INP (Inpatient) Medication.  This patch will display that category 
      of medications as CLN, identified in the legend as Clinic Medications.
       
      Tool #1 - Medication Reconciliation and Tool #4 - Remote Active Medications
        The statuses of remote outpatient medications shown in the Medication 
      Reconciliation profile and the Remote Active Medications health summary 
      component will now include "HOLD" medications.
       
       
      Tool #2 - Medication Worksheet
        The hard-coded display of a the patient's last four digits of the SSN in
      the body of the work sheet is removed. The release of health summary patch
      GMTS*2.7*85 now permits the removal of the patient SSN from the health
      summary overall header, but this change permits the worksheet to be
      printed with no SSN references remaining.
       
      Tool #2 - Medication Worksheet
        The internal programming that selects the name of the pharmacy
      division shown at the top of the worksheet and the pharmacy phone
      This patch corrects issues that have been reported with Medication 
      number associated with it has been revised. The impact of this correction
      will be seen mostly at legacy integrated systems.
       
      Also included in this patch is the removal of routine PSOQUAP.  This
      routine was orphaned during the final testing of patch PSO*7*294.  Its
      functionality is fully incorporated into routine PSOQUAP2 which is
      referenced in the implementation guide.
      Reconciliation Tool #1 (Medication Reconciliation Health Summary) and 
      Medication Reconciliation Tool #2 (Medication Worksheet).
       
      Tool #1 - Medication Reconciliation
      
    • 514 SEQ #438
      DATE APPLIED:   2018-10-04 16:20:20
      APPLIED BY:   USER,FIFTYFOUR
      DESCRIPTION:   
      This patch will resolve the following issues.
       
      1. I9914421FY16 - all prescription information is not displayed on the
                        Pharmacy verification screen
      2. R18151128FY18 - QTY Recalculation when Drug Changed
      
    • 534 SEQ #439
      DATE APPLIED:   2018-10-04 17:25:53
      APPLIED BY:   USER,FIFTYFOUR
      DESCRIPTION:   
      One VA Pharmacy, redirect HL7 link PSORRXSEND from EMI to VIERS.
      
    • 539 SEQ #440
      DATE APPLIED:   2018-11-02 14:52:03
      APPLIED BY:   USER,FIFTYFOUR
      DESCRIPTION:   
      This patch will resolve the following issue:
      INC0998874 - LON Cannot Print to suspense/ clear old records from RX suspense
      (Duplicate)  file death causing suspense print to error out.
      INC0785349 - suspense function in Vista is not working 
      (Duplicate) 
      INC0411672 - PSO OPTION NOT WORKING
      (Duplicate) 
      INC0301071 - TUA - prescriptions not printing
      (Duplicate) 
      INC0190642 - CA SDM Ticket I18597371FY18 moved to SN. UNABLE TO RUN FULL LIST
      (Duplicate)  SUSPENSE FUNCTION
       
              
      Problem: 
      --------
      The Marion VA Medical Center reported getting an <UNDEFINED> error when trying
      to print local labels in the RX SUSPENSE file (#52.5). Upon further analysis
      it was determined that a bad "AC" cross-reference entry in the RX SUSPENSE
      file (#52.5) is causing the problem. Although the cross-reference is set, the
      record it is pointing to is no longer present on the file which consequently
      causes the routine PSOSULBL to error out with an <UNDEFINED> error at BEG+6.
              
      INC1866048 - Suspense not printing, previously entered ticket INC1658361 which
      Resolution:
      -----------
      The reason why the "AC" cross-reference entry was not deleted along with the
      original record could not be identified. However, this patch modifies the
      routine PSOSULBL to prevent the <UNDEFINED> error from happening when the
      corrupted "AC" cross-reference is present. Furthermore, the PSOSULBL routine
      was also modified to clean up the corrupt "AC" cross-reference.
        
      Technical Resolution:
      ---------------------
                   was closed without assistance
      Changed the routine PSOSULBL at line tag BEG and TMP to prevent the
      <UNDEFINED> error and to kill off the corrupt "AC" cross-reference entry.
            
      Defect Tracking System Ticket(s) & Overview:
      --------------------------------------------
      INC1866048 - Suspense not printing, previously entered ticket INC1658361 which
                   was closed without assistance
      
    • 540 SEQ #441
      DATE APPLIED:   2018-11-02 14:52:41
      APPLIED BY:   USER,FIFTYFOUR
      DESCRIPTION:   
      This patch will fix the following issue:
      1.      Able to DC non-verified Rx order when another user is editing
      it in CPRS
      
    • 507 SEQ #442
      DATE APPLIED:   2018-11-02 15:30:23
      APPLIED BY:   USER,FIFTYFOUR
      DESCRIPTION:   
      This patch has the following enhancements for Clinical Ancillary Services
         editing the Listman screen field "3)  *Schedule:".  Upon typing a ?
         at that prompt and selecting "A" for Administration Schedule File, the
         entries displayed will now include the Inactive text.
       
       
      2. Manage Hidden Icons (Actions)  Outpatient
       
         Two new hidden actions are provided for Outpatient Pharmacy's menu 
         option Patient Prescription Processing [PSO LM BACKDOOR ORDERS].
       
      (CAS) Enhancements (RXSU2).
         a. New hidden action "DM" for displaying dispense drug information 
            during data entry.  This hidden action will display key information
            about the order to help aid in the verification process of an order
            and also allow user to Enter another drug if desired.  Key
            information includes:
       
            Example:
       
                 DRUG NAME:  xxxxxxxxxxxxxxxxxxx   (IEN: 3)
                   ORDERABLE ITEM TEXT:
       
                    xxx xx xxxxx xxxxx xx xxxxx
                    x xxxxxxxx xx xxxxxxxxxxxx
       
                 MESSAGE:   xxxx xxx xx xxxxx x xxxxxxxx
                 QTY DISP MESSAGE:   x xxxxxxxx xx xxxxxxxxx xxxx
        
                 Return to continue or
                 Select DRUG GENERIC NAME:
       
         b. New hidden action "VP" for displaying Provider information during 
       
            data entry.  This hidden action will display key information about
            the PROVIDER to help aid in the verification process of an order and
            also allow user to enter another provider if desired.  Key 
            information includes:
       
            Example:
       
                 PROVIDER TITLE:     xxxxxxxx
       
                 PROVIDER REMARKS:   xxx xxxxx xxxx
      1. Manage Lookup List Inactive Entries 
       
                 PROVIDER SPECIALTY: xxxxxx
       
                 Return to continue or
                 Select NEW PERSON NAME: 
       
       
      3. Suppress Duplicate - Therapy Alerts
       
         Duplicate Therapy order check is suppressed in CPRS if the same
       
         provider is ordering the same drug within the last 25% of the
         medications' calculated days supply.  All 3 above criteria must be
         met for this order check to be suppressed.
         Modified Pharmacy Backdoor menu option Patient Prescription Processing 
         [PSO LM BACKDOOR ORDERS]. Added the text "** INACTIVE **" to the end 
         the display of the ADMINISTRATION SCHEDULE file (#51.1) entries during
      
    • 517 SEQ #443
      DATE APPLIED:   2018-12-06 16:06:31
      APPLIED BY:   USER,FIFTYFOUR
      DESCRIPTION:   
      MPDU - MEDICATION PERMISSIONS/DISPENSING UPDATES - Build 3
          order items are not able to be marked for titrate.
      4.  Outpatient Medication Controlled Substance order edit, unnecessary 
          code removed.
      5.  Manilla Phillippines unique address is stopping controlled substance
          orders from finishing.
      6.  Undefined Error at ACP+21^PSOORNEW
      7.  Patient address, risk of carryover information between patients in 
          VAPA array.
      8.  Allow "# of refills" entry to be edited on Controlled Substance orders
       
      This patch will address the following issues:
       
      1.  The PHARMACY PATIENT file (#55) should have only one logical data 
          piece corresponding to RX PATIENT STATUS on the "PS" node.
      2.  Display in the Patient's Medication Profile there is a leading zero 
          in the quantity if it is a fractional quantity.
      3.  An intermittent issue was found that some Non-Controlled Substance 
      
    • 508 SEQ #444
      DATE APPLIED:   2018-12-06 16:12:01
      APPLIED BY:   USER,FIFTYFOUR
      DESCRIPTION:   
      Inbound eRx Version 3 updates.
      
    • 452
      DATE APPLIED:   2018-12-06 16:17:04
      APPLIED BY:   USER,FIFTYFOUR
      DESCRIPTION:   
      Patch PSO*7*452 is part of a Multi Build with patch PSS*1.0*215.
      PSO*7.0*452 contains the routine changes.
      PSS*1.0*215 contains the DD changes.
       
      The NSRs involved in this build are:
      NSR20150311 High Cost Rx Report;  NSR20151109 Pharmacy Print from Suspense
      by Category; NSR20150512 Early Warning Advisory for Approaching the 
      end of Rx Number Ranges; and NSR20151001 Pharmacy Patient Demographics.
      
    • 525 SEQ #446
      DATE APPLIED:   2018-12-06 16:19:59
      APPLIED BY:   USER,FIFTYFOUR
      DESCRIPTION:   
      As part of the Clinical Ancillary Services project (CAS) - Medication 
      --------
      As a pharmacist using the List of Patients/Prescriptions for Recall 
      Notice Report, I need the system to correctly identify the Lot # of each 
      individual prescription fill (original or refill and locally dispensed or 
      CMOP) so that all prescriptions fills with that Lot # are accurately 
      reported.
       
      1. I want the report to pull the Lot # that corresponds to the 
         individual fill represented by a line of data (original or refill or 
         partial).
      Permission/Dispensing Updates (MPDU), the Outpatient package has been
      2. I want the report to pull the Lot # that corresponds to the 
         manner in which the prescription was dispensed (VAMC-local or CMOP
         fill).
      3. I want the structure and header of the report to remain unchanged.
       
       
      Resolution:
      -----------
      Line tag LOT^PSORLST2 has been modified to also check the CMOP node 
      for a CMOP fill (original or refill) and include it in the report.
      modified to address the following:
       
       
      Item #2:
      --------
      As a pharmacist entering an outpatient prescription through VistA, I want 
      only medication routes that are appropriate for use with the medication I 
      select displayed so that I am prevented from selecting the incorrect 
      route subsequently increasing patient safety.
       
      1. When entering an outpatient prescription into VistA, I only want 
       
         medication routes associated with the medication dosage form for the 
         medication selected displayed as available for selection. 
      2. If I enter a medication route that is not associated with the 
         medication's dosage form, I want the route entered matched to the 
         available routes as an exact full-text match.
         a. If I enter a route that is only a partial match, I want the 
            standard FileMan response of "??" to alert me that a match was not
            found.
         b. If I enter a complete and exact-match route, I want that route 
            selected for use with that medication order.
      1. Modify the List of Patients/Prescriptions for Recall Notice Report
       
       
      Resolution:
      -----------
      Routines PSOORED5 and PSOBKDED were modified with the following:
      1. If a default med route is not defined, "PO" will not be displayed; a
         null value will be displayed as default.
      2. Med routes that are exact matches or abbreviated matches will be 
         allowed.
      3. A single "?" will show a short list of med routes that are defined
      2. Limit the Display of Medication Routes for Outpatient Order Dialogs
         under the orderable item.
      4. Partial matches will be allowed if found in the short list, but not
         otherwise.
      3. Check dosage form to determine appropriate default route
       
      Item #1:
      
    • 49 SEQ #45
      DATE APPLIED:   2000-10-04 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      1) When using the call DFN^PSOSD1 provided by DBIA #1281, an undefined
      checks for the inactivation date before building the drug-drug
      interactions.
       
      3) The following NOISs, CON-0300-11493, DUB-0400-31698, and NCH-0800-41306
      reported a problem when editing prescriptions in a certain sequence was
      being saved with the name of the patient from a previously edited
      prescription. This error did not occur every time a prescription was
      edited, but after using certain options and actions together where
      variables were not being cleaned up appropriately. With the release of
      PSO*7*36 and PSO*7*37 to the field the name-changing problem has no longer
      variable error was reported (HD+11^PSOSD1:1, %DSM-E-UNDEF, undefined
      been reported. In an effort to try an identify any possible prescriptions
      where the patient name may have been changed inappropriately a new option,
      Search For Mismatched Patient Orders [PSO RX SEARCH] will be sent out in
      this patch. This new option will search the PRESCRIPTION file (#52) and
      produce a report with any possible problem prescriptions. This new option
      will not be attached to any menu, but can be assigned to anyone Pharmacy
      and IRM deems appropriate.
      variable PSOBAR4). This patch fixes this problem.
       
      2) The INACTIVATION DATE field (#7) of DRUG INTERACTION file (#56) is
      being populated by Pharmacy Data Management module, Enter/Edit Local Drug
      Interaction [PSS INTERACTION LOCAL ADD] option, to inactivate a
      particular set of drugs that was once set up as interactive. This patch
      ensures that the call to the routine EN^PSOORDRG provided by DBIA #2190,
      
    • 550 SEQ #447
      DATE APPLIED:   2019-01-31 16:43:11
      APPLIED BY:   USER,FIFTYFOUR
      DESCRIPTION:   
      Restoration of changes introduced in patch PSO*7*504. The changes made to 
      PSORENW and PSORENW4 were inadvertently left out of patch PSO*7*508.
      
    • 512
      DATE APPLIED:   2019-02-01 14:38:00
      APPLIED BY:   USER,FIFTYFOUR
      DESCRIPTION:   
      MCCF EDI TAS EPHARMACY BUILDS 5 & 6
      
    • 547 SEQ #449
      DATE APPLIED:   2019-02-01 15:22:20
      APPLIED BY:   USER,FIFTYFOUR
      DESCRIPTION:   
      This patch will resolve the following issue.
      INC2842893 - Removed from CMOP Suspense, returned to OP Suspense - outpatient
                   prescriptions not suspending to CMOP after PSO*7*482 SEQ #435
                
      Problem: 
      --------
      Outpatient pharmacists at Louis Stokes Cleveland VA Medical Center reported a
      glitch where a suspended Rx is edited and re-suspended appropriately but they
      are not being sent to CMOP. This problem happens when a new CMOP prescription
      is entered/finished and immediately after (without leaving the patient's
      profile) the user requests a partial fill on the same prescription and
        
      performs and edit on any field (e.g., QTY, FILL DATE, DAYS SUPPLY, etc.).
      These steps wrongly caused the prescription to be removed from the CMOP
      Suspense queue and placed on the Local Suspense queue.
       
      Resolution:
      -----------
      Outpatient Pharmacy will now check whether a partial was entered for a CMOP
      suspended prescription and it will not move it from the CMOP Suspense queue
      into the Local Suspense queue if that's the case.
         
      INC2842893 - Removed from CMOP Suspense, returned to OP Suspense - outpatient
      Technical Resolution:
      ---------------------
      Changed the line UNSUS+1^PSOCMOPC to check whether a partial was placed by
      checking the variable RXPR and PSOFROM and it will not move the CMOP
      Suspended prescription into the Local Suspense queue.
       
      INC2882730 - Erroneous SC conditions are being displayed during pharmacy
                   prescription processing
                
      Problem: 
                   prescriptions not suspending to CMOP after PSO*7*482 SEQ #435
      --------
      Outpatient pharmacists at St. Cloud VA Health Care System reported a glitch
      that started happening after patch PSO*7*514 was installed. They noticed that
      numerous male patients were showing up in outpatient pharmacy prescription
      processing as having SC conditions for ovarian disease or gynecological
      issues. When checking back to the patient information screen in VISTA
      pharmacy prescription processing or CPRS, the pharmacists discovered in many
      cases the patient was only SC for tinnitus, yet a big list of other 
      disabilities were listed at the very end of pharmacy prescription processing
      when it lists the patient's SC conditions, often with the gynecological 
      INC2882730 - Erroneous SC conditions are being displayed during pharmacy
      condition. After investigating the issue it was discovered PSO*7*514 changes
      did not clear the list of disabilities from the previous patient worked on
      by the user and carried them over to the subsequent patient worked on the
      same session before exiting the Patient Prescription Processing [PSO LM 
      BACKDOOR ORDERS] option.
       
      Resolution:
      -----------
      The Patient Prescription Processing [PSO LM BACKDOOR ORDERS] option was 
      changed to properly reset the list of disabilities every time the user 
                   prescription processing
      selects a new patient.
          
      Technical Resolution:
      ---------------------
      Added the command K PSODISAR at CHKPAG+1^PSOMLLD2 in order to reset the
      list of disabilities before retrieving it from the PATIENT file (#2).
       
      Defect Tracking System Ticket(s) & Overview:
      --------------------------------------------
      
    • 537 SEQ #450
      DATE APPLIED:   2019-02-01 16:00:46
      APPLIED BY:   USER,FIFTYFOUR
      DESCRIPTION:   
      When users are entering a new complex order using option PSO LM BACKDOOR 
      ORDERS and afterwards are editing the dosage fields and they jump out of
      certain fields, the medication's SIG is truncated after the first THEN
      conjunction of the medication profile.
      
    • 532 SEQ #451
      DATE APPLIED:   2019-03-01 14:01:20
      APPLIED BY:   USER,FIFTYFOUR
      DESCRIPTION:   
      This patch will resolve the following issues:
      1.  INC0698370 - OneVA Can't see patient's remote RX's
      2.  INC0908814 - Last Fill Date shows incorrect MAIL/WINDOW value
      3.  INC1033035 - Documentation changes needed
      
    • 481 SEQ #452
      DATE APPLIED:   2019-03-01 15:50:20
      APPLIED BY:   USER,FIFTYFOUR
      DESCRIPTION:   
      This patch will upload "new" providers for a site into the New Person 
      The law creates a new paradigm for providing health care, set forth in the
      Veterans Choice program provisions within Title I Section 101 of VACAA. VA
      is utilizing a Contractor to provide health care and third party
      administrative (TPA) services set forth through VACAA Section 101. 
       
      As a result of this law, VA must upload a list of non-VA medical care
      providers into the VistA system in order to maintain an accurate and
      updated list of non-VA providers in the Choice program.  Refer to the
      Non-VA Care Provider SharePoint site for further information:
      https://vaww.dwh.cdw.portal.domain.ext/sites/Non-VA%20Care%20PC3%20and%20Choic
      (#200) file.  A "new" provider is defined as a provider whose National 
      e/SitePages/Home.aspx.
       
      CA-SDM Ticket: I12935021FY17
       
      NOTE: The providers loaded by this patch are not eligible to be selected 
      as ordering providers in CPRS. Use is restricted to the option "PSO LM 
      BACKDOOR ORDERS" ("Patient Prescription Processing").
      Provider Identifier (NPI) is not on file yet at a site.
       
      On August 7, 2014, the President signed into law PL 113-146, the Veterans 
      Access, Choice, and Accountability Act of 2014 (VACAA). The law offers an 
      additional authority for VHA to expand current capacity and ensure that 
      Veterans have timely access to high-quality care. 
       
      
    • 541 SEQ #454
      DATE APPLIED:   2019-04-02 17:21:27
      APPLIED BY:   USER,FIFTYFOUR
      DESCRIPTION:   
      This patch will address the following two issues:
      Defect Tracking System Ticket(s) & Overview:
      --------------------------------------------
       
      1. INC2091135 - Incorrect drug on label for OneVA refill request
       
      Problem: 
      --------
      A pharmacist refilled a OneVA Rx and verified the correct local drug 
      matched to the remote site drug. 
      The labels printed with a different drug that was on the patient's 
       
      profile. This happened with 5 prescriptions. Some did print correct. 
      Partials were done and some came through in the same erroneous way.
       
      Resolution:
      -----------
      Resolve this with the following:
      - A 3 second hang will be added prior to reading the HL7 response
      with the label information from the Host site
      - Once the HL7 message is read, the Rx number selected at the
      Remote site will be compared to the Rx number returned in the HL7 label
      1. Incorrect drug on label for OneVA refill request
      message from the Host site and if this is a match, processing will
      continue as normal
      - If the two Rx's do not match, the message below will be displayed
      and processing will cease 
         'Label interrupted due to HL7 message corruption.'
         'Please request a Partial Fill in order to generate a reprint label.'
      - In the background, invisible to the user, an error trap entry
      will be made so more research can be done to find the root cause of this
      happening.  The error in the error trap will show as 'MISMATCH RX'
      Modify the following routines: PSORRX2, PSORWRAP 
      2. OneVA prescription error
       
      2. INC2394703 - OneVA prescription error
                 
      Problem: 
      --------
      The Saginaw VA Medical Center reported that a OneVA prescription fill
      request appears to have prompted ScripTalk label to print at host site. The
      Host site requeued Vista label and it appears prescription was filled twice.
       
      Resolution:
       
      -----------
      The OneVA Pharmacy functionality did not prevent a ScripTalk label from
      printing at the host site when a refill/partial was requested by the patient
      at a remote site. A fix is being introduced by this patch to prevent the
      ScripTalk label from printing at the host site when a OneVA prescription
      refill/partial is requested is filed.
          
      Technical Resolution:
      ---------------------
      Changed the routine PSORWRAP to set the variable PSOONEVA before calling the
      Patient Safety Issues (PSIs):
      label printing routines (DQ^PSOLBL) and then changed the routine PSOTALK to
      QUIT if the label being printed is a OneVA Pharmacy label at the remote site.
      -----------------------------
      HITPS-6386 - INC2091135
       
      
    • 555 SEQ #455
      DATE APPLIED:   2019-05-01 14:57:10
      APPLIED BY:   USER,FIFTYFOUR
      DESCRIPTION:   
      This patch addresses one (1) VistA Outpatient Pharmacy issue:
       
      The installment of patch PSO*7*537 introduced an error that occurs 
      after a user edits a dosage.
      
    • 538 SEQ #456
      DATE APPLIED:   2019-05-01 14:57:55
      APPLIED BY:   USER,FIFTYFOUR
      DESCRIPTION:   
      CORRECT INAPPROPRIATE DATE ENTRY IN COPY FUNCTION
      
    • 551 SEQ #457
      DATE APPLIED:   2019-06-04 17:54:27
      APPLIED BY:   USER,FIFTYFOUR
      DESCRIPTION:   
      INBOUND ERX MAINTENANCE PATCH 1
      
    • 41 SEQ #46
      DATE APPLIED:   2000-10-27 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      The Outpatient Pharmacy package utilizes a field in the NOUN (#50.6066)
      Subfile of the DOSAGE FORM (#50.606) File called NOUN. It is used to
      build Possible Sigs for Outpatient orders entered through Computerized
      Patient Record System (CPRS). The use of that field will be expanded upon
      in the Pharmacy Ordering Enhancements project. The changes in this patch
      will not affect any of the current Outpatient Pharmacy functionality, but
      this patch will be a requirement of the Pharmacy Ordering Enhancements
      project.
      
    • 556 SEQ #458
      DATE APPLIED:   2019-06-04 17:59:30
      APPLIED BY:   USER,FIFTYFOUR
    • 543 SEQ #459
      DATE APPLIED:   2019-06-04 18:03:00
      APPLIED BY:   USER,FIFTYFOUR
      DESCRIPTION:   
      The description of this build can be found in the National Patch Module 
      under PSO*7*543.
      
    • 548 SEQ #461
      DATE APPLIED:   2019-07-22 16:40:13
      APPLIED BY:   USER,SIXTYFIVE
      DESCRIPTION:   
      When finishing a non-controlled drug order immediately after finishing a
      renewal of a controlled drug, an incorrect expiration date occurs. The
      non-controlled drugs are finished with the expiration date of the
      controlled drug.
      
    • 558 SEQ #462
      DATE APPLIED:   2019-07-22 16:46:44
      APPLIED BY:   USER,SIXTYFIVE
      DESCRIPTION:   
      This patch will fix an issue where NON-VA medications are being returned 
      in the VPR XML results when they are dated outside of the entered date 
      range for resulting.
      
    • 559 SEQ #464
      DATE APPLIED:   2019-07-22 17:16:44
      APPLIED BY:   USER,SIXTYFIVE
      DESCRIPTION:   
      This patch will address the following two issues:
      --------
      Ann Arbor VAMC reported about 5 or 6 entries in their error trap related to
      OneVA Pharmacy functionality. After some research it was determined that the
      error was happening because OneVA Pharmacy HL7 messages were being sent to
      the Ann Arbor VAMC erroneously. The prescription number in the HL7 message
      request did not exist in the Ann Arbor site as it was probably supposed to
      be sent to a different site. That was what caused the hard error reported.
      At this point it is not clear why HL7 messages have been routed the wrong
      site.
        
       
      Resolution:
      -----------
      The processing of incoming HL7 messages for OneVA Pharmacy fill requests
      is being changed to check whether the prescription in the request actually
      belongs to the site it arrived. If the prescription does not exist at the
      site the message below will be displayed to the dispensing site user that
      is requesting the OneVA fill:
       
        Processing refill request. Please be patient as it may take a moment
        for the host site to respond and generate your label data...
      1. $ZE= <UNDEFINED>PROCESS+24^PSORWRAP *MW
       
        Unable to complete transaction. 
       
        The Rx #999999 does not belong to this facility (REMOTE SITE NAME). Please,
        try to place the fill request again. It may take up to 4 attempts to get a
        successful response. If the issue continues, please contact IT Support for
        assistance.
        
        Press RETURN to continue: 
           
         
      Technical Resolution:
      ---------------------
      Changed the routine PSORWRAP at REMOTE+21 to verify that the prescription 
      number in the incoming OneVA HL7 message actually belongs to the site
      receiving the message. If it does not, stop processing and respond back to
      the sending site with the message above. 
      Defect Tracking System Ticket(s) & Overview:
      --------------------------------------------
      1. INC5310207 - $ZE= <UNDEFINED>PROCESS+24^PSORWRAP *MW
       
      Problem: 
      
    • 528
      DATE APPLIED:   2019-08-01 08:49:34
      APPLIED BY:   PATCH,USER
    • 565 SEQ #466
      DATE APPLIED:   2019-08-15 16:12:42
      APPLIED BY:   USER,SIXTYFIVE
      DESCRIPTION:   
      This patch will address the following two issues:
      1. INC6047771    - ERX not including info after patch PSO*7*551
         (d)INC6131517 - Recommendations for improvements to new eRx system
         (d)INC6087293 - Inbound eRx prescriptions not showing quantity, days
                         supply and refills under the
       
      Problem: 
      --------
      VA Sierra Nevada Health Care System reported that after the installation of 
      the patch PSO*7*551 they noticed that some fields related to the eRx 
      prescription (Qty, Days Supply and Refills) were no longer being displayed
       
      when viewing the corresponding VistA Pending Order or Active Prescription. 
      It was confirmed that this issue was indeed caused by the patch PSO*7*551.
         
      Resolution:
      -----------
      This patch will restore the functionality accidently removed by the patch
      PSO*7*551 by restoring the display of the fields Qty, Days Supply and 
      Refills from the original external prescription (eRx).
            
      Technical Resolution:
      INC6047771    - ERX not including info after patch PSO*7*551
      ---------------------
      Changed the routine PSOERXU1 at line tag DERX1+95 to re-include the line 
      below that was removed by PSO*7*551:
       
         S IEN=IEN+1,@GL@(IEN,0)=LINETXT
      (d)INC6131517 - Recommendations for improvements to new eRx system
      (d)INC6087293 - Inbound eRx prescriptions not showing quantity, days supply
                      and refills under the
          
      Defect Tracking System Ticket(s) & Overview:
      --------------------------------------------
      
    • 567 SEQ #468
      DATE APPLIED:   2019-09-04 10:06:25
      APPLIED BY:   USER,SIXTYFIVE
      DESCRIPTION:   
      The description of this build can be found in the National Patch Module 
      under PSO*7*567.
      
    • 564 SEQ #469
      DATE APPLIED:   2019-09-05 16:46:06
      APPLIED BY:   USER,SIXTYFIVE
      DESCRIPTION:   
      The description of this build can be found in the National Patch Module 
      under PSO*7*564.
      
    • 457
      DATE APPLIED:   2019-09-30 10:36:46
      APPLIED BY:   USER,SIXTYFIVE
      DESCRIPTION:   
      MENTAL HEALTH NCC PROJECT 5.01
      
    • 50 SEQ #47
      DATE APPLIED:   2000-11-06 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      The following NOISs, NJH-0600-21694, SLC-0200-50488, PRO-0700-10326 
       In an effort to try and identify any possible prescriptions where the drug 
       name may have been changed inappropriately, a new option Search for 
       Mismatched Drug Orders [PSO RX DRUG SEARCH] will be sent out in this patch.  
       This new option will search the PRESCRIPTION file (#52) and produce a 
       report with any possible problem prescriptions. This new option will not 
       be attached to any menu, but can be assigned to anyone Pharmacy and 
       Information Resources Management (IRM) deems appropriate.   
       reported the following problem.  When editing prescriptions in a certain 
       sequence they were being saved with the name of the patient from a 
       previously edited prescription. This error did not occur every time 
       a prescription was edited, but after using certain options and 
       actions together where variables were not being cleaned up appropriately.  
       With the release of PSO*7*44 to the field, the drug name-changing problem 
       has no longer been reported.  
       
      
    • 569 SEQ #470
      DATE APPLIED:   2019-10-03 15:49:30
      APPLIED BY:   USER,SIXTYFIVE
      DESCRIPTION:   
      The description of this build can be found in the National Patch Module 
      under PSO*7*569.
      
    • 568 SEQ #471
      DATE APPLIED:   2019-10-24 12:11:27
      APPLIED BY:   USER,SIXTYFIVE
      DESCRIPTION:   
      When entering a duplicate prescription, if the original prescription was
      sent to CMOP, rejected and filled locally, then the discontinue message
      will report that the original prescription was not filled.
      
    • 557 SEQ #472
      DATE APPLIED:   2019-10-24 12:13:03
      APPLIED BY:   USER,SIXTYFIVE
      DESCRIPTION:   
      When choosing a primary sort of PATIENT or ROUTE and secondary sort of 
      FLAGGED, the no orders are displayed. Also, when changing orderable item 
      on a prescription, if the units are omitted from the dose, the DISPENSE 
      UNITS PER DOSE field in computed incorrectly.
      
    • 573 SEQ #473
      DATE APPLIED:   2019-12-06 14:54:03
      APPLIED BY:   USER,SIXTYFIVE
      DESCRIPTION:   
      DUPLICATE RX CREATED IN PSO LM BACKDOOR ORDERS
      
    • 572 SEQ #474
      DATE APPLIED:   2019-12-06 15:50:33
      APPLIED BY:   USER,SIXTYFIVE
      DESCRIPTION:   
      HPS patch to address overwritten error messages and deleted providers in
      PSO LM BACKDOOR, and an index error in PSO COPAY RESET.
      
    • 582 SEQ #475
      DATE APPLIED:   2019-12-09 16:40:56
      APPLIED BY:   USER,SIXTYFIVE
      DESCRIPTION:   
      This patch will address the following issue: 
      (d)INC7720939 - Inbound eRx 2 prescriptions with fatal errors
      (d)INC7774257 - Inbound eRx - Fatal Errors
      (d)INC7793995 - Inbound eRx fatal error on one prescription in Corpus Christi
                      Outpatient Clinic Pharmacy
       
      Patient Safety Issues (PSIs):
      -----------------------------
      N/A
       
           
        
      Defect Tracking System Ticket(s) & Overview: 
      --------------------------------------------
      INC7463016 - Septra SS prescription - Inbound eRx (CORPUS CHRISTI) received
                   an Rx and an error message was generated
      (d)INC7463169 - Ammonium Lactate prescription - Inbound eRx (CORPUS CHRISTI)
                      received an Rx and an error message was generated Detailed
                      Description 
      (d)INC7216102 - Inbound eRx (CORPUS CHRISTI) received an Rx and an error
                      message was generated
      (d)INC7720939 - Inbound eRx 2 prescriptions with fatal errors
      INC7463016 - Septra SS prescription - Inbound eRx (CORPUS CHRISTI) received
      (d)INC7774257 - Inbound eRx - Fatal Errors
      (d)INC7793995 - Inbound eRx fatal error on one prescription in Corpus Christi
                      Outpatient Clinic Pharmacy
       
      Problem: 
      --------
      Corpus Christi VA Specialty Outpatient Clinic reported a fatal error 
      (<SUBSCRIPT> error) when trying to validate the Drug/SIG for an eRx record
      when using the Complete Orders from eRx [PSO ERX FINISH] option. The same
      error was reported by McAllen Outpatient Clinic. The error happens due to a
                   an Rx and an error message was generated
      missing "B" cross-reference entry in the PHARMACY PATIENT file (#55) for the
      patient being processed. It is unknown the reason why the "B" cross-reference
      entry is missing for certain patients.
         
      Resolution: 
      -----------
      This patch will prevent the error from happening for patients that have the
      "B" cross-reference entry missing by ignoring it. The missing "B" cross-
      reference entry will have no negative impact in the processing of eRx 
      prescriptions for such patient because its use in the code was unnecessary
      (d)INC7463169 - Ammonium Lactate prescription - Inbound eRx (CORPUS CHRISTI)
      for the option to work properly.
             
      Technical Resolution: 
      ---------------------
      Modified the line tag DU+1^PSOERXD1 to instead of using the "B" cross-
      reference to retrieve the patient IEN (Internal Entry Number) and set the 
      PSODFN variable to set the variable PSODFN directly with the PATIEN content.
                      received an Rx and an error message was generated Detailed
                      Description 
      (d)INC7216102 - Inbound eRx (CORPUS CHRISTI) received an Rx and an error
                      message was generated
      
    • 531 SEQ #476
      DATE APPLIED:   2019-12-19 14:39:43
      APPLIED BY:   USER,SIXTYFIVE
      DESCRIPTION:   
      This patch will fix the following issue:
       
      The incorrect fill is marked as dispensed and released if two fills for
      one prescription is sent to the dispensing machine.
      
    • 570 SEQ #477
      DATE APPLIED:   2020-02-20 14:14:56
      APPLIED BY:   USER,SIXTYFIVE
      DESCRIPTION:   
      The description of this build can be found in the National Patch Module 
      under PSO*7*570.
      
    • 583 SEQ #478
      DATE APPLIED:   2020-02-28 13:02:35
      APPLIED BY:   USER,SIXTYFIVE
      DESCRIPTION:   
      This patch will address the following issue: 
      Defect Tracking System Ticket(s) & Overview: 
      --------------------------------------------
      INC6715041 - software problem - instructions (#TABS PER DOSE) got altered on
                   prescriptions with renewals. RX 4879200 -TO RX 487920A,B,C
       
      Problem: 
      --------
      The CPRS patch OR*3*440 was released Back in 2017 to address a problem with
      the Ward Clerk Menu [OR MAIN MENU WARD CLERK] option that was causing some
      Outpatient Pharmacy orders and prescriptions to have the wrong dispense units.
        
      Although the patch seems to have resolved the problem by preventing new orders
      with this issue from being created it did not go far enough to prevent that
      existing orders with the issue could be copied or renewed and pass the problem
      forward the problem to newly created orders.
       
      Resolution: 
      -----------
      The patch will generate a list (see example below) of potential outpatient
      prescriptions and will send it via Mailman message to all users that hold the
      PSNMGR security key. These entries on this list should be analyzed one by one
      INC6715041 - software problem -- instructions (#TABS PER DOSE) got altered on
      by the Pharmacy ADPAC and a determination should be made as to whether the
      outpatient prescription dose and dispense units are correct for the dispense
      drug or not. If it is determined that the prescription dose and dispense unit
      are incorrect the Outpatient Pharmacy staff should discontinue the prescription
      and re-renter it with the correct dosing and dispense unit information.   
       
      List example:
      ---------------------------------------------------------------------------
      PATIENT (L4SSN)
        RX #         DISPENSE DRUG                DOSE ORD.     UNITS    STRENGTH
                   prescriptions with renewals. RX 4879200 -TO RX 487920A,B,C
      ---------------------------------------------------------------------------
      Division: CHEYENNE VAM&ROC 
      PSOPATIENT,ONE (3202)
        2298748      ACETAMINOPHEN 325MG TAB         325          1         999
      PSOPATIENT,THREE (7894)
        2298875      ACETAMINOPHEN 325MG TAB         325          1         999
       
      Division: GREELEY CLINIC 
      PSOPATIENT,TWO (1234)
        2298877      ACETAMINOPHEN 325MG TAB         325          1         999
        
       
      3 prescriptions found.       
       
      Technical Resolution: 
      ---------------------
      Created post-install routine PSO583PI loop through the PRESCRIPTION file (#52)
      and check the dose for current prescriptions and the dispense unit and
      strength of the dispense drug. If a discrepancy is found a prescription is
      included on the Mailman message sent to the PSSMGR security key holders.
      Patient Safety Issues (PSIs):
      -----------------------------
      HITPS-6775
            
      
    • 591 SEQ #480
      DATE APPLIED:   2020-03-11 11:25:37
      APPLIED BY:   USER,SIXTYFIVE
      DESCRIPTION:   
      This patch will address the following eRx issues: 
       
         list of status screened out for "Refill Response" type records, which will
         drop the erroneously RRP records from the Work Queue as soon as the patch
         is installed.
      2) Changed the routine PSOERX1B at line tag ADD+64 and the routine at line tag
         AUTODC+38 to only update the record status to RRP if the record type is a
         "Refill Request". This will prevent "Refill Response" records from being 
         wrongly updated to RRP.
      Patient Safety Issues (PSIs):
      -----------------------------
      N/A 
           
      Defect Tracking System Ticket(s) & Overview: 
      --------------------------------------------
      1. INC7957997 - Grammar error in eRx processing screen
       
      Problem: 
        
      --------
      Alaska VA Healthcare System reported a grammar issue while accepting an eRx
      prescription into VistA via the Complete Orders from eRx [PSO ERX FINISH]
      option. After validating a patient via this option the software checks whether
      the same patient has other eRx prescriptions waiting to be validated and if
      any additional are found it will issue the following message/prompt (example):
       
         This patient has other prescriptions for: Dec 04, 2019
         Patient: XXXXXX,XXXXXXX
       
      1. INC7957997 - Grammar error in eRx processing screen
             DRUG                      PROVIDER                      REC DATE
         --------------------------------------------------------------------------
         1.) GABAPENTIN 300 MG ORAL CAPSUSMITH,KATELON               JAN 04, 2020
         2.) METOPROLOL SUCCINATE ER 100 SMITH,KATELON               JAN 04, 2020
         
         Would you like apply the above validation to these prescriptions?
         Enter Yes or No: N//
        
      The issue is with "...like apply..." which should read "...like to apply..."
       
       
      Resolution: 
      -----------
      Inserted "to" between "like" and "apply".
             
      Technical Resolution: 
      ---------------------
      Changed the routine PSOERX1B at line tag BPROC+41 to include "to" between
      "like" and "apply".
         
       
      2. INC6442610    - inbound eRx issue - order stuck in queue
      2. INC6442610    - inbound eRx issue - order stuck in queue
         INC6659074(d) - Wrong erx status code generated in VistA inbound erx
                         software version 3.0
         INC6245922(d) - eRX issue with acknowledging messages in RRD status that
                         change to RRP status for 1 patient
       
      Problem: 
      --------
      VA Puget Sound Health Care System reported that Refill Response eRx records
      with a status of RRP (REFILL REQUEST PROCESSED) are accumulating on their eRx
         INC6659074(d) - Wrong erx status code generated in VistA inbound erx
      Work Queue and the users do not have a mechanism to remove them. This problem
      interferes with their work because these types of records fills up pages and
      of their Work Queue and there is no further processing needed to be performed
      on them. Upon extensive research it was determined that RXA (REFILL RESPONSE
      ACKNOWLEDGED) Refill Request records were erroneously being updated to RRP
      once a new prescription was accepted via eRx for the same medication that was
      previously designed. To illustrate a little further the sequence of events
      happened the following way:
       
        1) Patient had eRx 'A' that had already been previously filled and did not
                         software version 3.0
           have any more refills left. 
        2) The VA Pharmacist uses the RR (eRx Refill Request) through the Patient
           Prescription Processing [PSO LM BACKDOOR ORDERS] option and a message is
           sent out to the Dr's Office. 
        3) The Dr's Office denies the Refill/Renewal by sending a new eRx record to
           VistA which create a Refill Request records with a status of RXD (REFILL
           RESPONSE DENIED/DNTF).
        4) The VA Pharmacist then acknowledges the RXD record through the Complete
           Orders from eRx [PSO ERX FINISH] option, which changes the status of the
           Refill Response from RXD to RXA successfully removing it from the eRx
         INC6245922(d) - eRX issue with acknowledging messages in RRD status that
           Work Queue.
        5) Later, the Dr's Office sends to VistA a new prescription for the patient 
           with the same medication
        6) The VA Pharmacist processes the new eRx prescription and Accepts it. 
           This action creates the problem because it mistakenly changes the status
           of the previously updated Refill Response from RXA to RRP, bringing it
           back to the eRx Work Queue which does not offer any means for the users
           to remove such records from the Work Queue.
       
      Resolution: 
                         change to RRP status for 1 patient
      -----------
      This patch will stop the status update from RXA to RRP described in the step
      #6 above. Furthermore, it will remove all RRP records from the eRx Work Queue.
      The RRP records will still be visible if users intentionally are looking for
      them through the SR (Search Queue) action, which is how the Work Queue was
      designed to work originally.
            
      Technical Resolution: 
      ---------------------
      1) Changed the routine PSOERX at line tag BLDITEM+22 to include "RRP" in the 
      
    • 53 SEQ #48
      DATE APPLIED:   2000-11-27 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      1.  Pharmacy Benefits Management (PBM) has requested that Technical
      the ordering processes by entry of the IEN.
      Services develop a software patch that would disable the DRUG file (#50)
      lookup by Internal Entry Number (IEN) during order entry
      processes.  The pharmacy software has always allowed IEN lookup and quick
      code lookups at the request of field users.  A quick code is a
      user-defined synonym for a drug (i.e., A325->Acetaminophen 325mg Tab).  PBM
      provided guidance to VA Medical Centers in the past to not use low numbers
      for quick codes and to inactivate the first 50 entries in the drug file to
      reduce the chances of error.  This patch would eliminate drug selection in
      
    • 586 SEQ #481
      DATE APPLIED:   2020-03-11 11:28:52
      APPLIED BY:   USER,SIXTYFIVE
      DESCRIPTION:   
      INC8357891 - Inbound eRX drug incorrectly filtered.
      The detailed description of this build can be found in the National Patch 
      Module under PSO*7*586.
      
    • 595 SEQ #482
      DATE APPLIED:   2020-03-24 16:57:57
      APPLIED BY:   USER,SEVENTY
      DESCRIPTION:   
      CPRS patch OR*3*397 allowed a user with ORSUPPLY key to release supply 
      item orders. In backdoor pharmacy, when finishing a pending renewal 
      supply item order that was released by ORSUPPLY/ORELSE key holders (not 
      authorized to write med orders), a hard error is generated. This issue is 
      addressed in this patch. Jazz #1203196
      
    • 587 SEQ #484
      DATE APPLIED:   2020-03-25 10:37:11
      APPLIED BY:   USER,SEVENTY
      DESCRIPTION:   
      IDENTIFY USER EDITING NEW PROVIDER
      
    • 593 SEQ #483
      DATE APPLIED:   2020-03-25 12:00:02
      APPLIED BY:   USER,SEVENTY
      DESCRIPTION:   
      INC9101449 - Errors encountered when running List of Override 
      Prescriptions Report
      
    • 574
      DATE APPLIED:   2020-04-10 15:41:18
      APPLIED BY:   USER,SEVENTY
      DESCRIPTION:   
       
      (NCCC).  The NCCC is responsible for VA's compliance with the clozapine 
      --------
      At least one site has reported temporary registration starting with the 
      letter "R" when they were expecting it to start with "Z".
       
      Resolution:
      -----------
      The PSO574P pre-init routine also updates the CLOZAPINE WEEKEND 
      REGISTRATION list that is stored in ^XTMP("PSJ CLOZ").  This will ensure 
      that any temporary registration numbers that were generated during IOC 
      tests and were not used will be recovered.  This issue was revealed in 
      Risk Evaluation and Mitigation Strategy (REMS), which is mandated by the 
      the MailMan messages sent to the CLOZAPINE ROLL-UP Mail Group in Forum.
       
      6. Ensure "Expires:" Date is Correct
      Defect 1132368
       
      Problem:
      --------
      The CPRS team found a typo in routine PSODIR2.  The code had a comma 
      where it should have a less than sign.  Only clozapine prescriptions 
      would have been affected. This logic is used to create the value for the 
      Food and Drug Administration (FDA) for tracking clozapine patients. 
      "Expires:" prompt in Patient Prescription Processing.
       
      Resolution:
      -----------
      Routine PSODIR2 was corrected.
       
      7. Dose default is missing for active or pending prescriptions.
      Defect 1106891
       
      Problem:
       
      --------
      The default dose is missing when editing all prescriptions in Pharmacy 
      backdoor orders.  It should be there for non-clozapine prescriptions.  
      The prior fix removed this for all prescriptions.
       
      Resolution:
      -----------
      The logic in routines PSOBKDED and PSONEW1 was modified to only remove 
      the default dose for Clozapine prescriptions.
       
      The multi-build contains the Mental Health patch YS*5.01*154 and the 
       
      8. Remove the "Quantity Being Changed" message displaying during backdoor 
      pharmacy processing of a Clozapine Outpatient 4 Day Override Order.
      Defect 1155637
       
      Problem:
      --------
      The "Quantity Being Changed" message was being displayed when a 
      pharmacist was editing a 4 day temporary override Clozapine 
      prescription.  Users at the IOC sites found this to be confusing wand 
      Outpatient Pharmacy patch PSO*7.0*574.  The list of defects and their 
      wanted it removed.
       
      Resolution:
      -----------
      The routine PSOSIG was modified to display this message ONLY for 
      non-clozapine prescriptions.
       
      9. CPRS Complex Order Default Dose Incorrect
      Defect 1180952
       
      resolution is below.
      Problem:
      --------
      Complex orders which have multiple dosages were not displaying the 
      correct defaults during dosage edit.
       
      Resolution:
      -----------
      Routine PSOBKDED was modified to add the default dose.
       
      10. Missing Unit Price of Drug
       
      Defect 1181628
       
      Problem:
      --------
      Prescriptions for certain medications were not storing the UNIT PRICE OF 
      DRUG field.  This occurred when the DRUG had a REORDER LEVEL field (#11) 
      value of zero or null.
       
      Resolution:
      -----------
      Defect Tracking System Ticket(s) & Overview:
      The branching logic in the SET^PSODRG subroutine was corrected.
       
       
      11. Temporary numbers generated off the date
      Defect 1181858
       
      Problem:
      --------
      The logic to generate a temporary clozapine registration number was not 
      always generating a sequential counter.
      --------------------------------------------
       
      Resolution:
      -----------
      The logic in FINDNEXT^PSOCLUTL was modified.
       
       
      12. ^XTMP("PSJ CLOZ",0) purge date
      Defect 1181868
       
      Problem:
      The MENTAL HEALTH NCC WARRANTY RELEASE 5.01 multi-build is a warranty 
       
      --------
      The purge date in the ^XTMP("PSJ CLOZ",0) global node was not always set 
      to the same number of days in the future. This is a matter of programming 
      style.  No error was generated; no functionality was affected.  The 
      development accepted this as a defect to end the discussion.  The change 
      cannot be seen by users and there is no way to test this.
       
      Resolution:
      -----------
      Routine PSOCLO1 was changed to call the line tag XTMPZRO^PSOCLOU.
      Patch PSO*7.0*574 contains the following fixes:
       
      13. Expiration Date Calculated Incorrectly
      Defect 1182728
       
      Problem:
      --------
      When a Clozapine prescription was being edited the expiration date may 
      not have been computed correctly.  This was related to editing the 
      quantity and days supply values.
       
       
       
      Resolution:
      -----------
      Routines PSOCLO1, PSODIR1, and PSOORED6 were modified.  The logic to 
      compute the expiration was moved to the new subroutine EXPDT^PSOCLO1.
       
      14. Patient Lookup in Register Clozapine Patient [PSOL REGISTER PATIENT]
      Defect 1210946
       
      Problem:
      1.      Incorrect computation of drug costs
      --------
      The Patient Lookup in the Register Clozapine Patient [PSOL REGISTER 
      PATIENT] option doesn't allow a user to enter the last initial and last 4 
      digits of the patient's Social Security Number (SSN).
       
      Resolution:
      -----------
      Routine PSOCLUTL was modified in the REG subroutine to add an "M" to the 
      DIC(0) value to allow a patient lookup on multiple cross-references.
       
       Defect 1132310
      15. Error on Clozapine Inpatient Medication
      Defect 1227862
       
      Problem:
      --------
      When a user enters the Inpatient Order Entry [PSJ OE] option for 
      Clozapine patients an <UNDEFINED> error occurs.  The PSODFN variable is 
      undefined,
       
      Resolution:
       INC7277287 - East Bay Division - Martinez Outpatient Clinic
      -----------
      Routine PSOCLO1 was modified to set PSODFN if it's undefined, based on 
      the value in DFN.
       
         *   *   *   *   *   *
       
      Test Sites:
      ----------
       - West Los Angeles VAMC (691)
       - N. Florida /S. Georgia VAMC (573)
       INC7340377 - VA Connecticut Healthcare System West Haven Campus
       - VA Connecticut Healthcare System - West Haven Division (689)
       
      There are no documentation updates associated with this patch.
       
      Patch Installation:
       
      Pre/Post Installation Overview:
      -------------------------------
      There are no tasks to be performed before the installation of this 
      multi-build.  Note that the routines should be backed up to a PackMan 
       
      message before installing the build.
       
      Pre-Installation Instructions:
      ------------------------------
      This patch may be installed with users on the system although it is
      recommended that it be installed during non-peak hours to minimize
      potential disruption to users.  This patch should take less than 5 minutes
      to install.  It should not be installed when the YSCL DAILY TRANSMISION 
      option is running.  If unsure when that is check the OPTION SCHEDULING 
      file (#19.2) using FileMan:
      Problem:
       
      Select VA FileMan Option: Inquire to File Entries
       
      Output from what File: OPTION SCHEDULING//   (17 entries)
      Select OPTION SCHEDULING NAME:  YSCL DAILY TRANSMISSION
      Another one: 
      Standard Captioned Output? Yes//   (Yes)
      Include COMPUTED fields:  (N/Y/R/B): NO//  - No record number (IEN), no 
      Computed  Fields
       
      --------
      NAME: YSCL DAILY TRANSMISSION
        QUEUED TO RUN AT WHAT TIME: OCT 05, 2019@01:30
        RESCHEDULING FREQUENCY: 1D            TASK ID: 2577736
       
      Installation Instructions:
      --------------------------
      1. The KIDS multi-build can be found in the VistA software repository at 
      download.vista.domain.ext
       
          ANON$:[ANONYMOUS.ANONYMOUS]MH_NCC_WARRANTY_5_01_T06.KID
      release for the National Clozapine Registry (NCR) software. This release 
      Users would see incorrect values for the costs of prescriptions.
       
      Place the KIDS multi-build file into a local directory and use the KIDS 
      option Load a Distribution option to load it into the transport global.
       
      2. Choose the INSTALL/CHECK MESSAGE PackMan option.
       
      3. From the Kernel Installation and Distribution System Menu, select the
      Installation Menu.  From this menu, you may elect to use the following
      options. When prompted for the INSTALL NAME enter:
         MENTAL HEALTH NCC WARRANTY RELEASE 5.01
       
       
      a. Backup a Transport Global - This option will create a backup message
      of any routines exported with this patch.
       
      b. Compare Transport Global to Current System - This option will (allow
      you to view all changes that will be made when this patch is installed.  
      It compares all components of this patch routines, DDs, templates, etc.).
       
      c. Verify Checksums in Transport Global - This option will allow you to
      ensure the integrity of the routines that are in the transport global.
      Resolution:
       
      4.  From the Installation Menu, select the Install Package(s) option and
      choose the patch to install (MENTAL HEALTH NCC WARRANTY RELEASE 5.01).
       
      5. Accept the default when prompted 'Want KIDS to Rebuild Menu Trees Upon 
      Completion of Install? NO//'
       
      6. Accept the default when prompted 'Want KIDS to INHIBIT LOGONs during 
      the install? NO//'
       
      -----------
      7. Accept the default when prompted 'Want to DISABLE Scheduled Options, 
      Menu Options, and Protocols? NO//'
       
      8. If prompted 'Delay Install (Minutes):  (0 - 60): 0// enter 0 (zero).
       
      Backout /Rollback Strategy:
      ---------------------------
      Backout will be done only with the concurrence and participation of
      development team and appropriate VA site/region personnel. The decision to
      backout the software will be a joint decision between development
      The PSODRG routine has been updated to fix the problem with incorrect 
      team, VA site and regional personnel, and other appropriate VA 
      personnel.  Rollback applies to data only and is not applicable to this 
      multi-build.
       
      Prior to installing the KIDS multi-build, the site/region should have
      saved a backup of the routines in a PackMan message using the Backup a
      Transport Global [XPD BACKUP] menu option (this is done at time of
      install). The message containing the backed-up routines can be loaded with
      the "Xtract PackMan" function at the Message Action prompt. The PackMan
      function "INSTALL/CHECK MESSAGE" is then used to install the backed up
      computation for prescription costs.
      routines onto the VistA System.
       
      Validation of Backout Procedure
      -------------------------------
      The backout Procedure can be verified by printing the first 2 lines of
      the PSO* and YS* Routines contained in the MENTAL HEALTH NCC WARRANTY 
      RELEASE 5.01 multi-build using the option First Line Routine Print [XU 
      FIRST LINE PRINT]. Once the old routines listed in the multi-build patch 
      have been restored, the first two lines of the Routines will no longer 
      contain the designation of patch 574 (for Outpatient Pharmacy PSO* 
       
      routines) and patch 154 (for Mental Health YS* routines) in the patch 
      list section on line 2 of the routines.
      The PSODRG routine was incorrectly referencing this field for the drug 
      cost:
        50,15        DISPENSE UNITS PER ORDER UNIT 660;5 NUMBER
      will fix the defects and incidents reported by the sites to the 
      It has been changed to this field:
        50,16        PRICE PER DISPENSE UNIT 660;6 NUMBER
       
      2. During backdoor pharmacy process of Outpatient 4 Day Override order, a 
      field called LIMITED DURATION appears.
      Defect 981761
       
      Problem:
      --------
      When entering a clozapine prescription for an Outpatient 4 Day Override 
      developers of the National Clozapine Coordination (NCC) Project. The 
      order, a field called LIMITED DURATION is presented.  The IOC sites 
      stated that this may be misleading to the pharmacy staff and want it 
      removed.
       
      Resolution:
      -----------
      The logic in routine PSOORED5 was modified to remove the LIMITED DURATION 
      field for clozapine prescriptions.  Routine PSONEW1 was modified to 
      correct the sig for the clozapine prescription.
       
      project is also referred to as the Clozapine Modernization (ClozMod) 
      3. Patients who are actively receiving clozapine (e.g. had a prescription 
      last month) are discontinued.
      Defect 1132329
       
      Problem:
      --------
      The YSCL DAILY TRANSMISSION option checks for clozapine patients who 
      should be discontinued.  The code uses a Mail Group and an ^XTMP storage 
      location that are in the Pharmacy namespace.
       
      Project.
      Resolution:
      -----------
      The PSO574P pre-init routine was created to ensure that the PSOCLOZ Mail 
      Group TYPE is set to "PUBLIC" and ALLOW SELF ENROLLMENT? is set to "NO".  
      This will prevent any issues when email messages are sent to that Mail 
      Group.
       
      Note: There are routines in the YS*5.01*154 patch that also address this 
      defect.
       
       
      4. The Register Clozapine Patient option needs a restriction to only 
      allow registered patients.
       Defect 1133724
       
      Problem:
      --------
      The Register Clozapine Patient [PSOL REGISTER PATIENT] option needs a 
      restriction to only allow patients that have a CLOZAPINE REGISTRATION 
      NUMBER in the CLOZAPINE PATIENT LIST file (#603.01).  The option updates 
      fields in the PHARMACY PATIENT file (#55).
      The NCR is maintained by the National Clozapine Coordinating Center 
       
      Resolution:
      -----------
      The PSOCLUTL routine was modified to only allow patients who have a 
      registration number to be updated in the PHARMACY PATIENT file (#55).
       
      5. Temporary Clozapine Authorization Number not in correct format
       Defect 1132422
       
      Problem:
      
    • 544
      DATE APPLIED:   2020-04-10 16:08:08
      APPLIED BY:   USER,SEVENTY
      DESCRIPTION:   
      MCCF EDI TAS EPHARMACY BUILD 13
      
    • 608 SEQ #489
      DATE APPLIED:   2020-05-14 16:49:43
      APPLIED BY:   USER,SEVENTY
      DESCRIPTION:   
      This patch changes the upper limit of the DAYS TO PULL FROM SUSPENSE Field
      transmission, then the software will add the number of days from this
      parameter to the print through date and process any other prescriptions it
      finds in that extended print through date for that patient.
       
      The DAYS TO PULL SUSPENDED CS CMOP Field (#3.1) controls the bundling of 
      controlled substances for CMOP transmissions. So, if a patient has at
      least one prescription that falls within the print through date for the
      controlled substances CMOP transmission, then the software will add the
      number of days from this parameter to the print through date and process
      any other prescriptions it finds in that extended print through date for
      (#3) and the DAYS TO PULL SUSPENDED CS CMOP Field (#3.1) of the OUTPATIENT
      that patient.
       
      The field name DAYS TO PULL SUSPENDED CS CMOP has been changed to DAYS TO 
      PULL SUSPENSE CMOP CS.
       
       
      ****NOTE****
      The change to the DAYS TO PULL FROM SUSPENSE Field (#3) and DAYS TO PULL 
      SUSPENSE CMOP CS Field (#3.1) of the OUTPATIENT SITE File (#3) may lead to
      NCPDP Reject 79 Refill Too Soon (RTS) claims.
      SITE File (#59) from 10 to 15 days.
       
      If the claim submission returns a Refill Too Soon (79) reject, the label 
      is NOT printed for the prescription and it is moved to the Refill Too 
      Soon/DUR section of the patient Medication Profile screen until the user 
      resolves the reject. The prescription will also display on the Third-Party
      Payer Reject Worklist. If the claim submission returns a Reject Resolution
      Required reject, the label is NOT printed for the prescription and it is
      moved to the Reject Resolution Required section of the Third-Party Payer
      Reject - Worklist.
       
       
      Please search for additional guidance on the eRevenue Resources main 
      landing page for Refill Too Soon. Guidance documents for COVID-19 Refill 
      Too Soon Override. The landing page may be accessed at:  
      https://vaww.vashare.domain.ext/sites/eRevenueResources/Pages/HomePage.asp
      x
      The DAYS TO PULL FROM SUSPENSE Field (#3) controls the bundling of all 
      prescriptions for local dispensing suspense batches and for non-controlled
      substances for Consolidated Mail Outpatient Pharmacy (CMOP) transmissions.
      So, if a patient has at least one prescription that falls within the print
      through date for the local batch or non-controlled substances CMOP
      
    • 566 SEQ #490
      DATE APPLIED:   2020-06-01 16:22:41
      APPLIED BY:   USER,SEVENTY
      DESCRIPTION:   
      This patch adds data to output for some existing encapsualtion APIs, and 
      also creates a new API to return Non-VA Med information.
      
    • 477
      DATE APPLIED:   2020-06-24 12:14:44
      APPLIED BY:   USER,SIXTYFIVE
      DESCRIPTION:   
      This patch is part of CPRS v31 updates. It includes changes to the Outpatient
         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 
      Pharmacy application related to DAYS SUPPLY values over 90 days verification
         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                                       
      when a specific dispense drug is not defined in the pending order from CPRS.
          (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  
         
      This patch also contains a new function for CPRS to call before authorizing
         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 
       
      the user to copy an Outpatient Pharmacy order.
         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.
       
      Below Are some details regarding the two changes in this patch:
      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.
       
      1. Patient Prescription Processing [PSO LM BACKDOOR]
      
    • 546 SEQ #494
      DATE APPLIED:   2020-07-07 16:43:31
      APPLIED BY:   USER,SIXTYFIVE
      DESCRIPTION:   
      This patch addresses one (1) issue:
       
      Status mismatches might occur between the ORDERS (#100) file and the 
      associated medication file - PRESCRIPTION (#52) or PHARMACY PATIENT (#55).
      
    • 54 SEQ #49
      DATE APPLIED:   2001-02-02 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      1.  Clinical Reminders has requested the addition of the last RELEASED
      expanded version of the SIG as displayed by the Action/Information Profile
      in Outpatient Pharmacy.  Many physicians do not know some of the
      abbreviations used by Pharmacy.  This patch addresses this issue.  
       
      3.  A problem has been reported that can occur when a pending Outpatient
      order is transferred from Outpatient Pharmacy to Inpatient Medications in
      Computerized Patient Record System (CPRS). It is possible that an
      incorrect dispense drug is assigned to the order. This patch resolves the
      problem.
       
      DATE/TIME and the associated DAYS SUPPLY to the ^TMP("PS",$J,D0,0) node
      4.  When selecting from the Drug file (#50), the user entered lowercase
      letters and was returned a drug based on the VA Drug Class lookup and was
      not offered a choice of drugs starting with the letters entered.  This
      patch corrects this problem.  
      returned by the OCL^PSOORRL API. This will allow the developers to rewrite
      the way Clinical Reminders handles drug findings providing a speed-up of
      somewhere between 5 and 10 times. IA 2400.  This patch addresses this issue.
       
      2.  E3R #15111 has requested the SIG be expanded on the Health Summary 
      Component RXOP. The RXOP component displays the shorthand version of the SIG
      for backdoor enter prescriptions.  The physicians would like to see the
      
    • 584 SEQ #496
      DATE APPLIED:   2020-07-07 16:50:24
      APPLIED BY:   USER,SIXTYFIVE
      DESCRIPTION:   
      INC7454020 - PRN schedules calculating erroneous default quantity
      INC7698142 - Duplicate HL7 messages sent to OPAI device INC7444486 - Drug
      Costs report is incorrect
      
    • 596 SEQ #495
      DATE APPLIED:   2020-07-07 16:52:54
      APPLIED BY:   USER,SIXTYFIVE
      DESCRIPTION:   
      Release of Controlled Substance (CS) after Return to Stock issue.
      
    • 603 SEQ #493
      DATE APPLIED:   2020-07-09 16:13:53
      APPLIED BY:   USER,SIXTYFIVE
      DESCRIPTION:   
      This patch will address the following issue: 
      (d)INC9792380 - Scriptpro not releasing partial filled rx since PSO*7*531
                      INSTALL
      (d)INC9744639 - kb0107373 - GLA PARTIALS NOT RELEASING/SCRIPTPRO
       
        
      Patient Safety Issues (PSIs):
      -----------------------------
      HITPS-6704 - INC9398751/INC9586108/INC9663815/INC9768476/INC9792380/INC9744639
        
           
       
      Defect Tracking System Ticket(s) & Overview: 
      --------------------------------------------
      1. INC9398751    - Partialed RXs are not releasing automatically from VISTA
         (d)INC9586108 - outpatient partial Rxs not releasing after PSO*7*531
         (d)INC9663815 - VistA: Outpatient Pharmacy: Rx Won't Go to CMOP Because of
                         Local Partial?
         (d)INC9768476 - Issue with VistA option PSO LM BACKDOOR ORDERS - Refill is
                         released instead of partial then Rx cannot be suspended to
                         CMOP
         (d)INC9792380 - Scriptpro not releasing partial filled rx since PSO*7*531
      INC9398751    - Partialed RXs are not releasing automatically from VISTA
                         INSTALL
         (d)INC9744639 - kb0107373 - GLA PARTIALS NOT RELEASING/SCRIPTPRO
       
      Problem: 
      --------
      VA New Jersey Health Care System reported that after the installation of the
      patch PSO*7*531 partial fills are no longer being automatically released when
      the dispense message is received from the OPAI (Outpatient Pharmacy Automated
      Interface) dispensing machines. The issue happens because incoming messages
      from OPAI don't identify whether a fill was a partial or a regular fill. It
      (d)INC9586108 - outpatient partial Rxs not releasing after PSO*7*531
      was confirmed that this issue was indeed caused by the patch PSO*7*531.  
         
      Resolution: 
      -----------
      This patch changes the logic for matching incoming HL7 message from OPAI 
      dispensing machines by matching it with the outgoing HL7 message via the
      MESSAGE SERVER ID field (#10) in the PHARMACY EXTERNAL INTERFACE file 
      (#52.51) first. This logic should always find a match, however if for some
      reason the matching fails it will resort to matching the Rx# along with the
      fill, which should work as well. 
      (d)INC9663815 - VistA: Outpatient Pharmacy: Rx Won't Go to CMOP Because of
            
      Technical Resolution: 
      ---------------------
      Changed the routine PSOHLDS at line tag FACK2 to re-write the logic for 
      matching an incoming HL7 OPAI message with a record in the PHARMACY EXTERNAL 
      INTERFACE file (#52.51). The old logic was improved and left in place in case
      the new logic fails for any reason. The change will assure an accurate
      matching of an incoming HL7 OPAI message to the corresponding record in the
      PHARMACY EXTERNAL INTERFACE file (#52.51).
                      Local Partial?
      (d)INC9768476 - Issue with VistA option PSO LM BACKDOOR ORDERS - Refill is
                      released instead of partial then Rx cannot be suspended to
                      CMOP
      
    • 594 SEQ #497
      DATE APPLIED:   2020-07-13 17:25:06
      APPLIED BY:   USER,SIXTYFIVE
      DESCRIPTION:   
      Using ONEVA remote data requires choosing local drug file entry to fill 
      prescriptions for traveling vets. Only part of drug name/dose is visible.
      
    • 592 SEQ #498
      DATE APPLIED:   2020-07-21 13:48:48
      APPLIED BY:   USER,SIXTYFIVE
      DESCRIPTION:   
      Correct display defect in Reset Copay Status
      
    • 597 SEQ #499
      DATE APPLIED:   2020-08-03 11:23:59
      APPLIED BY:   USER,SIXTYFIVE
      DESCRIPTION:   
      This patch will address the following issue: 
       
      Problem: 
      --------
      The Veterans Health Care System of the Ozarks reported that at the final step
      when verifying a non-verified prescription through the Patient Prescription 
      Processing [PSO LM BACKDOOR ORDERS] option it displays the incorrect
      prescription number, as shown below:
        ...
        Now Processing Enhanced Order Checks!  Please wait...
        
        
        Press return to continue: 
        
        TEST,PATIENT                 ID#:999-99-9999      RX#: 9999999  <<<< Wrong #
        SIMVASTATIN  5MG TAB
         
        VERIFY FOR MFR,OUTPATFOUR? (Y/N/Delete/Quit): Y// 
        ... 
        
      Resolution: 
      -----------
      1. INC9129002 - At the final step when verifying a non-verified prescription,
      It was determined that if a pharmacist first tries to verify a prescription
      entered by a pharmacy technician that had a significant order check and 
      instead of verifying the prescription s/he enters "Q" to quit and move on to
      a different patient, when s/he tried to verify a prescription for the newly
      selected patient the RX# field displayed the number of the prescription from
      the previous patient, the one with the significant order check. The problem 
      was addressed by resetting the variable that held the Rx# information every
      time the user selects to verify a prescription.
        
      Technical Resolution: 
                      VistA displays the incorrect prescription number. 
      ---------------------
      The problem was happening because the variable INT was being used and it was
      not properly NEWed or KILLed. So, the variable INT was added to the list of
      variables being NEWed at the line tag OERR+1 in the PSOVER routine.
       
      Defect Tracking System Ticket(s) & Overview: 
      --------------------------------------------
      1. INC9129002 - At the final step when verifying a non-verified prescription,
                      VistA displays the incorrect prescription number. 
      
    • 598 SEQ #500
      DATE APPLIED:   2020-08-10 12:54:52
      APPLIED BY:   USER,SIXTYFIVE
      DESCRIPTION:   
      This patch will resolve the following issue(s)
       
      1) When entering outpatient prescriptions and attempt to edit the issue 
      date, the system will allow you to change the issue date to more than 6
      months in the past.
       
      2) When inbound eRx prescriptions are processed duplicate entries in the 
      ERX EXTERNAL PERSON file [#52.48] can occur. 
      
    • 611 SEQ #501
      DATE APPLIED:   2020-08-10 12:56:04
      APPLIED BY:   USER,SIXTYFIVE
      DESCRIPTION:   
      When a user changes the Days Supply for a Clozapine Rx the user is now 
      also prompted to select the appropriate Refills #. See the patch 
      desciption on FORUM for more details.
      
    • 607 SEQ #503
      DATE APPLIED:   2020-09-23 10:59:49
      APPLIED BY:   USER,SIXTYFIVE
      DESCRIPTION:   
      When attempting to print a patient's outpatient medication profile from 
      VISTA, only one page prints (the page that includes only the patient 
      information). Subsequent pages do not print. Additionally, on the second 
      page of the Medication Profile [PSO P] report there is an additional Page 
      2 header printed in the middle of the page and not at a page break.
      
    • 602 SEQ #504
      DATE APPLIED:   2020-09-23 11:00:18
      APPLIED BY:   USER,SIXTYFIVE
      DESCRIPTION:   
      This patch addresses the following issue:
       
                                 Digits 
               DESCRIPTION:      Price per dispense unit.  
       
               TECHNICAL DESCR:  This is the price per dispense unit (per ML/MG
                                 etc.) that is calculated when entering the
                                 price per order unit, e.g. Price per order unit
                                 (bottle) =$0.49, dispense unit is ML & the
                                 bottle has 1000ML. Price per dispense unit =
                                 $(0.49/1000) = $0.00049 = $0.0005 (rounded to
                                 the 4th decimal).  
         
       
       
      Pre-Installation Instructions:
      =============================
      This patch may be loaded with users on the system. You may wish to 
      install it during non-peak hours. Installation will take less than 1 
      minute. 
       
       
      Installation Instructions:
      Files & Fields Associated:
      =========================
         1. Choose the PackMan message containing this patch.
       
         2. Use the 'INSTALL/CHECK MESSAGE' option of the PackMan menu. This
            option will load the KIDS patch onto your system.
       
         3. On the 'Kernel Installation & Distribution System' Menu (KIDS),
            select the 'Installation' menu.
       
         4. From this menu, you may elect to use the following option. When 
       
            prompted for the INSTALL NAME select the package 'PSO*7.0*602':
       
            a. Print Transport Global - This option will allow you to print 
               only a summary of the patch, to print a summary of the patch and
               the routines in the transport global, or to print only the
               routines in the transport global.
       
            b. Compare Transport Global to Current System - This option will 
               allow you to view all changes that will be made when this patch
               is installed. It compares all components of this patch (routines,
      File Name (Number)      Field Name (Number)          New/Modified/Deleted
               DDs, templates, etc.).
            
         5. From the Installation Menu, select Backup a Transport Global - This 
            option will create a backup message of any routines exported with 
            this patch. It will not backup any other changes such as DDs or
            templates.
       
         6. Use the 'Install Package(s)' option under the 'Installation' menu 
            and select the package 'PSO*7.0*602'.
       
      ------------------      --------------------------   --------------------
         7. When prompted 'Want KIDS to INHIBIT LOGONs during the install? 
            NO//', choose 'NO'.
       
         8. When prompted 'Want to DISABLE Scheduled Options, Menu Options, 
            and Protocols? NO//', choose 'NO'.
       
       
      Installation Verification:
      =========================
      Review the Data Dictionary changes listed above using VA FileMan. 
      PRESCRIPTION (#52)      UNIT PRICE OF DRUG (#17)     Modified
       
      Select OPTION: 8  DATA DICTIONARY UTILITIES
      Select DATA DICTIONARY UTILITY OPTION: 1  LIST FILE ATTRIBUTES
       START WITH What File: PRESCRIPTION//     (1863777 entries)
            GO TO What File: PRESCRIPTION//     (1863777 entries)
            Select SUB-FILE: 
      Select LISTING FORMAT: STANDARD//   
      Start with field: FIRST// 17  UNIT PRICE OF DRUG
      Go to field: 17  UNIT PRICE OF DRUG
       
                     
       
      Back-out/Rollback Strategy:
      ==========================
      In the event of a catastrophic failure, the Facility CIO may make the 
      decision to back-out the patch.
       
      The back-out plan is to edit the Data Dictionaries returning them to
      original pre-install state.
       
      To verify the back-out completed successfully, ensure the INPUT 
       
      TRANSFORMS have been edited as follows.
       
      Using FileMan, go to UTILITY FUNCTIONS, INPUT TRANSFORM (SYNTAX)
       
      Select OPTION: 6  UTILITY FUNCTIONS
      Select UTILITY OPTION: 5  INPUT TRANSFORM (SYNTAX)
       
      Modify what File: PRESCRIPTION//          (1863777 entries)
      Select FIELD: 17  UNIT PRICE OF DRUG
      UNIT PRICE OF DRUG INPUT TRANSFORM: 
      Associated ticket(s):
      K:+X'=X!(X>999999)!(X<0)!(X?.E1"."5N.N) X
        Replace 999999 With 9999  Replace 
         K:+X'=X!(X>9999)!(X<0)!(X?.E1"."5N.N) X
      'HELP'-PROMPT: Type a Number between 0 and 999999, 4 Decimal Digits
                 Replace 999999 With 9999  Replace 
         Type a Number between 0 and 9999, 4 Decimal Digits
      XECUTABLE 'HELP': 
       
      =====================
       
      1. INC9558577 Sites' seeing Not ECME Billable: Cannot find price for Item
       
       
      Associated NSR(s):
      ==================
      N/A
       
      Participating Test Sites:
      1. When the UNIT PRICE OF DRUG in the Drug file (#50) is set to a higher
      =========================
      TBD
       
       
      Defect Tracking System Ticket(s) & Overview:
      ===========================================
       
      1. INC9558577 Sites' seeing Not ECME Billable: Cannot find price for Item
       
         Problem:
      value than 9999.00 then when a RX is entered the value is not filed into
         -------
       
         When the UNIT PRICE OF DRUG in the Drug file (#50) is set to a higher
         value than 9999.00 then when a RX is entered the value is not filed
         into the Prescription file and (if ECME is setup) the message 'Cannot
         find price for Item' is also displayed during the RX entry process
         (Patient Prescription Processing).   The Input Transform of the UNIT
         PRICE OF DRUG field in file 52 prevents a value from being stored when
         it is greater than 9999.0000.  During testing it was also found that 
         the field CURRENT UNIT PRICE OF DRUG (#1.2) in the Refill sub record
      the Prescription file and (if ECME is setup) the message 'Cannot find
         allowed the price of the drug to be filled with a value greater than
         the input transform was defined to allow.
       
       
         Resolution:
         ----------
         The input Transform of the UNIT PRICE OF DRUG in the Prescription file
         (#52) is modified to allow a maximum value of 999999.0000.  This 
         matches the maximum values in fields PRICE PER ORDER UNIT, PRICE PER
         DISPENSE UNIT, and PRICE PER DISPENSE UNIT in the Drug File (#50)
      price for Item' is also displayed during the RX entry process (Patient
         The input Transform of the CURRENT UNIT PRICE OF DRUG (#1.2) in the 
         Prescription file (#52) is also modified to allow a maximum value of 
         999999.0000.  Routine PSOR52 is also modified to not stuff the price of
         the drug into the refill field which avoided the input transform
         specifications. 
       
       
       
      Test Sites:
      ==========
      Prescription Processing).   The Input Transform of the UNIT PRICE OF DRUG
       
       
      Data Dictionaries Before:
      ========================
       
      52,17    UNIT PRICE OF DRUG     0;17 NUMBER (Required)
       
               INPUT TRANSFORM:  K:+X'=X!(X>9999)!(X<0)!(X?.E1"."5N.N) X
               LAST EDITED:      FEB 27, 2020 
               HELP-PROMPT:      Type a Number between 0 and 9999, 4 Decimal 
      field in file 52 prevents a value from being stored when it is greater
                                 Digits 
               DESCRIPTION:      Price per dispense unit.  
       
               TECHNICAL DESCR:  This is the price per dispense unit (per ML/MG
                                 etc.) that is calculated when entering the
                                 price per order unit, e.g. Price per order unit
                                 (bottle) =$0.49, dispense unit is ML & the
                                 bottle has 1000ML. Price per dispense unit =
                                 $(0.49/1000) = $0.00049 = $0.0005 (rounded to
                                 the 4th decimal).  
      than 9999.0000
       
       
      Data Dictionaries After:
      =======================
       
      52,17    UNIT PRICE OF DRUG     0;17 NUMBER (Required)
       
               INPUT TRANSFORM:  K:+X'=X!(X>999999)!(X<0)!(X?.E1"."5N.N) X
               LAST EDITED:      FEB 27, 2020 
               HELP-PROMPT:      Type a Number between 0 and 999999, 4 Decimal 
      
    • 55 SEQ #50
      DATE APPLIED:   2001-02-27 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      1. When returning a prescription using Return Medication to Stock [PSO
      problem.
       
      3. The Most Commonly Dispensed Drugs report obtained by using Commonly
      Dispensed Drugs [PSO COMMON] option, is skipping printing some sites even
      though there are valid records. This patch fixes this problem.
       
      4. A problem can occur when a prescription is placed on hold through the
      Outpatient Pharmacy options, and then taken off hold through these same
      options. The prescription will not display correctly on the orders tab
      in CPRS. The order text is not being updated appropriately.  The status
      RETURNED STOCK] option, it was reported that the NEXT POSSIBLE FILL field
      will show as active, but the word "Hold" will still show on the left side
      of the order text. This patch corrects this problem.
       
      5. Additional data has been added to the routine that returns prescription
      and drug information to the Integrated Billing package, for Tricare
      billing purposes. This has been done for future enhancements.
       
      6. With the release of PSO*7*40 an interface was added for the Controlled 
      Substances V. 3.0 package (PSD*3*24).  This interface sends notification
      to the Controlled Substances V. 3.0 package when a fill, refill or partial
      (#102) of PRESCRIPTION file (#52) was not getting reset to what it was
      is returned to stock. This patch further enhances the interface by
      preventing users who do not hold the PSDMGR key from updating vault
      balances and returning controlled substances to stock. For this new
      enhancement to be completely functional PSD*3*30 must be installed.
      prior to the refill. This patch fixes this problem.
       
      2. When using Complete Orders from OERR [PSO LMOE FINISH] option,
      finishing orders entered through Computerized Patient Record System
      (CPRS), it was reported that the number of refills did not always update
      appropriately when Days Supply was edited. This patch corrects this
      
    • 612
      DATE APPLIED:   2020-09-23 15:25:17
      APPLIED BY:   USER,SIXTYFIVE
      DESCRIPTION:   
       The Health Integration & Modernization (HI&M) CLOZAPINE NCCC OVRD 
       
       used as an initial test to allow the patient to be selected for
       registration; existing code will still prevent the patient from being 
       selected due to previous registration, but the correct message will now 
       display regarding the patient's registration status.
       
       
       3. Requirement 2 Defect 1 - Patient with Temp Registration and an NCCC 
       Authorization and NCCC Override Date, but day supply limited to 4.
       
       INC9951972: COVID-19 VistA PSO defect - Clozapine National Override 
       The multi-build contains the Mental Health patch YS*5.01*166 and the 
       patient's prescription limited to 4 days.
       
       Problem:
       --------
       A Patient initially receives a 4-day emergency authorization, and later
       an NCCC Authorization and an NCCC Override Date. While the NCCC Override
       Date is still active, the Day Supply (for Outpatient Pharmacy) or Order
       Duration (for Inpatient Medications) continues to be limited to 4 days.
       Inpatient Medications Order Duration is defined as the number of days
       between the order's Start Date/Time and Stop Date/Time.
       Outpatient Pharmacy patch PSO*7.0*612.  The list of defects and their 
          
       Resolution:
       -----------
       If a NCCC Authorized National Override Date is in effect following an
       initial local override, the system shall process an active clozapine 
       patient's clozapine prescription under national override processes 
       allowing the patient to be provided with the approved quantity associated
       with their individual dispensing frequency from the DISPENSE FREQUENCY 
       field (#2) in the CLOZAPINE PATIENT LIST file (#603.01). The approved 
       quantity is determined by the order's Days Supply for Outpatient Pharmacy
       resolution is below.
       orders, and the Order Duration (days between Start Date/Time and Stop 
       Date/Time) for Inpatient Medications orders.
        
       Technical Resolution:
       ---------------------
        A change was made in several routines to look in the PHARMACY PATIENT 
       file (#55) for the patient's active clozapine authorization number before
       searching for the value in the patient's DISPENSE FREQUENCY field (#3) of
       the CLOZAPINE PATIENT LIST file (#603.01). This enables the clozapine 
       processing logic to any temporary initial local authorization on file 
       
       that have been replaced by a permanent NCCC authorization numbers.
       
       - To address backdoor entry of outpatient orders, routine DAYSEN^PSODIR1
       was changed to find the patient's registered clozapine 
       authorization number.
       
       - To address backdoor entry of inpatient orders, routine ^PSOCLO1 
       was changed to find the patient's registered clozapine authorization 
       number.
       
       This patch is also being released with informational patch PSJ*5*403 that
       - To properly calculate days supply during the finishing of pending 
       orders, routine CLOZ^PSOORFI2 was changed to find the patient's 
       registered clozapine authorization number.
       
       - To properly calculate days supply during the back door editing of 
       active orders, routine ACT^PSOORNE2 was changed to find the patient's 
       registered clozapine authorization number.
       
       - To properly calculate default Days Supply in CPRS, change 
       DSUP^PSOSIGDS was changed to find the patient's registered clozapine 
       documents changes to Inpatient Medications' processing of clozapine
       authorization number. This changed routine is used by the ORWDPS1
       DFLTSPLY Remote Procedure Call (RPC) to calculate default Days Supply.
       
       
       4. Requirement 2 Defect 2 - Patient with NCCC Authorization receives a 
       Special  Condition Fill, and later an NCCC Authorization and Override 
       Date, but day supply limited to 4.
       
       INC9951972: COVID-19 VistA PSO defect - Clozapine National Override 
       patient's prescription limited to 4 days 
       overrides that are a result of the defect fixes in PSO*7.0*612 and
       
       Problem:
       --------
       A patient with an initial NCCC Authorization receives a Special Condition
       override, followed by an NCCC override, is limited to a Day Supply
       (Outpatient Pharmacy orders) or an Order Duration (Inpatient Medications
       orders) limited to 4 for clozapine orders. The NCCC national clozapine
       override and the patient's regular clozapine dispense frequency are
       ignored.
       
       YS*5.01*166. 
       Resolution:
       -----------
       A patient with an initial NCCC clozapine authorization receiving a
       Special Condition override, followed by an NCCC override, shall be 
       processed under national override rules allowing the patient to be 
       provided with the approved quantity associated with their individual 
       dispensing frequency from the DISPENSE FREQUENCY field (#2) in the 
       CLOZAPINE PATIENT LIST file (#603.01). The approved quantity is reflected
       in the order's Days Supply for Outpatient Pharmacy orders, and the Order 
       Duration (days between Start Date/Time and Stop Date/Time) for Inpatient 
       
       Medications orders.
        
       Technical Resolution:
       ---------------------
       To address backdoor entry of outpatient orders, routine DAYSEN^PSODIR1
       was changed to find the patient's registered clozapine authorization
       number.
       
       To address backdoor entry of inpatient orders, routine ^PSOCLO1 was
       changed to find the patient's registered clozapine authorization 
       COVID-19 multi-build is an emergency patch to the National Clozapine 
       Defect Tracking System Ticket(s) & Overview: 
       number.
       
       
       5. Requirement 2 Defect 3 - Local Special Condition Override followed
       by valid lab results limits orders to 4-day supply.
       
       Problem:
       --------
       When a patient with an active NCCC clozapine registration and no 
       current clozapine lab results receives a Local Special Condition 
       --------------------------------------------
       override, followed by the entry of valid clozapine lab results, 
       subsequent pharmacy orders continue to be limited to a 4-day supply.
       
       Resolution:
       -----------
       When a patient with an active NCCC clozapine registration and no 
       current clozapine lab results receives a Local Special Condition 
       override, followed by the entry of valid clozapine lab results, 
       the Local Special Condition override is no longer in effect and should
       be ignored for new orders. New pharmacy orders should be processed 
       
       using the days supply associated with their individual dispense
       frequency. The patient's dispense frequency is reflected in the order's 
       Days Supply for Outpatient Pharmacy orders, and the Order Duration 
       (days between Start Date/Time and Stop Date/Time) for Inpatient 
       Medications orders.
       
       Technical Resolution:
       ---------------------
       Routine ^PSOCLO1 was modified to KILL the ^XTMP globals associated
       with the patient's local override when an active  NCCC clozapine 
       Patch PSO*7.0*612 contains the following changes: 
       registration and valid clozapine lab results exist. This prevents the 
       obsolete Local Special Condition override from interfering with the 
       patient's regular clozapine dispense frequency.
       
       
       6. Requirement 2 Defect 4 - Emergency Temp Override followed by new
       NCCC authorization limits orders to 4-day supply.
       
       Problem:
       --------
       
       When a patient with a discontinued clozapine registration and current
       valid lab results receives a Local Emergency Temp Override, followed
       by a new NCCC clozapine authorization number and registration, 
       subsequent pharmacy orders continue to be limited to a 4-day supply.
       
       Resolution:
       -----------
       When a patient with a discontinued clozapine registration and current
       valid lab results receives a Local Emergency Temp Override, followed
       by a new NCCC clozapine authorization number and registration, the Local
       1. Requirement 1 Enhancement - Automate the Pharmacy Registration of NCCC
       Emergency Temp override is no longer in effect and should
       be ignored for new orders. New pharmacy orders should be processed 
       using the days supply associated with the patient's dispense frequency.
       The patient's dispense frequency is reflected in the order's Days 
       Supply for Outpatient Pharmacy orders, and the Order Duration (days 
       between Start Date/Time and Stop Date/Time) for Inpatient Medications 
       orders.
       
       Technical Resolution:
       ---------------------
       Clozapine Authorizations.
       Modify routines PSOCLUTL and PSOCLADD to KILL the ^XTMP globals
       associated with the patient's local override at the time an NCCC
       clozapine authorization number is registered to the patient. This
       prevents an obsolete local override from interfering with order entry
       routines' calculation of the days supply based on the patient's regular 
       clozapine dispense frequency.
       
       
       Patch Components
       ================
       
       Files & Fields Associated:
       
       File Name (Number)    Field Name (Number)      New/Modified/Deleted      
       ------------------    ----------------------   --------------------      
       N/A (See YS*5.01*166 Patch Description related for Files/Fields)
       
       Forms Associated:
       Form Name             File #       New/Modified/Deleted
       ---------             ------       --------------------
       N/A
       Problem:
        
       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
       Registry (NCR) software to correct defects to Clozapine National 
       Currently, national clozapine authorization numbers are sent by the 
       
       Templates Associated:
       Template Name      Type      File Name (Number)  New/Modified/Deleted
       -------------      ----      ------------------  --------------------
       N/A
       
        *   *   *   *   *   *   *   *   *   *   *
       
       Test Sites: 
       ----------
       National Clozapine Coordinating Center (NCCC) and filed into the 
       New Jersey Health Care System (561)
       VA Connecticut Health Care System (689)
       Boise VA Medication Center (531)
       
       
       Software and Documentation Retrieval Instructions:
       --------------------------------------------------
       The software for this patch is being released as a host file.
       
       The host file is available at the following location:  
       CLOZAPINE PATIENT LIST file (#603.01). Later, a pharmacy user must
       /srv/vista/patches/SOFTWARE/PSO_YS_CLOZ_COVID.KID  
            
       Documentation describing the new functionality is included in this
       release. Documentation can be found on the VA Software Documentation 
       Library at: https://www.domain.ext/vdl/
       
       -------------------------------------------------------------------------
       Title                                 File Name                 
       -------------------------------------------------------------------------
       Technical Manual/Security Guide       pso_7_p612_tm.docx
       manually execute Vista option Register Clozapine Patient [PSOL REGISTER
       - Outpatient Pharmacy V.7.0           pso_7_p612_tm.pdf
       
       User Manual - Manager - Outpatient    pso_7_man_um.docx
       Pharmacy V.7.0                        pso_7_man_um.pdf
       
       Deployment Installation Back-Out      pso_7_p612_ys_501_p166_dibr.docx
       and Rollback Guide - HI&M             pso_7_p612_ys_501_p166_dibr.pdf
       Clozapine Overrides 
       
       Release Notes - HI&M Clozapine        pso_7_p612_ys_501_p166_rn.docx
       PATIENT] (for new patients), or Edit Data for a Patient in the Clozapine
       Overrides                             pso_7_p612_ys_501_p166_rn.pdf
       
       
       Patch Installation: 
       
       Pre/Post Installation Overview: 
       -------------------------------
       There are no tasks to be performed before the installation of this 
       multi-build. Note that the routines should be backed up to a PackMan
       message before installing the build.
       Program PSOL [EDIT] (for previously registered patients). 
        
       Pre-Installation Instructions: 
       ------------------------------
       This patch may be installed with users on the system although it is 
       recommended that it be installed during non-peak hours to minimize
       potential disruption to users.  This patch should take less than 5 
       minutes to install.  It should not be installed when the YSCL DAILY
       TRANSMISION option is running.  If unsure when that is check the OPTION
       SCHEDULING file (#19.2) using FileMan:
        
        
       Select VA FileMan Option: Inquire to File Entries 
        
       Output from what File: OPTION SCHEDULING//   (17 entries) Select OPTION
       SCHEDULING NAME:  YSCL DAILY TRANSMISSION Another one: Standard Captioned
       Output? Yes//   (Yes) Include COMPUTED fields:  (N/Y/R/B): NO//  - No 
       record
       number (IEN), no Computed  Fields 
        
       NAME: YSCL DAILY TRANSMISSION 
         QUEUED TO RUN AT WHAT TIME: OCT 05, 2019@01:30 
       Resolution:
         RESCHEDULING FREQUENCY: 1D            TASK ID: 2577736 
        
       Installation Instructions: 
       --------------------------
      1. Place the KIDS multi-build file PSO_YS_CLOZ_COVID.KID into a 
      local directory and use the KIDS option Load a Distribution option to 
      load it into the transport global.
        
      2. Choose the INSTALL/CHECK MESSAGE PackMan option.  
        
       ---------- 
      3. From the Kernel Installation and Distribution System Menu, select 
      the Installation Menu.  From this menu, you may elect to use the 
      following options. When prompted for the INSTALL NAME enter:
             PSO*7.0*612
        
        a. Backup a Transport Global - This option will create a backup message
           of any routines exported with this patch.
        
        b. Compare Transport Global to Current System - This option will (allow 
           you to view all changes that will be made when this patch 
       Automate the clozapine registration process by automatically updating the
           is installed.  It compares all components of this patch 
           (routines, DDs, templates, etc.).
        
        c. Verify Checksums in Transport Global - This option allows you to 
           ensure the integrity of the routines that are in the transport 
           global.
        
       4.  From the Installation Menu, select the Install Package(s) option and 
       choose the patch to install (PSO*7*612).
        
       Clozapine Coordinating Center (NCCC) Override functionality.
       patient's clozapine registration number and status when a new National 
       5. Accept the default when prompted 'Want KIDS to Rebuild Menu Trees 
       Upon Completion of Install? NO//'
        
       6. Accept the default when prompted 'Want KIDS to INHIBIT LOGONs during 
       the install? NO//'
        
       7. Accept the default when prompted 'Want to DISABLE Scheduled Options, 
       Menu Options, and Protocols? NO//'
        
       8. If prompted 'Delay Install (Minutes):  (0 - 60): 0// enter 0 (zero).  
       Clozapine number is received from the NCCC.
        
       Backout /Rollback Strategy: 
       ---------------------------
       Backout will be done only with the concurrence and participation of 
       development team and appropriate VA site/region personnel. The decision 
       to backout the software will be a joint decision between development
       team, VA site and regional personnel, and other appropriate VA personnel.
       Rollback applies to data only and is not applicable to this multi-build.
        
       Prior to installing the KIDS multi-build, the site/region should have 
        
       saved a backup of the routines in a PackMan message using the Backup a
       Transport Global [XPD BACKUP] menu option (this is done at time of
       install). The message containing the backed-up routines can be loaded 
       with the "Xtract PackMan" function at the Message Action prompt. The
       PackMan function "INSTALL/CHECK MESSAGE" is then used to install the
       backed up routines onto the VistA System.
       
       The new "AC" mumps cross reference for the CLOZAPINE PATIENT LIST file 
       (#603.01) must be manually deleted via FileMan prior to restoring the 
       backed up routines. 
       Technical Resolution:
       
       The steps to delete the cross reference:
         1. Access VA FileMan option Cross-Reference A Field via the VA FileMan 
         Utility Functions [DIUTILITY] menu.
         2. At the prompt, "What type of cross-reference (Traditional or New)?" 
         enter NEW.
         3. At the prompt, "Modify What File:" enter 603.01.
         4. The new "AC" cross reference should be selected by default.
         5. At the prompt "Choose E (Edit)/D (Delete)/C (Create):" enter DELETE.
         6. At the prompt "Are you sure you want to delete the index  
       ---------------------
         definition? NO// YES"
       
       Example deletion of new "AC" index if backout is required:
       
         VA FileMan 22.2   
       
         Select OPTION: UTILITY FUNCTIONS  
         Select UTILITY OPTION: CROSS-REFERENCE A FIELD OR FILE  
         What type of cross-reference (Traditional or New)? Traditional// NEW
         Modify what File: REMOTE PROCEDURE// 603.01  CLOZAPINE PATIENT LIST
       New Pharmacy API PSOCLADD has been created that accepts Patient DFN and 
                                                 (74 entries)
         Current Indexes on file #603.01:
           1589   'AC' index
         Choose E (Edit)/D (Delete)/C (Create): DELETE   
       
         Which Index do you wish to delete? 1589//  AC
         Are you sure you want to delete the index definition? NO// YES   
       
           Index definition deleted.
       
       NCCC Clozapine Authorization number as input and files the number into 
       
       
       
       Validation of Backout Procedure 
       -------------------------------
       The backout Procedure can be verified by printing the first 2 lines of 
       the PSO* and YS* routines contained in the HI&M CLOZAPINE NCCC OVRD 
       COVID-19 multi- build using the option First Line Routine Print [XU FIRST
       LINE PRINT]. Once the old routines listed in the multi-build patch have
       been restored, the first two lines of the Routines will no longer contain
       the CLOZAPINE REGISTRATION NUMBER field (#53) in the PHARAMCY PATIENT 
       the designation of patch 612 in the patch list section on line 2 of the
       routines.
       
       The backout of the new "AC" cross reference on the CLOZAPINE PATIENT 
       LIST file (#603.01) can be verified by repeating the backout steps and 
       verifying that there is no longer a selectable "AC" cross reference to 
       delete.
       file (#55), and updates the CLOZAPINE STATUS field (#54) to 'A' for 
       Active. This API is executed when a new clozapine authorization is filed 
        
       into the CLOZAPINE PATIENT LIST (#603.01) file via a mumps action cross 
       reference.
       
       
       2. Requirement 1 Defect 1 - Incorrect Messages Displayed in Clozapine 
       Vista Options
       
       Problem:
       --------
       When more than one clozapine authorization number exists for a patient,
       The NCR is maintained by the NCCC. The NCCC is responsible for VA's 
       the "Register Clozapine Patient" option currently displays the incorrect
       message, "Patient,Name has not been authorized for Clozapine by the NCCC
       (National Clozapine Coordinating Center). This option is only available
       for known NCCC-registered patients." when more than one entry in file
       603.01 for the patient. This message displays regardless of patient's
       Clozapine Status in file 55. 
           
       When more than one clozapine authorization number exists for a patient,
       the "Edit Data for a Patient in the Clozapine Program" option currently
       displays the incorrect message, "Patient,Name has not been authorized for
       compliance with the clozapine Risk Evaluation and Mitigation Strategy 
       Clozapine by the NCCC in Dallas. Contact the NCCC in Dallas for
       authorization." The patient cannot be selected.
       
       Resolution:
       -----------   
       The code associated with the 'Register a Clozapine Patient' option and
       the "Edit Data for a Patient in the Clozapine Program" shall be modified
       to display correct information about the patient's Clozapine registration
       status regardless of the number of clozapine numbers on file for the
       patient.
       (REMS), which is mandated by the Food and Drug Administration (FDA) for 
       
       The "Register Clozapine Patient" option shall display "Patient,Name is
       already registered with number CL99999. Use the edit option to change
       registration data, or contact your supervisor" when more than one entry 
       in file 603.01 for the patient. No other change in functionality to this 
       option.
       
       The "Edit Data for a Patient in the Clozapine Program" option shall 
       not display the incorrect message "Patient,Name has not been authorized 
       for Clozapine by the NCCC in Dallas. Contact the NCCC in Dallas for 
       tracking clozapine patients.
       authorization". The option will allow the selection of a patient with 
       more than one entry in file 603.01. No other change in functionality to 
       this option.
       
       Technical Resolution:
       ---------------------
       Correct routine PSOCLUTL's lookups by patient into the CLOZAPINE PATIENT
       LIST file (#603.01) from $$FIND1^DIC, which fails when there is more than
       one clozapine authorization number on file for a patient, to D FIND^DIC,
       which finds all clozapine authorization numbers. The defective lookup is
      
    • 606 SEQ #506
      DATE APPLIED:   2020-11-03 14:07:02
      APPLIED BY:   USER,SEVENTEEN
      DESCRIPTION:   
      This patch will address the following ePrescribing (eRx) issues: 
        
      Problem: 
      -------
      VA Black Hills Health Care System reported a stack error causing VistA to
      terminate the user's session when they used the Class III VistA option
      Inpatient Pending Orders Display [PSOZ INPATIENT PENDING ORDERS]. Although
      the HPS (Health Portfolio Software) Sustainment Team does not support Class
      III software, it was determined that the root cause of the problem was the
      fact that the LOGIN DATE field (#15) in the PENDING OUTPATIENT ORDERS file
      (#52.41) was being populated with only the date (YYYMMDD) and not the time
        
      (YYYMMDD.HHMMSS) by the new eRx functionality. Although the field allows
      for date only content, every other function that creates a new entry in
      the PENDING OUTPATIENT ORDERS file (#52.41) also sets the timestamp along
      with the date.
        
      Resolution: 
      ----------
      This patch will modify the setting of the LOGIN DATE field (#15) in the
      PENDING OUTPATIENT ORDERS file (#52.41) for eRx pending orders to include
      the date and timestamp (YYYMMDD.HHMMSS) of when the order was created.
      INC8108373 - Inbound eRx - Outpatient pharmacy bingo board causing stack error
      This will prevent the error users are getting when running the Class III
      option mentioned above.
       
      Note: This fix will apply to future orders only, filed after the patch is
            installed.
        
      Technical Resolution: 
      --------------------
      The setting of the array PSOHY("EDT") at SETUP+72^PSOERX1B and 
      PSOHY+34^PSOERXU3 was changed from PSOHY("EDT")=DT (DT holds the current
      INC10596781 - e-prescription missing SIG or patient instruction
      date in the YYYMMDD format) to PSOHY("EDT)=$$NOW^XLFDT() (the $$NOW^XLFDT()
      function returns the current date and time in the YYYMMDD.HHMMSS format).
         
      2. INC10596781 - e-prescription missing SIG or patient instruction
         
      Problem: 
      -------
      The VA Health Administration Center Denver reported that when viewing a 
      RefillResponse type record in the Complete Orders from eRx [PSO ERX FINISH]
      option the field 'Vista Sig' under the MEDICATION DISPENSED section was being
       
      suppressed as indicated in the screen capture example below:
       
         ****************************MEDICATION DISPENSED*************************    
         Vista Drug: CHLORAMBUCIL 2MG TAB                                                
         Vista Qty: 30              Vista Refills: 3        Vista Days Supply: 30     
         >>> 'Vista Sig' field should be displayed here.
         VA Rx#: Unable to resolve.                                                      
       
       
      Resolution: 
      Defect Tracking System Ticket(s) & Overview: 
      ----------
      It was confirmed that the software was hiding the 'Vista Sig' field because
      of an error in the code. The defect is being addressed by this patch and it
      display the 'Vista Sig' correctly, as shown in the example below:
       
         ****************************MEDICATION DISPENSED*************************    
         Vista Drug: CHLORAMBUCIL 2MG TAB                                                
         Vista Qty: 30              Vista Refills: 3        Vista Days Supply: 30     
         Vista Sig: TAKE ONE-HALF TABLE BY MOUTH TWICE A DAY FOR 30 DAYS ON A FULL       
         STOMACH                                                                         
      ===========================================
         VA Rx#: Unable to resolve.                                                      
       
       
      Technical Resolution: 
      --------------------
      The array variable DIRARY was misspelled at line MEDDIS+37^PSOERXU3 and at
      line MEDDIS+39^PSOERXU3 it was using the variable DIRECT instead of the 
      DIRARY array. Both issues were resolved.
       
       
      1. INC8108373 - Inbound eRx - Outpatient pharmacy bingo board causing stack
                      error
      
    • 624 SEQ #507
      DATE APPLIED:   2020-11-06 16:15:25
      APPLIED BY:   USER,SEVENTEEN
      DESCRIPTION:   
      When a user changes the DAYS SUPPLY for only a Clozapine flagged drug with
      at least one registered lab test, the user will also be prompted to select
      the appropriate # OF REILLS. See the patch desciption on FORUM for more
      details.
      
    • 604 SEQ #508
      DATE APPLIED:   2020-11-23 10:09:44
      APPLIED BY:   USER,SEVENTEEN
      DESCRIPTION:   
      1. EPharmacy prescriptions that are pulled from suspense using the action
      Variable RX0 is set during the speed refill and is not killed if the Rx
      is suspended when the speed refill process is done nor is it killed 
      when starting a New Order.
      PP in the PSO LM BACKDOOR ORDERS option remain suspended after a
      subsequent refill action of another prescription. 
       
      2.  During processing of Outpatient Pharmacy order, user was kicked out
      of VistA session with an undefined error DSPL+3^PSOORNE3 *PSLSTL.
      After doing a speed refill for a prescription that results in it 
      being suspended, the error occurs when entering a new order for a supply
      item and answering No to the final prompt 'Is this correct?'
      
    • 621 SEQ #509
      DATE APPLIED:   2020-12-04 17:24:42
      APPLIED BY:   USER,SEVENTEEN
      DESCRIPTION:   
      This patch will address the following issues: 
      --------------------------------------------
      1. INC11549905 - when you enter a new prescription the QTY rounds up unless
                       you change the days supply.
        
      Problem: 
      --------
      The Oscar G. Johnson VA Medical Center reported that when editing the Days 
      Supply fields for a Clozapine prescription that the QTY field value is not
      rounding up, instead it remains a factional value, forcing the user to fix
      it mannually.
        
       
      Resolution: 
      -----------
      The issue was confimed and the calculation of the QTY value was fixed to
      round any fractional value up. So, if the automatic calculation results in
      a value such 4.2, for example, it will be rounded up to 5. 
         
      Technical Resolution: 
      ---------------------
      Changed the routine PSOCLUTL at line tag QTYCHK+9 to always round the value of
      1. INC11549905 - when you enter a new prescription the QTY rounds up unless
      the variable QTY up.
       
        S:QTY PSORXARY("QTY")=(QTY+.99)\1,$P(PSORXARY("RX0"),U,7)=(QTY+.99)\1
        
      2. INC11595547 - CLOZAPINE ORDER - Day Supply- Quantity - # of Refill -
                       Expiration date calculation 
        
      Problem: 
      --------
      After the installation of patch PSO*7*574 the expiration date calculation for
                       you change the days supply.
      clozapine prescriptions is wrong for some scenarios after editing the # of
      Refills or Days Supply fields. For example, when you edited a prescription
      with 28-day supply and 0 refills, with an expiration date of 28 past the issue
      date, to 14-day supply and 1 refill it was setting the expiration to 14 days
      past the issue date, instead of keeping the 28 days.
        
      Resolution: 
      -----------
      The calculation of the expiration date for clozapine prescriptions was resolved
      to correctly calculate the total number of days supply of the entire 
      2. INC11595547 - CLOZAPINE ORDER - Day Supply- Quantity - # of Refill -
      prescription, including the refills.
         
      Technical Resolution: 
      ---------------------
      Removed a line of code in the PSOEXDT routine (shown below) introduced by
      PSO*7*574 that was preventing the expiration date from being calculated
      correctly for clozapine prescriptions.
       
                ; Added Clozapine check to not modify Expires date ; PSO*574
            A   Q:+$G(PSORXED("CLOZ EDIT")) 
                       Expiration date calculation 
       
      3. INC11627662 - PSOL EDIT - Edit Data for a Patient in the Clozapine Program
         
      Problem: 
      --------
      After the installation of patch PSO*7*574 the option Edit Data for A Patient in
      the Clozapine Program [PSOL EDIT] started resetting the REGISTRATION DATE field
      (#58) in the PHARMACY PATIENT file (#55) even after the user simply returns
      through the 3 fields in the option without modifying any of them. The
      REGISTRATION DATE field should only be reset when the user changes the value of
      3. INC11627662 - PSOL EDIT - Edit Data for a Patient in the Clozapine Program
      the CLOZAPINE REGISTRATION NUMBER.
       
        Edit Data for a Patient in the Clozapine Program [PSOL EDIT]
       
        Edit Data for a Patient in the Clozapine Program
        Select clozapine patient :    CLOZPAT,TEST
        CLOZAPINE REGISTRATION NUMBER: MR12345// MR12345
        CLOZAPINE STATUS: ACTIVE TREATMENT
        RESPONSIBLE PROVIDER: TEST,PROVIDER// TEST,PROVIDER
       
       
      Resolution: 
      -----------
      The Clozapine REGISTRATION DATE will only be reset when the value of the 
      CLOZAPINE REGISTRATION NUMBER is modified.The issue was confimed and the calculation of the QTY value was fixed to
      round any fractional value up. So, if the automatic calculation results in
      a value such 4.2, for example, it will be rounded up to 5. 
         
      Technical Resolution: 
      ---------------------
      Changed the routine PSOCLUTL at line tag QTYCHK+9 to always round the value of
      Defect Tracking System Ticket(s) & Overview: 
      the variable QTY up.
       
        S:QTY PSORXARY("QTY")=(QTY+.99)\1,$P(PSORXARY("RX0"),U,7)=(QTY+.99)\1
      
    • 549
      DATE APPLIED:   2020-12-08 08:27:24
      APPLIED BY:   USER,SEVENTEEN
    • 618 SEQ #511
      DATE APPLIED:   2020-12-18 15:18:28
      APPLIED BY:   USER,SEVENTEEN
      DESCRIPTION:   
      This patch addresses the following issues:
       
      Associated ticket(s):
      =====================
       
      1. INC11453884 - Reset Copay Status List Manager Start with Fill Date 
         should be a required response 
       
      2. INC11646025 - Issues with the Reset Copay Status List Manager Display 
         Option
       
       
      Associated NSR(s):
      ==================
      N/A
       
      Participating Test Sites:
      =========================
      Bay Pines VAMC
      Washington DC VAMC
       
       
      1. Reset Copay Status List Manager Start with Fill Date should be 
      Defect Tracking System Ticket(s) & Overview:
      ===========================================
       
      1. INC11453884 - Reset Copay Status List Manager Start with Fill Date 
         should be a required response
       
         Problem:
         -------
         Running option RESET COPAY STATUS LIST MANAGER [PSOCP RESET COPAY 
         STATUS LM] will encounter a subscript error if no date is entered at
      a required response.
         the Start with Fill Dates: prompt
       
         Resolution:
         ----------
         Modify PSOCPF to exit from the option when no date is entered for the 
         Start with Fill Dates: prompt. 
       
      2. INC11646025 - Issues with the Reset Copay Status List Manager Display 
         Option
       
       
         Problem:
         -------
         Up carat out should gracefully exit.  Report doesn't allow an up
         carat at several prompts
       
         Resolution:
         ---------------
         Modify PSOCPF to exit from the option when up carat ^ is entered on
         the Start with Fill Dates, Go to Fill Dates, and the Select(A)ll or
         (S)elected Prescription(s) prompts.  It was also found during testing 
      2. Up carat (^) out should gracefully exit.  Report doesn't allow 
         that the Change Patient (CP) function within the List Manager screen 
         had the same issues with ^ not working as it should and that is being 
         addressed with updates to routine PSOCPF2.  The patinet name was also 
         added to the List Manager screen when NO DATA FOUND FOR ENTERED 
         CRITERIA is displayed. 
      an up carat at several prompts
       
         
      
    • 581 SEQ #512
      DATE APPLIED:   2020-12-18 15:20:59
      APPLIED BY:   USER,SEVENTEEN
    • 627 SEQ #513
      DATE APPLIED:   2020-12-18 15:25:59
      APPLIED BY:   USER,SEVENTEEN
      DESCRIPTION:   
      This patch addresses the following issues in setting the "status" field 
      of the ORC segment which is sent to Optifill or ScriptPro:
       
      1. The "Print from Suspense File" option sends a status of "NEW" instead 
         of "REFILL" for refills.
       
      2. The "Reprint Batches from Suspense" option sends a status of "NEW" 
         instead of "REPRINT" when reprinting original (i.e. not refills) 
         prescriptions.
      
    • 628 SEQ #514
      DATE APPLIED:   2020-12-18 15:26:26
      APPLIED BY:   USER,SEVENTEEN
      DESCRIPTION:   
       
      Disconnect between order file discontinue action and 
      prescription file (prescription was filled multiple times after 
      discontinuation
      
    • 57 SEQ #51
      DATE APPLIED:   2001-02-27 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      When editing the drug of a prescription using the Patient Prescription
      orderable item with active/suspended status.
      These occurrences are very rare and it could lead to the following:
      1. As reported in NOIS MAN-1200-11563, the patient profile could change
      to that of another patient and result in dispensing drugs to the wrong
      patient (action 1 above).
      2. As reported in NOIS MAN-0101-10680, it could end up patients having
      duplicate drugs in their medical profile (action 2 above).
      This patch ensures that the TMP("PSORXDC",$J) global is killed
      accordingly.
      Processing [PSO LM BACKDOOR ORDERS] option, the TMP("PSORXDC",$J) global
      created to store the duplicate prescription(s) that was requested to be
      discontinued does not get deleted if either of the following action was
      taken:
      1. If the edit was terminated by up-arrowing at the point of accepting
      a new prescription.
      2. If the dispensed drug is changed to a drug which already exists in
      the medical profile (in another prescription) that is tied to the same
      
    • 609 SEQ #515
      DATE APPLIED:   2020-12-18 15:27:21
      APPLIED BY:   USER,SEVENTEEN
      DESCRIPTION:   
      OPAI NOT UTILIZING MAIL PREF 4-LOCAL CERTIFIED MAIL
      Prescription Dispense HL7 records for the OPAI (Out Patient 
      Automated Interface) 
       
       
      This patch will resolve the following issue:
            
      When using Menu Option PSO LM BACKDOOR ORDERS 
      and the user selects PU (Patient Update), if the user selects  
      option #4 LOCAL CERTIFIED MAIL for at the MAIL: prompt
      the selection will not be reflected in the RXD segment of the 
      
    • 629 SEQ #516
      DATE APPLIED:   2020-12-31 15:16:14
      APPLIED BY:   USER,SIXTYFIVE
      DESCRIPTION:   
      It was reported that the Return to Stock indicator not cleared after 
      original fill of a CS rx if returned to stock and later filled and 
      released.
      
    • 626 SEQ #518
      DATE APPLIED:   2021-02-26 10:10:41
      APPLIED BY:   USER,SEVENTEEN
      DESCRIPTION:   
      Rx entries always had a T-6M limit. Copy+Edit had a loophole that allowed
      any date into the past which created an error when a 19th century date was
      entered. The fix was done to match the new Rx-entry T-6M limit. However, 
      by removing the loophole of the previous code the sites that developed a
      conversion workflow based on Copy+Edit and backdating non-CS Rx's between
      6 and 12 months lost that capability.
      
    • 613 SEQ #519
      DATE APPLIED:   2021-02-26 10:10:49
      APPLIED BY:   USER,SEVENTEEN
      DESCRIPTION:   
      See FORUM for patch description.
      
    • 616 SEQ #520
      DATE APPLIED:   2021-03-04 10:17:43
      APPLIED BY:   USER,SEVENTEEN
      DESCRIPTION:   
      File #52 Label multiple created with a missing header node
      
    • 625b
      DATE APPLIED:   2021-04-05 00:00:00
      DESCRIPTION:   
      Backup of PSO*7.0*625 on Apr 05, 2021
       
      Warning:  Installing this backup patch message will install older versions
      of routines and Build Components (options, protocols, templates, etc.).
      Please verify with the Development Team that it is safe to install.
      
    • 625 SEQ #521
      DATE APPLIED:   2021-04-05 09:44:33
      APPLIED BY:   USER,SEVENTEEN
      DESCRIPTION:   
      The description of this build can be found in the National Patch Module 
      under PSO*7.0*625.
      
    • 635b
      DATE APPLIED:   2021-04-20 00:00:00
      DESCRIPTION:   
      Backup of PSO*7.0*635 on Apr 20, 2021
       
      Warning:  Installing this backup patch message will install older versions
      of routines and Build Components (options, protocols, templates, etc.).
      Please verify with the Development Team that it is safe to install.
      
    • 635 SEQ #522
      DATE APPLIED:   2021-04-20 15:03:52
      APPLIED BY:   USER,SEVENTEEN
      DESCRIPTION:   
      Inbound eRx version 4.0 defect remediation.
      
    • 560b
      DATE APPLIED:   2021-05-19 00:00:00
      DESCRIPTION:   
      Backup of BPS PSO IB BUNDLE 16.0, BPS*1.0*28, PSO*7.0*560, IB*2
       
      Warning:  Installing this backup patch message will install older versions
      of routines and Build Components (options, protocols, templates, etc.).
      Please verify with the Development Team that it is safe to install.
      
    • 7
      DATE APPLIED:   1999-04-16 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      This KIDS build fixes a problem when pending orders are received from CPRS.  
      profile screen, hit return at the action prompt an undefined error occurred.
      NOIS: HUN-0398-20933
       
      Routines: PSOORFI1, PSOORFI2, PSOORFIN, PSOPOST3, PSOPTPST, PSORN52C, PSORX1 
      PSOHLNE2, PSOHLNEW, PSOHLSN
      They are not finished in a first in first out order.  Added "AD" cross 
      reference to Login Date field (#15) from the Pending Outpatient Orders file 
      (#52.41).  Added an 'AE' xref to the Related Institution field.
       NOIS: WAS-0298-21178 
       
      Error generated when pharmacist was finishing outpatient med orders for an
      inpatient. From the medication profile screen, she typed IP to view the
      inpatient profile and after the review, she went back to the medication
      
    • 52 SEQ #52
      DATE APPLIED:   2001-02-27 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      Problem: The CMOP Controlled Substance Rx Dispense Report generates an
      undefined error when it is trying to report on a prescription refill that
      was filled locally and not sent to CMOP.
       
      Resolution:
       
      The CMOP coding has been changed to handle the case when a refill was
      filled locally and not by CMOP.
      
    • 560
      DATE APPLIED:   2021-05-19 16:10:28
      APPLIED BY:   USER,SEVENTEEN
    • 631b
      DATE APPLIED:   2021-06-04 00:00:00
      DESCRIPTION:   
      Backup of PSO*7.0*631 on Jun 04, 2021
       
      Warning:  Installing this backup patch message will install older versions
      of routines and Build Components (options, protocols, templates, etc.).
      Please verify with the Development Team that it is safe to install.
      
    • 631 SEQ #525
      DATE APPLIED:   2021-06-04 09:35:32
      APPLIED BY:   USER,SEVENTEEN
      DESCRIPTION:   
      This patch will address the following issues: 
         INC15788649 - RxRenewal Response - Replace status get assigned wrong 
      to be marked with the RRX (RXRENEWAL REQUEST EXPIRED) status after 14 days
      without a response.
        ...
               Select one of the following:
       
                    PT        PATIENT(Grouped)
                    RX        PRESCRIPTION RECEIVED DATE
                    E         EXIT
         
          Select By: (PT/RX): PT// RX  PRESCRIPTION RECEIVED DATE
                       status code
        ...
          
      Technical Resolution: 
      --------------------
      The functionality responsible for the auto expiration of CRN and RRN records
      in the PSOERX routine lines BLDITEM+11 thru BLDITEM+14 for the RX view were
      copied over to the PSOERXC1 routine which is used by the PT view. This way
      no matter which way the user enters the option it will always check and mark
      eligible CRN and RRN records as expired.
       
       
       
      Test Sites: 
      -----------
      TBD
       
      Documentation Retrieval Instructions:
      -------------------------------------
      N/A (No documentation changes)
        
      Installation Instructions: 
      2. INC12814745 - Rx Sig Not Upper-cased when processing inbound eRX
      --------------------------
      This patch may be installed with users on the system although it is recommended
      that it be installed during non-peak hours to minimize potential disruption to
      users.  Staff should not be processing prescriptions while patch is being
      installed.  This patch should take less than 5 minutes to install.  
       
         1. Choose the PackMan message containing this patch.  
       
         2. Choose the INSTALL/CHECK MESSAGE PackMan option.  
        
       
         3. From the Kernel Installation & Distribution System menu, select 
            the Installation menu.  From this menu, select Backup a Transport 
            Global. This option will create a backup message of any routines
            exported with this patch. It will not backup any other changes such
            as DD's or templates.  When prompted for INSTALL NAME, enter the
            patch #, PSO*7.0*631.
        
         4. From the Kernel Installation & Distribution System menu, select 
            the Installation menu.  From this menu, you may select to use the 
            following options: 
      3. INC16106925 - Pharmacy messages not assigned appropriate status by
            when prompted for INSTALL NAME, enter the patch #, PSO*7.0*631: 
              a. Compare Transport Global to Current System - This option will 
                 allow you to view all changes that will be made when this patch 
                 is installed.  It compares all components of this patch 
                 routines, DDs, templates, etc.  
       
              b. Verify Checksums in Transport Global - This option will allow 
                 you to ensure the integrity of the routines that are in the 
                 transport global.  
       
                       software
         5. From the Installation menu, select the Install Package(s) option and
            choose the patch to install.  
       
         6. When prompted 'Want KIDS to INHIBIT LOGONs during the install? 
            NO//', respond NO.  
       
         7. When prompted 'Want to DISABLE Scheduled Options, Menu Options, and 
            Protocols? NO//', respond NO.  
       
         8. If prompted 'Delay Install (Minutes): (0-60): 0//' respond 0.  
        
       
       
      Back-out/Rollback Strategy:
      ---------------------------
      Back-out will be done only with the concurrence and participation of
      development team and appropriate VA site/region personnel. The decision to
      back-out or rollback software will be a joint decision between development
      team, VA site/region personnel and other appropriate VA personnel.  
       
      Prior to installing an updated KIDS package, the site/region should have saved
      Defect Tracking System Ticket(s) & Overview: 
      a backup of the routines in a mail message using the Backup a Transport Global
      [XPD BACKUP] menu option (this is done at time of install). The message
      containing the backed up routines can be loaded with the "Xtract PackMan"
      function at the Message Action prompt. The Packman function "INSTALL/CHECK
      MESSAGE" is then used to install the backed up routines onto the VistA System. 
       
      The back-out plan is to restore the routines from the backup created.
       
      No data was modified by this patch installation and, therefore, no 
      rollback strategy is required.
      --------------------------------------------
       
       
      Validation of Roll Back Procedure 
      ---------------------------------
      The Roll Back Procedure can be verified by printing the first 2 lines of the
      PSO Routines contained in this patch using the option First Line Routine Print
      [XU FIRST LINE PRINT]. Once the routines contained in the PSO*7.0*631 patch
      have been rolled back, the first two lines of the Routines will no longer
      contain the designation of patch PSO*7.0*631 in the patch list section on line
      2.
        
      1. INC13163644 - Assist with deleting eRx order on inbound eRx queue
        
      Problem: 
      --------
      The Fresno VA Medical Center reported that 'Denied' incoming eRx response
      records were sitting in their eRx Holding Queue (Complete Orders from eRx
      [PSO ERX FINISH] option) for months because they do not have any way to
      remove them. This issue usually happens when the sites manually renews a
      prescription after placing an eRx refill/renewal request for the eRx
      prescription. Once the incoming response is received the software is unable
      1. INC13163644 - Assist with deleting eRx order on inbound eRx queue
      to process the renewal because the eRx is already renewed and files the
      record with an RXN (RXRENEWAL RESPONSE - NEW) status instead of assigning it
      a more appropriate status such as RXF RXN (RXRENEWAL RESPONSE - FAILED), 
      which is removed from the eRx Holding Queue once the user acknowledges it.
        
      Resolution: 
      -----------
      The eRx incoming response processing code was changed to automatically assign
      a status of RXF to an incoming renewal eRx response if the prescription has
      already been manually renewed. This will allow users to successfully remove
         Duplicates:
      such records from their by using the hidden action ACK (Acknowledge).
       
      Technical Resolution: 
      ---------------------
      The line of code below was inserted at REFRESP+24 in the PSOERXA5 routine. 
       
       .D UPDSTAT^PSOERXU1(ERXIEN,"RXF","eRx already Renewed.")
       
      It will ensure that when an Denied incoming eRx response is received for an
      already renewed prescription the status will be set to RXF instead of RXN. 
         -----------
      Furthermore, another potential code for leaving records in the RXN was 
      identified in the use of the API $$FIND1^DIC because it did not require an
      exact match of the related eRx when the incoming eRx response arrived. The
      third parameter was changed to include "O", which will force an exact match
      in order to identify the related eRx record.
        
      2. INC12814745 - Rx Sig Not Upper-cased when processing inbound eRX
        
      Problem: 
      --------
         INC15788594 - RxRenewal Response was assigned wrong status flag
      The Tucson VA Medical Center reported that when using the eRx Holding Queue
      (Complete Orders from eRx [PSO ERX FINISH] option) the user added a patient
      instruction (code) with a lower case text to the eRx and the medication
      instruction expanded as expected however it did not convert to upper case in
      the Inbound ERX Holding queue. The text was appended to the SIG and remained in
      lower case through the finishing process in the Patient Prescription Processing
      [PSO LM BACKDOOR ORDERS] option. 
       
      Resolution: 
      -----------
         INC15794278 - RxRenewal Response - Processing Error (RXE) message is not 
      It was confirmed that the eRx Holding Queue was not converting the medication
      instruction text to upper case when it was retrieved from the MEDICATION 
      INSTRUCTION file (#51). This patch addresses this problem by always converting
      the medication instruction text to upper case.
         
      Technical Resolution: 
      ---------------------
      The line tag LSIG in the routines PSOERXU6 and PSOQUTIL was modified to always
      convert the medication instruction text to upper case before returning it to
      the calling routine. 
         INC15788861 - RxRenewal Response - Approved failed to generate renewed
        
      3. INC16106925 - Pharmacy messages not assigned appropriate status by software
                       patch PSO*7*581
        
      Problem: 
      -------
      The VA Health Administration Center Denver reported that the CRN (RXCHANGE
      REQUEST - NEW) status of some old (older than 14 days) RxChange request
      records without a response were not being assigned the appropriate status CRX
      (RXCHANGE REQUEST EXPIRED) as described in the user manual.
                       order
         
      Resolution: 
      ----------
      After some research it was determined that the functionality for automatically
      marking the records mentioned above as expired worked when the user selected
      RX (PRESCRIPTION RECEIVED DATE) in the prompt below when entering the eRx
      Holding queue (Complete Orders from eRx [PSO ERX FINISH] option).  However,
      if they select PT (PATIENT(Grouped)) the software did NOT check for records
      CRN elegible for expiration to mark them as expired. Furthermore, the issue
      also seem affect RRN (RENEWAL REQUEST - NEW) records which are also supposed
      
    • 449
      DATE APPLIED:   2021-06-17 13:02:28
      APPLIED BY:   USER,SEVENTEEN
      DESCRIPTION:   
      See patch description for PSO*7.0*449.
      
    • 639b
      DATE APPLIED:   2021-07-07 00:00:00
      DESCRIPTION:   
      Backup of PSO*7.0*639 on Jul 07, 2021
       
      Warning:  Installing this backup patch message will install older versions
      of routines and Build Components (options, protocols, templates, etc.).
      Please verify with the Development Team that it is safe to install.
      
    • 639 SEQ #527
      DATE APPLIED:   2021-07-07 09:14:05
      APPLIED BY:   USER,SEVENTEEN
      DESCRIPTION:   
      This patch will address the following issues: 
      Defect Tracking System Ticket(s) & Overview:
      --------------------------------------------
      1. INC17106168 - Cincinnati VISTA application is not allowing me to renew
                       prescription orders.
         INC17248638 - Speed renewal function in HAC back door VistA is kicking
         (Duplicate)   all our users out of VistA.
       
      Problem:
      -------
      The Dayton VA Medical Center reported an <UNDEFINED> error with the Speed
       
      Renew action in the Patient Prescription Processing [PSO LM BACKDOOR ORDERS]
      option. It was confirmed that this issue was introduced by patch PSO*7.0*626.
       
      Resolution:
      ----------
      The patch address the <UNDEFINED> error and also allows the user to enter an
      ISSUE DATE up to 1 year in the past for speed renewals. Before the users were
      limited to a date no greater than 6 months. Then, it will screen out any CS
      prescriptions if the ISSUE DATE entered is greater than 6 months with the
      following message:
      1. INC17106168 - Cincinnati VISTA application is not allowing me to renew
       
       Rx# 2299064 - Rx is for a CS Drug and the Issue Date entered (Jul 17, 2020)
       is greater than 6 months.
       
        Type <Enter> to continue or '^' to exit: 
        
      Technical Resolution:
      --------------------
      Changed the code under line tags CID and CIDH to allow and ISSUE DATE value 
      of up to 366 days in the past if the variable DA is defined and the Rx is
                       prescription orders.
      non-CS or if the variable DA is not defined. And restrict a date up to 184
      days in the past if the variable DA is defined and the Rx is CS. Introduced
      code at PROCESS+22 in the routine PSORENW4 to screen out CS prescriptions if
      the ISSUE DATE value is greater than 184 days.
       
      Patient Safety Issues (PSIs):
      -----------------------------
      N/A 
       
      
    • 636b
      DATE APPLIED:   2021-07-08 00:00:00
      DESCRIPTION:   
      Backup of PSO*7.0*636 on Jul 08, 2021
       
      Warning:  Installing this backup patch message will install older versions
      of routines and Build Components (options, protocols, templates, etc.).
      Please verify with the Development Team that it is safe to install.
      
    • 636 SEQ #528
      DATE APPLIED:   2021-07-08 08:49:54
      APPLIED BY:   USER,SEVENTEEN
      DESCRIPTION:   
      RESET COPAY LIST MANAGER UPDATES
      
    • 524b
      DATE APPLIED:   2021-07-13 00:00:00
      DESCRIPTION:   
      Backup of PSO*7.0*524 on Jul 13, 2021
       
      Warning:  Installing this backup patch message will install older versions
      of routines and Build Components (options, protocols, templates, etc.).
      Please verify with the Development Team that it is safe to install.
      
    • 524 SEQ #529
      DATE APPLIED:   2021-07-13 09:23:50
      APPLIED BY:   USER,SEVENTEEN
      DESCRIPTION:   
      The description of this build can be found in the National Patch Module 
      under PSO*7.0*524.
      
    • 51 SEQ #53
      DATE APPLIED:   2001-03-05 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      1) When filling pending orders either using Complete Orders from OERR
      this type of routing pharmacy should see the routing as window, but was
      displaying as mail causing prescriptions to be mailed to the patient.
       
      3) When a refill is created for an active order with a fill date of today
      using the Patient Prescription Processing [PSO LM BACKDOOR ORDERS]
      option, and in the same session if this refill is deleted, it was observed
      that the label print routine was trying to process this refill even though
      it had been deleted. This patch fixes this problem.
      [PSO LMOE FINISH] option or through Patient Prescription Processing 
      [PSO LM BACKDOOR ORDERS] option, the issue date does not show the correct
      entry date, instead it shows the filling date. This patch fixes this
      problem.
       
      2) This patch corrects a problem when renewing prescriptions through the
      Computerize Patient Record System (CPRS) package and the routing is
      entered as administered in clinic.  When prescriptions are entered with
      
    • 630b
      DATE APPLIED:   2021-08-09 00:00:00
      DESCRIPTION:   
      Backup of PSO*7.0*630 on Aug 09, 2021
       
      Warning:  Installing this backup patch message will install older versions
      of routines and Build Components (options, protocols, templates, etc.).
      Please verify with the Development Team that it is safe to install.
      
    • 630 SEQ #530
      DATE APPLIED:   2021-08-09 12:38:57
      APPLIED BY:   USER,SEVENTEEN
      DESCRIPTION:   
      The description of this build can be found in the National Patch Module 
      under PSO*7.0*630.
      
    • 503b
      DATE APPLIED:   2021-09-09 12:32:05
      APPLIED BY:   USER,SEVENTEEN
      DESCRIPTION:   
      Backup of PSO*7.0*503 on Aug 24, 2021
       
      Warning:  Installing this backup patch message will install older versions
      of routines and Build Components (options, protocols, templates, etc.).
      Please verify with the Development Team that it is safe to install.
      
    • 503 SEQ #531
      DATE APPLIED:   2021-08-24 14:28:19
      APPLIED BY:   USER,SEVENTEEN
      DESCRIPTION:   
      The description of this build can be found in the National Patch Module 
      under PSO*7.0*503.
      
    • 641 SEQ #532
      DATE APPLIED:   2021-08-30 09:25:27
      APPLIED BY:   USER,SEVENTEEN
      DESCRIPTION:   
      1. INC17334684 - When doing a speed reprint on a suspended Rx, it is not 
         BE PRINTED using this option, use SUSPENSE FUNCTIONS Options.'
       
         Resolution:
         ----------
         Modify routine PSORXRP1 to display the message:
         #2  Rx 2297932 MAY NOT BE PRINTED using this option
         use SUSPENSE FUNCTIONS Options.
       
         Type <Enter> to continue or '^' to exit:
      giving you a warning message
       
         Problem:
         -------
         When doing a reprint from the Medication Profile and doing a reprint 
         of a suspended RX, the label doesn't print and no warning message is
         displayed to the user.  Conversely, when doing a reprint on the single
         RX (OP Medications) screen, a warning message is displayed; 'RX MAY NOT
      
    • 638 SEQ #533
      DATE APPLIED:   2021-09-09 10:14:25
      APPLIED BY:   USER,SEVENTEEN
      DESCRIPTION:   
      This patch will fix the following:
       
      The Rx reference of an original fill that is displayed on an activity log 
      record is incorrect when the CMOP site reports a change in the Rx's 
      National Drug Code (NDC). This occurs when the Rx has a suspended refill 
      and the original fill's fill date is changed.            
      
    • 561
      DATE APPLIED:   2021-09-13 11:09:35
      APPLIED BY:   USER,SEVENTEEN
    • 43 SEQ #54
      DATE APPLIED:   2001-03-19 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      1. Problem: Consolidated Mail Outpatient Pharmacy fills that have been
      2. Problem: Prescriptions that have a faulty status of 'Suspended' error
      out in CMOP code trying to update the prescription suspense comments.
       
      Resolution:
       
      The Outpatient code has been changed to test for the existence of the
      prescription in the RX SUSPENSE file (#52.5) prior to performing a CMOP
      update.
       
      3. Problem: New prescriptions with drugs that have been marked for CMOP
      returned to stock are being allowed to be re-suspended to CMOP
      but have drug warnings greater than 11 characters are being dropped into
      normal suspense without any message to the user. The intent is to have
      these prescriptions go to CMOP. 
       
      Resolution:
       
      The Outpatient code has been modified to send an appropriate message to
      G.CMOP Managers regarding the prescription and the drug warning length
      problem.
       
      Resolution:
       
      The Outpatient coding has been changed to test the prescription fill's
      CMOP activity and will not allow it to go to CMOP suspense if the status
      is not proper.
       
      
    • 59 SEQ #55
      DATE APPLIED:   2001-03-19 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      1) During the order entry process using Patient Prescription Processing
      Outpatient Pharmacy when requested from Computerized Patient Record
      System (CPRS). This problem only occurs when invalid data is found in the
      PENDING OUTPATIENT ORDERS file (#52.41).
       
      3) When renewing a prescription using Patient Prescription Processing
      [PSO LM BACKDOOR ORDERS] option, it was observed by some sites (set for
      auto suspend), that the renewed prescription is getting suspended to the
      wrong date. The renewal process calculates the FILL DATE field (#22)
      based on the NEXT POSSIBLE FILL field (#102) of PRESCRIPTION file (#52).
      It also checks to see if a record exits in RX SUSPENSE file (#52.5)
      [PSO LM BACKDOOR ORDERS] option, if the user opts to address more than
      and its PRINTED field (#2) is set. For some reason (timing delay/system
      problems), this field is not being set for CMOP drugs even when the drug
      was released. In such situations the renewal process tends to set the FILL
      DATE field (#22) to the LAST DISPENSED DATE field (#101) of PRESCRIPTION
      file (#52). This patch ensures that, for these situations, if the
      calculated FILL DATE field (#22) of PRESCRIPTION file (#52) is less than
      the current date then it gets set to the current date unless a lesser date
      than the current date is requested by the users.
      one prescription at a time simultaneously, the word "Release" is being
      displayed along with the routing type (Mail/Window) for each prescription
      even though it is not released. It had picked up the release status of a
      prior prescription. This is due to one of the variables not being killed.
      This patch fixes this problem.
       
      2) This patch corrects a problem of a refill request not being seen in
      
    • 56 SEQ #56
      DATE APPLIED:   2001-03-26 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      1) It was reported that the PATIENT STATUS field (#3) in PRESCRIPTION
       
      3) This patch corrects a problem when editing CLOZAPINE STATUS field
      (#54) of PHARMACY PATIENT file (#55) using Edit Data for a Patient in the
      Clozapine Program [PSOL EDIT] option.
       
      4) During an edit of a partial prescription, up-arrowing at any fields
      other than the partial date, causes that record to be killed instead of
      quitting the edit process. This patch fixes this problem.
       
      5) When finishing orders entered through Computerized Patient Record
      file (#52) randomly gets changed to the bingo board wait time when using
      System (CPRS), it was reported that for a patient status of value AUTH ABS
      +96 or AUTH ABS -96, it triggers the duplicate drug alert check when
      duplicates are found. This patch corrects this problem.
       
      6) This patch fixes a spelling error found in the report that is being
      generated when using the High Cost Rx Report [PSO HI COST] option.
       
      7) When renewing orders entered through CPRS or backdoor, the warning
      message that is being displayed during the duplicate drug/same class check
      against other pending orders was found to have incorrect data on the
      the Display Patient's Name on Monitor [PSO BINGO DISPLAY PATIENT] option.
      instruction field and the provider comments field. Also the data on these
      two fields were transposed. This patch fixes these problems.
       
      8) When entering the first refill using Patient Prescription Processing
      [PSO LM BACKDOOR ORDERS] option, if the user edits any field on the
      original prescription, it was reported that the refill is getting
      suspended (sites having auto suspense flag set) to the original fill date
      instead of the last dispensed date. This patch corrects this problem.
      This patch corrects this problem.
       
      2) This patch contains a fix for the HL7 messaging routine PSOHLSG1,
      which is provided to transmit Outpatient Pharmacy prescriptions to
      Optifil, (an automated dispensing unit) to include a patient's temporary
      address functionality if made active.
      
    • 63 SEQ #57
      DATE APPLIED:   2001-04-30 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      1) When discontinuing a prescription entered through Computerized Patient
      "YES".  This error was introduced by patch PSO*7*56. Routine PSODRDU1 was
      modified to correct multiple issues, with some of the redundant code
      removed. This patch fixes this problem.
      Record System (CPRS), if an up-arrow is entered at the "Nature of Order:"
      dialog and if the default entries are accepted for the remainder of the
      dialogs without entering an up-arrow, the discontinue process errors out.
      This patch corrects this problem.
       
      2) When renewing orders entered through CPRS or backdoor, the duplicate
      drug check against other pending refill orders was found to error out if
      the entry to the dialog "Discontinue Pending Order?" was entered as
      
    • 60 SEQ #58
      DATE APPLIED:   2001-04-30 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      1. When using the Start Bingo Board Display [PSO BINGO START] option, to
      is not always being built into the DISPENSING INSTRUCTIONS field (#.01) of
      the DISPENSING INSTRUCTIONS sub-file (#52.4124) of the PENDING OUTPATIENT
      ORDERS file (#52.41) when the order comes to the OP package. This is the
      information that displays as the Possible SIG on the OP finish screen.
      This patch resolves that problem.
       
      3. This patch fixes a problem when using the Label/Profile Monitor Reprint
      [PSO B] option, to reprint labels onto another printer. It was using the
      control codes of the original printer instead of the selected printer.
      restart a stopped bingo board, a task number is assigned by the Task
      Manager to queue this task. The assigned task number is not being set in
      the TASK # field (#15) of GROUP DISPLAY FILE (#59.3), for the selected
      bingo board display. This patch fixes this problem.
       
      2. When an order is transferred in Computerized Patient Record System
      (CPRS) from Inpatient Medications to Outpatient Pharmacy (OP), or a change
      is done on an OP order in CPRS, the Noun that is associated with the order
      
    • 62 SEQ #59
      DATE APPLIED:   2001-04-30 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      When a prescription is reinstated using the Discontinue Prescription(s)
      Discontinue Prescription(s) [PSO C] option.
      [PSO C] option, and immediately afterwards the Patient Prescription
      Processing [PSO LM BACKDOOR ORDERS] option is used to edit the SIG of a
      prescription, the change of SIG creates a new order. The generated order
      has a different dispensed drug. It contains the drug of the prescription
      that was most recently reinstated using the Discontinue Prescription(s)
      [PSO C] option. This could result in dispensing the wrong drug to the
      patient. In order to correct this problem this patch insures that all
      related variables are killed appropriately when quitting from the
      
    • 64 SEQ #60
      DATE APPLIED:   2001-06-08 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      1) Currently when a prescription is renewed either using the Patient
       
      2) This patch corrects a problem of an undefined variable error that
      can occur during the speed renewal process within the Patient Prescription
      Processing [PSO LM BACKDOOR ORDERS] option.
      Prescription Processing [PSO LM BACKDOOR ORDERS] or Complete Orders from
      OERR [PSO LMOE FINISH] option, the FILL DATE field (#22) of the
      PRESCRIPTION file (#52) in the renewed prescription is calculated based on
      the LAST DISPENSED DATE field (#101) of the PRESCRIPTION file (#52). The
      renewal process does not check whether the last refill was released or a
      label has been printed. If such a refill existed, the FILL DATE field
      (#22) of the PRESCRIPTION file (#52) of the renewed prescription was being
      set to a date far into the future. This patch corrects this problem.
      
    • 65 SEQ #61
      DATE APPLIED:   2001-06-25 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      This patch corrects the following problems when using the Site Parameter
      NAME: ALBANY//. Deleting a site could lead to an "undefined error" problem
      as reported in NOIS AMA-0700-71379. This patch prevents the users from
      deleting a site.
       
      This patch also updates the Data Dictionary of the NAME field (#.01) of
      the OUTPATIENT SITE file (#59).
      Enter/Edit [PSO SITE PARAMETERS] option:
       
      1) The dialog "Would you like to see all site parameters for this
      division? Y//", only responds to upper case "Y". Now the routine is
      patched to accept both upper and lower case responses of "y".
       
      2) Currently the users have the option of deleting a site from the
      OUTPATIENT SITE file (#59) by entering "@" key at the dialog
      
    • 8
      DATE APPLIED:   1999-04-16 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
       
      2. Another problem occurred when using the Pull Early from Suspense option.
      If the routing was changed while pulling a prescription from suspense,
      then a "^" was entered at the Label prompt, the original routing was
      not restored to the prescription, which caused prescriptions that
      were originally intended to be filled at the CMOP to be printed locally.
       
      Routines: PSOLBL, PSORXL, PSOSUPAT, PSOSUPOE, PSOSUPRX
       
      3. When sites have install the CMOP package but are not actively transmitting
      to a host facility and reinstates discontinued prescriptions with a drug that
      1. This patch fixes problems involving pulling prescriptions from suspense
      has been marked for use for CMOP they are being suspended for transmission to a
      CMOP host facility. Routine: PSOCAN2
       
      4. A problem occurred when trying to discontinue Pending orders for a patient
      by using the Discontinue Prescription(s) option. Routine: PSOCAN1
      to fill locally that were originally suspended for CMOP. If a prescription
      is suspended for CMOP, and is pulled from suspense using the Patient
      Prescription Processing option, then an up-arrow is entered when the user
      is prompted for a label action, the CMOP INDICATOR field in the RX SUSPENSE
      File would have been set to "P", for PRINTED LOCALLY, although the label
      never printed
       
      
    • 66 SEQ #62
      DATE APPLIED:   2001-08-02 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      1) When using the Action Profile (132 COLUMN PRINTOUT) [PSO ACTION
      provided by the Integration Agreement (IA) 1281. Currently this entry
      point does a form feed at the beginning of the report. The AICS
      package requests that this form feed be suppressed. Now the routine is
      patched to suppress a form feed at the beginning of the report when the
      passing variable PSONOPG (as per IA 1281) is set to 2.
      PROFILE] option, the FILL DATE field (#22) of the PRESCRIPTION file (#52) 
      in the report, at times shows the date as "--1700". This is because the
      FILL DATE field (#22) of the PRESCRIPTION file (#52) is set to null when
      the original prescription is on HOLD status. This patch fixes this
      problem.
       
      2) The AUTOMATED INFO COLLECTION SYS (AICS) package requests a
      modification to routine PSOSD1. Access to the entry point DFN^PSOSD1 is
      
    • 61 SEQ #63
      DATE APPLIED:   2001-08-02 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      1. Problem: Prescriptions that need to be resubmitted to CMOP with a CMOP
      2. Problem: A concurrent window and a mail fill for a single prescription
      are being allowed to be processed with the mail fill going into CMOP
      suspense. 
       
      Resolution:
       
      The code has been changed to test for and block a request of a multiple
      fill for the same prescription being sent to CMOP.
      status of 'Not Dispensed' are failing internal testing and are blocked
      from being transmitted to CMOP.
       
      Resolution:
       
      The internal testing code has been corrected to allow resubmission of
      prescriptions to CMOP.
       
      
    • 72 SEQ #64
      DATE APPLIED:   2001-09-26 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
       1. During the completion process of renewing a prescription, the
       leading 3 digits as numeric, otherwise it reports an undefined error
       when using the Archive CMOP Data [PSX ARCHIVE] option.
        
       3. When using the All Reports [PSO MGMT MONTHLY ALL REPORTS] option,
       the date entry for the prompt "Beginning    MONTH/YEAR :", accepts only
       the full name of the month and the 4 digit year. This patch corrects this
       problem to allow any valid month/year format.
       software gathers the co-pay information for patient status SC LESS THAN
       50%. During this process, there is a possibility of getting an undefined
       error. This patch fixes this problem.
        
       2. This patch modifies the Input Template of the SITE NUMBER field (#.06)
       of the OUTPATIENT SITE file (#59) from eight free text characters to
       three numeric and five alphanumeric characters. The Consolidated Mail
       Outpatient Pharmacy (CMOP) V. 2.0 package expects this field to have the
      
    • 69 SEQ #65
      DATE APPLIED:   2001-09-26 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
       This is an emergency patch and should be installed as soon as possible.
       patients. When the software displays a profile it uses the field and
       cross-references to gather the prescriptions to be listed. If a corrupted
       node pointed to a prescription for a different patient, the wrong
       prescription would display on the profile. In some cases, a prescription
       may have been discontinued because a Date of Death or an Admission was
       entered for the patient with a corrupt cross-reference. This patch
       ensures that all bad entries in the sub-file and corresponding "A",
       cross-references are deleted. During this process, it generates a mail
       message to the installer for each Outpatient Site entry, listing those
       patients that may have had a prescription discontinued because a Date of
       
       Death or an Admission was entered for the patient with a corrupt cross-
       reference. These prescriptions must be manually reviewed and if
       appropriate reinstated. The patch installer should forward the mail
       message to the Pharmacy Application Coordinator, or the appropriate
       Outpatient Pharmacy Personnel, for their review and correction. It will
       send summary information to G.PL2 PATCH TRACKING group on FORUM so that
       counts of bad nodes by site can be collected. This patch will also scan
       through the PRESCRIPTION file (#52) using the "AD" cross-reference and
       will check if a corresponding entry exists in the PHARMACY PATIENT file
       (#55). The software will provide a count of missing entries in a separate
       The Upstate New York HealthCare System reported a problem concerning
       mail message that will be sent to G.PL2 PATCH TRACKING on FORUM for their
       review.
       
       We recommend re-indexing the "B" cross-reference of the PHARMACY
       PATIENT file (#55), during non-peak hours or when the number of pharmacy
       users on the system is at a minimum any time after completion of this
       job.
        
       A subsequent patch will be released to provide additional safeguards in
       the event that the cross-reference gets corrupted in the future.
       outpatient pharmacy profiles containing prescriptions for patients other
       than the patient selected. The problem happened as a result of corrupted
       data in the PRESCRIPTION PROFILE sub-file (#55.03) of the PHARMACY
       PATIENT file (#55). This field links the PHARMACY PATIENT file (#55) to
       the PRESCRIPTION file (#52). The link to the PRESCRIPTION file (#52) and
       the "A", cross-reference on this sub-file were corrupted for some
      
    • 67 SEQ #66
      DATE APPLIED:   2001-09-26 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      Problem: Prescriptions can be edited from mail to window and then released
      while the prescription still has an active Consolidated Mail Outpatient
      Pharmacy (CMOP) status. Those statuses are Transmitted, Dispensed, and
      Retransmitted.
       
      Resolution:
       
      The internal code has been corrected to block the facilities from
      releasing prescriptions that have an active CMOP status.
      
    • 46
      DATE APPLIED:   2001-09-26 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      1) The Pharmacy Ordering Enhancements (POE) project provides enhancements
      Inpatient Medications and Outpatient Pharmacy applications.  This project
      directly supports Computerized Patient Record System (CPRS), which is a
      key component of Veterans Health Administration's (VHA) plan to expand
      support for clinical operations. Additionally, order checks will be
      provided for medication orders for which a dispense drug has not been
      selected during the CPRS order entry process. It is also intended as a way
      to help meet the goal outlined in Objective 8, Action 1 in the
      Prescription for Change, which outlines the need to coordinate
      national/Veterans Integrated Service Network (VISN) formularies and share
      drug treatment guideline information. This project will promote system-
      to Pharmacy Data Management (PDM) V. 1.0, Inpatient Medications
      wide sharing of drug reviews and treatment guidelines thereby enhancing
      patient safety.
       
      This project consists of four patches that work together to accomplish
      these goals listed in order of install:
       
           PSO*7*46
           OR*3*94
           PSS*1*38
           PSJ*5*50
      V. 5.0, Outpatient Pharmacy V. 7.0, and Order Entry/Results Reporting
       
       2) This patch corrects a problem as reported in CON-0300-11347.
      When reinstating a Prescription an order alert was displayed for a
      duplicate drug.  The alert was occurring incorrectly for the Prescription
      that was being reinstated.
       
       3) As reported in NYH-0300-12247 and BIL-1100-30086 the NSC/SC prompt is
      not asked consistently between Outpatient Pharmacy and Computerized
      Patient Record System (CPRS) packages.  This patch provided an enhanced
      interface for both packages to use when placing orders. 
      (OE/RR) V. 3.0 medication ordering dialogues to eliminate redundant entry
       
       4) As reported in SAG-0500-41497 when renewing prescription request from
      CPRS the screen was not displaying correctly.   This patch corrects this
      problem.
       
       5) As reported in AMA-0900-71796 when renewing prescriptions that had
      a cosigner tied to the provider and the cosigning provider changed the
      cosigner was not being updated to show the new cosigning provider.
       
       6) As reported in NYH-0900-10553 cost in the PRESCRIPTION file (#52) for
      of drug information during medication order entry, provide a more
      the drug would not allow a cost higher than 999 with 4 decimals.  This
      patch will allow cost to be entered for all fills to be 9999 with 4
      decimals.
       
       
      consistent medication order entry process, provide expanded order
      checking, display documented drug formulary statuses and corresponding
      restriction/guidelines to the provider and pharmacist at the time of order
      entry, and improve the process of medication order transfer between
      
    • 74 SEQ #68
      DATE APPLIED:   2001-09-26 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
       
      when finishing pending orders.
       
      3. This patch runs a post-install routine to look for pre-POE pending orders
      without dispense drugs and remove data stored on the wrong node.
      1. When entering new outpatients into the Pharmacy Patient file (#55), the
      patient's prescription status is a required data element.  When entering
      this data element into the Pharmacy Patient file (#55) eligibility and
      disabilities will display to help the pharmacy user answer this prompt.
       
      This patch also corrects a typo.
       
      2. This patch corrects a problem where a missing dosage check did not work
      
    • 58 SEQ #69
      DATE APPLIED:   2001-10-16 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      This patch is an enhancement to the Outpatient Pharmacy routine that
      gathers and returns patient and prescription information for the Hepatitis
      C Extract project. Prior to this patch, data was returned without
      integrated site consideration. With the release of this patch, a check
      will now be done on original fill prescriptions. If the original fill
      prescription information has been moved to another site, that finding will
      not be included in the extract.
      
    • 68 SEQ #70
      DATE APPLIED:   2001-11-06 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      A problem has been found where it is possible for an Outpatient Pharmacy
       
      As part of the Pharmacy Ordering Enhancements (POE) project (patch
      PSO*7*46 for Outpatient Pharmacy) a change will be made to assign Routine
      as the priority to an order received from CPRS that does not have a
      priority.
       
      What this patch will do is run a Post-Install routine that will look for
      Pending Outpatient Orders that do not have a Priority assigned. A list of 
      Patients with these orders will be sent in a mail message to the person
      installing the patch. This mail message should then be forwarded by the
      order to be entered through Computerized Patient Record System (CPRS), and
      patch installer to the Pharmacy Application Coordinator, or the
      appropriate Outpatient Pharmacy Personnel, for their review.
      the priority of the order to be deleted in CPRS, before the order is sent
      to Outpatient Pharmacy. When finishing orders in Outpatient Pharmacy using
      the Complete Orders from OERR [PSO LMOE FINISH] option, Priority is one of
      the sort selections. It has been reported that orders were not being
      finished because orders had been sent without a priority, and all
      finishing in Outpatient Pharmacy was done by priority, and not by any
      other means of sorting.
      
    • 75 SEQ #71
      DATE APPLIED:   2001-11-06 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      1. This patch corrects an undefined error that could occur when trying to 
      defaulting for the second order.  
       
      4. When speed renewing POE orders the SIG does not display.  
       
      5. Site reported not being able to edit the verb when finishing pending
      renewals for phase 2 of POE. The site was instructed to select the field for
      dosage and then type ^VERB to jump to the Verb field.  In doing this you
      are prompted twice for schedule, duration and conjunction.  
      display Special Instructions (SIG) for a prescription entered before
      PSO*7*46.  
       
      2. Added check for missing SIG before filing a renewal.  
       
      3. When speed renewing through Outpatient Pharmacy and the first order is a
      pre-POE order with a possible dosage and the second order is a pre-POE order
      with a local possible dosage, the quantity from the first order is
      
    • 10
      DATE APPLIED:   1999-04-16 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      This patch corrects the finding as reported by the QA review.  Most if not
       
       PSOARCLT
       PSOARCTG
       PSOARX
       PSOB
       PSOBGMG1
       PSOBGMG2
       PSOBSET
       PSOCPC
       PSOCPTRI
      all changes will be transparent to the user.
       PSOCST11
       PSOCST2
       PSOCST4
       PSODELI
       PSODGDGI
       PSOHLEXP
       PSOHLSG1
       PSOHLSN1
       PSOHLUP1
       PSOLSET
       
       PSOORCPY
       PSOORNW2
       PSOR52
       PSOSTART
       PSOSULB1
       PSOSUP
       PSOSURST
       PSOSUTL
       
      Also added NDF file structure changes to routines PSOHLSN1, PSOHLSG1, and
       Removal of nonstandard reference to ^DPT(.
      PSOHLSN.
       Removal of naked global references at the start of lines.
       Added timeouts to locking global.
       Removal of nonstandard reference to ^%ZIS(1, and ^%ZIS(2,.
       Write commands in data dictionaries changed to EN^DDIOL.
       Variable DT sets were changed to supported $$DT^XLFDT.
      
    • 79 SEQ #72
      DATE APPLIED:   2001-12-10 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
       When Pharmacy is finishing a Renewal entered through Computerized Patient
       Record System (CPRS), for Consolidated Mail Outpatient Pharmacy (CMOP)
       sites, if the Routing, MAIL/WINDOW field (#11) of the PRESCRIPTION file
       (#52) is edited from "Mail" to "Window" when having the LOGIN DATE field
       (#21) a date prior to the current date and the FILL DATE field (#22) of
       the PRESCRIPTION file (#52) set for today's date with the intention of
       dispensing the prescription locally, there is a possibility of such a
       prescription getting suspended for CMOP. This patch fixes this problem.
      
    • 77 SEQ #73
      DATE APPLIED:   2001-12-10 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
       1) This patch makes the DAYS SUPPLY field (#.041) of the PARTIAL DATE
       possibility of viewing prescriptions belonging to other patients. This
       patch fixes this problem.
       
       3) When deleting a device from the DEVICE file (#3.5), using FileMan and
       requesting the software either to delete all pointers or changing its
       pointers to point to a different device, it was found to error out at
       times. During the process of re-pointing the device, FileMan would
       encounter an orphaned multiple (#59.30001). This multiple may have been
       used by Outpatient Pharmacy at some time, but they are no longer needed.
       This patch removes this multiple.
       multiple (#52.2) of the PRESCRIPTION file (#52), a required field as
       requested by the NOIS ISH-0401-40089. The Data Dictionary is not changed
       here. The fix is made in the routine PSORXPA1.
       
       2) When using the Status of Patient's Order [PSO BINGO STATUS] option,
       or using the Patient Prescription Processing [PSO LM BACKDOOR ORDERS]
       option, and selecting the OTH (Other OP Actions) hidden action, and then
       selecting the DO (Display Orders' Statuses) option, there is a
      
    • 80 SEQ #74
      DATE APPLIED:   2001-12-10 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
       This patch adds the Free Text Dosage Report [PSO DOSAGE REPORT] option,
       Dosages selectable instead of requiring it to be typed in, during the
       medication order entry process.
       as an addition to the Output Reports [PSO OUTPUTS] menu option. It
       provides a list of drugs for those prescriptions where the DOSAGE ORDERED
       field (#.01) of the MEDICATION INSTRUCTION sub-file (#52.0113) of the
       PRESCRIPTION file (#52), has a free text entry or a dosage that results
       in the calculation of the number of tablets. This report is designed to
       help in the identification of all such entries so that the sites can
       determine if these dosages should be added to the LOCAL POSSIBLE DOSAGE
       sub-file (#50.0904) of the DRUG file (#50), making the Local Possible
      
    • 71 SEQ #75
      DATE APPLIED:   2001-12-10 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      This patch reflects changes made to copay charges by Public Law 106-117, 
      priority groups 2-6. Provisions are included to automatically increase 
      the copayment and the cap amount under certain conditions.  
       
      Effective on January 1, 2002, a medication is exempt from copay charges 
      if it is used to treat the following conditions:
       
         Vietnam-era herbicide (Agent Orange) exposure
         Radiation exposure
         Exposure to environmental contaminants during Persian Gulf War Service
         Military Sexual Trauma 
      The Veterans Millennium Health Care and Benefits Act. Public Law 106-117 
         Cancer of the Head and/or Neck 
        
      The Outpatient Pharmacy patch PSO*7*71 and Consolidated Mail Outpatient
      Pharmacy (CMOP) patch PSX*2*35 must be installed and implemented by
      facilities no later than December 31, 2001. On January 1, 2002, the new
      medication copay exemptions provided by patch PSO*7*71 will go into
      effect. Changes to increase the amount of medication copay and to
      establish the annual copay cap will go into effect when the law is
      approved and signed.
       
      will not go into effect until early 2002. The exact effective date is not 
       
      A post-installation routine is included in patch PSO*7*71 to review 
      prescriptions entered over the last year and to populate, whenever 
      possible, the new SERVICE CONNECTED field (#116) of the PRESCRIPTION
      file (#52). This routine queues a background task to look at all
      prescriptions entered over the last year and to attempt to populate the
      new SERVICE CONNECTED field (#116) of the PRESCRIPTION file (#52) based on
      the prescription data. If the COPAY TRANSACTION TYPE field (#105) of the
      PRESCRIPTION file (#52) is set to "2," this indicates that the Service
      Connected question was asked for this prescription, and the response was
      known at this time. Prior to the changes that will be implemented with 
      "NO." In these cases, the software will set the new SERVICE CONNECTED
      field (#116) to "NO." If the COPAY TRANSACTION TYPE field (#105) of the
      PRESCRIPTION file (#52) is null, and the drug is not marked as a supply or
      as an investigational drug, and the Rx Patient Status of the prescription
      contains "50," and either the "<" character or the words "LESS THAN" (for
      'SC LESS THAN 50%'), and the COPAY INCOME EXEMPTION STATUS field (#.04) of
      the BILLING PATIENT file (#354) is set to "NON-EXEMPT, " then the software
      will set the new SERVICE CONNECTED field to "YES."
       
      When the job is complete, a mail message will be sent to the person who 
      Public Law 106-117, certain veterans paid a $2 copayment for each 30-day 
      installed the patch.
       
       
      Complete information for all the changes included in this patch can be 
      found in the Outpatient Medication Copay Release Notes document. In 
      addition to the Release Notes, there are changes to the Outpatient 
      Pharmacy Technical Manual and the Outpatient Pharmacy User Manual.
       
       
      Sites may retrieve documentation in one of the following ways:
      or less supply of medication furnished for the outpatient treatment of a 
       
      (1) The preferred method is to FTP the files from
          download.vista.domain.ext, which will transmit the files from the
          first available FTP server.
       
      (2) Sites may also elect to retrieve documentation directly from a
          specific server as follows:
       
          Albany          ftp.fo-albany.domain.ext
          Hines           ftp.fo-hines.domain.ext
      nonservice-connected disability or condition. With Public Law 106-117, 
          Salt Lake City  ftp.fo-slc.domain.ext
       
       
      The documentation distribution includes: 
       
          FILE NAMES                 DESCRIPTION
               
          OP_Med_Copay_RN.pdf        Release Notes
          OP_7_0_P71_UM_CP.pdf       User Manual (change pages)
          OP_7_0_P71_TM_CP.pdf       Technical Manual (change pages)
      the copayment amount will increase from $2 to $7. An annual copayment cap 
          OP_7_0_UM_R1101.pdf        User Manual (updated)
          OP_7_0_TM_R1101.pdf        Technical Manual (updated)
       
       
      (3) Documentation can also be retrieved from VISTA Document Library (VDL)
          on the VA Intranet at the following address,
          http://vista.domain.ext/vdl.
      of $840 will be set through calendar year 2002 for veterans in enrollment 
      
    • 76 SEQ #76
      DATE APPLIED:   2001-12-10 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      Problem: The testing for duplicate drugs is bringing back false 
      duplicates from the Consolidated Mail Outpatient Pharmacy (CMOP) module 
      when the PSO LM BACKDOOR ORDERS option is used.
       
      Resolution: The code has been corrected by clearing a variable prior to 
      testing the prescription.
      
    • 82 SEQ #77
      DATE APPLIED:   2002-01-08 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
       1) When the PP Pull Rx (OP) protocol (hidden action) is used in the
       prescription).
       
       2) When entering a new prescription through backdoor pharmacy and if the
       prescription is put on hold then the label LABEL QUEUE/CHANGE
       PRINTER/SUSPEND or '^' to bypass Q// prompt is displayed. If the new
       prescription is the only order in the session then no label is required
       therefore, this prompt should not be displayed. This patch fixes this
       problem.
       
       3) In the API's OCL^PSOORRL and OEL^PSOORRL, provided by Outpatient
       backdoor pharmacy to fill a suspended prescription early, it sometimes
       Pharmacy V. 7.0, there is a possibility of an undefined error occurring
       when the "SIG" node of the PRESCRIPTION file (#52) for the prescription
       in process is missing. This patch corrects this problem.
       errors out. This is due to a bad "B" cross-reference entry for that
       prescription in the RX SUSPENSE file (#52.5). This patch will ensure that
       the corresponding entries of such a prescription in the RX SUSPENSE file
       (#52.5) are complete when building the patient medical profile. If
       the entries are incomplete this patch will clean up the bad "B"
       cross-reference entry in the RX SUSPENSE file (#52.5) and change the
       STATUS field (#100) of the PRESCRIPTION file (#52) to 0 (an active
      
    • 83 SEQ #78
      DATE APPLIED:   2002-01-08 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
       
      complaints from patients about their full Social Security Number (SSN)
      printing on their prescription reorder documents.  Currently the SSN at
      the top of the refill document shows the last 6 digits, however the full SSN
      shows next to the patient's name on the last page, just above the
      NARRATIVE REFILLABLE RX document.  This patch will change all
      instances of the patient's SSN on the reorder documents to display only the
      last 6 digits.  
       
       
       
      This patch addresses the following concerns:
       
      1. When entering an outpatient pharmacy prescription a schedule 
      is required to complete the order. If the user should enter a question
      mark at the schedule field prompt to list the available choices, a list is
      not displayed as expected. This patch corrects this problem.
       
      2. Central Texas Veterans Health Care System has received multiple
      
    • 73 SEQ #79
      DATE APPLIED:   2002-01-08 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
       When editing a prescription through the pharmacy backdoor, if the
       Prescriptions [PSO EXPIRE PRESCRIPTIONS] and the Manual Auto Expire Rxs
       [PSO MANUAL AUTO EXPIRE] options both use the "AG" cross-reference to
       flag prescriptions past the expiration date as expired and they do
       not flag those prescriptions that had a missing "AG" cross-reference
       entry. Hence, the expired prescriptions show as active, especially when
       using the Orders Tab protocol from the Computerized Patient Record System
       (CPRS) package. This patch ensures that the "AG" cross-reference is reset
       only when the expiration date changes.
       
       The Expire Prescriptions [PSO EXPIRE PRESCRIPTIONS] and the Manual Auto
       following fields are edited: QTY field (#7), DAYS SUPPLY field (#8) or #
       Expire Rxs [PSO MANUAL AUTO EXPIRE] options are patched to have an
       additional check to ensure that the expiration date subscript in the
       "AG" cross-reference is equal to the EXPIRATION DATE field (#26) of the
       PRESCRIPTION file (#52), and to flag those prescriptions that have
       expired in Outpatient Pharmacy but show as active in the CPRS Orders Tab
       as expired.
       
       The Expire Prescriptions [PSO EXPIRE PRESCRIPTIONS] option flags
       prescriptions that have passed the expire date as expired and sends an
       HL7 message across to CPRS to flag those prescriptions as expired.
       OF REFILLS field (#9), of the PRESCRIPTION file (#52), the software
       Currently, this functionality not only sends the expire message for
       expired prescriptions but also for discontinued prescriptions, and as a
       result in CPRS the discontinued prescriptions are flagged as expired,
       which is incorrect. This patch will ensure that only expired
       prescriptions are sent across to CPRS to be flagged as expired.
       
       Note: There is an optional site selectable post-install background job
       included in this patch. This job will make sure that the "AG"
       cross-reference of the EXPIRATION DATE field (#26) of the PRESCRIPTION
       file (#52) is properly set, starting from the date Outpatient Pharmacy V.
       recalculates the EXPIRATION DATE field (#26) of the PRESCRIPTION file
       7.0 was installed. It will also reset the statuses of all those
       discontinued prescriptions which were flagged as expired in CPRS by the
       Expire Prescriptions [PSO EXPIRE PRESCRIPTIONS] option back to
       discontinued statuses. At the completion of this job, a MailMan message
       with the subject "PATCH PSO*7*73 - 'AG' Cross-reference Cleanup
       Information", will be sent to the installer notifying the time of
       completion. The date/time to queue this job is site selectable and can be
       queued to run during the installation of the patch or at another time by
       calling the entry point BEG^PSOPOST from programmer mode. Also the site
       could use this entry point at any time to re-start the cleanup process in
       (#52) and also kills the corresponding "AG" cross-reference entry of the
       case the job was interrupted for any reason.
       
       For sites experiencing the problem reported above, i.e., prescriptions
       past the expiration date appearing as active, it is recommended that
       they also run the Manual Auto Expire Rxs [PSO MANUAL AUTO EXPIRE] option
       any time after the completion of the Post-Install run of this patch.
       PRESCRIPTION file (#52). In the case when the expiration date remains the
       same after the edit process, it does not reset the "AG" cross-reference
       entry and therefore the link to the PRESCRIPTION file (#52) for that
       prescription from the "AG" cross-reference is lost. The Expire
      
    • 81 SEQ #80
      DATE APPLIED:   2002-02-04 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
       The routine PSOORDRG contains an  Application Programmer Interface
       patch by itself will produce no changes, visible or otherwise. The
       original NOIS submitted to CPRS is DUR-0801-32713.
       
       
       Associated NOISs:
       =================
       DUR-0801-32713
       (API),  IA #2190, used by the Computerized Patient Record System
       (CPRS). This API requires modification to accommodate changes to the
       incoming data passed in by CPRS. The intended effect of this change is to
       improve CPRS order checking functionality, specifically, to help CPRS
       distinguish between Inpatient orders and Outpatient orders when
       performing order checks. The changes described will not be implemented
       until OR*3*123 and PSJ*5*56 are also installed. However, this patch does
       not formally require OR*3*123 or PSJ*5*56, and installation of this
      
    • 93 SEQ #81
      DATE APPLIED:   2002-02-04 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
       
      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.
       
      
    • 11
      DATE APPLIED:   1999-04-16 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
       
      4. Removed commented out code. Routine: PSOBKDED, PSOORNEW.  Also in the routine PSOORNEW, fixed an undefined error.  NOIS: HUN-0298-22095
       
      5. Added Prescription Delivery to Patient Information screen. Routine: PSOORUT2
       
      6. Added timed lock to globals.  Routine: PSOPRVW, PSONEW
       
      7. Newed PSODRUG variable in routine PSOCAN
       
      8. In the supported reference PSOORDER which returns prescription data, the external value of the Rx Patient Status was added.  Added $G around global reference to prevent a possible undefined error. Routine: PSOORDER.
       
      1. Second line of routine has incorrect package release month and year.  Second line of all routine should read as follows prior to any patches being applied: <tab>;;7.0UTPATIENT PHARMACY;;DEC 1997
      9. Changed a $Select statement to make it consistent with other displays when showing method of pick up.  Routine: PSOBGMG3
       
      10. Added additional data validation checks for prescription being renewed.
      Routine: PSOORNE5, PSORENW, PSORENW0, PSORENW4
       
      11. As determined by the Programming Conventions and Standards, no line can
      start with a naked global reference. Routines: PSORXPA1, PSORXRP1.
       
      12. When requesting a reprint of a prescription label and the prescription
      was entered through CPRS there's the possibility that the SIG will not
      Routines: PSOCMOPB, PSOCPDUP, PSODRDUP, PSOLMRN, PSONGR, and PSORDS
      display to the screen. Routine: PSORXRP2
       
      13. Added code to removed date an Rx was canceled when renewed.
      Routine: PSORN52
       
      14. Fixed problem of CMOP barcoded refills from being printed locally.
       
      15. Fixed duplicate active drug problem.
       
      16. Along with PSO*7*7, will now show Provider Instruction enter through
       
      CPRS in the Pharmacy options.
       
      17. Added # of refills prompt for speed renewing.
       
      18. Added a PSNDF reference change to comply with new file structure.
      2. Added a 'Press to Continue' prompt for the Order Summary list.
        NOIS: WNY-0398-11868.  Routine: PSOORNE1
       
      3. Added check for on the fly conversion when using the Batch Barcode Refill/Renew option.  Routine: PSOBBC. NOIS: CTX-0398-70637
       
      
    • 84 SEQ #82
      DATE APPLIED:   2002-02-07 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
       1) When finishing pending orders using the Complete Orders from OERR [PSO
       ORDERS file (#52.41) is missing. This patch corrects these problems.
       
       2) When finishing pending orders through the backdoor or using the
       Complete Orders from OERR [PSO LMOE FINISH] option, if multiple orders
       are selected, the BY Bypass ListMan action goes back to the patient
       profile instead of going to the next order in the selection list. This
       patch fixes this problem.
       LMOE FINISH] option, if PATIENT is selected for the sort prompt "Select
       By:", and ALL is selected for the prompt "All Patients or Single
       Patient:", it was found that the software does not show the medication
       profile of every patient who has pending orders. The problem is that if
       the software encounters a renewal and if that order is skipped by the
       user without completing it, then the process will quit instead of
       continuing with the rest of the patients. Also there is a possibility of
       getting an undefined error if the zero node of the PENDING OUTPATIENT
      
    • 90 SEQ #83
      DATE APPLIED:   2002-02-26 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      1. When using the Free Text Dosage Report [PSO DOSAGE REPORT] option, 
      [PSO RX] option when it puts you back to the VMS prompt. This patch 
      corrects this problem.
       
      3. When multiple edits are done while finishing a pending order, there is 
      a possibility of an undefined variable error occurring. This patch fixes
      this problem.
       
      4. When using the Rx Verification by Clerk [PSO VR] option, for pre POE 
      orders that do not have a SIG, there is a possibility of the patient 
      instructions not getting appended to the constructed SIG. This patch
      there is a possibility of a "string too long" error occurring when the 
      corrects this problem.
      date range selected is for a long period. This patch corrects this 
      problem.
       
      2. With programmer access only, most Outpatient Pharmacy options can be 
      executed by entering the option name at the XUP routine's, "Select OPTION 
      NAME:" prompt. On quitting from these options the software takes you back 
      to the MUMPS programmer prompt except when using the Rx (Prescriptions) 
      
    • 91 SEQ #84
      DATE APPLIED:   2002-02-26 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      This patch addresses the following concerns: 
       
      1. When entering an outpatient pharmacy prescription a schedule is required
      to complete the order. If the user enters a question mark at the "Schedule:"
      prompt to list the available choices, a list is not displayed as expected.
      This patch corrects this problem.  
       
      2. This patch corrects a possible undefined error when entering new
      Outpatient Backdoor Pharmacy orders. 
      
    • 87 SEQ #85
      DATE APPLIED:   2002-02-26 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      1. There is the potential for an undefined error to occur when renewing 
      In addition to correcting the problem, this install will loop through the 
      entire PRESCRIPTION file (#52) and look for the ^PSRX(DA,"SIG") node
      that has only an up-arrow (^), is a renewal, and has a pointer to the prescription
      that was renewed and then copy the SIG to the prescription with the missing SIG. 
      This looping that is a post-install routine could take up to an hour or more. 
      It is recommended that this install be queued to a printer so a terminal is
      available during the install.  
       
      2. With the release of the Pharmacy Ordering Enhancement (POE) patch the List
      Manager action, Other OP Actions [PSO LM HIDDEN OTHER] was mistakenly
      prescriptions that were entered using the Outpatient Pharmacy v.7.0
      Removed from the List Manager Protocol, Outpatient Pharmacy Hidden Actions #2
      [PSO HIDDEN ACTIONS #2]. This patch restores Other OP Actions [PSO LM HIDDEN
      OTHER] protocol as an item to the Outpatient Pharmacy Hidden Actions #2 [PSO 
      HIDDEN ACTIONS #2] protocol.  
      package prior to installing the Pharmacy Ordering Enhancement (POE)
      patch.  After POE has been installed and renewing these prescriptions from 
      the PRESCRIPTION file (#52), the SIG field (#10) could be blank which causes
      an undefined error when the software attempts to display these prescriptions to
      the screen.  This error does not affect prescriptions entered using Computerized
      Patient Record System (CPRS).  
       
      
    • 89 SEQ #86
      DATE APPLIED:   2002-02-26 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      This patch addresses the following concerns:
       
      When running the following options: Nightly Rx Cost Compile [PSO COSTDAY 
      NIGHTJOB], Monthly Rx Cost Compilation [PSO COSTMONTH], and Daily Rx Cost [PSO
      COSTDAY], a possible undefined error could happen if there is a bad 
      cross-reference in the REFILL DATE sub-file (#52.1) on the REFILL DATE field
      (#.01).  This patch corrects this potential error.  
       
      
    • 96 SEQ #87
      DATE APPLIED:   2002-02-26 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      1. When renewing a prescription and editing it before finishing the order,
      problem.
       
      3. Prior to the Pharmacy Ordering Enhancements patches, the Dispense 
      Drug of a prescription could be edited and not create a new order. This
      would happen if the new Dispense Drug was matched to the same Pharmacy
      Orderable Item as the old Dispense Drug. When this occurred, the drug was
      not updated in Computerized Record Patient System (CPRS). If the order is
      then renewed through CPRS after the install of the Pharmacy Ordering 
      Enhancements patches, and if this order can have Possible Dosages, it is 
      possible that Dosages are automatically assigned to the order by CPRS 
      and if the nature of order was marked as "Verbal", there is a possibility
      based on the original order information. When the Pending Renewal is 
      displayed in Pharmacy, the Dispense Drug is always replaced with the 
      current Dispense Drug of the order. This could lead to the Possible 
      Dosages not matching the Dispense Drug on the Pending Renewal.
       
      To fix this problem, when the Renewal is done in CPRS, Pharmacy will 
      check the Drug from the PRESCRIPTION file (#52) against the Drug in the
      ORDER file (#100), and if it is different, the order will be
      Non-Renewable through CPRS.
       
      of the renewed order not triggering an alert to the provider for his 
      This functionality of this patch will not be seen until both this patch 
      (PSO*7*96) and the CPRS patch (OR*3*134) are installed. It will not cause
      any problems if the Outpatient Pharmacy patch is installed without the 
      CPRS patch, it's just that the functionality will not be seen until both
      are installed.
       
      4. When Renewing prescriptions that were entered prior to the 
      installation of the Pharmacy Ordering Enhancements patches, it is
      possible that the Verb from one Renewal is carried over to the next
      Renewal. This patch will fix this problem.
      signature. This patch fixes this problem.
       
      5. A problem has been reported when finishing renewals entered through 
      CPRS, and when processing renewals through Outpatient Pharmacy. The
      Instructions field sometimes displays with incorrect Instructions. This 
      is a result of a data problem that occurred prior to the Pharmacy
      Ordering Enhancements project, and has since been fixed. But there is no
      way to clean up any of the invalid data, so these invalid Instructions
      still appear on the pending renewal screen. Since the Sig now shows on
      the pending renewal screen, the software no longer needs to show the
      Instructions, so the Instructions will now be removed from the display.
       
      2. When finishing a renewal entered through Computerized Patient Record 
      System (CPRS) in Outpatient Pharmacy and answering YES to the prompt "Do
      you want to enter a Progress Note?  No//", the software does not present
      the pharmacist with the progress notes template. This patch fixes this
      
    • 86 SEQ #88
      DATE APPLIED:   2002-03-15 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      A problem has been reported of a status mismatch between Outpatient 
      Pharmacy orders and the corresponding order in Computerized Patient 
      Record System (CPRS).The specific problem would be that an order would be 
      Discontinued or Expired in Pharmacy, but Active in CPRS. This patch will 
      identify those orders, and update the CPRS order with the correct status.
      
    • 78 SEQ #90
      DATE APPLIED:   2002-03-27 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      1. With the release of the Pharmacy Ordering Enhancement patch (POE), 
      reduced from 100 to 90.  The correction to the software is that the quantity
      for all renewals will not be calculated, but use the quantity already
      entered for the prescription being renewed.  
       
      2. The prescription editing functionality that allows prescriptions to be 
      edited has been enhanced to process all fields selected for editing and
      verify that the edits do not cause a new prescription (order) to be created
      before updating the PRESCRIPTION file (#52) and CPRS ORDERS file (#100).
      Currently the software will update the prescription being edited and the
      changes to the new prescription.  
      functionality was added to compute the quantity for prescriptions for
       
      3. An additional order check was added when entering backdoor prescriptions
      and finishing prescriptions entered by the provider.  If maximum dispense
      units per day is entered in the MAXIMUM DOSE PER DAY field (#4), in the DRUG
      file (#50) it is used as an order check when the day supply is entered for
      backdoor prescriptions.  The problem is that the order check is not done
      when the quantity is entered or when finishing orders entered using CPRS.
      This patch now checks for maximum dispense units per day when the quantity
      is entered through Backdoor Outpatient Pharmacy and when finishing
      prescriptions entered by a provider.  
      possible dosages.  During the testing phase for POE the computation of
       
      4. When entering prescriptions using the Outpatient Pharmacy package or the
      Computerize Patient Record System (CPRS) for schedule 2 through 5 drugs the
      maximum number of refills of 5 was being allowed.  A problem was discovered
      that schedule 2 drugs should not allow any refills.  This patch corrects
      this problem.  
       
      5. When finishing orders from the Computerize Patient Record System (CPRS)
      that have a dosage greater than 60 characters, pharmacy cannot finish those
      orders without editing the dosage down to 60 characters or less. When the
      quantity for CMOP prescriptions was not identified as being a problem.  The
      dosage was edited the software was getting into a loop, which prevented the
      edited order from being accepted.  This patch corrects this problem.  
       
      6. When entering a backdoor order and an up-arrow is entered in the Route
      field, the order entry process should abort but does not, which causes an
      undefined error.  This patch corrects this.  
       
      7. It appears that when a pharmacist is finishing orders and one is for a
      possible dose, which would have units in parenthesis, and the second order
      is for a local possible dosage, the units pointer variable is not killed
      problem for the CMOP prescription happens when, for instance a prescription
      from the previous order and is displaying on the screen, but is not added
      to the order.    
      has a medication instruction that states to "TAKE 1 TABLET FOR 90 DAYS".
      For non-CMOP prescriptions a quantity of 90 tablets would normally be
      dispensed, but for CMOP prescriptions the quantity often times should be a
      quantity of 100.  When the CMOP prescriptions are renewed the quantity is
      
    • 95
      DATE APPLIED:   2002-04-23 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      As a part of the Pharmacy Benefits Management (PBM) Extract enhancement 
      packages affected since only one installation is necessary.  The patches, in
      order of install, are: 
        
             PSS*1*52  PHARMACY DATA MANAGEMENT V. 1.0 
             PSJ*5*68  INPATIENT MEDICATIONS V. 5.0 
             PSO*7*95  OUTPATIENT PHARMACY V. 7.0 
        
      Upon completion of the installation of these three patches, the master build
      will start a routine that will build the two new fields from historical data
      in the PHARMACY PATIENT file (#55).  When the build is complete, the user
      project, two new fields were added to the PHARMACY PATIENT file (#55).  
      who initiated the install and the members of the PSU PBM mail group will
      receive a message with a subject of BUILD OF FIRST PHARMACY SERVICE INFO
      COMPLETE.
      They are FIRST SERVICE DATE (#.07) and ACTUAL/HISTORICAL FLAG (#.08).
      With the addition of these two fields, Inpatient Medications V. 5.0 and
      Outpatient Pharmacy V. 7.0 have been modified to set this information when
      the first order for a patient becomes active.  
        
      This project consists of three patches combined in a master build.  
      Installation of this master build should be coordinated among the three 
      
    • 100 SEQ #92
      DATE APPLIED:   2002-04-23 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      1) When orders entered prior to the Pharmacy Ordering Enhancements patches
      with a Sig that can be valid, since it is from the previous order. The
      problem occurs when that order is renewed again, because the Sig from that
      point on is built from the Dosing information, which could produce an
      invalid Sig.
       
       
      To fix this problem, CPRS patch OR*3*134 will identify these orders to
      Pharmacy in a mail message. Pharmacy should then go and act accordingly on
      these orders. Please refer to patch OR*3*134 for complete information.
       
      are renewed through Computerized Patient Record System (CPRS), CPRS will
      As an added precaution, this patch, PSO*7*100, is being released. This 
      patch will check the dosages associated with an order when that order is 
      renewed or copied through Outpatient Pharmacy, and if a Dosage is found in
      the order that contains "0..", the process will not continue, and a
      message will be given to the user giving the reason. In addition, when a
      renewal of an Outpatient order is entered through CPRS, a call is made to
      Outpatient Pharmacy that determines whether or not the order is renewable.
      When this occurs, a check will now be in place to look for dosages that
      contain "0..", and if found, the renewal will not be allowed through
      CPRS. And to prevent any other invalid Sigs from being created as a 
      sometimes automatically assign Possible Dosages to these orders, based on
      result of invalid Dosing information automatically assigned to pre-POE
      orders, this patch makes the change to the renewal process to always carry
      over the Sig from the prescription being renewed, instead of building the
      Sig from the Dosing information that could have been assigned improperly
      when that prescription was originally renewed as a Pre-POE order.
       
      Since the change has been made to always populate the Sig from the 
      previous prescription on Renewals, a check will now be in place for a
      missing Sig when prescriptions are renewed. If a prescription is renewed,
      and that prescription is missing the Sig, the prescription will not be 
      prior order information. A problem was reported in that process that
      renewable, and a message will be given to the user giving the reason.
       
              
       
      2) When using the Speed Renew function in Outpatient Pharmacy, after 
      selecting the orders to renew, a number of prompts appear, one of those 
      prompts being PATIENT STATUS. The response to that prompt is entered as 
      the Patient Status in the PHARMACY PATIENT (#55) file, but the 
      prescriptions that are renewed still have the same Patient Status of the 
      prescriptions being renewed. This patch will make the change to update 
      involved CPRS passing an invalid dosage that began with "0..5", or another
      all of the renewals with the Patient Status entered at the PATIENT STATUS 
      prompt.
      dosage that started with "0..", to Pharmacy when the Dispense Units per
      Dose contained a decimal point. When these pre-POE orders are renewed, the
      Sig is brought into the order from the order being renewed. If this 
      invalid dosage information is not edited, it stays with the order, along
      
    • 16
      DATE APPLIED:   1999-04-16 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
       
      from hold.  Routines: PSOHLD, PSOLBLN
       
      Also added a check in the routine PSOLBLN to check for the barcode on and
      off sequences being defined for Rx label printing.
       
      3. Added a check for site parameters being defined when using the Rx
      Verification by Clerk option [PSO VR]. Routine: PSOVER
       
      4. Corrected a problem where inventory deduction from the Drug file (#50)
      could happen unnecessarily. Routine: PSORXED, PSORXED1.
      1. When Controlled Rxs are renewed, the expiration date was defaulting to
       
      5. Added a site parameter, VERIFYING PHARMACIST ON LABELS, that will allow
      sites to print the Verifying Pharmacist number on the 2nd line of labels.
       
      6. Fixed problem of refilling an Rx, and the refill suspending to the
      original Fill Date, instead of the Refill Date. Routine PSORXED
       
      7. Fixed problem of Editing a released Rx, and that Rx then suspending for
      CMOP instead of suspending locally. Routine PSOCMOP.
       
      one year instead of six months.  Routine: PSON52
      8. On line 2 of the labels, the first number printed after the phone
      number for CPRS entered orders has been the internal entry number of the
      person entering the order in CPRS. This patch changes that number to the
      person who Finishes the order in Pharmacy.
       
      2. When prescriptions are removed from Hold the user can reprint the label
      if they want.  In the activity multiple events are recorded (placed on,
      removed from hold).  If a label is printed the label log does not show that
      the label was printed because the Rx was removed from hold.  This patch will
      record in the label log that the label was printed because an Rx was removed
      
    • 98 SEQ #93
      DATE APPLIED:   2002-05-06 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      1) A problem was reported where a Pending Outpatient Pharmacy Order did 
         generate a mail message to the patch installer, and to all holders of
         the PSNMGR key. This message should be reviewed by the appropriate
         pharmacy personnel. The orders will not automatically be fixed to show
         up in the Complete Orders from OERR [PSO LMOE FINISH] option, since
         some of the orders may be old orders. But Pharmacy can review these
         orders from the mail message using the Patient Prescription Processing
         [PSO LM BACKDOOR ORDERS] option to determine the appropriate action.
       
      2) When a renewal is entered through CPRS for an outpatient pharmacy
         order, and that renewal is signed and sent to the Outpatient Pharmacy
         not show up in the Complete Orders from OERR [PSO LMOE FINISH] option.
         package, there are validation checks done on the renewal before the
         Outpatient Pharmacy package accepts the renewal. This patch will add
         two more validation checks.
       
         When the renewal is received in Outpatient Pharmacy, the software will
         now check the patient in the message against the patient in the
         PRESCRIPTION file (#52) from the previous pharmacy order number sent in
         the message, and if the patient does not match, then renewal will not
         be accepted by the Outpatient Pharmacy package. A previous order number
         check will also be added to this process. When the renewal is received,
         The problem occurs when the order is a "change" order from Computerized
         if the previous CPRS number does not match the CPRS number stored in
         the previous pharmacy order, then the renewal will not be accepted by
         the Outpatient Pharmacy package.
       
      3) This patch fixes two problems with the Medication Profile [PSO P]
         option. If a profile is printed for a patient who has pending
         outpatient pharmacy orders, those pending orders print at the end of
         the report, but the patient name is not at the top of these pages. This
         patch adds the patient name to the top of those pages. Also, if a
         patient only had pending outpatient orders, and no prescriptions, the
         Patient Record System (CPRS), and it is a complex order with very long 
         pending outpatient orders would not display. This patch fixes the 
         problem.
         Dosing Instructions. The order would show up in the Patient
         Prescription Processing [PSO LM BACKDOOR ORDERS] option, but would not
         always show up in the Complete Orders from OERR [PSO LMOE FINISH]
         option. This patch fixes the problem, and also as part of a post-init,
         will find all of these Pending Outpatient orders, if there are any, and
      
    • 101 SEQ #94
      DATE APPLIED:   2002-05-06 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      A problem was reported where certain Outpatient Pharmacy orders displayed 
      installer of this patch.  Other than installing these two patches, IRM 
      does not need to take any additional action.
      in Computerized Patient Record System (CPRS) with a truncated Sig. This 
      problem only happens on complex Outpatient Pharmacy orders. CPRS patch 
      OR*3*134 contains a fix that will prevent the problem for occurring. 
      For the currents orders that already have this problem, this patch,
      PSO*7*101, will search for all Outpatient Pharmacy orders with complex
      Dosing Instructions. A background job will synchronize the medication 
      instructions between CPRS and Pharmacy so the displays will be correct.  
      When the post install completes, a Mailman message will be sent to the 
      
    • 102 SEQ #95
      DATE APPLIED:   2002-05-06 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      1. With the release of PSO*7*78 and editing of the PHARMACIST field (#20) or
      should be zero (0) refills remaining, but if a user were to edit the # OF
      REFILLS field (#9) to 2 after dispensing 3, the refills remaining would show -1
      refills remaining.  This patch will prevent a total number of refills entered
      to be less than the number of refills already dispensed.  
       
      3. When editing # OF REFILLS field (#9) in the PRESCRIPTION file (#52) an 
      undefined error could occur when doing a VA FileMan lookup on the DRUG file
      (#50).  This patch corrects this problem.
      the DIVISION field (#23) in the PRESCRIPTION file (#52) data can become 
      corrupted by storing extra characters.  This patch prevents further corruption. 
       
       
      2. Currently when editing the # OF REFILLS field (#9) in the PRESCRIPTION file
      (#52) there is not currently a check to prevent a number from being entered
      less than the number of refills already dispensed.  If the prescription was
      originally entered with a total of 3 refills and 3 refills are dispensed, there
      
    • 94 SEQ #96
      DATE APPLIED:   2002-05-16 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
       1. When placing a new order through Outpatient Pharmacy that generates a 
       Orderable Item has Drug Text associated with it, then an error would 
       occur if the ListMan hidden action "DIN  Drug Restr/Guide (OP)" is used. 
       This patch prevents the error from occurring.
       
       3. This patch fixes the problem of patient names sometimes not displaying
       on the bingo board when the patient has window prescriptions released 
       through the Outpatient Pharmacy package.
       
       4. This patch changes the default Nature of Order response from WRITTEN
       to SERVICE CORRECTION when edits are made to pending orders and
       duplicate drug check on another active order, if that new order is viewed
       prescriptions that create a new order. (E3R 16682)
       
       5. When using the Complete Orders from OERR [PSO LMOE FINISH] option, it
       is possible that the METHOD OF PICK-UP entered for one patient's
       prescription can be carried over as the default response to the METHOD OF
       PICK-UP prompt for the next patient's prescription. This patches fixes
       this problem.
       
       6. When a Renewal is done through Outpatient Pharmacy, a Nature of Order
       is prompted. The response to the Nature of Order prompt is sent to CPRS
       through Computerized Patient Record System (CPRS) utilizing the Detailed 
       as the nature of Order for the new prescription, and also for the 
       prescription that was discontinued because of the Renewal. Sending the
       Nature of Order for the discontinued order can possibly require a
       signature for the original provider in CPRS. This patch makes the change 
       to not send the Nature of Order on the discontinued prescription.
       Display, the nature of order will show as "Duplicate", regardless of what
       nature of order was entered during the prescription entry process. This 
       patch corrects this problem.
       
       2. When finishing an order entered through CPRS in Outpatient Pharmacy, 
       and there is no Dispense Drug associated with the order, and the Pharmacy
      
    • 85 SEQ #97
      DATE APPLIED:   2002-05-16 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      Patch PSO*7*71 is required before the installation of this patch.
      cancellation that have already been cancelled.
        b. Use the current value of the SERVICE CONNECTED field (#116) of the
      PRESCRIPTION file (#52) instead of attempting to derive it from
      information from a call to Integrated Billing.
        c. Added patient name on the line following the prompt "Select
      PRESCRIPTION RX #:".
        d. Made correction to display the released date for the original fill
      if it is present in the selection list for cancels.
        e. Display (RTS) beside original fills that have been Returned to Stock
      since there will not be a released date.
       
        f. When choosing from the selection list for cancels, validate that the
      response only includes items that are on the list.
       
      2. At release of a fill changes were made to:
        a. Use the current value of the SERVICE CONNECTED field (#116) of the
      PRESCRIPTION file (#52) instead of attempting to derive it from
      information from a call to Integrated Billing.
        b. Unless the prescription is already exempt, always call Integrated
      Billing to check for income exemption. (Before this change, some
      prescriptions may appear in the copay activity log as being changed from
       
      no copay to copay and then immediately changed back from copay to no
      copay).
       
      3. For the RETURN MEDICATION TO STOCK option changes were made for:
        a. If the last fill of a copay prescription has previously been
      cancelled, a message to that effect is displayed instead of prompting
      for the CHARGE REMOVAL REASON.
        b. If the last fill of a copay prescription has previously been
      cancelled, Integrated Billing is not called to cancel the charge.
      This will prevent an error message from IB.
      This patch is a follow-up to patch PSO*7*71 for the Mill Bill Medication
        c. When an original fill for a copay prescription is returned to stock,
      the IB node contains the IB cancellation number. Now that a new call to
      Integrated Billing is available to check whether an IB number is a bill
      number or a cancel number, a change was made to call IB to bill if the
      fill is released again when the IB number present is a cancellation
      number.
        d. Messages were changed from "No Action Taken!" to "Prescription Not
      Returned to Stock!" if the return to stock action is not completed.
        e. Correction was made to cancel "potential charge" (charge exceeding
      annual cap) if it exists for the fill being returned to stock.
      Copay functionality. Items included in this patch are:
       
      4. The site number was added to the subject line of the MailMan message
      generated when one or more copay exemption questions has never been
      answered. e.g. Subj: RX COPAY STATUS REVIEW NEEDED (7121). Also a change
      was made to the MailMan message to clarify. The "Providers:" section was
      added and "Staff assigned to update the Prescription Copay Status:" was
      added just before the instructions for follow-up. The new text appears as:
       
       
      Providers:
       
      Please respond with your answer to the question(s) as a reply to this
      message. The prescription will be updated by the appropriate staff.
       
      Staff assigned to update the Prescription Copay Status:
      Please use the RESET COPAY STATUS/CANCEL CHARGES option to enter the
      responses to the questions above, which may result in a Rx copay status
      change and/or the need to remove copay charges.
      1. Under the Reset Copay Status/Cancel Charges [PSOCP RESET COPAY STATUS]
      option changes were made to:
        a. Display an informative message for any fills selected for
      
    • 103 SEQ #98
      DATE APPLIED:   2002-06-05 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      Before the release of the Pharmacy Ordering Enhancement patch (POE) pharmacy
      users entered the patient medication instructions (SIG) using quick codes that
      expand into readable instructions for the patient.  There are some reported
      instances  where the quick codes are missing and an undefined error occurs. 
      This patch corrects this problem.
      
    • 104 SEQ #99
      DATE APPLIED:   2002-06-05 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      This patch addresses the following concerns: 
      prescription to ask the user, "Are You Sure You Want to Update Rx
      #? Yes//", if the edits did not create a new prescription.  Updates
      to the prescription do not occur now until after the user finishes making
      changes to the fields selected for editing and accepts the changes at the
      new prompt.  A problem was introduced with this patch in that when editing
      free text fields and the input data contains a semi-colon (;), an error would
      occur when trying to update the PRESCRIPTION file (#52) entry.
      This patch corrects this problem. 
       
      3. When editing prescriptions that cause new prescriptions to be created,
       
      prescription numbers were being skipped.  For example, if the last number
      used for a prescription was 5 and the next number to be used was 6.  A
      prescription is edited in that it causes a new prescription to be created, the
      next number was defaulting to 7 instead 6.  This patch corrects this problem.
      1. This patch corrects an undefined error that occurs when all the dosage 
      information is not asked for by the software when entering new
      prescriptions.  This was a random error that only happened on occasion.
      When this error occurred it caused incomplete data to be added to the
      PRESCRIPTION file (#52).
       
      2. With the release of PSO*7*78 a prompt was added after editing a
      
    • 105 SEQ #100
      DATE APPLIED:   2002-06-05 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      Both Computerized Patient Record System (CPRS) V. 1.0 and Inpatient 
      Medications V. 5.0 packages were inappropriately display order check with 
      an Inaction Date entered in the Inaction Date field (#7) of the Drug 
      Interaction file (#56).
      
    • 92 SEQ #101
      DATE APPLIED:   2002-06-26 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      Central Texas Veterans Health Care System has received multiple complaints
      only the last 6 digits.  
       
      Please Note: If your site is using any class 3 software that requires the
      full social security number, it may be necessary to make that this patch will
      not cause that software to malfunction if installed. 
      from patients about their full Social Security Number (SSN) printing on
      their prescription reorder documents.  Currently the SSN at the top of the
      refill document shows the last 6 digits, however the full SSN shows next to
      the patient's name on the last page, just above the NARRATIVE REFILLABLE RX
      document.  This patch will change all instances of the patient's SSN on the
      reorder documents to display only the last 6 digits. This patch will change
      all instances of the patient's SSN on the reorder documents and to the
      section that shows any possible allergies and adverse reactions to display
      
    • 106 SEQ #102
      DATE APPLIED:   2002-06-26 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      1. When a user who does not possess the PSORPH key finishes a pending 
      prompt for the rest of the prescriptions on the same patient. This patch
      fixes this problem. 
      order using the Complete Orders from OERR [PSO LMOE FINISH] option, the 
      order is flagged as active instead of non-verified. This patch corrects
      this problem.
       
      2. When finishing a pending order using either the Patient Prescription 
      Processing [PSO LM BACKDOOR ORDERS] option, or the Complete Orders from
      OERR [PSO LMOE FINISH] option, the METHOD OF PICK-UP entered for one
      prescription is not carried over as the default response to the same
      
    DATE INSTALLED AT THIS SITE:   1999-04-16 00:00:00
    INSTALLED BY:   USER,ONE
    DESCRIPTION OF ENHANCEMENTS:   
    Version 7.0 of Outpatient Pharmacy will interface with version 1.0 of
    OERR/CPRS.
     
    
FILE
  • FIELD:
    • NUMBER
    • REORDER LEVEL
    • ORDER UNIT
    • PRICE PER ORDER UNIT
    • NORMAL AMOUNT TO ORDER
    • DISPENSE UNITS PER ORDER UNIT
    • PRICE PER DISPENSE UNIT
    • SOURCE OF SUPPLY
    • EXPIRATION DATE
    • NDC
    • CURRENT INVENTORY
    • GENERIC NAME
    • NON-FORMULARY
    • INACTIVE DATE
    • MESSAGE
    • LAB TEST MONITOR
    • MONITOR MAX DAYS
    • SPECIMEN TYPE
    • MONITOR ROUTINE
    • LAB TEST MONITOR
    • MONITOR MAX DAYS
    • SPECIMEN TYPE
    • VA CLASSIFICATION
    • MONITOR ROUTINE
    • *LAB TEST MONITOR
    • *MONITOR MAX DAYS
    • *SPECIMEN TYPE
    • *MONITOR ROUTINE
    • DEA, SPECIAL HDLG
    • MAXIMUM DOSE PER DAY
    • STANDARD SIG
    • FSN
    • WARNING LABEL
    • SYNONYM
    UPDATE THE DATA DICTIONARY:   YES
    ASSIGN A VERSION NUMBER:   NO
    MAY USER OVERRIDE DD UPDATE:   NO
    DATA COMES WITH FILE:   NO
    MAY USER OVERRIDE DATA UPDATE:   YES
  • UPDATE THE DATA DICTIONARY:   YES
    ASSIGN A VERSION NUMBER:   YES
    MAY USER OVERRIDE DD UPDATE:   NO
    DATA COMES WITH FILE:   NO
  • UPDATE THE DATA DICTIONARY:   YES
    ASSIGN A VERSION NUMBER:   YES
    MAY USER OVERRIDE DD UPDATE:   NO
    DATA COMES WITH FILE:   NO
    MAY USER OVERRIDE DATA UPDATE:   YES
  • UPDATE THE DATA DICTIONARY:   YES
    ASSIGN A VERSION NUMBER:   YES
    MAY USER OVERRIDE DD UPDATE:   NO
    DATA COMES WITH FILE:   NO
    MAY USER OVERRIDE DATA UPDATE:   NO
  • UPDATE THE DATA DICTIONARY:   YES
    ASSIGN A VERSION NUMBER:   YES
    MAY USER OVERRIDE DD UPDATE:   NO
    DATA COMES WITH FILE:   NO
    MAY USER OVERRIDE DATA UPDATE:   YES
  • FIELD:
    • NAME
    • RESPITE PATIENT START DATE
    • RESPITE PATIENT END DATE
    • ACTIVE SCRIPTS
    • PRESCRIPTION PROFILE
    • CLOZAPINE REGISTRATION NUMBER
    • CLOZAPINE STATUS
    • DATE OF LAST CLOZAPINE RX
    • DEMOGRAPHICS SENT
    • RESPONSIBLE PROVIDER
    • REGISTRATION DATE
    • CAP
    • ARCHIVE DATE
    • NUMBER
    • MAIL
    • DIALYSIS PATIENT
    • NARRATIVE
    • PATIENT STATUS
    • COMMUNITY NURSING HOME
    • NURSING HOME CONTRACT
    • LAST DATE OF CONTRACT
    UPDATE THE DATA DICTIONARY:   YES
    ASSIGN A VERSION NUMBER:   NO
    MAY USER OVERRIDE DD UPDATE:   NO
    DATA COMES WITH FILE:   NO
    MAY USER OVERRIDE DATA UPDATE:   YES
  • UPDATE THE DATA DICTIONARY:   YES
    ASSIGN A VERSION NUMBER:   YES
    MAY USER OVERRIDE DD UPDATE:   NO
    DATA COMES WITH FILE:   NO
    MAY USER OVERRIDE DATA UPDATE:   YES
  • UPDATE THE DATA DICTIONARY:   YES
    ASSIGN A VERSION NUMBER:   YES
    MAY USER OVERRIDE DD UPDATE:   NO
    DATA COMES WITH FILE:   NO
    MAY USER OVERRIDE DATA UPDATE:   YES
  • UPDATE THE DATA DICTIONARY:   YES
    ASSIGN A VERSION NUMBER:   YES
    MAY USER OVERRIDE DD UPDATE:   NO
    DATA COMES WITH FILE:   NO
    MAY USER OVERRIDE DATA UPDATE:   YES
  • UPDATE THE DATA DICTIONARY:   YES
    ASSIGN A VERSION NUMBER:   YES
    MAY USER OVERRIDE DD UPDATE:   NO
    DATA COMES WITH FILE:   NO
    MAY USER OVERRIDE DATA UPDATE:   YES
  • UPDATE THE DATA DICTIONARY:   YES
    ASSIGN A VERSION NUMBER:   YES
    MAY USER OVERRIDE DD UPDATE:   NO
    DATA COMES WITH FILE:   NO
    MAY USER OVERRIDE DATA UPDATE:   YES
  • UPDATE THE DATA DICTIONARY:   YES
    ASSIGN A VERSION NUMBER:   YES
    MAY USER OVERRIDE DD UPDATE:   NO
    DATA COMES WITH FILE:   NO
    MAY USER OVERRIDE DATA UPDATE:   YES
  • UPDATE THE DATA DICTIONARY:   YES
    ASSIGN A VERSION NUMBER:   YES
    MAY USER OVERRIDE DD UPDATE:   NO
    DATA COMES WITH FILE:   NO
    MAY USER OVERRIDE DATA UPDATE:   YES
  • FIELD:
    • DEFAULT OUTPATIENT SITE
    • DATE 200 CONVERSION
    • DATE OP INSTALLED
    • OUTPATIENT VERSION
    • SITE NAME
    • DEFAULT OUTPATIENT SITE
    • LAST RX PRE V6
    • LAST RX CONVERTED
    • CLOZAPINE DATA MOVE
    • PROVIDER DATA UPDATE
    • ADMISSION CANCEL OF RXS
    • DAYS PRINTED RX STAYS IN 52.5
    • INTERDIVISIONAL PROCESSING
    • DIVISION PROMPT ASKED
    • REFILL/RENEW DIVISION
    • TOTAL RX'S PURGED TO DATE
    UPDATE THE DATA DICTIONARY:   YES
    ASSIGN A VERSION NUMBER:   NO
    MAY USER OVERRIDE DD UPDATE:   NO
    DATA COMES WITH FILE:   NO
    MAY USER OVERRIDE DATA UPDATE:   NO
  • UPDATE THE DATA DICTIONARY:   YES
    ASSIGN A VERSION NUMBER:   YES
    MAY USER OVERRIDE DD UPDATE:   NO
    DATA COMES WITH FILE:   NO
    MAY USER OVERRIDE DATA UPDATE:   YES
  • UPDATE THE DATA DICTIONARY:   YES
    ASSIGN A VERSION NUMBER:   NO
    MAY USER OVERRIDE DD UPDATE:   NO
    DATA COMES WITH FILE:   NO
    MAY USER OVERRIDE DATA UPDATE:   YES
  • UPDATE THE DATA DICTIONARY:   YES
    ASSIGN A VERSION NUMBER:   YES
    MAY USER OVERRIDE DD UPDATE:   NO
    DATA COMES WITH FILE:   NO
    MAY USER OVERRIDE DATA UPDATE:   YES
  • UPDATE THE DATA DICTIONARY:   YES
    ASSIGN A VERSION NUMBER:   YES
    MAY USER OVERRIDE DD UPDATE:   NO
    DATA COMES WITH FILE:   NO
    MAY USER OVERRIDE DATA UPDATE:   YES
  • UPDATE THE DATA DICTIONARY:   YES
    ASSIGN A VERSION NUMBER:   YES
    MAY USER OVERRIDE DD UPDATE:   NO
    DATA COMES WITH FILE:   NO
    MAY USER OVERRIDE DATA UPDATE:   YES
  • UPDATE THE DATA DICTIONARY:   YES
    ASSIGN A VERSION NUMBER:   NO
    MAY USER OVERRIDE DD UPDATE:   NO
    DATA COMES WITH FILE:   YES
    MERGE OR OVERWRITE SITE'S DATA:   OVERWRITE
    MAY USER OVERRIDE DATA UPDATE:   NO
    SCREEN TO DETERMINE DD UPDATE:   I $G(^DD(56,0,"VR"))<3
  • FIELD:
    • NAME
    UPDATE THE DATA DICTIONARY:   YES
    ASSIGN A VERSION NUMBER:   NO
    MAY USER OVERRIDE DD UPDATE:   NO
    DATA COMES WITH FILE:   NO
    MAY USER OVERRIDE DATA UPDATE:   NO
  • UPDATE THE DATA DICTIONARY:   YES
    ASSIGN A VERSION NUMBER:   YES
    MAY USER OVERRIDE DD UPDATE:   NO
    DATA COMES WITH FILE:   NO
  • UPDATE THE DATA DICTIONARY:   YES
    ASSIGN A VERSION NUMBER:   YES
    MAY USER OVERRIDE DD UPDATE:   NO
    DATA COMES WITH FILE:   YES
    MERGE OR OVERWRITE SITE'S DATA:   OVERWRITE
    MAY USER OVERRIDE DATA UPDATE:   NO
  • UPDATE THE DATA DICTIONARY:   YES
    ASSIGN A VERSION NUMBER:   YES
    MAY USER OVERRIDE DD UPDATE:   NO
    DATA COMES WITH FILE:   NO
    MAY USER OVERRIDE DATA UPDATE:   NO
  • UPDATE THE DATA DICTIONARY:   YES
    ASSIGN A VERSION NUMBER:   YES
    MAY USER OVERRIDE DD UPDATE:   NO
    DATA COMES WITH FILE:   YES
    MERGE OR OVERWRITE SITE'S DATA:   OVERWRITE
    MAY USER OVERRIDE DATA UPDATE:   NO
  • UPDATE THE DATA DICTIONARY:   YES
    ASSIGN A VERSION NUMBER:   YES
    MAY USER OVERRIDE DD UPDATE:   NO
    DATA COMES WITH FILE:   NO
    MAY USER OVERRIDE DATA UPDATE:   NO
  • UPDATE THE DATA DICTIONARY:   YES
    ASSIGN A VERSION NUMBER:   YES
    MAY USER OVERRIDE DD UPDATE:   NO
    DATA COMES WITH FILE:   NO
    MAY USER OVERRIDE DATA UPDATE:   NO
  • UPDATE THE DATA DICTIONARY:   YES
    ASSIGN A VERSION NUMBER:   YES
    MAY USER OVERRIDE DD UPDATE:   NO
    DATA COMES WITH FILE:   NO
    MAY USER OVERRIDE DATA UPDATE:   NO
  • UPDATE THE DATA DICTIONARY:   YES
    ASSIGN A VERSION NUMBER:   YES
    MAY USER OVERRIDE DD UPDATE:   NO
    DATA COMES WITH FILE:   NO
    MAY USER OVERRIDE DATA UPDATE:   NO
  • FIELD:
    • AUTHORIZED TO WRITE MED ORDERS
    • LICENSING STATE
    • STATE ISSUING DEA NUMBER
    • DEA#
    • VA#
    • INACTIVE DATE
    • PROVIDER CLASS
    • PROVIDER TYPE
    • REQUIRES COSIGNER
    • USUAL COSIGNER
    • REMARKS
    UPDATE THE DATA DICTIONARY:   YES
    ASSIGN A VERSION NUMBER:   NO
    MAY USER OVERRIDE DD UPDATE:   YES
    DATA COMES WITH FILE:   NO
  • FIELD:
    • OUTPATIENT SITE
    UPDATE THE DATA DICTIONARY:   YES
    ASSIGN A VERSION NUMBER:   NO
    MAY USER OVERRIDE DD UPDATE:   NO
    DATA COMES WITH FILE:   NO
    MAY USER OVERRIDE DATA UPDATE:   NO
  • UPDATE THE DATA DICTIONARY:   NO
    ASSIGN A VERSION NUMBER:   NO
    MAY USER OVERRIDE DD UPDATE:   NO
    DATA COMES WITH FILE:   NO
    MAY USER OVERRIDE DATA UPDATE:   NO
  • UPDATE THE DATA DICTIONARY:   YES
    ASSIGN A VERSION NUMBER:   YES
    MAY USER OVERRIDE DD UPDATE:   NO
    DATA COMES WITH FILE:   NO
    MAY USER OVERRIDE DATA UPDATE:   NO
  • UPDATE THE DATA DICTIONARY:   YES
    ASSIGN A VERSION NUMBER:   YES
    MAY USER OVERRIDE DD UPDATE:   NO
    DATA COMES WITH FILE:   NO
PRINT TEMPLATE
INPUT TEMPLATE
ENVIRONMENT CHECK ROUTINE PSOPREI
ENVIRONMENT CHECK DONE DATE 1996-07-02 16:00:07
POST-INITIALIZATION ROUTINE PSOPOST
POST-INIT COMPLETION DATE 1996-07-02 16:48:17
PRE-INIT AFTER USER COMMIT PSOSTART
PRE-INIT COMPLETION DATE 1996-07-02 16:01:05
EXCLUDED NAME SPACE
  • PSIV
  • PSG
  • PSZ