ORDER ENTRY/RESULTS REPORTING (35)    PACKAGE (9.4)

Name Value
NAME ORDER ENTRY/RESULTS REPORTING
PREFIX OR
DEVELOPER (PERSON/SITE) KCDC/SLC
DEVELOPMENT ISC Salt Lake City
CLASS National
CURRENT VERSION 3.0
ADDITIONAL PREFIXES
  • OCX
  • ORAM
SHORT DESCRIPTION Order Entry/Results Reporting
VERSION
  • 2.5
    DATE DISTRIBUTED:   1992-11-25 00:00:00
    PATCH APPLICATION HISTORY:
    • 46 SEQ #43
      DATE APPLIED:   1996-06-25 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      This patch addresses many problems associated with Electronic Signature in
signed online and not allow for 'wet' signatures on the paper chart
(paperless).  2 or Yes (allow chart signature) is for sites that want all
orders signed online, but also allow for those cases where there might be
a manually signed order in the chart somewhere.  This last option is the
most likely scenerio for most hospitals at this point in time.
 
The printing of new and unsigned orders has been modified.  Orders print
(chart copies, labels, service copies, requisitions) when they are
released.  Prior to this patch, they would print again when they were
signed.  This is no longer the case because of the confusion and potential
OE/RR 2.5.  A new field has been added to the Order Parameters file called
for error when duplicate orders are printed.
Electronic Record.  It can be set to 1 of 3 choices:
   0 for No
   1 for Yes
   2 for Yes (allow chart signature)
 
No entry or 0 will essentially keep the functionality for Electronic
Signature the same.  1 or Yes is for sites that want to have all orders
    • 57 SEQ #53
      DATE APPLIED:   1997-12-01 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      The description of this build can be found in the National Patch Module 
under patch OR*2.5*57.
    • 61 SEQ #54
      DATE APPLIED:   1997-12-13 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      The description of this build can be found in the National Patch Module
under patch OR*2.5*61.
    • 58 SEQ #55
      DATE APPLIED:   1998-02-20 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      The description of this build can be found in the National Patch Module
under patch OR*2.5*58.
    • 60 SEQ #56
      DATE APPLIED:   1998-02-20 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      The description of this build can be found in the National Patch Module
under patch OR*2.5*60.
    • 62 SEQ #57
      DATE APPLIED:   1998-03-18 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      The description of this build can be found in the National Patch Module
under patch OR*2.5*62.
    • 64 SEQ #58
      DATE APPLIED:   1998-05-01 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      The description of this build can be found in the National Patch Module 
under the description of patch OR*2.5*64
    • 63 SEQ #59
      DATE APPLIED:   1998-05-13 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      See description of build in National Patch Module under the patch OR*2.5*63.
    • 49
      DATE APPLIED:   1999-03-22 00:00:00
      APPLIED BY:   USER,ONE
    • 48
      DATE APPLIED:   1996-11-29 00:00:00
      APPLIED BY:   USER,ONE
    • 50 SEQ #46
      DATE APPLIED:   1997-02-04 00:00:00
      APPLIED BY:   USER,ONE
    • 51 SEQ #47
      DATE APPLIED:   1997-03-03 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      An optional parameter is added to the formal list of the subroutine
       D PATIENT^ORU1(.ORPAT,1) ; Will suppress initial page feed
 
