============================================================================= Run Date: APR 16, 2026 Designation: OR*3*508 Package : OR - ORDER ENTRY/RESULTS REPORTING Priority: Mandatory Version : 3 SEQ #539 Status: Released Compliance Date: JUL 17, 2026 ============================================================================= Associated patches: (v)OR*3*429 <<= must be installed BEFORE `OR*3*508' (v)OR*3*531 <<= must be installed BEFORE `OR*3*508' (v)OR*3*593 <<= must be installed BEFORE `OR*3*508' (v)OR*3*601 <<= must be installed BEFORE `OR*3*508' (v)OR*3*604 <<= must be installed BEFORE `OR*3*508' (v)OR*3*606 <<= must be installed BEFORE `OR*3*508' (v)OR*3*608 <<= must be installed BEFORE `OR*3*508' (v)OR*3*609 <<= must be installed BEFORE `OR*3*508' (v)OR*3*629 <<= must be installed BEFORE `OR*3*508' Subject: CPRS GUI V33CON-CONGRESSIONAL MANDATES Category: - Routine - Enhancement (Mandatory) - Data Dictionary - Print Template - Other Description: ============ This patch is part of the Computerized Patient Record System (CPRS) v33CON updates. Below is a list of all the applications involved in this project along with their patch numbers: APPLICATION/VERSION PATCH --------------------------------------------------------------- ORDER ENTRY/RESULTS REPORTING v3.0 OR*3.0*508 CLINICAL REMINDERS v2.0 PXRM*2.0*87 PATIENT CARE ENCOUNTER v1.0 PX*1.0*244 PROBLEM LIST v2.0 GMPL*2.0*58 MENTAL HEALTH v5.01 YS*5.01*253 This patch covers several New Service Requests (NSRs). 1. NSR 20200806 Exclude Community Care-Only Providers from Inappropriate Selection in CPRS. Office of Community Care is requesting an enhancement to CPRS. Currently, CPRS presents names of Community Care (Non-VA) only providers in the drop-down selection windows for scenarios where only in-house providers are the correct and appropriate selection. The issue occurs with the selection of a Community Care (Non-VA) only provider in situations requiring an in-house VA provider, which can result in patient result notifications (critical alerts for lab or imaging results) being sent to the wrong place, which could result in patient harm through delay in a correct notification. The intended recipient never sees them and this can delay patient care. An enhancement in CPRS is requested to provide a method for CPRS to identify, filter and exclude Community Care (Non-VA) only providers from certain drop-down selection choices. Providers would be excluded when they are Community Care (Non-VA) only, but not when they are also VA providers (or dual providers) who have the COR Tab (i.e., can directly access CPRS). This will allow patient result notifications (critical alerts for lab or imaging results) to be sent to the correct in-house provider. Additionally, the same filters should be available for selection of names to sign documents in CPRS. Community Care (Non-VA) only providers will never be the correct name to select for signing documents. Also included in this release of CPRS GUI is a new VistA-based mechanism that allows some modifications to CPRS without the need to also update the GUI. This new method of delivering features in CPRS will only require one (or more) VistA patch(es). Eliminating the need for GUI updates will improve the delivery speed for any new features deemed suitable to this new mechanism. EHRM Impact Statement: ---------------------- VOCCB review is pending. - This patch should have no EHRM impact, and can be installed at all sites, including EHRM converted sites. Patch Components: ----------------- Files & Fields Associated: File Name (Number) Field Name (Number) New/Modified/Deleted ------------------ ------------------- -------------------- ORDER (#100) Modified SPECIAL AUTHORITIES Mult (#100.0112) SPECIAL AUTHORITY(#.01) New VALUE (#1) PANELS UI (#101.71) New CLASS TYPE (#.01) ACTIVE (#.02) UPDATE DATE/TIME (#.03) UPDATE SOURCE (#.04) RESPONSIBLE PACKAGE (Multiple 101.711) (#1) RESPONSIBLE PACKAGE (#.01) LOCATION (Multiple-101.7112) (#2) LOCATION SEQUENCE (#.01) LOCATION (#.02) DISPLAY TEXT (#.03) ABBREVIATION (#.04) BACKGROUND COLOR (#.05) DISABLED (#.06) COLLAPSIBLE (#.07) IMAGE/ICON (#.08) ITEMS (Multiple-101.71123) (#3) ITEM SEQUENCE (#.01) NAME (#.02) STATUS (#.03) ABBREVIATION (#.04) DISPLAY TEXT (#.05) BACKGROUND COLOR (#.06) MANDATORY (#.07) IMAGE/ICON (#.08) EVALUATION TYPE (#10) REMINDER COMPONENT (#11) REMINDER STATUS (#12) EVALUATION CODE (#13) DISPLAY IF NOT APPLICABLE (#20) APPLICABLE ABBREVIATION (#21) APPLICABLE DISPLAY TEXT (#22) APPLICABLE BACKGROUND COLOR (#23) APPLICABLE IMAGE/ICON (#24) ACTION (#30) FORM TYPE (#31) DETAIL CODE (#32) CALL DETAIL RPC (#33) EDITOR (#34) DESCRIPTION (Multiple-101.712) (#40) DESCRIPTION (#.01) DETAIL TEXT (Multiple-101.713) (#50) DETAIL TEXT (#.01) REQUIRED DATA (Multiple-101.714) (#60) REQUIRED DATA (#.01) REQUIRED (#.05) URL (#70) INFORMATION/EDITOR New COMPONENTS (#101.73) NAME (#.01) TYPE (#1) COMPONENT NAME (#2) DESCRIPTION (Multiple-101.731 (#20) DESCRIPTION (#.01) ERROR MESSAGE (#30) DATA PROPERTIES (Multiple-101.734)(#40) PROPERTY ID (#.04) REQUIRED (#1) IMAGE/ICON (Multiple-101.7351)(#40) IMAGE/ICON (#.01) PAGE ID (#60) EDITOR (#101.74) New NAME (#.01) DISPLAY NAME (#1) INACTIVE (#2) NUM OF COL (#3) NUM OF ROWS (#4) HIDE BUTTONS (#5) SAVE BUTTON TEXT (#6) CANCEL BUTTON TEXT (#7) REFRESH ALL PANELS (#8) DESCRIPTION (Multiple-101.742)(#20) DESCRIPTION (#.01) LAYOUT (Multiple-101.743)(#30) CELL NAME (#.04) EDITOR TYPE (#1) DISABLED (#2) LABEL (#10) COLUMN (#11) ROW (#12) COLUMN SPAN (#13) ROW SPAN (#14) REQUIRED (#15) SET DEFAULT VALUE (#16) NEED SORT (#30) SHOW POSSIBLE VALUES (#31) LONGLIST LOOKUP (#32) LONGLIST PARAMETER (#40) HINT (Multiple-101.744)(#50) HINT (#.01) PLUGIN (#40) DOCUMENT DEFINITION (#42) CAN CHANGE NOTE (#43) SCHEMA (#50) UISCHEMA (#51) OR M CODE PLUGIN (#101.75) New NAME (#.01) ROUTINE (#1) ENTRY POINT (#2) TYPE (#3) MANDATORY PARAMETER (#4) SHORT DESCRIPTION (#10) DESCRIPTION (Multiple-101.752)(#20) DESCRIPTION (#.01) WEB CONTENT (#101.76) New NAME (#.01) CONTENT TYPE (#.02) RESERVED FOR SYSTEM (#.03) CONTENT (Multiple-101.761)(#1) CONTENT (#.01) LINKED CONTENT (Multiple-101.762)(#2) SEQUENCE (#.01) LINKED CONTENT (#.02) WEB CONTENT TYPE (#101.77) New NAME (#.01) CODE (#.02) DESCRIPTION (#.03) Forms Associated: Form Name File Number New/Modified/Deleted --------- ----------- -------------------- N/A Mail Groups Associated: Mail Group Name New/Modified/Deleted --------------- -------------------- N/A Options Associated: Option Name Type New/Modified/Deleted ----------- ------ -------------------- OR CPRS GUI CHART BROKER Modified OR M PLUGIN ADD/EDIT ACTION New ORE EDITOR ADD/EDIT ACTION New ORI COMPONENT ADD/EDIT ACTION New ORI MENU MENU New ORI PANEL ADD/EDIT ACTION New ORI PARAM COLORS ACTION New ORI PARAM DEFAULT COLOR ACTION New ORI PARAM IMAGES ACTION New ORI PARAM INDENT TEXT ACTION New ORI PARAM MENU MENU New ORI PARAM MOUSE CLICK ACTION New ORI PARAM ON/OFF ACTION New ORI PARAM PANEL POSITION ACTION New ORI PARAM REFRESH BUTTON ACTION New ORI PARAM TEXT ALIGN ACTION New ORI TESTER ACTION New ORW CLEAR USER INFO PANEL SIZE ACTION New Protocols Associated: Protocol Name New/Modified/Deleted ------------- -------------------- N/A Security Keys Associated: Security Key Name ----------------- N/A Templates Associated: Template Name Type File Name (Number) New/Modified/Deleted ------------- ------ ------------------ -------------------- OR PRINT M PLUGIN PRINT FILE #101.75 New ORE PRINT EDITOR PRINT FILE #101.74 New ORI PANEL INQUIRY PRINT FILE #101.71 New ORI PRINT COMPONENT PRINT FILE #101.73 New Remote Procedures Associated: Remote Procedure Name New/Modified/Deleted ------------------------- -------------------- OREDITOR LONGLIST New OREDITOR SAVE New ORHEDITOR SAVE New ORHRPC LOOKUP New ORIRPC GETPANELS New ORIRPCCL GETCLICK New ORNEWPERS NEWPERSON New ORSPECAUTH SAFORORDERS New ORSPECAUTH UPDATEORDERSA New ORWEB GETWEBCONTENT New Parameter Definitions Associated: Parameter Name New/Modified/Deleted ------------------------------- -------------------- OR CPRS LAST BROKER RPC MAX New OR CPRS WIN MESSAGE LOG SIZE Deleted OR INFO COLORS New OR INFO DEFAULT COLOR New OR INFO IMAGES New OR INFO INDENT New OR INFO MOUSE CLICK New OR INFO PANEL ALIGNMENT New OR INFO PANEL ON New OR INFO REFRESH BUTTON New OR INFO TEXT ALIGN New OR LOAD SA FROM EXISTING ORDER New OR SPECAUTH ADD PROB TO VISIT New OR SPECAUTH UNANSWERD TO VALUE New OR UPDATE PSO ENV INDICATOR New ORWCH NON-VA PROVIDERS New ORWCH NON-VA PROVS FEATURE New Additional Information: ----------------------- A new entry, COMPACT UPDATES, is added to OE/RR NOTIFICATIONS (#100.9). This notification will remain disabled until a future release. New Service Requests (NSRs): ---------------------------- NSR 20200806 Exclude Community Care-Only Providers from Inappropriate Selection in CPRS Office of Community Care is requesting an enhancement to CPRS. Currently, CPRS presents names of Community Care (Non-VA) only providers in the drop-down selection windows for scenarios where only in-house providers are the correct and appropriate selection. The issue occurs with the selection of a Community Care (Non-VA) only provider in situations requiring an in-house VA provider, which can result in patient result notifications (critical alerts for lab or imaging results) being sent to the wrong place, which could result in patient harm through delay in a correct notification. The intended recipient never sees them and this can delay patient care. An enhancement in CPRS is requested to provide a method for CPRS to identify, filter and exclude Community Care (Non-VA) only providers from certain drop-down selection choices. Providers would be excluded when they are Community Care (Non-VA) only, but not when they are also VA providers (or dual providers) who have the COR Tab (i.e., can directly access CPRS). This will allow patient result notifications (critical alerts for lab or imaging results) to be sent to the correct in-house provider. Additionally, the same filters should be available for selection of names to sign documents in CPRS. Community Care (Non-VA) only providers will never be the correct name to select for signing documents. Patient Safety Issues (PSIs): ----------------------------- HITPS-8424 Defect Tracking System Ticket(s) & Overview: -------------------------------------------- 1. INC26132519 - Reminder Patient List Issue Problem: -------- When a user uses menu options "ORLP PATIENT LIST MGMT" or "ORLP SETUP TEAM LIT FROM REM" to update a team list, VistA may hard error if there are too many patients to filter through (~250k). Resolution: ----------- A code fix has been made that will allow more patients through the patient team list filter code. VistA will no longer hard error and will work as expected. 2. INC20821664 - CPRS GAF tab allows future date entry Problem: -------- The Date Determined calendar component can be used to select a future date. Resolution: ----------- The date entered for Date Determined is checked to make sure it is a valid date for the encounter, including making sure it's not a future date. 3. INC26019603 - Can't add a dx problem list from encounter if the name for the DX starts with same name. Problem: -------- If the user's Problem List in CPRS includes a diagnosis, e.g. "HYPERTENSION", that is both a single-word diagnosis, as well as a word used in other diagnoses, e.g. "OCCULAR HYPERTENSION", the user will not be able to add the other diagnosis to the Problem List from the CPRS Encounter Form. Resolution: ----------- A more complete check is done for possible duplicates, beyond just looking for overlap in wording. When there is a possible duplicate based on the wording of the diagnosis name/narrative, the ICD10 diagnosis codes are also checked. 4. INC33228299 - Latency when staff launch/complete clinical reminders Problem: -------- At sites where a lot of additional reminder categories have been created for use in CPRS, processing reminder dialogs can have lag or cause CPRS to "freeze" for a significant length of time (10+ seconds). This lag can happen as the user is processing the active reminder, when they click "Back" or "Next", or when they finish the reminder. This is a result of the BuildReminderTree procedure being called. As the reminder tree is being rebuilt, the OnExpanded and OnExpanding event handlers are being triggered, which is (a) not necessary, and (b) causes CPRS to evaluate all the reminders again and again. Further, the procedure uses a linear lookup of reminder category nodes that becomes problematic (i.e., "slow") when there are lots of additional reminder categories. Resolution: ----------- In the BuildReminderTree procedure, in uReminders.pas, the OnExpanding and OnExpanded event handlers are disabled prior to rebuilding the reminder tree, then enabled again afterward. In addition, a dictionary is used to speed lookup of reminder category parent nodes. 5. INC31395339 Wrong administration date populating on VIMM form when using clinical reminders to document immunization administration Problem: -------- When the user is using a reminder dialog to document an immunization administration, if the user clicks on an older note (for example, to review a previous immunization administration), the VIMM form's "Administration Date" field is populated with the date of the older note. This is happening because the encounter data for the new note is being overwritten by the encounter data of the older note, and the adminstration date is loaded from the encounter data. Resolution: ----------- The caching of the new notes encounter data for the reminder dialog was improved by creating a copy that won't be overwritten when the user views another note. 6. INC35588033 R4 - (FLX) CPRS v33 SWD can not see my alerts in CPRS Problem: -------- Under certain combinations of both font and window sizing, it is possible for the notification pane of the patient selection window to become hidden. When in this state, the user is unable to correct the issue and therefore unable to view or process notifications. Resolution: ----------- The patient selection screen resizing logic has been updated to prevent the notification pane from becoming hidden. 7. INC26623557 (INC27753177, INC38707567) Notifications do not include entire text when there is a ":" in the title NAME. Problem: -------- Document titles with a ':' are missing the full alert text. Resolution: ----------- The logic has been updated to account for ':'s in the document title. 8. INC26388194 - CPRS User reported Medication Order appeared in patient's Orders Tab List that DID NOT belong to that patient Problem: -------- When taking actions on a group of orders it was possible to change patients prior to the order's action screen opening. This the causes the order to "migrate" to the next patient's chart. Resolution: ----------- Code has been added to ensure that the user remains on the current chart in CPRS while processing multiple orders. 9. INC21083514 - CPRS DOCUMENT FROM DIFFERENT PATIENT FROM 1999 AUTOMATICALLY INSERTS INTO UNSIGNED ADDENDUM, - HITPS-8424 Problem: -------- There were situations where the communication between the patient context management software and CPRS could cause CPRS to display one patient's information in the title bar but another patient's information in the chart. It could also result in the chart displaying mixed patient information. Resolution: ----------- Code was put in place ensuring that no part of CPRS will load the next patient's chart until all other applications participating in a patient context session are ready. 10. INC13991180 - In CPRS the provider checks the 99308 code the modifiers for unusual anesthesia automatically checks. Problem: ------- When certain visit types are selected in the Encounter form, one or more modifiers are being incorrectly checked automatically. This was caused by old code added for testing purposes and never removed. Resolution: ---------- The old testing code was purged from the procedures which setup the internal data structure for the visit types. 11. INC35659601 (INC36868899, INC37099504, INC38434644) - PDMP relatedissue - "Report already delivered" error message Problem: -------- When queuing and generating the PDMP report in CPRS, the generated report intermittently returns a "Report already delivered" error rather than the expected report. Resolution: ----------- The internal components used in the PDMP process have been updated. 12. INC41457146 Cancelling Order Set with Narcotic Order may Cause CPRS to Hang Up Problem: ------- When a user in CPRS selects an order set with a controlled substance, if the user does not have a valid DEA number, CPRS pops up a warning with Cancel and Retry options. If the user selects Cancel, CPRS hangs and must be forcibly closed. Resolution: ---------- CPRS GUI was updated to respond appropriately when the Cancel button has been pressed. The user may continue working in CPRS GUI without a hang or need to shut down the application. Test Sites: ----------- VA North Texas Health Care System VA Southeast Louisiana Health Care System VA San Diego Health Care System, CA Test Sites - SNOW Change Order #: VA North Texas Health Care System - CO#: CHG0715639 VA Southeast Louisiana Health Care System - CO#: CHG0715638 VA San Diego Health Care System, CA - CO#: CHG0714475 Software and Documentation Retrieval Instructions: -------------------------------------------------- The software for this patch is being released using a host file. The host file is available at the following location: /srv/vista/patches/SOFTWARE/CPRS_V33CON_COMBINED_BUILD.KID Other Software Files: This release also includes other software files. Other software files can be obtained by accessing the URL: https://download.vista.domain.ext/index.html/SOFTWARE File Title File Name Format --------------------------------------------------------------------- OR_30_508.ZIP CPRSChart.exe BINARY RoboEx32.dll borlndmm.dll CPRSChart.map CRC.TXT WebView2Loader.dll YS_MHA_A_XE10.dll HELP Directory OR_30_508_SRC.ZIP CPRS v33CON Source BINARY CPRS_v33CON_COMBINED_BUILD.KID CPRS v33CON COMBINED ASCII Documentation describing the new functionality is included in this release. Documentation can be found on the VA Software Documentation Library at: https://www.domain.ext/vdl/. Documentation can also be obtained at https://download.vista.domain.ext/index.html/SOFTWARE Documentation Title File Name --------------------------------------------------------------------- CPRS v33CON (OR*3.0*508) Deployment, OR_3_0_508_DIBR.DOCX Installation, Back-Out, and Rollback Guide OR_3_0_508_DIBR.PDF CPRS GUI v33CON Release Notes OR_3_0_508_RN.DOCX OR_3_0_508_RN.PDF CPRS National Information Panel CPRS NATIONAL INFORMATION PANEL SETUP GUIDE.DOCX CPRS NATIONAL INFORMATION PANEL SETUP GUIDE.PDF Computerized Patient Record System (CPRS) CPRSSETUP.DOCX Setup Guide CPRSSETUP.PDF Computerized Patient Record System (CPRS) CPRSLMTM.DOCX Technical Manual: List Manager Version CPRSLMTM.PDF Computerized Patient Record System (CPRS) CPRSGUITM.DOCX Technical Manual: GUI Version CPRSGUITM.PDF Computerized Patient Record System (CPRS) CPRSGUIUM.DOCX User Guide: GUI Version CPRSGUIUM.PDF Patch Installation: ------------------- Pre/Post Installation Overview: ------------------------------- ***Installation of this build must NOT be queued.*** Please refer to the "CPRS v33CON (OR*3.0*508) Deployment, Installation, Back Out, and Rollback Guide" for installation and set-up information. This document is exported as OR_3_0_508_DIBR.PDF and OR_3_0_508_DIBR.DOCX. Post-Installation Instructions: ------------------------------- Please refer to the "CPRS v33CON (OR*3.0*508) Deployment, Installation, Back Out, and Rollback Guide" for installation and set-up information. Back-Out/Roll Back Plan: ------------------------ Please refer to the "CPRS v33CON (OR*3.0*508) Deployment, Installation, Back Out, and Rollback Guide" for back-out and rollback information, along with risks and criteria for back-out. Routine Information: ==================== The second line of each of these routines now looks like: ;;3.0;ORDER ENTRY/RESULTS REPORTING;**[Patch List]**;Dec 17, 1997;Build 40 The checksums below are new checksums, and can be checked with CHECK1^XTSUMBLD. Routine Name: ORB3 Before:B161486362 After:B174747565 **31,74,91,105,139,190,220,253, 265,296,348,350,452,377,453, 508** Routine Name: ORB3FUP2 Before: B69924581 After: B70267550 **31,64,88,112,243,434,508** Routine Name: ORBSMART Before: B48077990 After: B45775411 **377,498,593,508** Routine Name: ORCSAVE Before:B121792460 After:B137327552 **7,56,70,73,92,94,116,141,163, 187,190,195,243,303,293,280, 306,286,269,423,421,382,397, 377,453,405,499,609,508** Routine Name: ORCSAVE2 Before:B103460867 After:B117810809 **4,27,56,70,94,116,190,157, 215,265,243,293,280,346,269, 421,382,377,405,508** Routine Name: ORDD71 Before: n/a After: B31531820 **508** Routine Name: OREDITOR Before: n/a After: B60382623 **508** Routine Name: OREDITOR1 Before: n/a After:B121676245 **508** Routine Name: OREDITOR2 Before: n/a After:B127859820 **508** Routine Name: OREDITOR3 Before: n/a After: B80458029 **508** Routine Name: OREDITOR4 Before: n/a After: B76214904 **508** Routine Name: ORHEDITOR Before: n/a After: B78974933 **508** Routine Name: ORHRPC Before: n/a After: B31667120 **508** Routine Name: ORICHECK Before: n/a After: B30468214 **508** Routine Name: ORIHELP Before: n/a After: B8357368 **508** Routine Name: ORIMGR Before: n/a After:B160865359 **508** Routine Name: ORIMGR1 Before: n/a After: Delete Routine Name: ORIRPC Before: n/a After:B139043596 **508** Routine Name: ORIRPC1 Before: n/a After: B8281023 **508** Routine Name: ORIRPCCL Before: n/a After: B46968118 **508** Routine Name: ORITEST Before: n/a After: B67289725 **508** Routine Name: ORIUTL Before: n/a After: B27707526 **508** Routine Name: ORLPREM Before: B32531974 After: B34212211 **377,498,508** Routine Name: ORMBLDPS Before: B94496686 After: B93507147 **7,38,54,86,97,94,116,129,141, 190,195,237,254,243,293,280, 266,395,405,508** Routine Name: ORMPS Before: B91044566 After: B90816166 **3,54,62,86,92,94,116,138,152, 141,165,149,213,195,243,306, 350,480,609,508** Routine Name: ORMPS1 Before: B85031239 After: B84071990 **86,92,94,116,134,152,158,149, 190,195,215,265,275,243,280, 350,382,397,413,405,508** Routine Name: ORMPS2 Before: B57890711 After: B56706745 **94,116,129,134,186,190,195, 215,265,243,280,363,350,462, 413,405,577,602,604,508** Routine Name: ORMPS3 Before: B35632895 After: B34944162 **213,243,413,547,405,508** Routine Name: ORNEWPERS Before:B101521437 After:B110517008 **596,609,508** Routine Name: ORPATCHUTILS Before: n/a After: B14303376 **508** Routine Name: ORQ21 Before: B46334719 After: B46677197 **141,190,195,215,243,361,350, 417,377,521,405,508** Routine Name: ORQQPL Before: B33314965 After: B34962327 **9,10,85,173,306,361,385,350,508** Routine Name: ORQQPL1 Before:B140973389 After:B150263693 **10,85,148,173,203,206,249, 243,280,306,361,385,350,479, 377,508** Routine Name: ORQQPL3 Before: B81488349 After: B80906954 **10,148,173,243,280,306,361, 385,429,508** Routine Name: ORSPECAUTH Before: n/a After:B146604994 **508** Routine Name: ORWCH Before: B12902368 After: B16697577 **10,109,149,508** Routine Name: ORWDX Before: B52638400 After: B53359339 **10,85,125,131,132,141,164, 178,187,190,195,215,246,243, 283,296,280,306,350,424,421, 461,490,397,377,539,405,588, 601,508** Routine Name: ORWEB Before: n/a After: B9543407 **508** Routine Name: ORWORB Before:B144620893 After:B146915845 **10,85,116,148,173,190,215, 243,296,329,334,410,377,498, 405,596,508** Routine Name: ORWOTHER Before: B3589793 After: B3586104 **485,377,531,508** Routine Name: ORWPCE3 Before:B144178790 After:B133368046 **10,85,116,190,280,306,371, 361,385,377,498,405,598,588, 606,508** Routine Name: ORWPT2 Before: B6696868 After: B6694356 **485,608,508** Routine Name: ORWU Before:B161693263 After:B164332006 **10,85,132,148,149,187,195, 215,243,350,424,377,519,539, 405,596,588,608,629,508** Routine Name: ORY508 Before: n/a After: B60985655 **508** Routine list of preceding patches: 429, 434, 531, 593, 601, 604, 606, 609 629 ============================================================================= User Information: Entered By : Date Entered : MAR 28, 2019 Completed By: Date Completed: APR 16, 2026 Released By : Date Released : APR 16, 2026 ============================================================================= Packman Mail Message: ===================== No routines included