whereas,
 
       D PATIENT^ORU1(.ORPAT) ; Will allow initial page feed/no side-
                              ; effect (this is how the subroutine was
                              ; uniformly called by v2.5
PATIENT^ORU1, which will suppress the initial page feed issued by the
look-up, prior to presenting the list of patients from which the user may
select.  Because the parameter is optional, and must be set to 1 by the
calling application to affect the look-up, the change is backward
compatible, and without side-effects.
 
Annotated example of use:
    • 54 SEQ #48
      DATE APPLIED:   1997-08-19 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      The description of this build can be found in the National Patch Module 
under patch OR*2.5*54.
    • 55 SEQ #49
      DATE APPLIED:   1997-08-22 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      The description of this build can be found in the National Patch Module 
under patch OR*2.5*55.
    • 52 SEQ #50
      DATE APPLIED:   1997-10-21 00:00:00
      APPLIED BY:   USER,ONE
    • 56 SEQ #51
      DATE APPLIED:   1997-11-27 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      The description of this build can be found in the National Patch Module 
under patch OR*2.5*56.
    • 59 SEQ #52
      DATE APPLIED:   1997-12-01 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      The description of this build can be found in the National Patch Module
under patch OR*2.5*59.
    DATE INSTALLED AT THIS SITE:   1996-06-13 00:00:00
  • 3.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:   
      This patch corrects OPENERR errors which occur in DEL^%ZISH when no data
is returned for a CPRS report.
    • 22
      DATE APPLIED:   1999-04-16 00:00:00
      APPLIED BY:   USER,ONE
    • 100 SEQ #100
      DATE APPLIED:   2001-06-25 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      This patch will add the edit/resubmit consults option to the
list manager.
 
Please see the patch module on FORUM for a complete description
of this patch.  In addition, you may want to review consult
patches GMRC*3*15 and GMRC*3*18, which are also required to see
the entire functionality.
    • 85
      DATE APPLIED:   2001-06-25 00:00:00
      APPLIED BY:   USER,ONE
    • 113 SEQ #102
      DATE APPLIED:   2001-08-02 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      The description for this patch can be found in the National Patch Module
under OR*3*113.
    • 115 SEQ #103
      DATE APPLIED:   2001-09-26 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      You can see the description of this build in the National Patch Tracking 
module under patch number OR*3*115.
    • 109 SEQ #104
      DATE APPLIED:   2001-09-26 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      This build includes the GUI specific portions of CPRS that were pulled
out of the OR3.0 build.
 
Routines: ORW* 
OR*
Option:   OR CPRS GUI CHART
 
also TIUSRVP and TIUEDIT
    • 95 SEQ #105
      DATE APPLIED:   2001-09-26 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      Patch OR*3*95 updates a number of menu editor and related items.  Please
see the FORUM patch description for a complete description of all of the
changes included in this patch.
    • 94
      DATE APPLIED:   2001-09-26 00:00:00
      APPLIED BY:   USER,ONE
    • 114 SEQ #107
      DATE APPLIED:   2001-10-16 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      This is the updated version of the performance monitor.  Please see the
FORUM patch description for complete details regarding this patch.
    • 119 SEQ #108
      DATE APPLIED:   2001-10-16 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      This is the updated version of the performance monitor.  Please see the
FORUM patch description for complete details regarding this patch.
    • 118 SEQ #109
      DATE APPLIED:   2001-10-16 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      Refer to the patch description on the patch message.
    • 16
      DATE APPLIED:   1999-04-16 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      This patch corrects a problem of getting a Null Subscript error when
printing orders that have no order text.
    • 124 SEQ #110
      DATE APPLIED:   2001-11-06 00:00:00
      APPLIED BY:   USER,ONE
    • 122 SEQ #111
      DATE APPLIED:   2001-11-06 00:00:00
      APPLIED BY:   USER,ONE
    • 120 SEQ #112
      DATE APPLIED:   2001-11-21 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      Refer to the patch description on the patch message.
    • 117 SEQ #113
      DATE APPLIED:   2001-11-21 00:00:00
      APPLIED BY:   USER,ONE
    • 105
      DATE APPLIED:   2001-12-10 00:00:00
      APPLIED BY:   USER,ONE
    • 116 SEQ #115
      DATE APPLIED:   2001-12-10 00:00:00
      APPLIED BY:   USER,ONE
    • 130 SEQ #116
      DATE APPLIED:   2001-12-31 00:00:00
      APPLIED BY:   USER,ONE
    • 129 SEQ #117
      DATE APPLIED:   2001-12-31 00:00:00
      APPLIED BY:   USER,ONE
    • 125 SEQ #118
      DATE APPLIED:   2001-12-31 00:00:00
      APPLIED BY:   USER,ONE
    • 112 SEQ #119
      DATE APPLIED:   2002-01-16 00:00:00
      APPLIED BY:   USER,ONE
    • 25
      DATE APPLIED:   1999-04-16 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      Refer to the patch description on the patch message.
    • 110 SEQ #120
      DATE APPLIED:   2002-01-16 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      Please see FORUM patch description for a complete analysis of this patch.
    • 121 SEQ #121
      DATE APPLIED:   2002-02-04 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      Refer to the patch description on the patch message.
    • 131 SEQ #122
      DATE APPLIED:   2002-02-26 00:00:00
      APPLIED BY:   USER,ONE
    • 128 SEQ #124
      DATE APPLIED:   2002-02-26 00:00:00
      APPLIED BY:   USER,ONE
    • 136 SEQ #125
      DATE APPLIED:   2002-02-26 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      Please see the full patch description on the FORUM account for this patch.
    • 135 SEQ #126
      DATE APPLIED:   2002-03-15 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      See National Patch Module.
    • 138 SEQ #127
      DATE APPLIED:   2002-04-08 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      Database clean up for POE related issues.  Please see FORUM for complete 
patch details.
    • 145 SEQ #128
      DATE APPLIED:   2002-04-08 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      See FORUM for the full description of this patch.  Update to database 
clean up distributed in patch OR*3*138.
    • 140 SEQ #129
      DATE APPLIED:   2002-04-23 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      Refer to the patch description on the patch message.
    • 134 SEQ #130
      DATE APPLIED:   2002-05-06 00:00:00
      APPLIED BY:   USER,ONE
    • 23
      DATE APPLIED:   1999-04-16 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      Refer to description on the patch message.
printing orders that have no order text.
    • 133 SEQ #131
      DATE APPLIED:   2002-05-16 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      BCMA ORDER COM V1.1
    • 132 SEQ #132
      DATE APPLIED:   2002-05-28 00:00:00
      APPLIED BY:   USER,ONE
    • 123 SEQ #133
      DATE APPLIED:   2002-05-28 00:00:00
      APPLIED BY:   USER,ONE
    • 147 SEQ #135
      DATE APPLIED:   2002-05-28 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      Refer to the patch description on the patch message.
    • 144 SEQ #136
      DATE APPLIED:   2002-07-10 00:00:00
      APPLIED BY:   USER,ONE
    • 142 SEQ #137
      DATE APPLIED:   2002-07-24 00:00:00
      APPLIED BY:   USER,ONE
    • 148 SEQ #138
      DATE APPLIED:   2002-07-24 00:00:00
      APPLIED BY:   USER,ONE
    • 146 SEQ #139
      DATE APPLIED:   2002-08-14 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      Refer to the patch description on the patch message.
    • 154 SEQ #140
      DATE APPLIED:   2002-08-15 00:00:00
      APPLIED BY:   USER,ONE
    • 150 SEQ #141
      DATE APPLIED:   2002-09-06 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      This patch includes a API EN^ORBCMA2 required by BCMA V2. The #DBIA for 
this API is 3616.
    • 3
      DATE APPLIED:   1999-04-16 00:00:00
      APPLIED BY:   USER,ONE
    • 155 SEQ #142
      DATE APPLIED:   2002-09-06 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      This patch is being released to turn off the spell checking functionality 
based on input from the National Center for Patient Safety.
    • 143 SEQ #143
      DATE APPLIED:   2002-10-08 00:00:00
      APPLIED BY:   USER,ONE
    • 139 SEQ #144
      DATE APPLIED:   2002-10-08 00:00:00
      APPLIED BY:   USER,ONE
    • 152 SEQ #146
      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 Interchange
project. The project provides a method for the one-way electronic transfer
of prescription orders from an external system to VistA.
    • 127 SEQ #147
      DATE APPLIED:   2002-11-08 00:00:00
      APPLIED BY:   USER,ONE
    • 161 SEQ #148
      DATE APPLIED:   2002-11-22 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      Fixes problem with November dates being interpreted as "NOW".  Please see 
patch description on FORUM for complete details.
    • 158 SEQ #149
      DATE APPLIED:   2002-12-09 00:00:00
      APPLIED BY:   USER,ONE
    • 141
      DATE APPLIED:   2002-12-09 00:00:00
      APPLIED BY:   USER,ONE
    • 166 SEQ #151
      DATE APPLIED:   2002-12-09 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      Update to post-install for patch OR*3*158.  Please see FORUM patch module 
for full details.
    • 168 SEQ #152
      DATE APPLIED:   2003-01-09 00:00:00
      APPLIED BY:   USER,ONE
    • 12
      DATE APPLIED:   1999-04-16 00:00:00
      APPLIED BY:   USER,ONE
    • 167 SEQ #153
      DATE APPLIED:   2003-01-09 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      Refer to the patch description on the patch message.
    • 159 SEQ #154
      DATE APPLIED:   2003-01-15 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      The description of this build is found in the National Patch Module under 
patch OR*3.0*159.
    • 164 SEQ #155
      DATE APPLIED:   2003-02-04 00:00:00
      APPLIED BY:   USER,ONE
    • 171 SEQ #156
      DATE APPLIED:   2003-02-04 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      The description of this build is found in the National Patch Module under 
patch OR*3.0*171.
    • 162 SEQ #157
      DATE APPLIED:   2003-02-04 00:00:00
      APPLIED BY:   USER,ONE
    • 165 SEQ #158
      DATE APPLIED:   2003-02-04 00:00:00
      APPLIED BY:   USER,ONE
    • 169 SEQ #159
      DATE APPLIED:   2003-03-01 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      Refer to the patch description on the patch message.
    • 170 SEQ #160
      DATE APPLIED:   2003-03-01 00:00:00
      APPLIED BY:   USER,ONE
    • 160 SEQ #161
      DATE APPLIED:   2003-03-01 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      Refer to the patch description on the patch message.
    • 177 SEQ #162
      DATE APPLIED:   2003-04-17 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      Updates to Event Delayed Order code.
See FORUM patch description for complete details.
    • 7
      DATE APPLIED:   1999-04-16 00:00:00
      APPLIED BY:   USER,ONE
    • 178 SEQ #163
      DATE APPLIED:   2003-04-17 00:00:00
      APPLIED BY:   USER,ONE
    • 175 SEQ #164
      DATE APPLIED:   2003-04-17 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      Refer to the patch description on the patch message.
    • 153 SEQ #165
      DATE APPLIED:   2003-04-30 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      Description:
The following is a list of the routine(s) included in this patch.  The
second line of each of these routine(s) will look like:
  
<tab>;;3.0;ORDER ENTRY/RESULTS REPORTING;**<patch list>**;Dec 17, 1997
  
                            CHECK^XTSUMBLD results
 Routine name         Before Patch      After Patch          Patch List
 ============         ============      ===========          ==========
 ORMGMRC                                   12946666      3,26,68,92,153
 ORMLR                                     15500365            3,92,153
===========
 ORMRA                                     16479106 3,53,92,110,136,153
 ORQRY                                     10982388                 153
 
Installation Instructions:
==========================
 
Installation of this patch will take less than 2 minutes.  Although
users need not be off the system when applying this patch, it should be
installed at a nonpeak time to minimize disruption to users.
  
 
 1.   Use the INSTALL/CHECK MESSAGE option on the Packman Menu, to 
      load the KIDS Transport Distribution global.  
   
 2.   Review your mapped set.  If any of the routines listed in the 
      ROUTINE SUMMARY section are mapped, they should be removed 
      from the mapped set at this time.  
   
 3.   From the Kernel Installation and Distribution System (KIDS) Menu, 
      select the Installation menu.  
   
This patch provides server side updates for the CPRS Query Tool.  This
 4.   From the installation menu, you may elect to use the following 
      options (when prompted for INSTALL NAME, enter OR*3.0*153): 
   
      a.  Backup a Transport Global
      b.  Compare Transport Global to Current System
      c.  Verify Checksums in Transport Global
   
 5.   Use the Install Package(s) option and select the package 
      OR*3.0*153.
  
tool allows queries to be created for Orders, Documents, Appointments,
 6.   When prompted 'Want KIDS to INHIBIT LOGONs during the install?
      YES//', respond 'NO'.
  
 7.   When prompted 'Want to DISABLE Scheduled Options, Menu 
      Options, and Protocols? YES//', respond 'YES', and disable
      OR* Options and Protocols.
  
 8.   If routines were unmapped as part of step 2, they should 
      be returned to the mapped set once the installation has 
      run to completion.
and Visits.
 
ROUTINE SUMMARY:
================
    • 185 SEQ #166
      DATE APPLIED:   2003-05-20 00:00:00
      APPLIED BY:   USER,ONE
    • 183 SEQ #167
      DATE APPLIED:   2003-06-03 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      CRSP CMOP FIX
    • 180 SEQ #168
      DATE APPLIED:   2003-06-28 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      Refer to the patch description on the patch message.
    • 163 SEQ #169
      DATE APPLIED:   2003-08-02 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      Refer to the patch description on the patch message.
    • 188 SEQ #170
      DATE APPLIED:   2003-08-02 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      Remove Race and Ethinicity codes
    • 149
      DATE APPLIED:   2003-08-13 00:00:00
      APPLIED BY:   USER,ONE
    • 173
      DATE APPLIED:   2003-08-13 00:00:00
      APPLIED BY:   USER,ONE
    • 14
      DATE APPLIED:   1999-04-16 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      See National Patch Module (NPM) on FORUM.
    • 184 SEQ #173
      DATE APPLIED:   2003-08-13 00:00:00
      APPLIED BY:   USER,ONE
    • 182 SEQ #174
      DATE APPLIED:   2003-09-12 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      Fixes problem with allergy orders that didn't pass correctly from CPRS.  
See the full description on FORUM.
    • 196 SEQ #175
      DATE APPLIED:   2003-09-12 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      Update to performance monitor for pharmacy transitional benefits 
program.  Please see FORUM for a complete description.
    • 203 SEQ #177
      DATE APPLIED:   2003-09-24 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      Emergency patch / GUI 22.12 to fix problems with GUI 22.11 / patch 
OR*3*173.
    • 181
      DATE APPLIED:   2003-09-24 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      Please see the National Patch Module for details of the enhancements 
included in this patch.
    • 186 SEQ #179
      DATE APPLIED:   2003-10-02 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      Please see the FORUM description for a complete review of the changes 
incorporated in this patch.
    • 201 SEQ #180
      DATE APPLIED:   2003-10-02 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      Refer to the patch description on the patch message.
    • 193 SEQ #182
      DATE APPLIED:   2003-10-23 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      Refer to the patch description on the patch message.
    • 191 SEQ #181
      DATE APPLIED:   2003-10-23 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      Refer to the patch description on the patch message.
    • 189 SEQ #183
      DATE APPLIED:   2003-11-07 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      Refer to the patch description on the patch message.
    • 20
      DATE APPLIED:   1999-04-16 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      See description on patch message.
    • 206 SEQ #184
      DATE APPLIED:   2003-12-31 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      Emergency Patch to reduce number of calls to RPC "ORWPT ID INFO."  Also 
includes fix for slow TIU Template loading.
    • 209 SEQ #185
      DATE APPLIED:   2003-12-31 00:00:00
      APPLIED BY:   USER,ONE
    • 214
      DATE APPLIED:   2004-01-31 00:00:00
      APPLIED BY:   USER,ONE
    • 179 SEQ #187
      DATE APPLIED:   2004-03-02 00:00:00
      APPLIED BY:   USER,ONE
    • 174
      DATE APPLIED:   2004-03-02 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      The description of this build is found in the National Patch Module under
patch OR*3*174.
    • 208 SEQ #189
      DATE APPLIED:   2004-03-02 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      Refer to the patch description on the patch message.
    • 176 SEQ #190
      DATE APPLIED:   2004-03-02 00:00:00
      APPLIED BY:   USER,ONE
    • 187
      DATE APPLIED:   2004-03-02 00:00:00
      APPLIED BY:   USER,ONE
    • 172 SEQ #192
      DATE APPLIED:   2004-03-30 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      Refer to the patch description on the patch message.
    • 198 SEQ #193
      DATE APPLIED:   2004-07-02 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      Refer to the patch description on the patch message.
    • 6
      DATE APPLIED:   1999-04-16 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      Note: This patch can only be installed at sites running CPRS.
 
The entry point to do medication order checks for drug-drug interactions,
duplicate drug orders and duplicate drug class orders was changed from
^PSOORDRG to EN^PSOORDRG.  This patch changes references in routine ORKPS
to the new entry point EN^PSOORDRG.
    • 190
      DATE APPLIED:   2004-08-02 00:00:00
      APPLIED BY:   USER,ONE
    • 224
      DATE APPLIED:   2004-09-03 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      See NPM on Forum for description.
    • 192 SEQ #196
      DATE APPLIED:   2004-10-15 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      Refer to the patch description on the patch message.
    • 223 SEQ #197
      DATE APPLIED:   2004-10-15 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      Refer to the patch description on the patch message.
    • 213
      DATE APPLIED:   2004-10-15 00:00:00
      APPLIED BY:   USER,ONE
    • 200 SEQ #199
      DATE APPLIED:   2004-10-15 00:00:00
      APPLIED BY:   USER,ONE
    • 194 SEQ #200
      DATE APPLIED:   2004-10-15 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      Refer to the patch description on the patch message.
    • 222 SEQ #201
      DATE APPLIED:   2004-11-11 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      Group Notes
    • 225 SEQ #202
      DATE APPLIED:   2004-11-26 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      Update to performance monitor to exclude Non-VA med entries.
    • 157
      DATE APPLIED:   2004-12-28 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      Implement Clinical Reminders index.
    • 5
      DATE APPLIED:   1999-04-16 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      This patch corrects a problem of getting a Null Subscript error when
printing orders that have no order text.
    • 28
      DATE APPLIED:   1999-04-16 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      See the patch description on the patch message.
    • 227 SEQ #204
      DATE APPLIED:   2004-12-28 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      Refer to the patch description on the patch message.
    • 217 SEQ #205
      DATE APPLIED:   2005-02-04 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      Patch Description:
matching source record. To address this issue a utility has been written 
OREORV2                  N/A       8511634             217
 
Installation Instructions:
==========================
This patch should be loaded during non-peak hours to minimize disruption 
to users. Installation should take less than 2 minutes. Users are allowed 
to be on the system during the installation. TaskMan does not need to be 
stopped.
 
1. Use the INSTALL/CHECK MESSAGE option on the PackMan menu.
that will perform an analysis of the ORDERABLE ITEM FILE, file # 101.43, 
 
2. From the Kernel Installation and Distribution System Menu, select the 
Installation menu.
 
3. From this menu, you may elect to use the following options (when 
prompted for INSTALL NAME, enter OR*3.0*217):
    a. Backup a Transport Global
    b. Compare Transport Global to Current System
    c. Verify Checksums in Transport Global
 
and produce a detailed report of its findings. This utility will scan the 
4. Use the Install Package(s) options and select the package OR*3.0*217.
 
5. When prompted 'Want KIDS to INHIBIT LOGONS during install? YES//', 
respond "NO".
 
6. When prompted 'Want to DISABLE Scheduled Options, Menu Options and 
Protocols? YES//', respond "NO".
the ORDERABLE ITEM FILE record by record. This utility  determines the 
following about the current ORDBERABLE ITEM FILE record being processed:
 
1. Is the ID field null?
 
2. Is the source record IEN stored in the ID field null?
 
==================
3. Is the source record package code stored in the ID field null?
 
4. Is the data stored in the ID field properly formatted?
 
5. Is the source record package code part of the current interface 
specification?
 
6. Is there a matching source record?
 
7. Is it currently flagged as active?
This patch provides a utility, consisting of a set of three routines, to 
 
A temporary global is build tracking all of the above for a detailed 
report. Only an ORDERABLE ITEM FILE record passing all tests is modified.
At this point it will be flagged as inactive effective immediately. After
the utility has printed its report the temporary global created by this
utility is deleted. The utility is to be run at any time the null
subscript error is encountered during the ordering process.
 
It is these invalid orderable items with no matching source records that 
are generating the NULLSUBSCR errors described in the associated NOIS 
find records in the ORDERABLE ITEM FILE # 101.43 which do not have 
cases. The flagging of records in the ORDERABLE ITEM FILE # 101.43 
without matching source records as inactive will prevent CPRS GUI from 
presenting them to the user as valid orderable items. The routines in 
this patch can be run anytime a selected orderable item generates the 
NULLSUBSCR error.
 
Associated NOIS:
================
1. ALB-1001-51034 - UNDEF VAR LOAD+6~ORWDLR32
2. DAN-0204-42157 - Error on Order of Lab Test
matching records in their source files. It will flag any active Orderable 
3. NJH-0402-20607 - Receiving error message in CPRS
4. SBY-0803-30443 - LOAD+4~ORWDLR32:1,%DSM-E-NULLSUBSCR
 
OPTIONS
=======
 
CPRS Clean-up Utilities menu (ORE MGR, a menu option) was modified. A new 
option was added to it.
 
Orderable Items Records Validation (ORE ORDERABLE ITEMS VALIDATION, a run 
Item record without a matching source record as inactive and print a 
routine option) was created. It has been added to the CPRS Clean-up 
Utilities menu.
 
The menu path to the new option is:
        CPRS Manger Menu
        CPRS Configuration (IRM) - IR
        CPRS Clean-up Utilities - UT
        Orderable Items Records Validation - OI
 
HOW TO RUN THE UTILITY:
detailed report of its findings.
=======================
 
1. Enter the "CPRS Manager Menu".
 
2. Select the "CPRS Configuration (IRM)" option.
 
3. Select the "CPRS Clean-up Utilities" option.
 
4. Select the "Orderable Items Records Validation" option.
 
 
5. The user will be presented with a screen with a brief description of 
the option's functionality. At the "Do you wish to run this program? 
Enter Yes or No?" prompt enter Y for yes. Entering N for No will return 
the user to the menu.
 
6. The user will be prompted for a device for the utilities output. The 
output can be sent to the terminal screen. A printer for hard copy can be 
selected. This is recommended. It can be queued to the Kernel Spool and 
set to run at a preferred later time. 
 
The issue is an active orderable item record that does not have a 
ROUTINE SUMMARY:
================
The following routines are included in this patch.  The second line of 
each of these routines now looks like:
 ;;3.0;ORDER ENTRY/RESULTS REPORTING;**[Patch List]**;Dec 17, 1997
 
Routine name    Before Patch    After Patch        Patch List
============    ============    ===========        ==========
OREORV                   N/A       4346077             217
OREORV1                  N/A       3985270             217
    • 195
      DATE APPLIED:   2005-02-04 00:00:00
      APPLIED BY:   USER,ONE
    • 216 SEQ #207
      DATE APPLIED:   2005-02-12 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      CPRS M-side changes in support of removing allergies as
orders.  Please see the forum module for a complete description
of this patch.
    • 226
      DATE APPLIED:   2005-03-11 00:00:00
      APPLIED BY:   USER,ONE
    • 210
      DATE APPLIED:   2005-03-11 00:00:00
      APPLIED BY:   USER,ONE
    • 231
      DATE APPLIED:   2005-05-06 00:00:00
      APPLIED BY:   USER,ONE
    • 229 SEQ #212
      DATE APPLIED:   2005-05-06 00:00:00
      APPLIED BY:   USER,ONE
    • 211
      DATE APPLIED:   2005-05-25 00:00:00
      APPLIED BY:   USER,ONE
    • 234 SEQ #215
      DATE APPLIED:   2005-06-25 00:00:00
      APPLIED BY:   USER,ONE
    • 33
      DATE APPLIED:   1999-04-16 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      This patch will make the CPRS-ARTS interface compatible with the re-design
of the National Drug File.
    • 235
      DATE APPLIED:   2005-07-09 00:00:00
      APPLIED BY:   USER,ONE
    • 233 SEQ #217
      DATE APPLIED:   2005-08-13 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      Support for allergy data standardization updates that are needed
in the CPRS package.  Please see FORUM for a complete description.
    • 221 SEQ #218
      DATE APPLIED:   2005-10-20 00:00:00
      APPLIED BY:   USER,ONE
    • 239 SEQ #219
      DATE APPLIED:   2005-10-20 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      Refer to the patch description on the patch message.
    • 220 SEQ #220
      DATE APPLIED:   2005-11-15 00:00:00
      APPLIED BY:   USER,ONE
    • 240 SEQ #221
      DATE APPLIED:   2005-12-21 00:00:00
      APPLIED BY:   USER,ONE
    • 241 SEQ #222
      DATE APPLIED:   2006-01-12 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      Refer to the patch description on the patch message.
    • 237
      DATE APPLIED:   2006-03-08 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      This the OR part of a multi package patch to add Additional IV Drug Units
- MG-PE & NANOGRAM the primary patch will be in PSJ*5.0*152.
    • 247 SEQ #224
      DATE APPLIED:   2006-04-10 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      CORRECT THE FILING OF THE PATIENT NAME IN THE AUTO LINKED LIST PROCESS.
    • 215
      DATE APPLIED:   2006-05-05 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      CPRS GUI 26
    • 30
      DATE APPLIED:   1999-04-16 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      Refer to the patch description on the patch message.
    • 251 SEQ #226
      DATE APPLIED:   2006-05-26 00:00:00
      APPLIED BY:   USER,ONE
    • 258
      DATE APPLIED:   2006-07-11 00:00:00
      APPLIED BY:   USER,ONE
    • 257 SEQ #228
      DATE APPLIED:   2006-07-11 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      UPDATING ORWRP TIME/OCC LIMITS ALL PARAMETER
    • 264 SEQ #229
      DATE APPLIED:   2006-08-07 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
       This patch fixes an incorrect Web address for activating VistaWeb from
 CPRS. The parameter: ORWRP VISTAWEB ADDRESS is changed to:
  "https://vistaweb.domain.ext/ToolsPage.aspx"
    • 253 SEQ #230
      DATE APPLIED:   2006-09-23 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      FIX UNSIGNED ORDERS NOT GENERATING ALERTS.
MORE USEFUL NUMERIC PROMPT ERROR MESSAGES
FIX RESTRICTED PATIENT LIST SCROLLING BUG.
    • 228 SEQ #231
      DATE APPLIED:   2006-09-23 02:03:38
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      This patch is part of the Patient Financial Services System (PFSS) 
billing replacement system, business process improvements, and 
enhancements to Veterans Health Information Systems and Technology 
Architecture (VistA) to support integration with the COTS billing 
replacement system.  Significant changes to VistA legacy systems and 
ancillary packages are necessary.
 
Some of the PFSS software components are not operational until the PFSS 
On/Off Switch, distributed with patch IB*2*260, is set to "ON .  The 
ability for the local site to set the switch to "ON  will be provided at 
the appropriate time with the release of a subsequent Integrated Billing 
project.  PFSS patches are being released on various schedules.  Some 
patch.
 
For more information about the PFSS project, review the documentation 
accompanying this patch and refer to the following website: 
http://vista.domain.ext/billreplace/
 
The OR*3.0*228 patch is phase II of the CPRS portion of the PFSS 
project.  Phase I of the CPRS portion of the project is contained in 
OR*3.0*215.
patch functionality will not be active until a new PFSS switch is 
activated during final implementation. PFSS will initially be implemented 
at select pilot sites ONLY.
 
The purpose of the PFSS project is to prepare the VistA environment for 
the implementation of a commercial off-the-shelf (COTS) billing 
replacement system.  The project consists of the implementation of the
    • 261 SEQ #232
      DATE APPLIED:   2006-11-22 21:30:07
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      Corrects problem with CIDC assign parameter and disable for all providers.
    • 255 SEQ #233
      DATE APPLIED:   2006-11-22 22:39:11
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      This patch addresses two issues, First orderable items not turning off
Reminders. Second the DEA# and VA# fields are not being check, when
narcotics are ordered with the outpatient IV dialog in CPRS.
    • 250 SEQ #234
      DATE APPLIED:   2006-11-22 23:01:12
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      This patch addresses problems with:
-The LAB Quick Orders not displaying (CH) LAB Quick Orders.
-Expert System VITALS^ORQQVI not finding all vital measurements.
-Display Patient Alerts and Alert Recipients, display truncating Order 
 number.
    • 249 SEQ #235
      DATE APPLIED:   2006-11-22 23:49:38
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      THIS PATCH ADDRESSES A PROBLEM WITH THE PROBLEM LIST LEX SEARCH AND ADDS 
THE WOR DRUG TO THE ORDER CHECK  DUPLICATE DRUG CHECK WARNING.
    • 8
      DATE APPLIED:   1999-04-16 00:00:00
      APPLIED BY:   USER,ONE
    • 244 SEQ #236
      DATE APPLIED:   2006-11-23 00:20:09
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      This patch contains the routine ORY244 which will scan Order file #100 
for missing abnormal results, from Fileman date 3050901 to present and 
restore them.
    • 242 SEQ #237
      DATE APPLIED:   2006-12-11 16:17:21
      APPLIED BY:   USER,ONE
    • 260 SEQ #238
      DATE APPLIED:   2006-12-29 09:21:30
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      CPRS Miscelaneous fixes.
    • 254 SEQ #239
      DATE APPLIED:   2007-06-27 21:28:11
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      This patch corrects an error that was causing IV orders to only be 
valid for 6 minutes after the time the order was placed.
    • 270
      DATE APPLIED:   2007-06-27 22:09:16
      APPLIED BY:   USER,ONE
    • 248 SEQ #241
      DATE APPLIED:   2007-09-04 22:58:00
      APPLIED BY:   USER,ONE
    • 262 SEQ #242
      DATE APPLIED:   2007-09-04 23:05:35
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      Refer to the patch description on the patch message.
    • 245 SEQ #243
      DATE APPLIED:   2007-09-04 23:06:21
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      Adds option for editing quick orders by user.  Fixes bugs when editing 
quick orders.
    • 232 SEQ #244
      DATE APPLIED:   2007-09-04 23:07:49
      APPLIED BY:   USER,ONE
    • 267 SEQ #245
      DATE APPLIED:   2007-09-04 23:12:58
      APPLIED BY:   USER,ONE
    • 35
      DATE APPLIED:   1999-04-16 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      Refer to the patch description on the patch message.
    • 265 SEQ #247
      DATE APPLIED:   2007-09-04 23:39:02
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      This build/patch address 3 issues:
5. The correct IEN for pointer for Imaging is
checked and update if needed by the post init routine ORY26508.
6. Modify SESSION^ORCHECK to also check the ADVERSE REACTION ASSESSMENT 
(120.86) for allergies before assuming the error message stored at 
^OR(100,+ORIFN,9 is up to date and displaying the "no allergy assessment" 
error again upon signing the order.
7. If they comment is the same, set the ORDIALOG flag 
"FORMAT" to "@" to prevent the duplication of the comment in CPRS.
8. Modify MEDHIST^ORWPS to set ORPHMID regardless if the flag CKPKG for 
PSB*2.0*19 is set.  Use ORPHMID in the call to HISTORY^PSBMLHS instead
1. "AW" Cross Reference on TO field of File 100 not updated when order 
of ORPSID.
changes.
2. Lab Threshold exceeded warning not working when results has a greater 
than or less than symbol. Example: <5 or >5
3. Quick Orders not retaining Dosage when edited and dose is over 20 
characters.
4.Update the routine ORB3TIM2 to work the alert even when not passed in 
ORBLST (expired).
    • 271 SEQ #249
      DATE APPLIED:   2007-09-04 23:44:34
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      Correct CPRS RPC used by CAPRI, that was trying to return future 
appointments.
    • 275 SEQ #250
      DATE APPLIED:   2007-09-05 01:22:06
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      This patch corrects the issue introduced in OR*3.0*265 where pending 
orders no longer display the Medication Administration History.It also 
addresses a subscript error and a disk full error from ORWPS1
    • 263 SEQ #251
      DATE APPLIED:   2007-12-12 20:46:07
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
       
the start date.
 
3. Creating a new menu by copying an existing menu is resulting in an 
error.
 
4. If a patient has only clinical procedures reports in the Procedures 
(local only) section of the CPRS reports tab, the reports will not print 
to a printer.
This patch will address a few issues:
1.  When using the Search orders by nature or status option, if the user 
entere a start date of T-1 and an end date of T, the search will return 
no results.
 
2. In the option 'Search orders by nature or status', the help text for
the date ranges state that the start date must be older than the end
date. But the option will allow the user to enter an end date older than
    • 278 SEQ #252
      DATE APPLIED:   2007-12-12 21:29:08
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      Corrects the issue with Tasks accumulating while  waiting  for a 
partition. Caused by ORMEVNT exiting without unlocking a global that it 
locked.
    • 274 SEQ #254
      DATE APPLIED:   2007-12-12 21:43:56
      APPLIED BY:   USER,ONE
    • 277
      DATE APPLIED:   2007-12-12 22:15:02
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      CPRS GUI 26
    • 256 SEQ #255
      DATE APPLIED:   2008-02-03 22:04:48
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      Refer to the patch description on the patch message.
    • 279 SEQ #256
      DATE APPLIED:   2008-02-03 22:35:06
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      The purpose of this patch is to address an issue that has been reported 
 
   Problem:
   --------
   The problem deals with the display of the order information for 
   Outpatient prescriptions once the order has been accepted in CPRS.
 
   The drug name is missing from the order text in the display. The 
   problem was traced back to 
 
   Resolution:
with the drug name missing from pending orders.
   -----------
   OR*2.5*49 released a menu option that performs a conversion on
   the ORDER DIALOG (#101.41) file. The [ORCM CONVERT MENUS] option is
   being removed.
 
Overview:
=========
1. HD199896      Drug name missing from Pending Orders
    HD154624     duplicate
    HD157144     duplicate
    HD163806     duplicate
    • 287 SEQ #257
      DATE APPLIED:   2008-05-26 15:03:02
      APPLIED BY:   USER,ONE
    • 37
      DATE APPLIED:   1999-04-16 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
       
See patch OR*3*37 in the National Patch Module for description on this
build.
    • 246 SEQ #258
      DATE APPLIED:   2008-07-22 07:41:40
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      UPDATE ORDER DOSAGE WITH NEW FORMAT
    • 238
      DATE APPLIED:   2009-04-21 10:15:00
      APPLIED BY:   USER,SEVENTEEN
    • 281 SEQ #259
      DATE APPLIED:   2009-04-21 14:38:32
      APPLIED BY:   USER,SEVENTEEN
      DESCRIPTION:   
      1. A problem was discovered with the Results Reporting [OR RESULTS
may need some text moved to "Reason for Study". Since "Reason for Study"
   --------
   Radiology and Imaging quick orders may need to be updated as a result
   of the changes in OR*3*243.
 
   Resolution:
   -----------
   A new option will be provided, Radiology/Imaging Quick Order Search
   [ORCM RA SEARCH]. This option will search for Radiology and Imaging
   quick orders that have free text fields that contain text. A sample
   message and additional details are included below the 'Important 
has a size limit of 64 characters changes must be made by a person who can
   Notes' section.
 
3. HD0000000232271 Need routine to identify Radiology QOs with default
                   date
 
   Problem:
   --------
   Radiology and Imaging quick orders should no longer contain a default
   of TODAY for Date Desired. Sites need assistance in locating and 
   updating the quick orders that need to be updated.
review what, if any, portion of the text should be moved into the new
 
   Resolution:
   -----------
   The search option for item 2 includes a search for quick orders that
   contain either 'T' or 'TODAY' for the Date Desired prompt. In addition,
   the option will remove the Date Desired default as requested by the
   user. A sample message and additional details are included below.
 
***Important Notes*** 
If you identify quick orders that need to be updated, you must wait 
field. This patch will allow sites to produce a list of existing quick
until after the installation of OR*3*243 to make these updates. Use the
Enter/edit quick orders [ORCM QUICK ORDERS] option to update the quick 
orders, where appropriate. It may also be necessary for providers to edit
their personal quick orders.
 
Even disabled quick orders will be shown, for review purposes. The results
will be sent as a mail message to the person who ran the option. Please
note, it may be necessary for this menu option to be assigned to the
person responsible for the review (i.e. Clinical Coordinator and/or
Radiology ADPAC).
orders that should be reviewed. HD0000000217362
 
The following shows a sample message. It is difficult to read since it is 
formatted to print 132 characters. In the column for "Text or Start 
Date/Time", there will be a "T" or "D" to indicate "Text" or "Date".
 
Select OPTION NAME: ORCM RA SEARCH     RADIOLOGY/IMAGING QUICK ORDER
SEARCH
RADIOLOGY/IMAGING QUICK ORDER SEARCH
Clear Date Desired with a response of "TODAY"? Y
Exclude quick orders with STAT urgency? Y
 
 
Requested Start Time: NOW//  (NOV 19, 2007@11:36:42)
 
The check of Radiology/Imaging Quick Orders is queued
 (to start NOW).
 
YOU WILL RECEIVE A MAILMAN MESSAGE WHEN TASK #154113 HAS COMPLETED.
 
Sample mail message:
Subj: RADIOLOGY/IMAGING QUICK ORDERS  [#668609] 04/15/08@20:39  592 lines 
3. There should no longer be a default of 'TODAY' for "Date Desired" on a 
From: CPRS, SEARCH  In 'IN' basket.   Page 1
--------------------------------------------------------------------------
  The check of Radiology/Imaging Quick Orders is complete.
 
  Here is the list of all quick orders that should be reviewed: 
 
Quick Order Name                       Disable Text     Text or Start 
Date/Time
                 Ancestors/Menus or Reminders
  
Radiology quick order. Some sites have requested the ability to
RAGR CHEST 2 VIEWS PA&LAT STAT QO                       D: TODAY
                 On a menu or in an order set
                                                        T: POST OP SURGERY
 
RAGR CHEST 2 VIEW                      DISABLED         T: TEST
 
ORWDQ E87030CE                         no longer used   T: TESTING
 
ORWDQ 3A173B44                                          T: h/o high grade 
fever
automatically remove 'TODAY' from the "Date Desired" prompt. In addition,
 
End sample mail message
there was a request to be able to exclude quick orders with an order
REPORTING] menu after the installation of GMTS*2.7*85. This patch corrects
urgency of 'STAT'. HD0000000232271
 
Associated Remedy:
==================
1. HD0000000241916 GMTS *85 Problem
2. HD0000000217362 Need routine to identify potential quick order problems
3. HD0000000232271 Need routine to identify Radiology QOs with default
                   date 
 
Associated NSR(s):
this problem. HD0000000241916
==================
N/A
 
Test Sites:
===========
TBD 
 
Overview:
=========
1. HD0000000241916 GMTS *85 Problem
 
 
   Problem:
   --------
   After a site installed GMTS*2.7*85, they discovered an error would
   occur if they used the Results Reporting Menu [OR RESULTS REPORTING]
   option to display Health Summary results.  It was discovered that the
   variable XQORNOD was being set by the Order Entry Results Reporting
   package incorrectly, with only one piece, and this was causing a
   <SYNTAX>OP+3^XQCHK error to appear.
 
2. OR*3*243 will add a "Reason for Study" prompt to the Computerized 
   Example:
   --------
Select OPTION NAME: OR RESULTS REPORTING       Results Reporting Menu
Results Reporting Menu
 
Select Patient:    GMTS,TEST PATIENT       DOB    ######### 
 
 
 
                        R E S U L T S   R E P O R T I N G           
Patient Record System (CPRS) Graphical User Interface (GUI) "Order an
GMTS,TEST PATIENT     ###-##-####             DOB (AGE)       Wt (lb): NF
-------------------------------------------------------------------------
                            --- Main Results Menu ---
 
1    Health Summary                8    Daily Order Summary
2    Lab Results (Interim)         9    Order Summary for Date/time Range
3    Graph Lab Tests               10   Customized Order Summary
4    Blood Bank Report             11   Print Chart Copy Summary
5    Anatomic Pathology Report     12   Outpatient RX Profile
6    Vitals SF511 Report                        
Imaging Procedure" dialog. The "Reason for Study" requirement was
7    Vitals Cumulative Report           Ad Hoc Health Summary
 
Select Item(s): 1   Health Summary  
 
                             --- Health Summary ---
Select Health Summary Type: CLINICAL REMINDERS//   <<<Can choose any 
Health
                                                      Summary Type
DEVICE: HOME//   TELNET TERMINAL
 
implemented in the Radiology package with  RA*5.0*75. Existing Radiology
                                                           04/22/2008 
11:58
***************  CONFIDENTIAL CLINICAL REMINDERS SUMMARY  
*****************
I $D(XQORNOD) S 
%XQ=+XQORNOD,%XQ1=U_$P(XQORNOD,";",2),%XQ=@(%XQ1_%XQ_",0)"),
                                                       ^
XQOPT=$P(%XQ,U)_U_$P(%XQ,U,2)
<SYNTAX>OP+3^XQCHK
 
and Imaging quick orders that have text in "History and Reason for Exam"
   Resolution:
   -----------
   Routine ORPRS07 has been modified to properly set two pieces into
   XQORNOD and thus not generate the error when displaying Health Summary
   results when using the Results Reporting Menu [OR RESULTS REPORTING]
   option.
 
2. HD0000000217362 Need routine to identify potential quick order problems
 
   Problem:
    • 243
      DATE APPLIED:   2009-04-21 15:51:25
      APPLIED BY:   USER,SEVENTEEN
    • 299 SEQ #261
      DATE APPLIED:   2009-04-21 15:53:32
      APPLIED BY:   USER,SEVENTEEN
      DESCRIPTION:   
      1. For very lengthy patient instructions, there is the possibility that
The report will contain the orderable item name, dispense drug name, 
prescription number and the internal entry number (IEN) of the entry from 
the ORDERS file (#100) as well as other information about the patient and 
order. Below is a sample output for the report:
 
Subj: TRUNCATED PATIENT INSTRUCTIONS  [#660505] 02/28/08@23:43  7 lines
From: CPRS, SEARCH  In 'IN' basket.   Page 1  *New*
--------------------------------------------------------------------------
  The check for truncated Patient Instructions is complete.
 
they can be truncated when transferred from Outpatient Pharmacy V. 7.0 to
  Here is the list of the affected orders: 
 
Patient/Division      SSN   Item/Dispense         Status/RX#    Stop/OIEN
CPRSPATIENT,GENERAL   1234  ACETAZOLAMIDE TAB     ACTIVE        09/24/2008
DAYTON                      ACETAZOLAMIDE 250MG   2666845       12608385
 
In addition to reporting the orders, this routine will also correct the 
information in the ORDERS file (#100). It is important to check these 
orders and verify the corrected information is accurate.
 
Order Entry/Results Reporting V. 3.0. Patch OR*3.0*243 corrects the
Associated Remedy:
==================
1. HD0000000236377    Patient instructions are truncated
 
Associated NSR(s):
==================
N/A
 
Test Sites:
===========
problem with the truncation. However, there is no way to identify orders
TBD 
 
Overview:
=========
1. HD0000000236377   Patient instructions are truncated
 
   Problem:
   --------
   For very lengthy patient instructions, there is the possibility that 
   they can be truncated when transferred from Outpatient Pharmacy V. 7.0
that need to be corrected. This patch corrects this problem by creating a 
   to Order Entry/Results Reporting V. 3.0. Patch OR*3.0*243 corrects the
   problem with the truncation. However, there is no way to identify 
   orders that need to be corrected.
 
   Resolution:
   -----------
   Routine ORY299 will execute as a post-install routine. It will search
   through the last 365 days of Outpatient prescriptions, comparing
   patient instructions. A report will be sent to the person who installed
   the patch. In addition, the routine will use the patient instructions
routine to search through the previous 365 days of Outpatient 
   from Pharmacy to correct truncated patient instructions.
prescriptions, comparing patient instructions. A report will be sent to 
the person who installs the patch. It will be sorted by division.
    • 304
      DATE APPLIED:   2009-04-22 15:20:01
      APPLIED BY:   USER,SEVENTEEN
    • 303 SEQ #264
      DATE APPLIED:   2009-04-22 16:09:08
      APPLIED BY:   USER,SEVENTEEN
    • 301 SEQ #265
      DATE APPLIED:   2009-04-23 10:51:12
      APPLIED BY:   USER,SEVENTEEN
      DESCRIPTION:   
      The description of this patch may be found in the National Patch Module 
under OR*3.0*301.
    • 292 SEQ #266
      DATE APPLIED:   2009-04-23 10:54:24
      APPLIED BY:   USER,SEVENTEEN
      DESCRIPTION:   
      1. A site reported a problem with accessing a patient's records afte r
 
Associated Remedy:
==================
1. HD0000000223856 Intermittent Error message when signing lab orders.
2. HD0000000069676  help description no longer true
 
Associated NSR(s):
==================
N/A
 
their system was co-located. A problem was discovered with the length of
Test Sites:
===========
 
Overview:
=========
1. HD0000000223856 Intermittent Error message when signing lab orders.
 
   Problem:
   --------
   The problem has to do with errors occasionally showing up when
the lock timeouts. This patch corrects this problem by modifying the locks
   attempting to sign orders. However, the message detail shows no name
   for the person who is working on the order.
 
   Resolution:
   -----------
   The lock timeouts in routine ORX2 have been updated to use the new
   system parameter.
 
2. HD0000000069676 help description no longer true
 
to use the system parameter for timeouts, if available. HD0000000223856
   Problem:
   --------
   The problem has to do with the description associated with the OR
   OREMAS MED ORDERS parameter. The description does not indicate that
   this parameters only affects Inpatient Medications orders.
 
   Resolution:
   -----------
   The DESCRIPTION field (#8989.512) of the PARAMETER DEFINITION file
   (#8989.51) was updated to accurately reflect what orders are covered by
 
   this paramter.
2. A site reported an issue with the help text/description associated with
the parameter OR OREMAS MED ORDERS. The description for this parameter
does not make it clear that it only affects Inpatient Medications orders. 
HD0000000069676
    • 285 SEQ #267
      DATE APPLIED:   2009-04-23 11:01:12
      APPLIED BY:   USER,SEVENTEEN
      DESCRIPTION:   
      Currently, the Computerized Patient Record System (CPRS) V. 1.0 uses the
 
A new software package, Clinical Observations, will also collect patient
vital signs but store the records in a different file. However, both GEN.
MED. REC. - VITALS V. 5.0 and the new Clinical Observations package will
update the Clinical Reminders Index global, specifically, the 120.5
section. This patch ensures that vitals information, regardless of its'
source will continue to display appropriately on the CPRS cover sheet.
 
Associated Remedy:
==================
GMRV VITAL MEASUREMENT file (#120.5) to retrieve vitals information to
HD 222625       CPRS Vitals API
 
Associated NSR(s):
==================
N/A
 
Test Sites:
===========
TBD 
 
display on the Cover Sheet.
Overview:
=========
1. HD222625     CPRS Vitals API
 
   Problem:
   --------
   Vitals information will no longer be stored in file 120.5. CPRS must
   retrieve data using the Clinical Reminders Index global.
 
   Resolution:
 
   -----------
   CPRS access to retrieve vitals information will now be retrieved using
   the Clinical Reminders Index global and the Application Programming
   Interface (API) provided by the GEN. MED. REC. - VITALS V. 5.0 package.
The purpose of this patch is to modify the retrieval of vitals 
information to use the Clinical Reminders Index global in conjunction 
with a standard Application Program Interface supplied by the GEN. MED. 
REC. - VITALS V. 5.0 package. No functional changes are included, only the
access method.
    • 24
      DATE APPLIED:   1999-04-16 00:00:00
      APPLIED BY:   USER,ONE
    • 289 SEQ #268
      DATE APPLIED:   2009-04-23 11:17:47
      APPLIED BY:   USER,SEVENTEEN
      DESCRIPTION:   
      1. When an Outpatient complex prescription contains an EXCEPT conjunction 
corrects this problem by prompting for 'Give additional dose NOW' if the 
schedule does not have a schedule type of 'ONE-TIME'. 
HD0000000277913, PSPO #1140
there is a problem when it is transferred to Inpatient Medications. The 
new order created does not adequately reflect the provider's intent. This 
patch corrects this problem by no longer allowing an Outpatient complex 
order with a conjunction of 'EXCEPT' to be transferred to Inpatient. 
HD0000000269669, PSPO #1031
 
2. With the release of OR*3*243, there is no longer a 'Give additional 
dose NOW' prompt in the [ORCM QUICK ORDERS] menu option. This patch
    • 282 SEQ #269
      DATE APPLIED:   2009-04-23 13:49:44
      APPLIED BY:   USER,SEVENTEEN
      DESCRIPTION:   
      1. A site reported that the parameter ORQQLR DATE RANGE INPT does not
and time of the parent order. when an inpatient is selected. 
HD0000000069365, HD0000000069851
 
3. When entering a continuous lab order, with a response to 'How Long?'
that exceeds one day, the stop date is displaying incorrectly. The change
in item #2 for ORCSEND1 corrects this issue, as well, The collection date
and time of the last child order created will be used as the stop date and
time of the parent order. HD0000000070009
 
4. A provider accidentally selected both a parent lab order as well as
honor the value at the location level. Routine ORWCV has been modified to
multiple child orders and then chose the action of 'discontinue'. Upon 
signature, an error box displayed indicating the order had already been
signed. Two changes have been made to address this issue. 
 
First, lab orders will no longer display the parent order. Only the child
orders will be displayed once the parent order is signed and released to
service. Routine ORCSEND1 has been modified to 'veil' the parent order
once the child orders are all created.
 
Second, routine ORQ2 was modified to include the parent's stop date and
include the patient's location when an inpatient is selected. 
time in the detail display of the child order. This refers to the detail
display from the Orders tab. HD0000000070670
 
5. When troubleshooting an alert problem, it appears that the child orders
for a lab order do not show all the needed information. Routine ORCSEND3
was modified to treat child orders exactly as parent orders or a single
lab order. All the available information, such as signature, order checks,
etc. will now be found in the detailed display of each child order.
HD0000000069279
 
2. When entering continuous lab orders with schedules that have a 'once
daily' frequency, a response to 'How Long?' of n or xn should calculate
the same stop date/time. Routine ORCSEND1 has been modified to use the
collection date and time of the last child order created as the stop date
    • 212
      DATE APPLIED:   2009-06-09 15:36:08
      APPLIED BY:   USER,SEVENTEEN
      DESCRIPTION:   
      This patch implements the interface between CPRS and VBECS, installing
a new order dialog and other supporting components.  CPRS and VBECS are
both required to install this patch.
    • 298 SEQ #271
      DATE APPLIED:   2009-06-24 14:40:52
      APPLIED BY:   USER,SEVENTEEN
      DESCRIPTION:   
      Refer to the patch description on the patch message.
    • 283 SEQ #272
      DATE APPLIED:   2009-07-02 12:34:23
      APPLIED BY:   USER,SEVENTEEN
      DESCRIPTION:   
      1. A site reported a problem with duplicate orders in Inpatient
the ORWDX routine.
 
4. During unit testing of the changes for the problem of duplicate 
orders, an issue was found with locking of patient events. When multiple 
orders for the same event are manually released, a lock on the patient 
event remains after the process is completed.
 
 
Overview:
=========
Medications V. 5.0. If there were delayed-event orders manually released
1. HD0000000199004     Discontinued order not showing in CPRS
   HD0000000069901     duplicate
   HD0000000070256     duplicate
   HD0000000092874     duplicate
   HD0000000165137     duplicate
   HD0000000174026     duplicate
   HD0000000280582     duplicate
   HD0000000300668     duplicate
 
   Problem:
at the same time that the associated event occurred, duplicate orders were
   --------
   A series of delayed orders for Inpatient Medications was written. The 
   orders were released to the service manually from the Computerized 
   Patient Record System (CPRS) GUI at the same time the associated
   patient movement was performed. This resulted in some of the orders
   being duplicated in Inpatient Medications.
 
   Resolution:
   -----------
   The locking logic in the release process has been modified to handle 
sent to the service. PSI-07-128
   this situation. If the movement and manual release begin at the same 
   time, only one will be allowed to process the orders. Routine ORWDX 
   was modified to handle this.
 
   In addition to the locking issue that was identified, there was a 
   check added to ORWDX to ensure that the order had not already been 
   released by a movement if the user selected manual release. This check 
   already existed in the movement routine.
 
2. HD0000000281619     Delayed Radiology orders discontinuing on release
 
   HD0000000284481     duplicate
 
   Problem:
   --------
   Delayed Radiology orders were being rejected by Radiology upon manual 
   release. The error message was 'missing/invalid location'.
 
   Resolution:
   -----------
   Routine ORWDX has been modified to record the location and treating    
2. Two of the test sites reported a problem regarding the change in item 
   specialty for an order after the lock is successful, but before 
   transmitting the order to the service.
 
3. HD0000000298397     Intermittent ORWDX errors
 
   Problem:
   --------
   Under certain conditions, an error occurs in ORWDX when attempting to
   build the error message back to the user.
 
#1 adversely affecting delayed Radiology orders.
   Resolution:
   -----------
   Routine ORWDX has been modified to ensure the error message array
   contains all the appropriate information so that no error will occur
   when the patient event is locked.
 
4. HD0000000307535     Manual release of delayed orders could leave event 
                       lock
 
   Problem:
 
   --------
   When manually releasing more than one delayed order for a single 
   patient event, the event can remain locked once the process finishes.
   Specifically, ^ORE(100.2,event number,0) will remain locked.
 
   The problem is that routine ORWDX issues an incremental lock for the 
   patient event associated with each order that is being released.
   However, when the process completes, a single 'unlock' is issued. For 
   example: three orders, associate with event number 9573 are manually 
   released. When the process completes, the following entry remains in
3. Two test sites reported a problem of receiving intermittent errors in 
   the lock table:
   38) 20E5C892 2       ^["^^_$1$DGA228:[CHEY19.VBB]"]ORE(100.2,9573, 0)
 
   Solution:
   ---------
   Routine ORWDX has been modified to only issue one lock per event, 
   regardless of the number of orders released that are associated with
   the event.
    • 296
      DATE APPLIED:   2009-08-28 10:15:32
      APPLIED BY:   USER,SEVENTEEN
    • 302
      DATE APPLIED:   2009-09-24 10:47:29
      APPLIED BY:   USER,SEVENTEEN
    • 268 SEQ #275
      DATE APPLIED:   2009-09-28 11:33:27
      APPLIED BY:   USER,SEVENTEEN
      DESCRIPTION:   
      A site reported a patient safety issue with the alert information 
 
In the interim, the alert text is being modified to alleviate some of the 
confusion. In addition, some documentation updates are being made to 
remind sites to enable both of the alerts to ensure the provider gets all 
the appropriate information.
 
The NAME field (.01) and the MESSAGE TEXT field (.03) of the OE/RR 
NOTIFICATIONS file (#100.9) are being modified for alerts 22 and 25 
(internal entry numbers for the two alerts). Alert 22 is being changed 
from IMAGING RESULTS to IMAGING RESULTS, NON CRITICAL. Alert 25 is being 
displayed when imaging results, either abnormal or not, are completed. 
changed from ABNORMAL IMAGING RESULTS to ABNL IMAGING RESLT, NEED ATTN.
 
The change is being made using a post-installation routine. The person 
installing the patch will receive a MailMan message with a subject of 
'OE/RR NOTIFICATIONS ALERT NAME UPDATES' when the update is complete.
 
This patch requires a change in the Radiology/Nuclear Medicine V. 5.0 
package. The documentation changes to update the notification name will 
be included in a separate documentation release.
 
The problem stems from the fact that the alerts can be disabled and, if 
Please note: the post-install routine, ORY268, will be removed in a 
future patch.
 
Associated Remedy:
==================
1. HD0000000132027 Imaging Results versus Abnormal imaging results
 
Associated NSR(s):
==================
N/A
so, due to the text of the alert, the provider may miss some critical 
 
Test Sites:
===========
TBA
 
Overview:
=========
 
1. HD0000000132027 Imaging Results versus Abnormal imaging results
 
information.
   Problem:
   =========
   The Radiology Package currently always sends the following alert 
   notifications to OERR/CPRS, conditioned on the type of result (normal, 
   abnormal, amended - normal or abnormal)
      22 - IMAGING RESULTS (contains normal results)
      25 - ABNORMAL IMAGING RESULTS (contains abnormal results)
      53 - IMAGING RESULTS AMENDED (contains both normal and abnormal)
   Based on the parameter settings, some of these alerts may not display. 
   Due to the text of the alert subject, this may be misleading for the 
 
   provider.
 
   Solution:
   =========
   The 'imaging results' notification may refer to both normal and 
   abnormal results. The abnormal results are non-critical. The agreement 
   between the Computerized Patient Record System (CPRS) Clinical
   Workgroup and the Radiology subject matter expert is to modify the
   text of alerts 22 and 25 to reduce the confusion. Alert 22 will    
   become 'IMAGING RESULTS NON CRITICAL'. Alert 25 will become 'ABNL
The final solution is considered an enhancement and the Radiology subject 
   IMAGING RESLT, NEED ATTN'.
matter expert will be working with the patient safety office to formulate 
a new service request to outline the desired behavior.
    • 295
      DATE APPLIED:   2009-11-18 09:56:39
      APPLIED BY:   USER,SEVENTEEN
    • 319 SEQ #277
      DATE APPLIED:   2010-01-05 17:00:32
      APPLIED BY:   USER,SEVENTEEN
      DESCRIPTION:   
      The description of this patch may be found in the National Patch Module
under OR*3*319.
    • 41
      DATE APPLIED:   1999-04-16 00:00:00
      APPLIED BY:   USER,ONE
    • 307 SEQ #278
      DATE APPLIED:   2010-03-17 10:13:49
      APPLIED BY:   USER,SEVENTEEN
      DESCRIPTION:   
      The description of this patch may be found in the National Patch Module
under OR*3*307.
    • 309 SEQ #279
      DATE APPLIED:   2010-03-25 16:17:03
      APPLIED BY:   USER,SEVENTEEN
      DESCRIPTION:   
      Refer to the patch description on the patch message.
    • 290 SEQ #280
      DATE APPLIED:   2010-07-22 15:50:16
      APPLIED BY:   USER,SEVENTEEN
      DESCRIPTION:   
      A site reported a problem where a narcotic order replaced an audiology 
   Upon examining the order affected in the ORDERS file (#100), it was 
   discovered that an Outpatient Pharmacy prescription had over-written
   the audiology consult.
 
   Resolution:
   -----------
   An issue was found in the Class III code which performs the AudioCare 
   renewal process. The issue was in the difference between how the 
   Computerized Patient Records System (CPRS) assigns a new order number
   and the process AudioCare renewal was using.
consult order.
 
   The decision was to create a Class I interface from the AudioCare 
   refill/renewal system. The refill portion will not be affected. The 
   renewal process will now use a standard CPRS Application Programming 
   Interface (API) to perform the renewal.
 
Overview:
=========
HD0000000296920    Unexpected narcotic order found in OERR for a patient
 
   Problem:
   --------
    • 316 SEQ #281
      DATE APPLIED:   2010-10-18 11:28:45
      APPLIED BY:   USER,SEVENTEEN
      DESCRIPTION:   
      This patch will correct the following problems.
 
HD0000000339814 - Glucophage Contrast Media Order Check not triggered.
 
   Glucophage Contrast Media and Glucophage Lab Results Order Checks are 
   not triggered for a metformin order with lower case letters in the drug
   name.  For instance, a site using TALLman lettering for a metformin
   order (metFORMIN) did not fire checks.
    • 330 SEQ #282
      DATE APPLIED:   2010-10-19 11:16:55
      APPLIED BY:   USER,SEVENTEEN
      DESCRIPTION:   
      The description of this patch may be found in the National Patch Module
under OR*3*330.
    • 317 SEQ #283
      DATE APPLIED:   2010-11-16 09:54:25
      APPLIED BY:   USER,SEVENTEEN
      DESCRIPTION:   
      This patch corrects 2 issues within the ORDER ENTRY/RESULTS REPORTING 
package:
 
1. Signing multiple Lab Collect orders can result in a crash if their 
   collection time has passed.
 
2. IV Medication quick orders do not show the "Give additional dose NOW?" 
   prompt when appropriate.
    • 336 SEQ #284
      DATE APPLIED:   2011-01-10 11:51:21
      APPLIED BY:   USER,SEVENTEEN
      DESCRIPTION:   
      A site reported a problem where a narcotic order replaced an audiology 
   Upon examining the order affected in the ORDERS file (#100), it was 
   discovered that an Outpatient Pharmacy prescription had over-written
   the audiology consult.
 
   Resolution:
   -----------
   An issue was found in the Class III code which performs the AudioCare 
   renewal process. The issue was in the difference between how the 
   Computerized Patient Records System (CPRS) assigns a new order number
   and the process AudioCare renewal was using.
consult order.
 
   The decision was to create a Class I interface from the AudioCare 
   refill/renewal system. The refill portion will not be affected. The 
   renewal process will now use a standard CPRS Application Programming 
   Interface (API) to perform the renewal.
 
Overview:
=========
HD0000000296920    Unexpected narcotic order found in OERR for a patient
 
   Problem:
   --------
    • 323 SEQ #285
      DATE APPLIED:   2011-02-10 10:58:52
      APPLIED BY:   USER,SEVENTEEN
      DESCRIPTION:   
      This patch corrects the following issue within the ORDER ENTRY/RESULTS
 
HD0000000377607 - DC1+5^ORCSEND Errors
 
   The Order file's veiled field originally was used to hide unreleased 
   orders many years ago. The functionality was brought to use once more 
   by patch OR*3*282 to hide lab parent orders once they are signed.
   Unfortunately, it was not discovered that running the Lab Order Checks
   clean up utilities purged old veiled orders. This functionality may 
   have been appropriate for unsigned new orders but not for signed parent
   orders.
REPORTING package:
 
HD0000000352115 - Delayed order release event for repeating lab quick 
                  order.
 
   A repeating lab order with a released delay will wrongly copy the value
   Ordering Parameters Location field found in the firing event to the
   Ordering Location of the child order.
    • 294 SEQ #286
      DATE APPLIED:   2011-03-03 11:30:33
      APPLIED BY:   USER,SEVENTEEN
    • 293
      DATE APPLIED:   2011-03-08 13:52:03
      APPLIED BY:   USER,SEVENTEEN
    • 29
      DATE APPLIED:   1999-04-16 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      This patch corrects several problems withg Lab ordering via CPRS List
Manager.
    • 280
      DATE APPLIED:   2011-03-08 13:52:57
      APPLIED BY:   USER,SEVENTEEN
      DESCRIPTION:   
      The description of this patch may be found in the National Patch Module
under OR*3*280.
    • 337
      DATE APPLIED:   2011-03-08 13:57:21
      APPLIED BY:   USER,SEVENTEEN
      DESCRIPTION:   
      The description of this patch may be found in the National Patch Module
under OR*3*280.
    • 272
      DATE APPLIED:   2011-04-28 16:07:00
      APPLIED BY:   USER,SEVENTEEN
    • 339 SEQ #291
      DATE APPLIED:   2011-06-28 12:31:45
      APPLIED BY:   USER,SEVENTEEN
      DESCRIPTION:   
      This patch resolves the following problems:
 
  Implemented key filtering and range checking for daily dosages. Problem 
  with auto-calculation of daily dosage, and problem changing tablets in
  daily dosing.
 
  <UNDEFINED> error on start-up, which occurs when entering a New Patient 
  whose most recent INR was cancelled.
    
  Replacing the number of tablets in daily dosing may result in a zero 
  being appended unintentionally.
 
 
  Division by zero error in Rosendaal Report, which occurs when 
  patienthas two consecutive INRs which are identical, one in-range and 
  one-out, due to goal range change. 
    
  Problem where lab orders were not being placed by Anticoagulator unless 
  a note was also written. This was happening because the Order Entry API 
  requires an Encounter Location, and the corresponding variable was only 
  being set if a note was also entered.
 
  Assure that cosigner is identified as primary provider in PCE, if user 
  Problem where changes in the patient location were not being recorded 
  when the user clicked on the Save and Exit button.
    
  The original application didn't allow INRs to be ordered for collection 
  on the weekend. Site's reported that they often need to order for 
  weekend collection. The application was modified to inform the user 
  that the date they selected for the next draw is a Saturday (or 
  Sunday), and allow them to leave it or change it, as they deem 
  appropriate.
  is a non-Provider (e.g., Student, Pharmacy Tech, etc.).
 
  Problem with Other Indication not being "remembered" between sessions.
    
  Assure that Scheduled (in addition to Pending or Active) Consults get 
  completed when Initial Note is filed.
    • 346 SEQ #292
      DATE APPLIED:   2011-08-12 13:59:33
      APPLIED BY:   USER,SEVENTEEN
    • 333
      DATE APPLIED:   2011-09-08 14:09:05
      APPLIED BY:   USER,SEVENTEEN
      DESCRIPTION:   
       This patch will correct an issue with complex orders entered through
 CPRS. If the complex order uses a THEN conjunction and the admin time of 
 a single section of the order is before the current time, that
 administration was being dropped off. This would only happen on a section
 of the complex order other than the first section.
    • 338 SEQ #294
      DATE APPLIED:   2011-10-13 11:46:09
      APPLIED BY:   USER,SEVENTEEN
      DESCRIPTION:   
      This patch will correct an index out of bounds error that occurs when a 
user adds too many coversheet reports to the CPRS gui.
    • 329 SEQ #295
      DATE APPLIED:   2011-10-21 11:33:40
      APPLIED BY:   USER,SEVENTEEN
      DESCRIPTION:   
      Unseen orders are being auto-unflagged when processing a flagged orders 
alert.
 
A flagged order recipient doesn't see a notification if an order is 
flagged too soon after a previous flagged order.
    • 332 SEQ #296
      DATE APPLIED:   2011-11-29 12:49:10
      APPLIED BY:   USER,SEVENTEEN
      DESCRIPTION:   
      Refer to the patch description on the patch message.
    • 297 SEQ #297
      DATE APPLIED:   2011-12-12 15:14:26
      APPLIED BY:   USER,SEVENTEEN
      DESCRIPTION:   
      1. Patch OR*3*281 added a temporary menu option and routine to the system
be used. This patch removes PHARMACY as an option.
4. Enter/edit quick orders [ORCM QUICK ORDERS] option would get an 
undefined error when editing the infusion rate field if the text was over 
20 characters in length.
to assist in cleaning up Radiology quick orders. This patch removes that
option and routine. HD0000000218893
2. Patch OR*3*299 added a temporary routine to the system to clean up 
problem Outpatient medication orders. This patch removes that routine.
HD0000000284146
3. Enter/edit QO restriction [ORCM QO ITEMS] allows PHARMACY as a 
restriction. However, the code that processes restrictions does not check 
for this. The workgroup decision was that the specific package needed to
    • 36
      DATE APPLIED:   1999-04-16 00:00:00
      APPLIED BY:   USER,ONE
    • 204 SEQ #298
      DATE APPLIED:   2012-01-04 09:10:18
      APPLIED BY:   USER,SEVENTEEN
      DESCRIPTION:   
      Problem:
 
Resolution:
Modified routine ORCACT0 to disallow the transfer of a complex order with 
THEN as the conjunction.
 
Associated Remedy:
==================
HD0000000205100  -  1 Complex Orders Transferring for Providers
 
 
A site reported a problem with the transfer of complex Outpatient 
Associated NSR(s):
==================
N/A
 
 
Test Sites:
===========
Medication orders that contained a conjunction of THEN. The problem is 
that when the order goes (in its entirety) to Inpatient Medications there 
is no way for the provider or the finishing pharmacist to determine how 
far into the process the order has progressed.
 
The patient safety workgroup recommended that transfer of Outpatient 
medication orders with a THEN conjunction should be prevented.
    • 318 SEQ #299
      DATE APPLIED:   2012-01-04 09:10:27
      APPLIED BY:   USER,SEVENTEEN
      DESCRIPTION:   
      This patch corrects an issue within the ORDER ENTRY/RESULTS REPORTING 
package:
 
HD0000000343856 - If there are multiple lab orders in a given day then
the Lab Orders clinical report will only display one.
    • 347 SEQ #300
      DATE APPLIED:   2012-01-13 10:50:47
      APPLIED BY:   USER,SEVENTEEN
      DESCRIPTION:   
      This patch will correct the following issues:
 
4)Incorrect data is showing up on the Search orders by Nature or Status 
  [OR NATURE/STATUS ORDER SEARCH] report.
1)Relative dates are not saving time in custom views in the CPRS orders 
  tab.
 
2)Data on the clinical surgery report is hanging over from one item to 
  another.
 
3)When creating a new patient movement, discontinued orders are 
  displaying on the "Copy active orders for selected event" dialog
    • 324 SEQ #301
      DATE APPLIED:   2012-02-01 11:43:20
      APPLIED BY:   USER,SEVENTEEN
      DESCRIPTION:   
      This patch will correct the following issues
and/or dietetic orders, the auto discontinue of these orders is not being
recorded in the OE/RR PATIENT EVENT file (#100.2). There is also a rare
circumstance in which if the user discharging the patient is assigned to a
different division than the location of the ward. The entry to the OE/RR
PATIENT EVENT file (#100.2) is not created.
When a patient is discharged and the user, at the Review Delayed Orders 
prompt, enters "^^" or lets the system timeout the discharge process does
not fully complete. Once the Review Delayed Orders prompt is exited in one
of the ways described above, processes that are supposed to take place
during the discharge don't happen. This is causing some orders to not
discontinue.
 
It was discovered that if a patient is discharged and only has pharmacy
    • 340 SEQ #302
      DATE APPLIED:   2012-02-13 14:06:40
      APPLIED BY:   USER,SEVENTEEN
      DESCRIPTION:   
      This patch is part of the Identification of Principal Mental Health
Provider(IPMHP) project.  It is to be released in conjunction with PCMM
patch SD*5.3*575, with SD*5.3*575 being installed first.  The purpose of
this patch is to implement the API being released in SD*5.3*575 to display
the Principal Mental Health Provider in two locations within CPRS GUI, one
being the patient detail display and the other being the Primary Care
button detailed display.
    • 327 SEQ #303
      DATE APPLIED:   2012-03-23 12:51:47
      APPLIED BY:   USER,SEVENTEEN
      DESCRIPTION:   
      1.  HD0000000377325 - 9 SHWTLT+10^XPAREDT3 Error 
    selection.
 
 3. HD0000000300224 - 2 LAB QUICK ORDER
    --------------------------------------------
    When building a quick order the How long field does not properly
    apply the Max days limit when using Xnumber of times format.
 
 4. HD0000000406792 - 3 Standard Schedule (Changed) Creates Endless 
    Loop for Finishing Pharmacist
    --------------------------------------------
    --------------------------------------------
    When renewing an order with an invalid/changed schedule, IV orders
    are not properly verified.
    Selecting the GUI Reports User Display Parameters option causes a 
    SHWTLT+10^XPAREDT3 Error.
 
 2. HD0000000069559 - 9 PUG-1101-51042  Can't change user values-Report 
    parameters 
    --------------------------------------------
    The GUI Reports User Display Parameters option does not allow user
    • 314 SEQ #304
      DATE APPLIED:   2012-03-29 18:37:06
      APPLIED BY:   USER,SEVENTEEN
      DESCRIPTION:   
      This patch corrects an issue with a recursive lookup that causes a very
long pause in the software.  It also corrects a situation where a user
can select a large number of items to replace, but only some of them are
updated.
    • 284 SEQ #305
      DATE APPLIED:   2012-04-18 16:26:52
      APPLIED BY:   USER,SEVENTEEN
      DESCRIPTION:   
      1. The Display Patient Alerts and Alert Recipeients [ORB3 ALERT
information is written over the previous information. This patch corrects 
this problem by having the chart review information behave the same as the
other verify actions. If an action is chart reviewed, and the previous
action was not chart reviewed, the current chart review information is
used for the previous action. HD0000000268742
RECIPIENTS] option always uses the default action of 'Close' - even when 
there is more than one screen of alerts. This patch modifies this 
behavior so that if a screen is not the last screen of the display, the 
default action is 'Next Screen'. HD0000000069366
2. The Orders tab detailed display shows the order along with the most
recent Chart Review information. However, when there is a change to the
original order, and that change has a chart review performed, the detail
information is incorrect. The problem is that the current chart review
    • 341 SEQ #306
      DATE APPLIED:   2012-08-29 12:17:49
      APPLIED BY:   USER,SEVENTEEN
      DESCRIPTION:   
      This patch will correct the following issues:
3)A subscript error when an ordernumber of 0 is sent back to the ORWDX1 
ORDMATCH Remote procedure call.
1)An undefined error when a patient in observation is discharged.
 
2)When using the Manage orderable items [ORCM ORDERABLES MENU] for 
editing orderable items, orderable items are selectable for edit by 
internalentry number (IEN) even if they are not in the appropriate 
display group.
    • 322 SEQ #307
      DATE APPLIED:   2012-08-29 12:23:03
      APPLIED BY:   USER,SEVENTEEN
      DESCRIPTION:   
      This patch corrects 4 issues within the ORDER ENTRY/RESULTS REPORTING 
   option Medication Quick Order Report [OR MEDICATION QO CHECKER]. If 
   the user enters a lower case letter 'n' the report runs anyway.
 
3. When using the remove function for VistA option Team List Mgmt Menu
   [ORLP TEAM MENU] the special number '999' is used to display more 
   patients. When the list contains more than 998 patients, the entry
   '999' removes the patient in position 999 instead of displaying more
   patients.
 
4. When using the remove function for VistA option Team List Mgmt Menu
package:
   [ORLP TEAM MENU] the special number '999' is used to display more 
   patients. When the list contains more than 39 patients and one of the 
   patients has an IEN of 999, the entry '999' has you select between the 
   patient and the more option.
 
1. Cancelling orders from a Delayed Orders list in CPRS (Computerized 
   Patient Record System) GUI (Graphical User Interface) causes them 
   to appear in the Active Orders list. They should be filtered out 
   until the release event happens.
 
2. Patch OR*3*296 added the prompt 'Do you wish to continue?' to Vista
    • 2
      DATE APPLIED:   1999-04-16 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      This patch is described in the National Patch Module under OR*3*2.
    • 34
      DATE APPLIED:   1999-04-16 00:00:00
      APPLIED BY:   USER,ONE
    • 357
      DATE APPLIED:   2012-08-29 12:24:52
      APPLIED BY:   USER,SEVENTEEN
      DESCRIPTION:   
      The description of this patch may be found in the National Patch Module 
under OR*3.0*357.
    • 362 SEQ #309
      DATE APPLIED:   2012-11-01 11:57:08
      APPLIED BY:   USER,SEVENTEEN
      DESCRIPTION:   
      The purpose of this patch is to provide a software bug fix for CPRS.  
This patch corrects the following issue:
 
-Schedule change error for IMO orders
    • 331 SEQ #310
      DATE APPLIED:   2012-11-13 16:03:17
      APPLIED BY:   USER,SEVENTEEN
      DESCRIPTION:   
      This patch corrects 4 issues within the ORDER ENTRY/RESULTS REPORTING 
 
3. Copying a lab order with a static date results in a new order with a 
   blank date.
 
4. Copying a lab order will not generate a duplicate check against the
   original order.
package:
 
1. Copying a generic order that used static dates (eg Jul 9, 
   2010) instead of relative dates (eg T+3) may result in a new order with
   invalid dates.
 
2. Renewing a nursing order with static dates may result in a new order 
   with invalid dates.
    • 313 SEQ #311
      DATE APPLIED:   2013-01-03 11:51:31
      APPLIED BY:   USER,SEVENTEEN
      DESCRIPTION:   
      This patch updates the OE/RR NOTIFICATION (#100.9) alert CONSULT/REQUEST
UPDATED to inform the user of all actions that triggers the alert. The 
patch also updates the ORDER DIALOG (#101.41) entry GMRCOR REQUEST to 
always prompt the user with the RELATED SERVICES saved on the Quick Order 
and allow them to change it, if needed.  The help text when creating a 
new prompt has been updated to remove the "subfile" wording.
    • 351 SEQ #312
      DATE APPLIED:   2013-01-03 11:51:39
      APPLIED BY:   USER,SEVENTEEN
      DESCRIPTION:   
      This patch will correct the following
 
1. When a patient has changed clinics and is displaying on the team 
   list for the new clinic. They are not being removed from the old
   clinic's team list.
 
2. When listing all patients on a clinic team list using the 
   Anticoagulation Patinet Lists [ORAM PATIENT LIST MENU] option, patients
   whos name begins with the letter Z do not show up.
    • 352 SEQ #313
      DATE APPLIED:   2013-02-12 10:38:12
      APPLIED BY:   USER,SEVENTEEN
      DESCRIPTION:   
      This is a companion patch to the Medication Order Check Healthcare 
Application (MOCHA) version 1.0 Enhancements 1 group of patches that will
resolve a number of issues with the Computerized Patient Record System
(CPRS) version 3.0 order checking functionality. See the patch message for
a full listing of issues addressed and installation instructions.
    • 315 SEQ #314
      DATE APPLIED:   2013-02-13 12:02:14
      APPLIED BY:   USER,SEVENTEEN
      DESCRIPTION:   
      1. In the Computerized Patient Record System (CPRS), on the Labs tab,
2. In CPRS, on the Labs tab, under Microbiology, the accession number
display should be changed to show the COTS accession number. This patch
makes this change by looking for the presence of the API GETACC^LRJWLST
and, if present, uses the API to retrieve the COTS accession number from
the LAB DATA file (#63). If no COTS accession number is available, the 
legacy accession number will display.
 
3. Laboratory V5.2 patch LR*5.2*425 is adding the ability to inactivate a
collection sample. CPRS will now honor the INACTIVE DATE (#64.9101) field
in the COLLECTION SAMPLE (#62) file.
under Anatomic Pathology, the accession number display should be changed
 
4. An error was occurring in CPRS when attempting to display the Anatomic 
Pathology supplemental report. The error was caused by a modification 
done in support of the LEDI v4 release. In order to eliminate the error, 
a modification was done to CPRS to support the LEDI v4 change.
 
5. There are two new order reasons being used by Laboratory V5.2. They 
are Obsolete Order and Purged Order. A request was made that these two 
reasons be added to the ORDER REASON file (#100.03). The post install of 
this patch will automatically add these reasons.
to show the Commercial-Off-The-Shelf (COTS) accession number. This patch
 
6. The Lab users have requested that when certain fields are updated in 
the LABORATORY TEST (#60) file, there should be a CPRS call made to search
for quick orders that contain the test that was updated. If any are found,
the appropriate personnel will be notified. This patch addresses this
issue by creating a new routine ORLRQO that will search for the specified
test and notify the members of the OR CACS mail group. They will be told
the quick order name and whether it is active or inactive.
 
7. Since the COTS system, when present, will now be considered the Lab
makes this change by looking for the presence of the Application
system of record, the date/time completed from the COTS system should be
what is stored in the Lab system as the date/time completed. However, this
might cause some concern on the CPRS side since there may be a delay if
the interface from VistA to the COTS system is down for any reason. In
order to help mitigate this issue, this patch will modify the information
stored in the RESULTS DATE/TIME field (#71) of the ORDER file (#100) to
contain the date/time the results information was sent to CPRS, rather
than the date/time completed from the COTS system.
 
8. Laboratory V5.2 patch LR*5.2*425 is adding the ability to inactivate a
Programming Interface (API) GETACC^LRJWLST. If that API exists, CPRS will
topography. CPRS will now honor the INACTIVE DATE (#64.9103) field
in the TOPOGRAPHY FIELD (#61) file.
 
9. The Laboratory Lab System Re-engineering project (LSRP) has requested
an API to allow Lab to unveil an order in CPRS. This patch adds that new
API.
 
10. LSRP has requested an API to update the PACKAGE REFERENCE field (#33) 
of the ORDER file (#100). This patch adds that new API.
use it to retrieve the COTS accession number from the LAB DATA file 
(#63). If no COTS accession number is available, the legacy accession 
number will display.
    • 348
      DATE APPLIED:   2013-05-16 12:56:04
      APPLIED BY:   USER,SEVENTEEN
      DESCRIPTION:   
      The description of this patch may be found in the National Patch Module 
under OR*3.0*348.
    • 218
      DATE APPLIED:   2013-06-14 08:59:40
      APPLIED BY:   USER,SEVENTEEN
      DESCRIPTION:   
      CONTAINS COMPONENTS NEEDED TO COMPLETE THE PRE-INSTALLATION OF
COMPUTERIZED PATIENT RECORD SYSTEM (CPRS) VERSION 29. REFER TO THE PATCH
DESCRIPTION FOR INSTALLATION INSTRUCTIONS AND COMPONENT INFORMATION.
    • 306
      DATE APPLIED:   2013-06-14 09:03:05
      APPLIED BY:   USER,SEVENTEEN
      DESCRIPTION:   
      The description of this patch may be found in the National Patch Module
under OR*3*306.
    • 38
      DATE APPLIED:   1999-04-16 00:00:00
      APPLIED BY:   USER,ONE
    • 371
      DATE APPLIED:   2013-06-14 09:03:27
      APPLIED BY:   USER,SEVENTEEN
    • 366 SEQ #319
      DATE APPLIED:   2013-06-20 11:08:32
      APPLIED BY:   USER,SEVENTEEN
    • 356 SEQ #320
      DATE APPLIED:   2013-08-29 11:11:38
      APPLIED BY:   USER,SEVENTEEN
      DESCRIPTION:   
      This patch will correct the following issues:
 
3) In certain scenarios, when entries to the Orders File (#100) are  
   deleted, there are dangling cross references that are left behind. 
   These cause errors during nightly processing and cprs order views.
1) When ordering certain types of quick orders. Information about the 
   order such as service connected and treatment factors display, even 
   though there has been no opportunity to enter this information about 
   the order.
 
2) When orderable items are flagged to display an alert to the provider 
   when they are expiring. They were not creating alerts correctly for 
   the outpatient paramter.
    • 363 SEQ #321
      DATE APPLIED:   2013-09-04 09:45:32
      APPLIED BY:   USER,SEVENTEEN
    • 354 SEQ #322
      DATE APPLIED:   2013-09-05 13:01:32
      APPLIED BY:   USER,SEVENTEEN
      DESCRIPTION:   
      This patch will correct the following issues:
   range (TTR) using the Rosendaal method count inactive patients. 
   This is incorrect because the Rosendaal method makes no mention of 
   missed appointments.
 
4) It is possible to create progress notes that contain no text. This 
   is caused by the user having the ability to continue and file the 
   note before making a selection about what data to put in the note.
 
5) The patients lost to follow up utility does not take missed 
   appointments into account. This will cause a provider to incorrectly 
1) When running the Anticoagulation Management GUI, in some cases 
   believe that a patient has been seen, where he/she may have, in 
   reality, just missed an appointment.
   
6) Error "'' is not a valid floating point value" is displaying when 
   entering 0.25 as the tablet size for a Monday dose.
   the help file will fail to be found.
  
2) After a Missed Appointment has been filed, there are cases in 
   which the Daily dosing schedule and total weekly dose don't 
   coincide with what has been entered into the patient notes.
 
3) The clinic and facility-wide calculation of the time in therapeutic
    • 320 SEQ #323
      DATE APPLIED:   2013-09-10 10:41:20
      APPLIED BY:   USER,SEVENTEEN
      DESCRIPTION:   
      This patch corrects 1 issue within the ORDER ENTRY/RESULTS REPORTING 
package:
 
1. The Patient Selection screen can be set up to display a clinic's 
   appointments for a date range. The screen will show no more than 200
   appointments. The screen does not show the user any message that the
   maximum has been reached and that some of the appointments for the date
   range are not being displayed. The appointments dropped can be from any
   part of the date range.
    • 380 SEQ #324
      DATE APPLIED:   2013-10-18 16:27:55
      APPLIED BY:   USER,SEVENTEEN
    • 266 SEQ #325
      DATE APPLIED:   2013-12-12 14:11:53
      APPLIED BY:   USER,SEVENTEEN
      DESCRIPTION:   
      In support of the Clinic Orders project, a need has been identified to 
send Nurse Verify information from the Computerized Patient Record System 
V. 1.0 to Inpatient Medications V. 5.0. The purpose of this patch is to 
make this modification.
    • 372 SEQ #326
      DATE APPLIED:   2014-01-06 16:15:59
      APPLIED BY:   USER,SEVENTEEN
    • 383 SEQ #327
      DATE APPLIED:   2014-02-05 14:16:54
      APPLIED BY:   USER,SEVENTEEN
    • 39
      DATE APPLIED:   1999-04-16 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      Delayed orders for allergies were not properly released to the ADVERSE
orders were being left in an active status. This caused confusion in the
display of allergy orders. 
 
 
This patch will correct the above problems.
 
 
This patch includes one new protocol, OR GMRA UPDATE and also includes the
GMRAOR ALLERGY ENTER/EDIT order dialog. 
 
REACTION TRACKING (ART) package upon patient movement. The status of the
Changes have been made to the GMRAOR ALLERGY ENTER/EDIT order dialog and
its items in support of allergy entry via the CPRS GUI. 
 
A new routine ORMGMRA is also exported with this patch.
orders was not properly updated to active upon patient movement.
 
When an order for NO KNOWN ALLERGIES was entered, these orders were not
displaying properly with allergy orders. The post-install for this patch
will correct the "AW" cross-reference on all NKA orders in the file.
 
When a reaction to a causitive agent was entered, pre-existing NKA
    • 349 SEQ #328
      DATE APPLIED:   2014-02-20 15:04:01
      APPLIED BY:   USER,SEVENTEEN
      DESCRIPTION:   
      This patch will correct the following issues:
  
4) When a mail message from AudiCare Auto-renwal is alerting about an 
   invalid Provider status, the provider in question is not known.
1) Parameter definition description missing for OR AUTORENEWAL USER.
 
2) Renewed prescriptions processed by AUDIOCARE are showing the user 
   who processed audiocare renewals as the person who entered the 
   renewal.
 
3) Mail messages from AudioCare Auto-renewal are not displaying 
   enough information to identify a patient in CPRS.
    • 370 SEQ #329
      DATE APPLIED:   2014-03-07 08:55:29
      APPLIED BY:   USER,SEVENTEEN
      DESCRIPTION:   
      Prevent notes without text from being signed
    • 345
      DATE APPLIED:   2014-04-07 17:23:33
      APPLIED BY:   USER,SEVENTEEN
    • 311
      DATE APPLIED:   2014-04-07 17:24:03
      APPLIED BY:   USER,SEVENTEEN
      DESCRIPTION:   
      CONTAINS FOLLOW-UP FIXES FOR ORDER ENTRY/RESULTS REPORTING SOFTWARE 
VERSION 3.0 PATCH 345 (OR*3*345). REFER TO THE PATCH DESCRIPTION FOR 
INSTALLATION INSTRUCTIONS AND COMPONENT INFORMATION.
    • 381
      DATE APPLIED:   2014-04-07 17:24:18
      APPLIED BY:   USER,SEVENTEEN
      DESCRIPTION:   
      THIS PATCH CORRECTS THE SAME PATIENT SAFETY ISSUE CORRECTED IN PATCH 
OR*3*380, HOWEVER, IT INCORPORATES OTHER CHANGES MADE BY PATCH OR*3*311, 
PART OF THE MOCHA 2 BUILD. REFER TO THE PATCH DESCRIPTION FOR A DETAILED 
EXPLANATION.
    • 367 SEQ #333
      DATE APPLIED:   2014-04-14 10:46:38
      APPLIED BY:   USER,SEVENTEEN
    • 384 SEQ #334
      DATE APPLIED:   2014-04-14 10:46:45
      APPLIED BY:   USER,SEVENTEEN
    • 334 SEQ #335
      DATE APPLIED:   2014-04-21 16:06:48
      APPLIED BY:   USER,SEVENTEEN
      DESCRIPTION:   
      This patch corrects 1 issue within the ORDER ENTRY/RESULTS REPORTING 
package:
 
1. The Auto-unflagging of orders with the ORPF AUTO UNFLAG parameter set
   to YES has resulted in pharmacy queries or reccomendations not being
   read or responded to.
    • 375 SEQ #336
      DATE APPLIED:   2014-04-23 09:19:37
      APPLIED BY:   USER,SEVENTEEN
      DESCRIPTION:   
      Delayed order-Framestack-Cumulative Report fixes
    • 286 SEQ #337
      DATE APPLIED:   2014-04-24 14:17:21
      APPLIED BY:   USER,SEVENTEEN
      DESCRIPTION:   
      This patch corrects 3 issues within the ORDER ENTRY/RESULTS REPORTING 
   the Cover Sheet and the Vitals entry form.
package:
 
1. Changing an unsigned order does not update the entering provider.
 
2. Chart Copies are enabled for printing even when no format has 
   been set up.
 
3. There is a discrepancy in metric measure conversions for weight between
    • 27
      DATE APPLIED:   1999-04-16 00:00:00
      APPLIED BY:   USER,ONE
    • 379 SEQ #338
      DATE APPLIED:   2014-06-10 09:39:13
      APPLIED BY:   USER,SEVENTEEN
      DESCRIPTION:   
      Modified the API LMENTRY^ORB3U1 to properly parse out the alert message 
containing the CV tagged data in addition to the current parsing 
mechanism in place.
    • 388 SEQ #339
      DATE APPLIED:   2014-06-24 11:16:20
      APPLIED BY:   USER,SEVENTEEN
    • 361
      DATE APPLIED:   2014-08-05 16:37:19
      APPLIED BY:   USER,SEVENTEEN
      DESCRIPTION:   
      The description of this patch may be found in the National Patch Module
under OR*3*361.
    • 392 SEQ #341
      DATE APPLIED:   2014-08-07 10:07:29
      APPLIED BY:   USER,SEVENTEEN
      DESCRIPTION:   
      CPRS RPC changes for the VIA project. See patch description for further 
details.
    • 374 SEQ #342
      DATE APPLIED:   2014-08-11 17:34:40
      APPLIED BY:   USER,SEVENTEEN
      DESCRIPTION:   
      See patch description for full content description.
    • 386 SEQ #343
      DATE APPLIED:   2014-08-14 14:37:22
      APPLIED BY:   USER,SEVENTEEN
    • 394 SEQ #344
      DATE APPLIED:   2014-08-26 17:01:36
      APPLIED BY:   USER,SEVENTEEN
    • 111 SEQ #345
      DATE APPLIED:   2014-09-02 12:55:02
      APPLIED BY:   USER,SEVENTEEN
      DESCRIPTION:   
      The purpose of this patch is to provide an API to Pharmacy for returning 
the nature of order for a CPRS order.
    • 273 SEQ #346
      DATE APPLIED:   2014-09-05 10:09:25
      APPLIED BY:   USER,SEVENTEEN
      DESCRIPTION:   
      This patch corrects 6 issues within the ORDER ENTRY/RESULTS REPORTING 
4. CPRS will allow a duplicate team list name when entering personal 
   lists.
 
5. Occasionally, the option ORLP3M DISPLAY LIST SOURCE displays the
   current user's list source instead of the selected user.
 
6. Various ORLP options do not timeout when selecting a list in use 
   elsewhere.
package relating to team lists:
 
1. Error on entering "^" at the Type prompt of option ORLP TEAM ADD.
 
2. Team list visibility is changed when edited.
 
3. Locks are set late when creating or renaming lists.
    • 385
      DATE APPLIED:   2014-09-05 10:11:38
      APPLIED BY:   USER,SEVENTEEN
      DESCRIPTION:   
      The description of this patch may be found in the National Patch Module
under OR*3.0*385.
    • 9
      DATE APPLIED:   1999-04-16 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      Note: This patch can only be installed at sites running CPRS.
From: SHAPIRO.NANCY@SANFRANCISCO.DOMAIN.EXT    Page 1
--------------------------------------------------------------------------
 
I stumbled onto this minor problem.  If I access options in
the following order, I get my DUZ displayed instead of my name.
 
PATIENT LIST MGMT MENU
 DISPLAY USER'S TEAMS
TEAM LIST MGMT MENU
 EXAMINE/PRINT EXISTING LIST(S)  <--- DUZ appears instead of user's name
 
 
Select Patient List Mgmt Menu Option [TEST]: ?
 
   PS     Patient Selection Preference Mgmt ...
   TM     Display User's Teams
   PT     Display Patients Linked to a User via Teams
   TE     Team List Mgmt Menu ...
 
Select Patient List Mgmt Menu Option [TEST]: TM  Display User's Teams
 
Addresses NOIS: SFC-0198-60744
Find teams linked to user: SHAPIRO,NANCY//          NS     IRM
 
 
             SHAPIRO,NANCY IS ON THE FOLLOWING TEAMS:
 
12/31/97                                      PAGE:  001
--------------------------------------------------------------------------
1 NANCY
 
 
 
Select Patient List Mgmt Menu Option [TEST]: ?
 
   PS     Patient Selection Preference Mgmt ...
   TM     Display User's Teams
   PT     Display Patients Linked to a User via Teams
   TE     Team List Mgmt Menu ...
 
Select Patient List Mgmt Menu Option [TEST]: TE  Team List Mgmt Menu
Select Team List Mgmt Menu Option [TEST]: ?
 
Fixes a team list display problem as reported and described by Nancy
   CR     Create/Add to      Team List
   EX     Examine/Print      Existing List(s)
   PR     Remove             Providers from a List
   PT     Remove             Patients from a List
   DE     Delete             Existing List(s)
   AL     Remove             Autolinks
 
Enter ?? for more options, ??? for brief descriptions, ?OPTION for help
text.
 
Shapiro at San Francisco:
 Select Team List Mgmt Menu Option [TEST]: EX  Examine/Print      Existing
 
 Select LIST to examine/print: 1003201// 
 
 
Subj: CPRS TEAM DISPLAY PROBLEM  [#491781] 31 Dec 97 10:59 PDT  74 Lines
    • 353 SEQ #348
      DATE APPLIED:   2014-09-05 10:11:56
      APPLIED BY:   USER,SEVENTEEN
      DESCRIPTION:   
      The International Classification of Diseases, Tenth Revision (ICD-10) 
alpha-numeric characters. This value does not include the decimal point, 
which follows the third character for the ICD-10-CM code set. There is no 
decimal point in the ICD-10-PCS code set. 
 
These code sets have the potential to reveal more about quality of care, 
so that data can be used in a more meaningful way to better understand 
complications, better design clinically robust algorithms, and better 
track the outcomes of care. ICD-10-CM also incorporates greater 
specificity and clinical detail to provide information for clinical 
decision making and outcomes research.
Class 1 Software Remediation project replaces the 30-year-old set of 
diagnosis and procedure codes (ICD-9-CM) that medical personnel use. 
Dates of service, or dates of discharge for inpatients, that occur on or 
after the implementation date will use the ICD-10 code set. Clinical 
Modification (ICD-10-CM) diagnosis codes increase from about 13,000 ICD-9 
codes to more than 68,000. Procedure Coding System (ICD-10-PCS) procedure 
codes increase from about 3,800 ICD-9 codes to nearly 87,000. Both 
systems also expand the number of characters allotted to seven
    • 404
      DATE APPLIED:   2014-11-10 16:46:17
      APPLIED BY:   USER,SEVENTEEN
    • 398
      DATE APPLIED:   2015-01-28 15:54:31
      APPLIED BY:   USER,SEVENTEEN
      DESCRIPTION:   
      The description of this patch may be found in the National Patch Module
under OR*3.0*398.
    • 312 SEQ #351
      DATE APPLIED:   2015-03-17 16:46:04
      APPLIED BY:   USER,SEVENTEEN
      DESCRIPTION:   
      Refer to the patch description on the patch message.
    • 391
      DATE APPLIED:   2015-05-20 09:11:02
      APPLIED BY:   USER,SEVENTEEN
      DESCRIPTION:   
      The description of this patch may be found in the National Patch Module
under OR*3.0*391.
    • 406
      DATE APPLIED:   2015-09-16 11:10:12
      APPLIED BY:   USER,SEVENTEEN
      DESCRIPTION:   
      Sets the ORWRP TIME/OCC LIMITS INDV parameter at the Package level for 
several OE/RR REPORT file entries.
    • 418 SEQ #354
      DATE APPLIED:   2015-09-16 11:26:05
      APPLIED BY:   USER,SEVENTEEN
      DESCRIPTION:   
      Emergency release of 30.A to address ICD10 issues.
    • 409 SEQ #355
      DATE APPLIED:   2015-10-07 16:04:50
      APPLIED BY:   USER,SEVENTEEN
      DESCRIPTION:   
      The purpose of this patch is to provide a software bug fix for CPRS 
orders functionality.  This patch addresses the following issues:
 
-'Treating Specialty' disappears when order is renewed or Give Additional 
Dose Now is selected.
    • 410
      DATE APPLIED:   2015-12-01 17:42:29
      APPLIED BY:   USER,FIFTYFOUR
      DESCRIPTION:   
      This patch corrects 2 issues within the ORDER ENTRY/RESULTS REPORTING 
package:
 
1. Non-OERR alerts are being deleted without the rights to do so.
 
2. Typo in the CPRS User Guide:GUI Version.
    • 387
      DATE APPLIED:   2015-12-11 14:36:43
      APPLIED BY:   USER,SEVENTEEN
      DESCRIPTION:   
      This build changes the source of Primary Care information in the 
header and details wondow from VistA to PCMMR.
    • 43
      DATE APPLIED:   1999-04-16 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      See description on patch message.
    • 411 SEQ #358
      DATE APPLIED:   2015-12-11 14:40:41
      APPLIED BY:   USER,SEVENTEEN
    • 402 SEQ #359
      DATE APPLIED:   2016-01-08 11:42:23
      APPLIED BY:   USER,FIFTYFOUR
      DESCRIPTION:   
      OR*3.0*402
    • 395 SEQ #360
      DATE APPLIED:   2016-01-27 15:27:37
      APPLIED BY:   USER,FIFTYFOUR
    • 389 SEQ #361
      DATE APPLIED:   2016-03-10 14:52:31
      APPLIED BY:   USER,FIFTYFOUR
    • 350
      DATE APPLIED:   2016-03-10 15:48:08
      APPLIED BY:   USER,FIFTYFOUR
      DESCRIPTION:   
      This build contains the OE/RR items affected by the rename of EARLIEST 
DATE (123;17) to CLINICALLY INDICATED DATE.
This build should restore the M routines, order dialogs, and ORCDGMRC
EARLIEST DATE DEFAULT parameter to a pre-OR*3.0*350 state.
    • 424
      DATE APPLIED:   2016-03-10 17:00:55
      APPLIED BY:   USER,FIFTYFOUR
    • 390
      DATE APPLIED:   2016-04-07 16:02:28
      APPLIED BY:   USER,FIFTYFOUR
    • 426 SEQ #365
      DATE APPLIED:   2016-05-04 12:53:04
      APPLIED BY:   USER,FIFTYFOUR
    • 269
      DATE APPLIED:   2016-05-26 15:49:16
      APPLIED BY:   USER,FIFTYFOUR
      DESCRIPTION:   
      CONTAINS ROUTINE UPDATES THAT WILL ENABLE COMPUTERIZED PATIENT RECORD 
SYSTEM (CPRS) VERSION 1.0.29 TO DISPLAY SIGNS/SYMPTOMS WITH MEDICATION 
ORDER CHECK MESSAGES AND WILL ENABLE REMOTE DATA INTEROPERABILITY (RDI) 
TO RETRIEVE SIGN/SYMPTOM, SEVERITY, AND OBSERVED/HISTORICAL DATA FOR AN 
ADVERSE REACTION FROM THE HEALTH DATA REPOSITORY (HDR). REFER TO THE 
PATCH DESCRIPTION FOR INSTALLATION INSTRUCTIONS AND FURTHER INFORMATION.
    • 433 SEQ #367
      DATE APPLIED:   2016-09-16 13:40:41
      APPLIED BY:   USER,FIFTYFOUR
      DESCRIPTION:   
      OR RPC updates for VIAB*1*7.
    • 26
      DATE APPLIED:   1999-04-16 00:00:00
      APPLIED BY:   USER,ONE
    • 422 SEQ #368
      DATE APPLIED:   2016-09-23 15:53:34
      APPLIED BY:   USER,FIFTYFOUR
      DESCRIPTION:   
      The OR*3.0*422 patch allows the use of special characters (particularly 
 
--------
With the switch to using CPRS GUI Order Menus rather than ListManager 
ordering menu options, there remains a limitation on the characters 
allowed to build menu items.  Specifically, the equal sign (=), comma 
(,), semi-colon (;), and hyphen (-) are restricted when they do not need 
to be.
 
Resolution:
-----------
Remove the restrictions on certain special characters by modifying the 
Use of the following special characters will now be allowed: hyphen (-), 
CHKNAM tag inside the ORUTL routine in order to remove the restriction 
for the characters stated above.  The up-arrow (^) still remains as a 
restricted character because of M (MUMPS) restrictions.
 
Test Sites:
 
Hunter Holmes McGuire VA Medical Center (Richmond)
 
Orlando VA Medical Center
 
semicolon (;), comma (,), and equal sign (=). Use of the caret (^) is 
William S. Middleton Memorial Veterans Hospital (Madison)
 
VA Central Plains Health Care System (Omaha, Lincoln, Grand Island of NE, 
Des Moines, Knoxville, Iowa City of IA)
 
 
Documentation Retrieval Instructions
------------------------------------ 
 
 
still restricted because it is used as a field delimiter in VistA. 
Pre/Post Installation Overview
------------------------------
 
 
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.
 
 
 
Installation Instructions
-----------------------------
1.      Choose the PackMan message containing this patch.
 
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 
Additional changes will be made to the Data Dictionary elements of the 
        following options. When prompted for the INSTALL NAME enter
        OR*3.0*422.
 
        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 option will
            allow you to view all changes that will be made when this 
ORDER DIALOG (#101.41) file to modify the Help displayed when entering a 
            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.
 
4.      From the Installation Menu, select the Install Package(s) option 
        and choose the patch to install.
 
5.      When prompted 'Want KIDS to Rebuild Menu Trees Upon Completion of
question mark at a VistA prompt. The affected fields are: 
        Install? NO// Press <Enter>
 
6.      When prompted 'Want KIDS to INHIBIT LOGONs during the install? 
        NO// Press <Enter>
 
7.      When prompted 'Want to DISABLE Scheduled Options, Menu Options, 
        and Protocols? NO// Press <Enter>
 
8.      If prompted "Delay Install (Minutes):  (0 - 60): 0// respond 0.
 
 
 
Post-Installation Instructions
N/A
* ORDER DIALOG (#101.41) file, DISPLAY TEXT (#2) field 
punctuation) within the Order Menu Management Menu Editor. A previous 
 
* ORDER DIALOG (#101.41) file, ITEMS (#10) sub-file, DISPLAY TEXT (#4) 
field 
 
This intake has been implemented locally at the VA centers in Fargo, ND; 
Sioux Falls, SD; Meade, MD; Minneapolis, MN; Omaha, NE; Richmond, VA; St. 
Cloud, MN; Seattle, WA; Milwaukee, WI; Hot Springs, AR; Des Moines, IA; 
and Iowa City, IA. 
 
The NSR for this intake addresses the following requirement: 
VistA patch disallowed use of special characters. The patch was intended 
 
* VHBAO: NEED3045 Provide the ability for the users to include 
punctuation and other special characters in CPRS order menu notes.
 
Patch Components
================
 
Files & Fields Associated:
 
File Name (Number)       Field Name (Number)       New/Modified/Deleted
to prevent display problems within ListManager; however, most sites are 
---------------------    --------------------      --------------------
ORDER DIALOG (#101.41)   DISPLAY TEXT (#2)         MODIFIED
 
ORDER DIALOG,
ITEMS (#101.412)         DISPLAY TEXT (#4)         MODIFIED
 
 
 
Forms Associated:
 
using the Computerized Patient Record System (CPRS) Graphical User 
Form Name                File #       New/Modified/Deleted
---------                ------       --------------------
N/A
 
Mail Groups Associated:
 
Mail Group Name          New/Modified/Deleted
---------------          --------------------
N/A
 
Interface (GUI) and the inability to utilize punctuation can negatively 
Options Associated:
 
Option Name            Type               New/Modified/Deleted
-----------            ----               --------------------
N/A
 
Protocols Associated:
 
Protocol Name       New/Modified/Deleted
-------------       --------------------
impact the clarity of menu options and instructions. This modification 
N/A
 
Security Keys Associated:
 
Security Key Name
-----------------
N/A
 
Templates Associated:
 
restores the ability to use certain special characters in Order Menu 
Template Name      Type      File Name (Number)  New/Modified/Deleted 
-------------      ----      ------------------  --------------------
N/A
 
Additional Information:
 
 
New Service Requests (NSRs)
----------------------------
NSR 20131108 REMOVE LISTMANAGER RESTRICTIONS ON MNEMONICS
Management so that users can more clearly specify order menu options. 
 
Patient Safety Issues (PSIs)
-----------------------------
N/A
 
Remedy Ticket(s) & Overview
---------------------------
N/A
 
Problem:
    • 423
      DATE APPLIED:   2016-09-23 15:54:37
      APPLIED BY:   USER,FIFTYFOUR
      DESCRIPTION:   
      The description of this patch can be found in the National Patch Module.
    • 425 SEQ #370
      DATE APPLIED:   2016-12-12 12:10:14
      APPLIED BY:   USER,FIFTYFOUR
      DESCRIPTION:   
      Patch OR*3.0*425 allows inpatient delayed 
specific scenario in which inpatient delayed 
orders are written for an admission event, 
but then the patient is not admitted (post 
treatment/post procedure the patient remains 
an outpatient) and the delayed orders are 
required at an outpatient location, such as 
a Post Anesthesia Care Unit. Under the current 
functionality, these inpatient delayed orders 
cannot be released to the outpatient location 
because the admission event never occurred. 
orders (with the exception of Unit-Dose 
After implementation of this patch, the delayed 
orders (with the exception of Unit-Dose Meds 
orders and Diet orders) can be successfully 
released to an outpatient location.
Meds orders and Diet orders) to be manually 
released to outpatient locations. Without 
this modification, care to patients can be 
delayed while providers re-enter orders 
previously entered as inpatient orders.
 
This solution is designed to address the
    • 417 SEQ #371
      DATE APPLIED:   2016-12-20 14:57:32
      APPLIED BY:   USER,FIFTYFOUR
      DESCRIPTION:   
      OR*3.0*417 makes changes to order details in support of Bar Code
order:
 
1.      PSS*1*191
2.      PSJ*5*315
3.      PSB*3*83
4.      PSB*3*87
5.      OR*3*417
 
ATTENTION: This enhancement also includes a new Graphical User Interface
(GUI) executable, BCMA GUI PSB3_P083.EXE. Installation of this GUI is
Medications Administration (BCMA) and Inpatient Medications enhancements
required immediately after the KIDS install for the Patch to function.
 
For retrieval and installation instructions, please see the Client 
Installation Instructions section.
 
**************************************************************************
 
The change made by OR*3*417 is in support of requirements for patch
PSB*3.0*83.  All the patches in this group should be installed  prior to 
patch OR*3.0*417.
for Transdermal Administrations.
 
The change will add a line to the Order Details report and the Medication
Administration History Report in the Computerized Patient Record System
(CPRS). These reports will display the Removal times for Medications
that Require Removal (MRRs).
 
******************************* ATTENTION ********************************
  
Clinical Ancillary Services (CAS) Development-Delivery of Pharmacy 
Enhancements (DDPE) VA Inpatient Medication Administration - Transdermal
enhancement includes 5 patches which must be installed in the following
    • 421
      DATE APPLIED:   2017-01-23 14:26:30
      APPLIED BY:   USER,FIFTYFOUR
      DESCRIPTION:   
      Changes were needed in OE/RR to store data for the eHMP (Enterprise 
repository for the eHMP data.
 
The changes include tracking when an Order was flagged or unflagged by a 
user.  There were also changes to store clinical data in the JDS for 
unsigned, as well as signed, orders.  Additionally, discontinued orders 
now trigger updates to the JDS.
 
Includes changes related to patches: 286,424,269
Health Management Platform).  The eHMP needed data that has dates and 
times with seconds and also required triggers when relevant OE/RR data 
were created and/or edited.  The OR* namespace routines were modified to 
call the appropriate eHMP API (application programmer interface) line 
tags, where needed.
 
These eHMP APIs store the data with a date and time stamp that has 
seconds, which are required by the JDS (JSON data store).  The JDS is the
    • 415 SEQ #373
      DATE APPLIED:   2017-03-10 13:27:55
      APPLIED BY:   USER,FIFTYFOUR
      DESCRIPTION:   
      OR*3.0*415
    • 420 SEQ #374
      DATE APPLIED:   2017-04-03 13:50:25
      APPLIED BY:   USER,FIFTYFOUR
      DESCRIPTION:   
      Patch OR*3.0*420 modifies the existing Pharmacy package in VistA to
Item will be displayed in the Information field in the Medication Order 
-----------------
N/A
 
 
Templates Associated:
 
Template Name      Type      File Name (Number)  New/Modified/Deleted 
-------------      ----      ------------------  --------------------
N/A
 
dialog once an Orderable Item is selected. Once a dispense drug is chosen 
 
Additional Information:
N/A
 
 
New Service Requests (NSRs)
----------------------------
20100311  CPRS LAB MONITORING
 
 
(by selecting a dosage in the order dialog), the lab test information 
Patient Safety Issues (PSIs)
-----------------------------
N/A
 
 
Remedy Ticket(s) & Overview
---------------------------
N/A
 
Problem:
will be replaced by the National Standard Drug Information found in the
--------
 
Resolution:
-----------
 
 
Test Sites:
----------
James H. Quillen VA Medical Center (Mountain Home)      
VA Maryland Healthcare (Baltimore, Loch Raven & Perry Point)        
MESSAGE (#101) field of the DRUG (#50) file. This message currently
Tomah VA Medical Center
Edward Hines Jr., VA Hospital
 
Software and Documentation Retrieval Instructions:
---------------------------------------------------- 
Software being released as a host file and/or documentation describing the
new functionality introduced by this patch are available.
 
The preferred method is to retrieve files from download.vista.domain.ext.
This transmits the files from the first available server. Sites may also
shows in CPRS when ordering a dispense drug and is not changed by this
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:
   
Albany:                 fo-albany.domain.ext
Hines:                  fo-hines.domain.ext    
Salt Lake City:         fo-slc.domain.ext
   
modification.
Documentation can also be found on the VA Software Documentation Library 
at: http://www4.domain.ext/vdl/
 
Pre/Post Installation Overview
------------------------------
There are no Pre-installation routines associated with this patch.
 
 
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.
 
 
Installation Instructions
-----------------------------
1.      Choose the PackMan message containing this patch.
 
Note: Follow-on work to allow persistence of the lab test information in 
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
        OR*3.0*420.
 
        a.  Verify Checksums in Transport Global - This option will 
            allow you to ensure the integrity of the routines that are in
            the transport global.
the Medication Order dialog is expected to be addressed in CPRS v32.
        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 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.
 
display the most recent associated lab results when a clinician is
 
4.      From the Installation Menu, select the Install Package(s) option 
        and choose the patch to install.
 
5.      When prompted 'Want KIDS to INHIBIT LOGONs during the install? 
        NO// Press <Enter>
 
6.      When prompted 'Want to DISABLE Scheduled Options, Menu Options, 
        and Protocols? NO// Press <Enter>
 
7.      If prompted "Delay Install (Minutes):  (0 - 60): 0// enter 0.
In order to monitor lab results, lab tests are associated with an 
 
 
Post-Installation Instructions
------------------------------
A site Pharmacy CAC/ADPAC will have to set the OR CPRS LAB DISPLAY 
ENABLEd parameter to a value of "Yes" using he XPAR MENU TOOLS option 
in order for this functionality to be accessed.
Orderable Item using the PSS DRUG ENTER/EDIT option in VistA by entering 
a lab test in the LAB TEST MONITOR (#17.2) field of the DRUG (#50) file. 
 
The NSR for this intake addresses the following requirement: 
 
* VHBAO:NEED126: Ability to display laboratory test results, in a single 
                 view, for ordering inpatient and outpatient medications
                 while viewing the Medication Order dialog in CPRS.
ordering medication using the Computerized Patient Record System (CPRS)
 
This modification has been implemented locally at the VA centers in 
Clarksburg, WV; Hines, IL; Iron Mountain, MI; and Chicago, IL.
 
This build contains the components for the CPRS Graphical User Interface 
(GUI) to display relevant laboratory results in the Medication Ordering 
dialog.
 
To use the features, the following setup steps are advised:
 * Establish drug-to-lab mapping relationship using the PSS DRUG 
Inpatient or Outpatient Medication Order dialogs. Without this
   ENTER/EDIT option.  Follow the OUTPATIENT marking pathway to set up a
   LAB MONITOR drug.  Lab name, specimen type and number of days to look
   back are required fields for the program to work.
 
 * If not already set correctly, review the site local terms for SERUM 
   CREATININE and SERUM SPECIMEN in the CPRS Order Check menus.  This is 
   required for calculation of Creatinine Clearance.
 
 * When the lab requested is "Creatinine", a second line for CrCl will be 
   returned.
modification, the clinician must look in numerous locations for this
 
The routine ORWDPLM2 is included.  This is a version of the display that
will work as a TIU OBJECT.  The object method is:
 
S X=$$SL^ORWDLPM2(DFN,
$S($G(X0)]"":$P(X0,U),$G(NODE0)]"":$P(NODE0,U),1:""),"^TMP($J,""ORWDPLM2""
)")
 
The display is wrapped for ease of reading, but the object method must be 
entered as part of one single line.
information. The information is important for safe and effective
 
Patch Components
================
 
Files & Fields Associated:
 
File Name (Number)       Field Name (Number)       New/Modified/Deleted
-----------------------  ------------------------  --------------------
N/A
 
medication management. 
Forms Associated:
 
Form Name                File #       New/Modified/Deleted
---------                ------       --------------------
N/A
 
 
Mail Groups Associated:
 
Mail Group Name          New/Modified/Deleted
 
---------------          --------------------
N/A
 
 
Options Associated:
 
Option Name            Type               New/Modified/Deleted
-----------            ----               --------------------
N/A
 
The lab results for the most recent lab test associated with an Orderable 
 
Protocols Associated:
 
Protocol Name       New/Modified/Deleted
-------------       --------------------
N/A
 
Security Keys Associated:
 
Security Key Name
    • 440 SEQ #376
      DATE APPLIED:   2017-06-29 15:14:32
      APPLIED BY:   USER,FIFTYFOUR
    • 457
      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
    • 436 SEQ #378
      DATE APPLIED:   2017-07-26 13:06:06
      APPLIED BY:   USER,FIFTYFOUR
    • 52 SEQ #37
      DATE APPLIED:   1999-04-27 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      This patch contains corrections to the OE/RR patient selection screen.
See the National Patch Module for a complete description of the changes.
    • 461 SEQ #379
      DATE APPLIED:   2017-07-26 13:57:22
      APPLIED BY:   USER,FIFTYFOUR
    • 458 SEQ #380
      DATE APPLIED:   2017-09-07 18:09:12
      APPLIED BY:   USER,FIFTYFOUR
      DESCRIPTION:   
      NOTIFICATIONS SHOWING 'MANDATORY' WHEN THEY ARE NOT
    • 454 SEQ #381
      DATE APPLIED:   2017-11-01 12:41:49
      APPLIED BY:   USER,FIFTYFOUR
      DESCRIPTION:   
      Please see forum for a complete patch description.
    • 401 SEQ #382
      DATE APPLIED:   2017-11-02 11:26:24
      APPLIED BY:   USER,FIFTYFOUR
      DESCRIPTION:   
      Option ORK EDITABLE BY USER, ORQQPL4 RPC fix
    • 448 SEQ #383
      DATE APPLIED:   2017-11-02 12:22:22
      APPLIED BY:   USER,FIFTYFOUR
    • 434
      DATE APPLIED:   2017-11-27 13:55:26
      APPLIED BY:   USER,FIFTYFOUR
    • 429
      DATE APPLIED:   2017-12-27 13:40:12
      APPLIED BY:   USER,FIFTYFOUR
      DESCRIPTION:   
      The description of this patch can be found in the National Patch Module.
    • 456 SEQ #386
      DATE APPLIED:   2017-12-27 16:26:59
      APPLIED BY:   USER,FIFTYFOUR
      DESCRIPTION:   
      FLAGGED ORDER SURROGATE NOTIFICATION ISSUE
    • 467 SEQ #387
      DATE APPLIED:   2018-01-03 13:39:45
      APPLIED BY:   USER,FIFTYFOUR
    • 449 SEQ #388
      DATE APPLIED:   2018-01-03 13:40:50
      APPLIED BY:   USER,FIFTYFOUR
      DESCRIPTION:   
      See patch description for details.
    • 49 SEQ #38
      DATE APPLIED:   1999-05-10 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      See National Patch Module for full details of enhancements.
    • 459 SEQ #389
      DATE APPLIED:   2018-01-29 16:58:08
      APPLIED BY:   USER,FIFTYFOUR
      DESCRIPTION:   
      Patch OR*3.0*459 addresses the following issue:
 
1. Anti-Coagulation Show Rate not displaying correct information
    • 465 SEQ #390
      DATE APPLIED:   2018-02-28 16:48:21
      APPLIED BY:   USER,FIFTYFOUR
      DESCRIPTION:   
      This patch corrects 3 issues within the ORDER ENTRY/RESULTS REPORTING 
 
3. Users can't remove themselves from patient lists of type "Patient 
   Manual" 
package:
 
1. The hard error <UNDEFINED>EN+3^LEXAFIL occasionally and sporadically
   occurs when the user uses a function in CPRS that calls the Remote
   Procedure Call (RPC) ORWPCE4 LEX.
 
2. The automated monthly controlled substance report to providers is 
   sending the internal id for Prescription instead of the external id.
    • 428 SEQ #391
      DATE APPLIED:   2018-03-01 15:12:18
      APPLIED BY:   USER,FIFTYFOUR
      DESCRIPTION:   
      Patch OR*3.0*428 addresses the following two issues:
 
1. Undefined error at IN+27^ORDV06B when running the All Medications 
Report in CPRS for Inpatient orders.     
 
2.  Undefined error at IN+41^ORDV06B when running the All Medications 
report in CPRS for Oupatient or Non-VA orders.
    • 450 SEQ #393
      DATE APPLIED:   2018-03-01 15:27:04
      APPLIED BY:   USER,FIFTYFOUR
      DESCRIPTION:   
      Patch OR*3.0*450 will address the following two issues:
Note: issue 2 is documentation only
 
1. Flagged Orderable Item Alert not processing all inpatient items in an 
   order
2. CPRS GUI Technical Manual update Lab test order "other" clarification
    • 382
      DATE APPLIED:   2018-03-02 14:08:20
      APPLIED BY:   USER,FIFTYFOUR
    • 469
      DATE APPLIED:   2018-03-02 14:10:35
      APPLIED BY:   USER,FIFTYFOUR
      DESCRIPTION:   
      MOCHA 2.1 follow-up
    • 474 SEQ #396
      DATE APPLIED:   2018-04-03 16:52:36
      APPLIED BY:   USER,FIFTYFOUR
      DESCRIPTION:   
      The purpose of this build is to resolve the problem with Anticoagulation 
Management Tool (AMT) and how it deals with edits and complications.
 
R18005975FY18 - Problem with Complications
    • 471 SEQ #397
      DATE APPLIED:   2018-04-03 16:55:00
      APPLIED BY:   USER,FIFTYFOUR
      DESCRIPTION:   
      ORDER DETAILS, DRUG RESTRICTION, & RENEWED ORDER ISSUES
    • 443 SEQ #398
      DATE APPLIED:   2018-04-25 17:28:33
      APPLIED BY:   USER,FIFTYFOUR
      DESCRIPTION:   
      This patch corrects a single issue - an error the CPRS Debug report that 
only occurs if there is unexpected data in the XTMP debug log.
    • 462 SEQ #399
      DATE APPLIED:   2018-05-01 14:37:38
      APPLIED BY:   USER,FIFTYFOUR
      DESCRIPTION:   
       
Patch OR*3.0*462 addresses these 2 issues:
 
I10009975FY16 - If a user edits an existing diet Quick Order using option 
[ORCM QUICK ORDERS], the system allows a REGULAR/NPO diet to be ordered 
with another diet.
 
I10480945FY16 - Medication orders flagged by a pharmacist that are then 
updated by the pharmacists cannot then be un-flagged in CPRS or PSJ OE.
    • 46 SEQ #39
      DATE APPLIED:   1999-06-02 00:00:00
      APPLIED BY:   USER,ONE
    • 451 SEQ #400
      DATE APPLIED:   2018-05-01 14:40:23
      APPLIED BY:   USER,FIFTYFOUR
      DESCRIPTION:   
      This patch corrects 2 issues within the ORDER ENTRY/RESULTS REPORTING 
package:
 
1. The show rate calculation skips over visits with an INR that repeats
the previous visit's INR.
 
2. When a patient comes in early - 48 hours before the next draw date -
then it is counted as a missed appointment.
    • 452 SEQ #401
      DATE APPLIED:   2018-06-01 15:06:58
      APPLIED BY:   USER,FIFTYFOUR
    • 480 SEQ #402
      DATE APPLIED:   2018-06-01 16:16:16
      APPLIED BY:   USER,FIFTYFOUR
      DESCRIPTION:   
      This patch will resolve the following issue: 
1. Prevent truncation of drug data returned from Pharmacy when finishing 
an order.
    • 414 SEQ #403
      DATE APPLIED:   2018-06-01 16:27:05
      APPLIED BY:   USER,FIFTYFOUR
      DESCRIPTION:   
      This patch corrects 3 issues within the ORDER ENTRY/RESULTS REPORTING 
 
3. When a weight or height entry in to the patient's vitals is marked as
   Pass, Unavailable or Refused the CrCL value for the patient disappears
   even though there is a previous valid entry.
package:
 
1. Orderable Items with a value in the Type field of Neither appear as an
   available lab test when ordering in CPRS.
 
2. When the last creatinine lab has a "canc" result then the CrCL
   calculation will skip all results with the same specimen and go on to
   look at lab results for other specimens.
    • 463 SEQ #404
      DATE APPLIED:   2018-06-01 16:27:44
      APPLIED BY:   USER,FIFTYFOUR
    • 475 SEQ #405
      DATE APPLIED:   2018-06-01 16:29:02
      APPLIED BY:   USER,FIFTYFOUR
      DESCRIPTION:   
      Bug fixes to RTC Orders
    • 482 SEQ #406
      DATE APPLIED:   2018-07-06 12:09:01
      APPLIED BY:   USER,FIFTYFOUR
      DESCRIPTION:   
      Lab labels print when not requested
    • 481
      DATE APPLIED:   2018-07-06 15:43:55
      APPLIED BY:   USER,FIFTYFOUR
      DESCRIPTION:   
      MOCHA 2.1B Warranty Issues
    • 477 SEQ #408
      DATE APPLIED:   2018-10-04 14:50:21
      APPLIED BY:   USER,FIFTYFOUR
      DESCRIPTION:   
      This patch addresses two (2) issues:
--------------------------------------------
1. I7370452FY16 - PHARMACY ORDERABLE ITEMS / ORDERABLE ITEMS
   I10581756FY16 (d) 
 
   Problem: 
   --------
   The PHARMACY ORDERABLE ITEMS file (#50.7) NAME field (#.01) is  
   not always synced with the ORDERABLE ITEMS file (#101.43) NAME
   field (#.01).
 
 
   The NAME field (#.01) in the ORDERABLE ITEMS file (#101.43) is  
   a combination of the NAME field (#.01), max length 40, in the 
   PHARMACY ORDERABLE ITEMS file (#50.7) and the NAME field (#.01), 
   max length 30, in the DOSAGE FORM file (#50.606).  There is a  
   space between the two fields and a space at the end of the field.
   This could produce a NAME that is 72 characters in length.  
 
   The problem is that the maximum length for the NAME field (#.01)
   in the ORDERABLE ITEMS file (#101.43) is 63 characters.  This  
   can result in truncation, as well as failed update "pushes" when  
1.  The PHARMACY ORDERABLE ITEM file (#50.7) NAME field (#.01) is 
   the combination of the Pharmacy Orderable Items Name and Dosage
   Form Name is greater than 63 characters.
 
   The maximum field length for the NAME field (#.01) in the 
   ORDERABLE ITEMS file (#101.43) needs to be increased to 72 
   characters.
 
   Resolution:
   -----------
   A Data Dictionary update has been made to the NAME Field (#.01) in 
    not always synced with ORDERABLE ITEM file (#101.43) NAME field
   the ORDERABLE ITEM file (#101.43) to increase the maximum field 
   length limit to 72 characters.
 
2. I17614498FY18 - ROOM-BED PRINT DEVICE PARAMETER ISSUES
   
   Problem:
   --------
 
   If a default label printer is defined for a Room-Bed using any of the
   parameters "ORPF CHART COPY PRINT DEVICE ", "ORPF LABEL PRINT DEVICE",
    (#.01).
   "ORPF REQUISITION PRINT DEVICE" and "ORPF WORK COPY PRINT DEVICE", the
   parameter setting is ignored during the CPRS ordering process.
 
   Resolution:
   -----------
 
   Modify routine ORWD2 to determine whether a "device" parameter
   definition exists for the patient's Room-Bed. The "device" parameter 
   descriptions were updated to clarify that the location(s) for each 
   Room-Bed must have the corresponding "prompt" parameter defined in
2.  Room-Bed default printer parameters are ignored during the ordering 
   order for the Room-Bed device to display.  The CPRS Technical Manual
   was also updated to include that clarification.
    process.
 
Defect Tracking System Ticket(s) & Overview:
    • 487 SEQ #409
      DATE APPLIED:   2018-10-04 14:51:47
      APPLIED BY:   USER,FIFTYFOUR
      DESCRIPTION:   
      Issues:
 
2. When invoking option PSSJI SOLN:
 
   a) An error occurs if a solution is defined to have 'UNIT DOSE 
      MEDICATIONS" usage defined as "quick order only".
 
   b) Quick order restrictions are removed if "IV MEDICATIONS" and/or 
      "IV SOLUTIONS" usages are defined as "quick order only".
 
Resolution:
 
----------
 
Modified routines PSSVIDRG and ORMFN to preserve quick order settings on 
additives and solutions.  These changes also prevented the error which 
occurred when a solution or additive was defined to have unit doses as 
"quick order only".
 
Routine PSSVIDRG is included in patch PSS*1.0*229 which will be installed 
along with routine ORMFN in this patch.
1. When invoking option PSSJI DRUG:
 
   a) An error occurs if an additive is defined to have "UNIT DOSE 
      MEDICATIONS" usage defined as "quick order only".
 
   b) Quick order restrictions are removed if "IV MEDICATIONS" and/or 
      "IV ADDITIVES" usages are defined as "quick order only.
    • 13
      DATE APPLIED:   1999-04-16 00:00:00
      APPLIED BY:   USER,ONE
    • 45 SEQ #40
      DATE APPLIED:   1999-06-02 00:00:00
      APPLIED BY:   USER,ONE
    • 492 SEQ #410
      DATE APPLIED:   2018-11-02 15:26:49
      APPLIED BY:   USER,FIFTYFOUR
      DESCRIPTION:   
      LAB LABELS INCORRECTLY PRINTED
    • 483
      DATE APPLIED:   2018-11-02 15:38:21
      APPLIED BY:   USER,FIFTYFOUR
    • 441 SEQ #413
      DATE APPLIED:   2018-12-03 18:14:18
      APPLIED BY:   USER,FIFTYFOUR
      DESCRIPTION:   
      Please see forum for a complete description of patch OR*3.0*441
    • 484 SEQ #414
      DATE APPLIED:   2018-12-06 16:18:42
      APPLIED BY:   USER,FIFTYFOUR
    • 435 SEQ #415
      DATE APPLIED:   2018-12-06 16:19:19
      APPLIED BY:   USER,FIFTYFOUR
      DESCRIPTION:   
      Please see forum for a complete description of patch OR*3.0*435
    • 490 SEQ #416
      DATE APPLIED:   2019-01-02 17:41:14
      APPLIED BY:   USER,FIFTYFOUR
      DESCRIPTION:   
      The One Consult Admin Key Consult project is being designed to improve 
 
Remote Procedures Associated:
                                                          New/Modified/
Remote Procedure Name                                       Deleted   
---------------------                                     -------------
N/A
 
Security Keys Associated:
                                                          New/Modified/
Security Key Name                                           Deleted   
-----------------                                         -------------
Patch Components
GMRC ADMIN RBP TO CC                                      New
 
Templates, Input Associated:
                                                          New/Modified/
Template Name      Type      File Name (Number)             Deleted   
-------------      ----      ------------------           -------------
N/A
 
Templates, List Associated:
                                                          New/Modified/
================ 
Template Name      Type                                     Deleted   
-------------      ----                                   -------------
N/A
 
Templates, Print Associated:
                                                          New/Modified/
Template Name      Type      File Name (Number)             Deleted   
-------------      ----      ------------------           -------------
N/A
 
 
Templates, Sort Associated:
                                                          New/Modified/
Template Name      Type      File Name (Number)             Deleted   
-------------      ----      ------------------           -------------
N/A
 
Additional Information
---------------------------- 
N/A
 
Files & Fields Associated:
New Service Requests (NSRs)
---------------------------- 
N/A
 
Patient Safety Issues (PSIs)
-----------------------------
N/A
 
Defect Tracking System Ticket(s) & Overview
-------------------------------------------
 
N/A
 
Test Sites:
----------
TBD
        
Documentation Retrieval Instructions
------------------------------------
Updated documentation describing the new functionality introduced by this 
patch is available.
File Name (#)                                             New/Modified/
 
The preferred method is to retrieve files from download.vista.domain.ext. 
This transmits the files from the first available server. Sites may also 
select to retrieve files directly from a specific server.
 
Sites may retrieve the documentation directly using Secure File Transfer 
Protocol (SFTP) from the ANONYMOUS.SOFTWARE directory at the following OI 
Field Offices:
 
   Hines:                        fo-hines.domain.ext   
  Sub-file Name (#)         Field Name(Number)              Deleted
   Salt Lake City:               fo-slc.domain.ext
 
Documentation can also be found on the VA Software Documentation Library 
at: 
 
http://www.domain.ext/vdl/
 
Title                         File Name                       FTP Mode
-----------------------------------------------------------------------
N/A      
-------------------         ------------------            -------------
 
Patch Installation:
 
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. 
 
100                         100.008,80                     New
Pre-Installation Instructions
-----------------------------
N/A
 
Installation Instructions
-----------------------------
 
1.  Choose the PackMan message containing this patch.
 
2.  Choose the INSTALL/CHECK MESSAGE PackMan option. 
the current business process used by VistA providers when an imaging order
 
 
3.  From the Kernel Installation and Distribution System Menu, select
    the Installation Menu.  From this menu, you may elect to use the
    following option. When prompted for the INSTALL enter patch 
    OR*3.0*490:
 
    a.  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.
    b.  Compare Transport Global to Current System - This option will
Bulletins Associated:
        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.).
    c.  Verify Checksums in Transport Global - This option will allow
        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.
 
                                                          New/Modified/
5.  When prompted 'Want KIDS to Rebuild Menu Trees Upon Completion of
    Install? NO//NO  
   
6.  When prompted 'Want KIDS to INHIBIT LOGONs during the install?
    NO// 
                                                                
7.  When prompted 'Want to DISABLE Scheduled Options, Menu Options,
    and Protocols? NO//
  
8.  If prompted "Delay Install (Minutes):  (0 - 60): 0// respond 0.
Bulletin Name                                               Deleted    
 
Post-Installation Instructions
------------------------------
For all users who will need to be able to perform the task detailed 
above, these users will need the "GMRC ADMIN RBP TO CC" security key.
 
Backout and Rollback Procedure:
-------------------------------
This patch contains three RA routines.  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 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 "XtractPackMan" 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. 
  
N/A
Validation of Roll Back Procedure:
----------------------------------
The Roll Back Procedure can be verified by printing the first 2 lines of 
the three RA routines contained in this patch using the option First Line 
Routine Print  [XU FIRST LINE PRINT]. Once the routines contained in the 
OR*3.0*490 patch have been rolled back, the first two lines of the 
Routines will no longer contain the designation of patch OR*3.0*490 in 
the patch list section on line 2.
 
Back-out/Rollback Strategy:
 
---------------------------
In the event of a catastrophic failure, the Facility CIO may make the 
decision to back-out the patch.
    
It is imperative that you have performed a backup of the routines 
included in this patch prior to installation.
   
The back-out plan is to restore the routines from the backup created.
   
No data was modified by this patch installation and, therefore, no 
Dialogs Associated:
rollback strategy is required.
   
To verify the back-out completed successfully, ensure the checksum 
matches the pre-patch checksum from the patch descriptions.
                                                          New/Modified/
Dialog Name                                                 Deleted   
is referred to a Community Care provider. Currently, a user creates a new
-----------                                               -------------
N/A
 
Forms Associated:
                                                          New/Modified/
Form Name                    File Name (Number)             Deleted   
---------                    ------------------           -------------
N/A
 
Functions Associated:
consult, then signs the order on the orders tab.
                                                          New/Modified/
Function Name                                               Deleted   
-------------                                             -------------
N/A
 
HL Logical Link:
                                                          New/Modified/
HL Logical Name                                             Deleted   
---------------                                           -------------
N/A
 
 
HL7 Application Parameters:
                                                          New/Modified/
HL7 Parameter Name                                          Deleted   
------------------                                        -------------
N/A
 
HLO Application Registry:
                                                          New/Modified/
HLO Registry Name                                           Deleted   
The goal of this project is to automatically sign the consult if the 
-----------------                                         -------------
N/A
 
Help Frames Associated:
                                                          New/Modified/
Help Frame Name                                             Deleted   
---------------                                           -------------
N/A
 
Mail Groups Associated:
consult service name contains -DS or -ADMIN, and the user has the key
                                                          New/Modified/
Mail Group Name                                             Deleted   
---------------                                           -------------
N/A
 
Options Associated:
                                                          New/Modified/
Option Name                  Type                           Deleted   
-----------                  ----                         -------------
N/A                                                       
"GMRC ADMIN RBP TO CC", and then send the consult to community care.
 
Parameter Definitions:
                                                                                
Parameter Name                                            New/Modified/
                                                          Deleted   
--------------                                            -------------
N/A
 
Parameter Template:
                                                          New/Modified/
 
Template Name                                               Deleted   
-------------                                             -------------
N/A
 
Protocols Associated:
                                                          New/Modified/
Protocol Name                                               Deleted   
-------------                                             -------------
N/A
    • 494 SEQ #417
      DATE APPLIED:   2019-01-02 17:44:59
      APPLIED BY:   USER,FIFTYFOUR
      DESCRIPTION:   
      INC2101638: Missing Text on "Return to Clinic" Orders
a total of 1 appointment(s)."
 
Resolution: 
----------
 
Modify routine ORWDXM1 to force the user to edit the order which will 
include entering a new date. (The same date may be entered for the copied 
order if that complies with procedures to have two "Return to Clinic" 
orders for the same clinic and same date.)
 
 
INC2105632: RTC orders canceled when INTERVAL is zero (0)
 
Problem:
--------
 
When a using the VISTA CPRS CLINICIAN MENU option OR OE/RR MENU CLINICIAN 
to place a RTC order and the Number of Appointments is greater than one 
(1), the Interval should not be allowed to be zero (0).
 
Resolution:
Problem:
-----------
 
The patch modifies the INTERVAL item (OR GTX SCH INTERVAL) for the ORDER 
DIALOG SD RTC in the ORDER DIALOG file (#101.41).  The modification makes 
the INTERVAL a required field when the value of the Number of 
Appointments field is greater than one (1).
-------
 
When a "Return to Clinic" order is copied, the text "on or around" is 
missing before the date.  Example: The order should state "Return to 
Clinic ABC on or around (Sep 24, 2018) for a total of 1 appointment(s)."  
Instead, a copied order will state "Return to Clinic ABC Sep 24, 2018 for
    • 493 SEQ #418
      DATE APPLIED:   2019-02-01 14:48:40
      APPLIED BY:   USER,FIFTYFOUR
    • 479 SEQ #419
      DATE APPLIED:   2019-02-01 16:07:13
      APPLIED BY:   USER,FIFTYFOUR
      DESCRIPTION:   
      VSR RPC BACKDOOR UPDATES
    • 489 SEQ #420
      DATE APPLIED:   2019-03-01 15:42:48
      APPLIED BY:   USER,FIFTYFOUR
    • 53 SEQ #41
      DATE APPLIED:   1999-06-02 00:00:00
      APPLIED BY:   USER,ONE
    • 472 SEQ #421
      DATE APPLIED:   2019-03-05 14:42:01
      APPLIED BY:   USER,FIFTYFOUR
      DESCRIPTION:   
      The Mental Health Suicide Prevention - Suicide High Risk Patient 
 
This patch implements the functionality that allows CPRS to display the 
DBRS data stored in VistA Registration database.
Enhancements (SHRPE) effort incorporates enhancements that will modify the
VistA Registration application and CPRS.
 
The Disruptive Behavior Reporting System (DBRS) record numbers can now be 
recorded in the Registration (DG) files that are related to Patient Record
Flags (PRF) which now provides a convenient reference between VistA and 
the DBRS. The "Patient Record Flags" screen in CPRS is updated to display
DBRS numbers entered for the patient.
    • 503 SEQ #422
      DATE APPLIED:   2019-05-01 15:52:35
      APPLIED BY:   USER,FIFTYFOUR
      DESCRIPTION:   
      This patch addresses two issues:
 
1. The C index in the OE/RR NOTIFICATIONS file (#100.9) contains entries
   for the .01 NAME field.
 
2. A Lab VBECS component might have a modifier filed when there should be 
   no modifier.
    • 444 SEQ #423
      DATE APPLIED:   2019-05-01 15:57:32
      APPLIED BY:   USER,FIFTYFOUR
      DESCRIPTION:   
      This patch is for NSR20130714 Unified Action Profile
    • 509 SEQ #424
      DATE APPLIED:   2019-06-04 17:55:45
      APPLIED BY:   USER,FIFTYFOUR
      DESCRIPTION:   
      CPRS GUI corrections for Windows 10
    • 505 SEQ #425
      DATE APPLIED:   2019-06-04 18:00:41
      APPLIED BY:   USER,FIFTYFOUR
    • 495
      DATE APPLIED:   2019-07-22 17:10:56
      APPLIED BY:   USER,SIXTYFIVE
      DESCRIPTION:   
      OR*3.0*495 - Please refer to the patch description in Forum for 
installation instructions.
    • 510 SEQ #428
      DATE APPLIED:   2019-09-04 10:05:15
      APPLIED BY:   USER,SIXTYFIVE
      DESCRIPTION:   
      The patch addresses two (2) issues:
 
1. Lab order checking for order frequency does not occur for future 
   orders.
 
2. Lab order checking for duplicate orders does not occur for future 
orders.
    • 496 SEQ #429
      DATE APPLIED:   2019-09-16 09:42:25
      APPLIED BY:   USER,SIXTYFIVE
      DESCRIPTION:   
      This patch adds the VETERAN VIDEO CALL URL field to the Hospital Location 
file, Appointment multiple.
    • 427
      DATE APPLIED:   2019-09-30 10:36:54
      APPLIED BY:   USER,SIXTYFIVE
      DESCRIPTION:   
      MENTAL HEALTH NCC PROJECT 5.01
    • 500 SEQ #430
      DATE APPLIED:   2019-10-03 15:54:16
      APPLIED BY:   USER,SIXTYFIVE
      DESCRIPTION:   
      View Alerts Optimization.  Please see OR*3.0*500 Patch Description for 
details.
    • 54 SEQ #42
      DATE APPLIED:   1999-06-02 00:00:00
      APPLIED BY:   USER,ONE
    • 397 SEQ #431
      DATE APPLIED:   2019-10-28 12:15:57
      APPLIED BY:   USER,SIXTYFIVE
    • 514 SEQ #432
      DATE APPLIED:   2019-12-19 13:58:37
      APPLIED BY:   USER,SIXTYFIVE
      DESCRIPTION:   
      See the patch description for a full listing of functionality and changes.
    • 516 SEQ #433
      DATE APPLIED:   2020-02-11 09:54:15
      APPLIED BY:   USER,SIXTYFIVE
    • 518 SEQ #434
      DATE APPLIED:   2020-02-28 12:57:28
      APPLIED BY:   USER,SIXTYFIVE
      DESCRIPTION:   
      Please see the patch description for OR*3.0*518.
    • 485
      DATE APPLIED:   2020-04-20 12:40:59
      APPLIED BY:   USER,SEVENTY
      DESCRIPTION:   
      COVID-19 GUI changes supporting patch.
    • 377
      DATE APPLIED:   2020-06-24 12:14:49
      APPLIED BY:   USER,SIXTYFIVE
      DESCRIPTION:   
      This patch is the M side of CPRS GUI v31B. This patch will be distributed 
as part of a multi-package build. Please see the entry in the National 
Patch Module for detailed information about this patch and CPRS GUI v31B.
    • 515 SEQ #438
      DATE APPLIED:   2020-07-07 16:07:05
      APPLIED BY:   USER,SIXTYFIVE
      DESCRIPTION:   
      Refer to the patch description.
    • 531
      DATE APPLIED:   2020-07-13 17:11:31
      APPLIED BY:   USER,SIXTYFIVE
    • 523 SEQ #440
      DATE APPLIED:   2020-08-03 11:21:42
      APPLIED BY:   USER,SIXTYFIVE
    • 525 SEQ #441
      DATE APPLIED:   2020-08-10 12:54:04
      APPLIED BY:   USER,SIXTYFIVE
      DESCRIPTION:   
      See patch description.
    • 55 SEQ #43
      DATE APPLIED:   1999-06-02 00:00:00
      APPLIED BY:   USER,ONE
    • 507
      DATE APPLIED:   2020-08-24 16:09:10
      APPLIED BY:   USER,SIXTYFIVE
    • 533 SEQ #443
      DATE APPLIED:   2020-08-24 16:11:08
      APPLIED BY:   USER,SIXTYFIVE
      DESCRIPTION:   
      Please see the NPM on FORUM for the description.
    • 521 SEQ #446
      DATE APPLIED:   2020-09-23 15:28:21
      APPLIED BY:   USER,SIXTYFIVE
      DESCRIPTION:   
      ORDER DETAILS DISPLAYING INCORRECT DRUG
    • 413
      DATE APPLIED:   2020-09-23 15:43:41
      APPLIED BY:   USER,SIXTYFIVE
    • 530 SEQ #449
      DATE APPLIED:   2020-09-23 16:19:07
      APPLIED BY:   USER,SIXTYFIVE
      DESCRIPTION:   
      In CPRS, in the Current Order view of the Orders tab a clinical medication
order that is placed using a quick order and is subsequently edited by
changing the drug name, is displayed with a status of dc/edit. This status
should not display as the Current Order view should only be displaying
order statuses of active or pending.
    • 527 SEQ #445
      DATE APPLIED:   2020-09-23 16:40:41
      APPLIED BY:   USER,SIXTYFIVE
      DESCRIPTION:   
      This patch is being released in conjunction with VBEC 2.3.2 Rev F. 
Items addressed in VBECS 2.3.2 Rev F are listed in the VistA Blood 
         ii. 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 of the components
             of this patch, such as routines, DDs, templates, etc.
 
    D. Select the Install Package(s) option and choose the patch to
       install. 
  
       i.  If prompted 'Want KIDS to Rebuild Menu Trees Upon Completion
           of Install? NO//', answer No
Establishment Computer Software (VBECS) 2.3.2 Rev F Release Notes.
 
      ii. When prompted 'Want KIDS to INHIBIT LOGONs during the install?
          NO//', answer No
  
      iii. When prompted 'Want to DISABLE Scheduled Options, Menu
           Options, and Protocols? NO//', answer No
 
Post-Installation Instructions:
 N/A
 
 
Back-Out/Roll Back Plan:
------------------------
 This patch consists of three routines. During the VistA Installation 
 Procedure the installer should back up the modified routines by the
 use of the 'Backup a Transport Global' action (step 2B in
 the Installations Instructions).
  
 If rollback/backout is required, the installer can restore the routines
 using the MailMan message that were saved prior to installing the
 patch.
Associated ticket(s):
  
 If assistance is needed to rollback/backout the patch, please log a 
 Service Now ticket.
=====================
 N/A
 
Associated NSR(s):
==================
 N/A
 
 
Patient Safety Issues (PSIs):
============================
 N/A
 
Participating Test Sites:
=========================
 
TBD
 
A full description of patch changes and implementation process are 
Defect Tracking System Ticket(s) & Overview:
============================================
 
n/a
 
Additional Information:
-----------------------
 
Blood Bank Team Coordination:
-----------------------------
included in the VBECS 2.3.2 Rev F Release Notes.
EFFECT ON BLOOD BANK FUNCTIONAL REQUIREMENTS: Patch LR*5.2*535 does not 
contain any changes to the VISTA BLOOD BANK Software as defined by 
ProPath standard titled: BBM Team Review of VistA Patches.
 
EFFECT ON BLOOD BANK FUNCTIONAL REQUIREMENTS: Patch LR*5.2*535 does not 
alter or modify any software design safeguards or safety critical 
elements functions.
 
RISK ANALYSIS: Changes made by patch LR*5.2*535 have no adverse effect on 
Blood Bank software functionality, therefore RISK is none.
 
 
VALIDATION REQUIREMENTS BY OPTION: Because of the nature of the changes 
made, no specific validation requirements exist as a result of 
installation of this patch.
 
Software and Documentation Retrieval Instructions:
 
Documentation describing the new functionality introduced by this patch 
is available on the VA Software Documentation Library at:
http://www.domain.ext/vdl/application.asp?appid=182
The Test and Production accounts will be installed separately. There is 
 
Refer to the VBECS 2.3.2 Rev F Release Notes for a list of the user 
documentation associated with this revision letter patch.
 
Additional VBECS information can be accessed on the VBECS SharePoint site 
at:
https://dvagov.sharepoint.com/sites/oitepmovbecs
 
 
Patch Installation:
no downtime associated with this patch installation. Refer to the VBECS 
-------------------
 
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.
 
No options need to be disabled during installation.
 
2.3.2 Rev F Release Notes for further installation details.
 
Installation Instructions:
 
 1. Choose the PackMan message containing this build. Then select the
    INSTALL/CHECK MESSAGE PackMan option to load the build.
 
 2. From the Kernel Installation and Distribution System Menu, select the
    Installation Menu.  From this menu, 
 
    A. Select the Verify Checksums in Transport Global option to confirm 
 
       the integrity of the routines that are in the transport global.
       When prompted for the INSTALL NAME enter the patch name OR*3.0*527.
 
    B. Select the Backup a Transport Global option to create a backup
       message of any routines exported with this patch. It will not
       backup any other changes such as DDs or templates. 
 
    C. You may also elect to use the following options: 
         i.  Print Transport Global - This option will allow you to view
             the components of the KIDS build.
    • 534 SEQ #450
      DATE APPLIED:   2020-09-28 09:12:46
      APPLIED BY:   USER,SEVENTEEN
      DESCRIPTION:   
      This patch addresses two (2) issues:
1. The "Display the Notifications a User Can Receive" option does not 
   display the ORB PROCESSING FLAG parameter edits based on Team.
2. Results might erroneously flag as "critical" in two CPRS reports on 
   the Labs tab.
    • 512 SEQ #451
      DATE APPLIED:   2020-09-28 13:50:06
      APPLIED BY:   USER,SEVENTEEN
      DESCRIPTION:   
      Clinically indicated date is changing when using T+XXX or +XXX function.
    • 528 SEQ #452
      DATE APPLIED:   2020-10-15 12:33:49
      APPLIED BY:   USER,SEVENTEEN
      DESCRIPTION:   
      See patch description for information regarding modifications.
    • 519
      DATE APPLIED:   2020-11-12 17:52:19
      APPLIED BY:   USER,SEVENTEEN
    • 31 SEQ #44
      DATE APPLIED:   1999-06-22 00:00:00
      APPLIED BY:   USER,ONE
    • 524 SEQ #455
      DATE APPLIED:   2021-03-04 10:17:31
      APPLIED BY:   USER,SEVENTEEN
      DESCRIPTION:   
      The purpose of this patch is to swap the display of Imperial and Metric 
measurements on the CPRS coversheet display of Vitals. See the patch for 
a full description.
    • 540 SEQ #456
      DATE APPLIED:   2021-03-04 15:39:24
      APPLIED BY:   USER,SEVENTEEN
      DESCRIPTION:   
      This patch corrects the following issue:
 
If lengthy drug-drug interaction message is transmitted to a remote email 
address, a buffer error might occur and stall MailMan transmissions.
    • 476
      DATE APPLIED:   2021-03-10 12:06:02
      APPLIED BY:   USER,SEVENTEEN
      DESCRIPTION:   
      Please see OR*3.0*476 Patch Description for more info.
    • 437
      DATE APPLIED:   2021-03-22 12:46:37
      APPLIED BY:   USER,SEVENTEEN
      DESCRIPTION:   
      The patch modifies OR routine "OROTHCL" and RPC "OROTHCL GET" to update
There are no actual code changes made to these components.
the comments and description to indicate that this code and RPC, in
addition to Other Than Honorable (OTH), will display the following
information on the CPRS button at the top of the screen and in the
associated pop-up window:
- Presumptive Psychosis (PP) status based on the settings in the PATIENT
  file (#2) and in the INSURANCE VERIFICATION PROCESSOR file (#355.33) 
- Inactive Patient Record Flags (PRF) assigned to the patient and a
  history of PRF changes.
    • 545b
      DATE APPLIED:   2021-04-20 00:00:00
      DESCRIPTION:   
      Backup of OR*3.0*545 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.
    • 545 SEQ #460
      DATE APPLIED:   2021-04-20 15:03:17
      APPLIED BY:   USER,SEVENTEEN
      DESCRIPTION:   
      This patch addresses the following issue:
 
The order check message might not be accurate when signing a Clinic
Infusion order.
    • 544b
      DATE APPLIED:   2021-04-22 00:00:00
      DESCRIPTION:   
      Backup of OR*3.0*544 on Apr 22, 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.
    • 544 SEQ #461
      DATE APPLIED:   2021-04-22 12:33:10
      APPLIED BY:   USER,SEVENTEEN
      DESCRIPTION:   
      This patch addresses the issue of a hard M error during the patient look 
up using the last 5 digits of the social security number or the last 
letter of the last name and the last 5 digits of the social security 
number.
    • 529b
      DATE APPLIED:   2021-04-27 00:00:00
      DESCRIPTION:   
      Backup of OR*3.0*529 on Apr 27, 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.
    • 529 SEQ #462
      DATE APPLIED:   2021-04-27 09:08:39
      APPLIED BY:   USER,SEVENTEEN
      DESCRIPTION:   
      Please see the patch description for OR*3.0*529 for more information.
    • 56 SEQ #45
      DATE APPLIED:   1999-07-19 00:00:00
      APPLIED BY:   USER,ONE
    • 542b
      DATE APPLIED:   2021-04-29 00:00:00
      DESCRIPTION:   
      Backup of OR*3.0*542 on Apr 29, 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.
    • 542 SEQ #463
      DATE APPLIED:   2021-04-29 14:22:00
      APPLIED BY:   USER,SEVENTEEN
      DESCRIPTION:   
       
The patch modifies the ORPRF routine and adds a new ORPRFHST routine to 
display the history of active patient records flags in a pop-up window 
associated with the Flag button in CPRS.
    • 501b
      DATE APPLIED:   2021-05-04 00:00:00
      DESCRIPTION:   
      Backup of PCE STANDARDIZATION 1.0, PX*1.0*211, PXRM*2.0*42, GMT
 
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.
    • 501
      DATE APPLIED:   2021-05-04 15:57:31
      APPLIED BY:   USER,SEVENTEEN
      DESCRIPTION:   
      To take full advantage of the PCE standardization work, changes to VistA
Standardization 1.0 Installation Guide.

In the documentation for DATA2PCE the description of the variable PPEDIT,
which is one of the input parameters to DATA2PCE is:

PPEDIT
(Optional) If an existing encounter already has a Primary Provider and you
want to edit it set this to 1.

Although it was documented, DATA2PCE did not actually enforce this, the
applications that use PCE data are required. These applications include
primary provider could be edited even when PPEDIT did not equal 1. DATA2PCE
was changed in PX*1.0*211 to work as documented. After that change, internal
testing found that the primary provider could no longer be edited from CPRS.
The cause of this was tracked to the way CPRS was calling DATA2PCE, it was not
properly passing the PPEDIT parameter. The call to DATA2PCE in the routine
ORWPCE1 was corrected. 

Clinical Reminders, Health Summary, Problem List, and Order Entry/Results
Reporting. To make it easier for sites, the builds for PCE (PX*1.0*211),
Clinical Reminders (PXRM*2.0*42), Health Summary (GMTS*2.7*122), Problem List
(GMPL*2.0*53), and Order Entry/Results Reporting (OR*3.0*501) are being
distributed in a multi-package build named PCE STANDARDIZATION 1.0.

For detailed information and installation instructions, please see the PCE
    • 550b
      DATE APPLIED:   2021-05-06 00:00:00
      DESCRIPTION:   
      Backup of OR*3.0*550 on May 06, 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.
    • 550 SEQ #465
      DATE APPLIED:   2021-05-06 10:07:44
      APPLIED BY:   USER,SEVENTEEN
      DESCRIPTION:   
      1.      PDMP AoD Health Summary not always displaying manual PDMP notes 
   on the HS report, even though they were documented in the PDMP progress
   note.
 
   Resolution:
   ----------
   Routine ORPDMPHS is modified to not quit when the patient has no data 
   in the PDMP QUERY LOG (#101.62).  Instead, processing will bypass
   displaying the data in PDMP QUERY LOG when no data exists for the
   patient and allowing the data for manually entered PDMP notes to be
   displayed.
 
   Problem:
   -------
   The PDMP ADHOC Health Summary report is supposed to display PDMP 
   queries that were initiated from within CPRS as well as manual queries
   (if the manual PDMP query was documented in the standard PDMP progress
   note). However, if a patient never had a query initiated within CPRS
   (by using the PDMP query button), their manual queries are not showing
    • 548b
      DATE APPLIED:   2021-06-01 00:00:00
      DESCRIPTION:   
      Backup of OR*3.0*548 on Jun 01, 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.
    • 548 SEQ #466
      DATE APPLIED:   2021-06-01 16:54:14
      APPLIED BY:   USER,SEVENTEEN
      DESCRIPTION:   
      This patch addresses the following issue:
1. INC16882015 - Inactivated orderable items can be selected in the 
option Enter/edit QO restrictions
 
Associated NSR(s):
==================
N/A
 
Participating Test Sites:
=========================
TBD
 
 
 
Defect Tracking System Ticket(s) & Overview:
===========================================
 
1.      Inactivated orderable items can be selected in the option 
Enter/edit QO restrictions 
 
   Problem:
   -------
1. Inactivated orderable items can be selected in the option Enter/edit 
   Inactivated pharmacy or lab orderable items can be selected when using 
   the option Enter/edit QO restrictions. It was also found that the 'SR
   Search/replace orderables' option also displays inactive Orderable 
   Items to replace orderable items.
 
 
   Resolution:
   ----------
   Routine ORCMEDT6 is modified to display that inactive Orderable Items 
   (OI) are inactive. It will also display that inactive OIs are
QO restrictions
   inactive on the 'Search for:' and 'Replace with:' prompts in option
   Search/replace orderables.
   
 
Associated ticket(s):
=====================
    • 557b
      DATE APPLIED:   2021-06-10 00:00:00
      DESCRIPTION:   
      Backup of OR*3.0*557 on Jun 10, 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.
    • 557 SEQ #467
      DATE APPLIED:   2021-06-10 10:02:28
      APPLIED BY:   USER,SEVENTEEN
      DESCRIPTION:   
      See patch description for full details.
    • 57 SEQ #46
      DATE APPLIED:   1999-07-19 00:00:00
      APPLIED BY:   USER,ONE
    • 547
      DATE APPLIED:   2021-06-17 13:02:28
      APPLIED BY:   USER,SEVENTEEN
      DESCRIPTION:   
      See patch description for OR*3.0*547.
    • 546
      DATE APPLIED:   2021-06-17 13:03:08
      APPLIED BY:   USER,SEVENTEEN
    • 539
      DATE APPLIED:   2021-07-01 11:28:00
      APPLIED BY:   USER,SEVENTEEN
    • 556b
      DATE APPLIED:   2021-07-20 00:00:00
      DESCRIPTION:   
      Backup of OR*3.0*556 on Jul 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.
    • 556 SEQ #471
      DATE APPLIED:   2021-07-20 14:19:48
      APPLIED BY:   USER,SEVENTEEN
      DESCRIPTION:   
      This patch addresses the following issue:
 
If an order dialog is defined containing more than one prompt having the 
same "ID", information might not be stored when placing the order and/or 
a software error might occur in CPRS.
    • 553b
      DATE APPLIED:   2021-07-26 00:00:00
      DESCRIPTION:   
      Backup of OR*3.0*553 on Jul 26, 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.
    • 553 SEQ #472
      DATE APPLIED:   2021-07-26 13:06:28
      APPLIED BY:   USER,SEVENTEEN
    • 453b
      DATE APPLIED:   2021-07-29 00:00:00
      DESCRIPTION:   
      Backup of OR*3.0*453 on Jul 29, 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.
    • 453 SEQ #473
      DATE APPLIED:   2021-07-29 14:04:26
      APPLIED BY:   USER,SEVENTEEN
      DESCRIPTION:   
      Provider Role Tool changes. For detailed information, please refer to the 
patch description.
    • 560b
      DATE APPLIED:   2021-08-09 00:00:00
      DESCRIPTION:   
      Backup of OR*3.0*560 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.
    • 58 SEQ #47
      DATE APPLIED:   1999-07-19 00:00:00
      APPLIED BY:   USER,ONE
    • 560 SEQ #475
      DATE APPLIED:   2021-08-09 12:39:37
      APPLIED BY:   USER,SEVENTEEN
      DESCRIPTION:   
      The purpose of this patch is to revert the functionality for showing 
metrics Vitals first on the coversheet. See the patch description for a 
full description.
    • 562 SEQ #477
      DATE APPLIED:   2021-09-07 17:49:57
      APPLIED BY:   USER,SEVENTEEN
      DESCRIPTION:   
      Please see the patch description for information about this build.
    • 513 SEQ #478
      DATE APPLIED:   2021-09-09 10:14:15
      APPLIED BY:   USER,SEVENTEEN
      DESCRIPTION:   
      Care Management Decommission - Removes code from CPRS for Care
management.
    • 563 SEQ #479
      DATE APPLIED:   2021-09-29 14:49:30
      APPLIED BY:   USER,SEVENTEEN
      DESCRIPTION:   
      1. INC18693308 - CPRS NOW DOSE ISSUE IN CLINIC INFUSIONS
medications (BCMA for outpatients, unit dose) as well as IVs for non-BCMA 
units but appears broke in clinic infusions.
 
   Resolution:
   ----------
Routine ORCSEND is modified to allow order dialog 'CLINIC OR PAT FLUID 
OE' to work the same as dialog 'PSJI OR PAT FLUID OE' when determining if 
PSJI^ORCSEND3 should be executed.  After this patch, when an order that 
is for package PSJ and uses DIALOG 'CLINIC OR PAT FLUID OE' processing 
will continue through PSJI^ORCSEND3 and the NOW order will be created 
 
when signing of the order.
   Problem:
   -------
In CPRS, when using the clinic infusions (BCMA for outpatients, IV) 
ordering pathway, when ordering an IV and then clicking the "give 
additional dose now" button, upon signing the order the now dose never 
actually gets ordered. 
This is a glitch in the system. This "now" function works in clinic
    • 568 SEQ #480
      DATE APPLIED:   2021-09-29 14:50:03
      APPLIED BY:   USER,SEVENTEEN
    • 567 SEQ #481
      DATE APPLIED:   2021-10-06 17:33:29
      APPLIED BY:   USER,SEVENTEEN
      DESCRIPTION:   
      This patch addresses the following issue:
 
The prompts of an existing order dialog cannot be edited after the
install of OR*3.0*556.
    • 559
      DATE APPLIED:   2021-11-04 09:38:22
      APPLIED BY:   USER,SEVENTEEN
      DESCRIPTION:   
      Add ORAM as an Additional Prefix in the Package file entry for ORDER 
ENTRY/RESULTS REPORTING.
    • 498
      DATE APPLIED:   2021-12-07 15:11:19
      APPLIED BY:   USER,SEVENTEEN
    • 571 SEQ #485
      DATE APPLIED:   2021-12-14 10:41:21
      APPLIED BY:   USER,SEVENTEEN
      DESCRIPTION:   
      See patch description for full information.
    • 574 SEQ #486
      DATE APPLIED:   2022-01-05 12:11:57
      APPLIED BY:   USER,SEVENTEEN
      DESCRIPTION:   
      This patch addresses the following issue:
 
In the History of Actions Taken section of the Patient Record Flag (PRF) 
display in CPRS, the Site ID should reflect the STATION NUMBER (#99) 
field of the INSTITUTION (#4) file, not the internal entry number.
    • 11 SEQ #48
      DATE APPLIED:   1999-09-14 00:00:00
      APPLIED BY:   USER,ONE
    • 572 SEQ #487
      DATE APPLIED:   2022-01-10 14:55:52
      APPLIED BY:   USER,SEVENTEEN
      DESCRIPTION:   
      Defect Tracking System Ticket(s) & Overview:
CPRS, the medication is not showing in BCMA as being nurse verified.  In 
BCMA, after being nurse verified, the medication is still showing *** in 
the Ver column of the Coversheet, Unit Dose, and IV tabs.
 
Resolution:
-----------
The issue is due to not sending an HL7 message for nurse verification.  
This occurs because the processing quits out when the order action is not 
a change (XX) or new (NW).  When the medication has put on hold and then 
released off hold, the action of the nurse to verify it is a Release Hold 
 
(RL) action and fails to continue to the code that sends the message.  
The correction is to modify routine ORCSEND to move the quit logic to 
after the message is sent for the pharmacy package.
 
Technical Resolution:
---------------------
Routine ORCSEND is modified to move the quit logic and conditionally call 
VER^ORMBLDPS for package PS only when the action is NW, XX, or RL.
 
The quit in line VR+6^ORCSEND is commented out, that quit is then added 
1. INC19397308 - MEDICATION RELEASED FROM HOLD NOT SHOWING NURSE 
after line VR+9^ORCSEND. Line VR+9^ORCSEND is changed from 'I 
$$NMSP^ORCD(ORPKG)="PS" D VER^ORMBLDPS(ORIFN) Q' to 'I 
$$NMSP^ORCD(ORPKG)="PS"&(ORX="NW!(ORX="XX")!(ORX="RL")) D 
VER^ORMBLDPS(ORIFN) Q'
                 VERIFIED IN BCMA
 
 
Problem:
--------
After a medication is released from hold and is verified by a nurse in
    • 564 SEQ #491
      DATE APPLIED:   2022-02-23 11:02:06
      APPLIED BY:   USER,EIGHTYFOUR
      DESCRIPTION:   
      See the patch description for full information.
    • 580 SEQ #492
      DATE APPLIED:   2022-03-03 14:59:30
      APPLIED BY:   USER,SEVENTEEN
      DESCRIPTION:   
      This patch addresses the following issue:
 
 
 
Associated NSR(s):
==================
N/A
 
Participating Test Sites:
=========================
TBD
 
 
 
Defect Tracking System Ticket(s) & Overview:
===========================================
 
1. CPRS - Wrong Message on Cancelled Order.
 
   Problem:
   -------
In CPRS, placed an order and then cancelled it.  Attempt to sign the 
1. CPRS - Wrong Message on Cancelled Order
order and you'll get the message "order has been signed".  The reason 
should say, this order has been cancelled.
 
   Resolution:
   ----------
Modify routine ORCACT01 so display the message "This order has been 
canceled!" when the SIGNATURE STATUS for the ORDER ACTION sub record of 
the order being signed is 5.  
 
   Technical Resolution:
 
   ---------------------
The value of 5 for the SIGNATURE STATUS field is 'NOT REQUIRED due to 
cancel/lapse'.  At line ES+7^ORCACT01 add code:
I X=5 S ERROR="This order has been canceled!" Q ;p580
 
Associated ticket(s):
=====================
 
1. INC20497278 - CPRS - Wrong Message on Cancelled Order
    • 578 SEQ #493
      DATE APPLIED:   2022-04-11 14:44:11
      APPLIED BY:   USER,EIGHTYSIX
      DESCRIPTION:   
      This patch addresses the following issue:
 
Duplicate order checking might display an incorrect dispense drug against 
pending clinic medications.
    • 585 SEQ #494
      DATE APPLIED:   2022-04-27 10:34:35
      APPLIED BY:   USER,EIGHTYSIX
      DESCRIPTION:   
      This patch addresses the following issue:
 
When viewing Laboratory result alerts in CPRS and VistA as well as on
some CPRS Laboratory reports, abnormal flags display next to test results
with no spacing between the results and flags. (Example: POSITIVEH)
    • 455
      DATE APPLIED:   2022-07-06 15:59:28
      APPLIED BY:   USER,EIGHTYSIX
    • 538 SEQ #496
      DATE APPLIED:   2022-08-17 17:04:58
      APPLIED BY:   USER,EIGHTYSIX
    • 558
      DATE APPLIED:   2022-08-25 12:25:42
      APPLIED BY:   USER,EIGHTYSIX
      DESCRIPTION:   
      The purpose of this patch is to export the report for patient 
demographics, along with the supporting code, to add self identified 
gender. See the patch description for a full descriptions.
    • 569
      DATE APPLIED:   2022-09-20 22:14:58
      APPLIED BY:   USER,NINETY
    • 405
      DATE APPLIED:   2022-10-05 14:55:08
      APPLIED BY:   USER,EIGHTYNINE
      DESCRIPTION:   
      This patch is part of a combined build, made up of the following nine 
        PXRM*2.0*65    Reminder changes for VIMM
        TIU*1.0*289    CPRS V32 MODIFICATIONS
        PSJ*5.0*399    CPRS32 - INDICATIONS
        YS*5.01*211    CPRS V32B MENTAL HEALTH DLL
patches:
       
        GMRA*4.0*51    SUPPORT FOR CPRS V32
        GMTS*2.7*115   SUPPORT FOR CPRS V32
        OR*3.0*405     CPRS V32
        PSB*3.0*93     CPRS V32 BCMA CHANGES
        PSO*7.0*441    PARK-A-PRESCRIPTION MODIFICATIONS
        PX*1.0*217     Immunization Calculation Engine (ICE) interface
    • 42 SEQ #49
      DATE APPLIED:   1999-09-14 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      See description on patch message.
    • 591 SEQ #500
      DATE APPLIED:   2022-10-25 14:01:16
      APPLIED BY:   USER,NINETY
      DESCRIPTION:   
      The Health Data Repository (HDR) system will now require the 'client 
name' field to be populated for all requests. The purpose of this patch 
is to add this information to the requests sent from the Order 
Entry/Results Reporting package to HDR. These requests are necessary for 
performing functions such as remote order checking on outpatient 
prescriptions and allergies.
    • 594 SEQ #501
      DATE APPLIED:   2022-12-27 09:58:02
      APPLIED BY:   USER,NINETY
      DESCRIPTION:   
      This patch will correct a <SUBSCRIPT>RESETID+7^ORCDPS error that can
occur while editing quick orders while using the Update Meds Quick
Orders for indication prompt [ORCM UPD INDICATION QO] option.
    • 599 SEQ #502
      DATE APPLIED:   2023-01-09 17:30:37
      APPLIED BY:   USER,EIGHTYNINE
      DESCRIPTION:   
      This patch will temporarily remove the requirement for indication. This 
should only impact copy to new order actions.
    • 597
      DATE APPLIED:   2023-02-28 13:07:42
      APPLIED BY:   USER,EIGHTYNINE
    • 598
      DATE APPLIED:   2023-03-23 12:10:06
      APPLIED BY:   USER,EIGHTYNINE
      DESCRIPTION:   
      Emergency GUI release. Please see the patch description for the full 
information.
    • 596 SEQ #505
      DATE APPLIED:   2023-03-23 12:21:36
      APPLIED BY:   USER,EIGHTYNINE
      DESCRIPTION:   
      Please see FORUM for a complete description of OR*3.0*596.
    • 577 SEQ #506
      DATE APPLIED:   2023-04-14 11:23:00
      APPLIED BY:   USER,NINETY
      DESCRIPTION:   
      This patch addresses four defects, please look to the patch description
for specific technical details.
    • 602 SEQ #507
      DATE APPLIED:   2023-05-23 09:38:55
      APPLIED BY:   USER,EIGHTYNINE
      DESCRIPTION:   
      The purpose of this build is to revert ORMPS2. See the patch description 
for additional information.
    • 593
      DATE APPLIED:   2023-06-01 09:26:36
      APPLIED BY:   USER,EIGHTYNINE
      DESCRIPTION:   
      Please refer to the patch description for detailed information about the 
contents.
    • 499
      DATE APPLIED:   2023-06-29 17:04:02
      APPLIED BY:   USER,EIGHTYNINE
      DESCRIPTION:   
      See FORUM for patch description.
    • 18
      DATE APPLIED:   1999-04-16 00:00:00
      APPLIED BY:   USER,ONE
    • 48 SEQ #50
      DATE APPLIED:   1999-09-14 00:00:00
      APPLIED BY:   USER,ONE
    • 588
      DATE APPLIED:   2023-10-26 09:38:30
      APPLIED BY:   USER,EIGHTYNINE
    • 607 SEQ #511
      DATE APPLIED:   2023-12-06 15:40:54
      APPLIED BY:   USER,EIGHTYNINE
      DESCRIPTION:   
      See FORUM for patch description details.
    • 605 SEQ #512
      DATE APPLIED:   2024-01-16 18:15:20
      APPLIED BY:   USER,EIGHTYNINE
      DESCRIPTION:   
      This patch address the following issue:
 
MOCHA duplicate order check displaying "UNRELEASED" on a released 
prescription (Active, Discontinued, etc.), which is misleading.
 
See the patch description for additional information.
    • 614 SEQ #514
      DATE APPLIED:   2024-02-21 10:13:23
      APPLIED BY:   USER,EIGHTYNINE
    • 600 SEQ #515
      DATE APPLIED:   2024-03-04 10:13:14
      APPLIED BY:   USER,EIGHTYNINE
      DESCRIPTION:   
      The patch addresses two (2) issues
 
1. Reformat complications message, removing embedded line breaks in
message text that caused lower portion to be obscured
 
2. Update AntiCoagulate Splash Screen with features added to CPRS Splash
Screen
    • 603 SEQ #516
      DATE APPLIED:   2024-04-01 15:54:33
      APPLIED BY:   USER,EIGHTYNINE
      DESCRIPTION:   
      Description:
 
Installation Instructions:
 
1.  Choose the PackMan message containing this build. Then select 
    the INSTALL/CHECK MESSAGE PackMan option to load the build.
 
2.  From the Kernel Installation and Distribution System Menu, 
    select the Installation Menu.  From this menu, 
 
    A.  Select the Verify Checksums in Transport Global 
This patch addresses the following issues:
        option to confirm the integrity of the routines that 
        are in the transport global. When prompted for the 
        INSTALL NAME enter the patch name. 
        (OR*3.0*603)
 
        NOTE: Using <spacebar><enter> will not bring up a 
              Multi-Package build even if it was loaded 
              immediately before this step. It will only 
              bring up the last patch in the build.
 
 
    B. Select the Backup a Transport Global option to create
       a backup message. You must use this option and specify 
       what to backup; the entire Build or just Routines.
       The backup message can be used to restore the routines
       and components of the build to the pre-patch condition.
 
         i.  At the Installation option menu, select Backup 
             a Transport Global.
         ii. At the Select INSTALL NAME prompt, enter your 
             build OR*3.0*603.
1. In CPRS, the action of "Change Release Event" can be done on clinic
         iii. When prompted for the following, enter "R" for 
              Routines or "B" for Build.
 
               Select one of the following:
 
                      B         Build
                      R         Routines
 
                Enter response: Build
 
medications.
         iv.  When prompted "Do you wish to secure your build? 
              NO//", press <enter> and take the default response 
              of "NO".
         v.   When prompted with, "Send mail to: Last name, First 
              Name", press <enter> to take default recipient. Add 
              any additional recipients.
         vi.  When prompted with "Select basket to send to: IN//", 
              press <enter> and take the default IN mailbox or select 
              a different mailbox.
 
 
    C. You may also elect to use the following options: 
         i. Print Transport Global - This option will allow 
            you to view the components of the KIDS build.
        ii. 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 of the components of this patch, such as 
            routines, DDs, templates, etc.
 
    D. Select the Install Package(s) option and choose the 
2. In CPRS, Lab Overview (Collected Specimen) results are returned in 
       patch to install. 
         i. If prompted 'Want KIDS to Rebuild Menu Trees Upon 
            Completion of Install? NO//', answer NO.
        ii. When prompted 'Want KIDS to INHIBIT LOGONs during the 
            install? NO//', answer NO.
       iii. When prompted 'Want to DISABLE Scheduled Options, Menu 
            Options, and Protocols? NO//', answer NO.
wrong sort order by collection dates.
    • 62 SEQ #51
      DATE APPLIED:   1999-09-14 00:00:00
      APPLIED BY:   USER,ONE
    • 32
      DATE APPLIED:   1999-10-02 00:00:00
      APPLIED BY:   USER,ONE
    • 60 SEQ #53
      DATE APPLIED:   1999-10-03 00:00:00
      APPLIED BY:   USER,ONE
    • 61 SEQ #54
      DATE APPLIED:   1999-10-03 00:00:00
      APPLIED BY:   USER,ONE
    • 67 SEQ #55
      DATE APPLIED:   1999-10-03 00:00:00
      APPLIED BY:   USER,ONE
    • 66 SEQ #56
      DATE APPLIED:   1999-10-19 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      See description on patch message.
    • 70 SEQ #57
      DATE APPLIED:   1999-10-19 00:00:00
      APPLIED BY:   USER,ONE
    • 51 SEQ #58
      DATE APPLIED:   1999-12-10 00:00:00
      APPLIED BY:   USER,ONE
    • 59 SEQ #59
      DATE APPLIED:   1999-12-10 00:00:00
      APPLIED BY:   USER,ONE
    • 19
      DATE APPLIED:   1999-04-16 00:00:00
      APPLIED BY:   USER,ONE
    • 71 SEQ #60
      DATE APPLIED:   1999-12-10 00:00:00
      APPLIED BY:   USER,ONE
    • 64 SEQ #61
      DATE APPLIED:   1999-12-10 00:00:00
      APPLIED BY:   USER,ONE
    • 76 SEQ #62
      DATE APPLIED:   2000-02-04 00:00:00
      APPLIED BY:   USER,ONE
    • 72 SEQ #63
      DATE APPLIED:   2000-02-29 00:00:00
      APPLIED BY:   USER,ONE
    • 40 SEQ #64
      DATE APPLIED:   2000-03-06 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      See National Patch Module for description of this patch OR*3*40.
    • 81 SEQ #65
      DATE APPLIED:   2000-04-05 00:00:00
      APPLIED BY:   USER,ONE
    • 44 SEQ #66
      DATE APPLIED:   2000-04-17 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      See national patch module for description of this patch.
    • 75 SEQ #67
      DATE APPLIED:   2000-05-01 00:00:00
      APPLIED BY:   USER,ONE
    • 78 SEQ #68
      DATE APPLIED:   2000-05-16 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      Refer to the patch description on the patch message.
    • 74
      DATE APPLIED:   2000-05-25 00:00:00
      APPLIED BY:   USER,ONE
    • 15
      DATE APPLIED:   1999-04-16 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      This patch corrects a problem of getting a Null Subscript error when
printing orders that have no order text.
    • 68 SEQ #70
      DATE APPLIED:   2000-06-12 00:00:00
      APPLIED BY:   USER,ONE
    • 83 SEQ #71
      DATE APPLIED:   2000-06-12 00:00:00
      APPLIED BY:   USER,ONE
    • 79 SEQ #72
      DATE APPLIED:   2000-06-12 00:00:00
      APPLIED BY:   USER,ONE
    • 69 SEQ #73
      DATE APPLIED:   2000-06-26 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      Refer to the patch description on the patch message.
    • 47 SEQ #74
      DATE APPLIED:   2000-06-26 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      This patch filters inactive providers and inactive wards from team
selection lists during team list maintenance.
    • 63 SEQ #75
      DATE APPLIED:   2000-06-26 00:00:00
      APPLIED BY:   USER,ONE
    • 73 SEQ #76
      DATE APPLIED:   2000-07-11 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
       
 
Corrects dialogs in FH
    • 87 SEQ #77
      DATE APPLIED:   2000-07-24 00:00:00
      APPLIED BY:   USER,ONE
    • 86 SEQ #78
      DATE APPLIED:   2000-07-24 00:00:00
      APPLIED BY:   USER,ONE
    • 90 SEQ #79
      DATE APPLIED:   2000-08-16 00:00:00
      APPLIED BY:   USER,ONE
    • 4
      DATE APPLIED:   1999-04-16 00:00:00
      APPLIED BY:   USER,ONE
    • 65 SEQ #80
      DATE APPLIED:   2000-08-16 00:00:00
      APPLIED BY:   USER,ONE
    • 88 SEQ #81
      DATE APPLIED:   2000-08-24 00:00:00
      APPLIED BY:   USER,ONE
    • 93 SEQ #82
      DATE APPLIED:   2000-10-04 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      This patch removes several unused fields from the OE/RR NOTIFICATIONS file
(#100.9).  See the National Patch Module on FORUM for more details on this
patch.
    • 82 SEQ #83
      DATE APPLIED:   2000-10-27 00:00:00
      APPLIED BY:   USER,ONE
    • 10
      DATE APPLIED:   2000-10-27 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      OR*3.0*10  See National Patch Module for a description of the changes
incorporated in this patch.
    • 89 SEQ #85
      DATE APPLIED:   2000-11-06 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      Refer to the patch description on the patch message.
    • 84 SEQ #86
      DATE APPLIED:   2000-11-27 00:00:00
      APPLIED BY:   USER,ONE
    • 50 SEQ #87
      DATE APPLIED:   2001-01-03 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      Please see the patch module on forum for a complete description of
this patch.
 
The patch tracker message on forum is message number 29329466.
    • 97
      DATE APPLIED:   2001-01-03 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      This patch is a multi-build to address problems with date/time consistency
RMPR*3.0*54
GMRC*3.0*19
as a result of changes implemented in patch HL*1.6*66.  This patch will
include the following builds.  Please see the individual patch
descriptions for more detail regarding the changes made.
 
OR*3.0*97
GMRA*4.0*16
FH*5.0*28
LR*5.2*265
    • 91 SEQ #89
      DATE APPLIED:   2001-01-22 00:00:00
      APPLIED BY:   USER,ONE
    • 21
      DATE APPLIED:   1999-04-16 00:00:00
      APPLIED BY:   USER,ONE
    • 98 SEQ #90
      DATE APPLIED:   2001-01-22 00:00:00
      APPLIED BY:   USER,ONE
    • 92 SEQ #91
      DATE APPLIED:   2001-02-02 00:00:00
      APPLIED BY:   USER,ONE
    • 106 SEQ #92
      DATE APPLIED:   2001-02-05 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      Patch OR*3.0*92 changed the location where order text is saved.  This
patch will update two entries in the OE/RR PRINT FIELDS file to
accommodate this new location.
    • 96 SEQ #93
      DATE APPLIED:   2001-02-28 00:00:00
      APPLIED BY:   USER,ONE
    • 99 SEQ #94
      DATE APPLIED:   2001-04-05 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      Refer to the patch description on the patch message.
    • 101 SEQ #95
      DATE APPLIED:   2001-04-05 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      Refer to the patch description on the patch message.
    • 108 SEQ #96
      DATE APPLIED:   2001-04-12 00:00:00
      APPLIED BY:   USER,ONE
    • 104
      DATE APPLIED:   2001-04-30 00:00:00
      APPLIED BY:   USER,ONE
    • 107 SEQ #98
      DATE APPLIED:   2001-05-17 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      This patch distributes the CPRS Performance monitor report.  This report
is styled after a report developed by VISN 19.  Please see the patch
description on FORUM for a detailed description of this report.
    • 102 SEQ #99
      DATE APPLIED:   2001-05-29 00:00:00
      APPLIED BY:   USER,ONE
    DATE INSTALLED AT THIS SITE:   1999-04-16 00:00:00
    INSTALLED BY:   USER,ONE
    DESCRIPTION OF ENHANCEMENTS:   
    This build contains Order Entry/Results Reporting version 3.0.  It
is exported as part of the release of CPRS.
FILE
  • 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:   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:   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:   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:   NO
    MAY USER OVERRIDE DD UPDATE:   NO
    DATA COMES WITH FILE:   NO
    MAY USER OVERRIDE DATA UPDATE:   YES
  • FIELD:
    • PRIMARY OE/RR MENU
    • SUMMARY DEFAULT
    • PATIENT LIST ORDER
    • DEFAULT RESULTS REPORTING MENU
    • PRIMARY PROFILE MENU
    • PROVIDER LIST
    • SPECIALTY LIST
    • PRIMARY ORDER MENU
    • PRIMARY ORDER DISPLAY FORMAT
    • WARD LIST
    • PATIENT LIST
    • SELECT PATIENT FROM
    • CLINIC LIST
    • CLINIC APPOINTMENT START DATE
    • CLINIC APPOINTMENT STOP 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:   YES
  • UPDATE THE DATA DICTIONARY:   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
    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
    MAY USER OVERRIDE DD UPDATE:   NO
    DATA COMES WITH FILE:   NO
  • UPDATE THE DATA DICTIONARY:   YES
    MAY USER OVERRIDE DD UPDATE:   NO
    DATA COMES WITH FILE:   YES
    MERGE OR OVERWRITE SITE'S DATA:   MERGE
    MAY USER OVERRIDE DATA UPDATE:   NO
  • 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:   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:   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:   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
  • 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:   NO
    MAY USER OVERRIDE DD UPDATE:   NO
    DATA COMES WITH FILE:   YES
    MERGE OR OVERWRITE SITE'S DATA:   MERGE
    MAY USER OVERRIDE DATA UPDATE:   YES
PRINT TEMPLATE
ENVIRONMENT CHECK ROUTINE ORPRE
ENVIRONMENT CHECK DONE DATE 1996-06-13 09:53:51
POST-INITIALIZATION ROUTINE ORPOST
POST-INIT COMPLETION DATE 1996-06-13 09:58:16
PRE-INIT AFTER USER COMMIT ORPRE1
PRE-INIT COMPLETION DATE 1996-06-13 09:54:11
EXCLUDED NAME SPACE
  • ORZ