$TXT Created by CPRSNGUIA.DOMAIN.EXT (KIDS) on Thursday, 09/12/24 at 13:43 ============================================================================= Run Date: OCT 29, 2024 Designation: OR*3*535 Package : OR - ORDER ENTRY/RESULTS REPORTING Priority: Mandatory Version : 3 SEQ #527 Status: Released Compliance Date: NOV 29, 2024 ============================================================================= Associated patches: (v)OR*3*242 <<= must be installed BEFORE `OR*3*535' (v)OR*3*315 <<= must be installed BEFORE `OR*3*535' (v)OR*3*401 <<= must be installed BEFORE `OR*3*535' (v)OR*3*469 <<= must be installed BEFORE `OR*3*535' (v)OR*3*519 <<= must be installed BEFORE `OR*3*535' (v)OR*3*539 <<= must be installed BEFORE `OR*3*535' (v)OR*3*596 <<= must be installed BEFORE `OR*3*535' Subject: ORDER CHECK AND DEFECT CHANGES Category: - Routine - Other - Enhancement (Mandatory) - Data Dictionary Description: ============ This patch introduces the following modifications: 1. This patch creates a new Glucophage/Metformin Order Check that uses an estimated Glomerular Filtration Rate (eGFR) calculation instead of using the Serum Creatinine as the current Order Check does. 2. A problem was discovered in the Computerized Patient Record System (CPRS) v31b release with the display of ordering providers in the alert List resulting in the decision to blank out the Ordering Provider column. This patch corrects this issue and re-enables the display of the Ordering Providers. 3. The Care Management Package has been decommissioned. There are remaining API calls to Care Management routines in the Order Entry/Results Reporting (OE/RR) package. This patch removes those API calls. 4. It adds a new option to allow sites to edit the ORDER CHECK OVERRIDE REASONS (#100.04) file. As part of this change a new NATIONAL (#.05) field was created so that nationally released order check override reasons can be identified separately from locally created entries. 5. It corrects the display of the patient's name in the View Patient Notifications alert detail dialog where some names were cutoff. 6. It corrects an Integration Control Registrations (ICR) documentation issue recently discovered during development activities. 7. It adds a new entry to the ORDER CHECK OVERRIDE REASONS (#100.04) file. Patch Components: ----------------- Files & Fields Associated: File Name (Number) Field Name (Number) New/Modified/Deleted ------------------ ------------------- -------------------- ORDER CHECK OVERRIDE NATIONAL (#.05) New REASONS (#100.04) 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 ----------- ---- -------------------- Edit Override Reasons run routine New [ORCL OVERRIDE REASON] CPRS Configuration (Clin menu Modified Coord) [OR PARAM COORDINATOR MENU] Set eGFR Date Range for run routine New Metformin-Lab Rslts [ORK METFORMIN EGFR] Order Checking Mgmt Menu menu Modified [ORK ORDER CHK MGMT MENU] 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 ------------- ---- ------------------ -------------------- N/A Remote Procedures Associated: Remote Procedure Name New/Modified/Deleted --------------------- -------------------- N/A Parameter Definitions Associated: Parameter Name New/Modified/Deleted -------------- -------------------- ORK METFORMIN EGFR New Additional Information: ----------------------- New File Entries Associated: File Name (Number) Field (Number) Value ------------------ --------------- ----- ORDER CHECK NATIONAL NAME (#.01) PLASMA SPECIMEN Term (#860.9) FILE NUMBER (#.02) 61 OCX MDD ATTRIBUTE NAME (#.01) METFORMIN-EGFR DAYS (#863.4) PARAMETER (#1) PARAMETER NAME (#.01) DATA TYPE VALUE (#1) NUMERIC OCX MDD ATTRIBUTE NAME (#.01) METFORMIN-EGFR FLAG (#863.4) PARAMETER (#1) PARAMETER NAME (#.01) DATA TYPE VALUE (#1) BOOLEAN OCX MDD ATTRIBUTE NAME (#.01) METFORMIN-EGFR RESULT (#863.4) PARAMETER (#1) PARAMETER NAME (#.01) DATA TYPE VALUE (#1) NUMERIC OCX MDD ATTRIBUTE NAME (#.01) METFORMIN-EGFR TEXT (#863.4) PARAMETER (#1) PARAMETER NAME (#.01) DATA TYPE VALUE (#1) FREE TEXT OCX MDD LINK (#863.3) NAME (#.01) PATIENT.METFORMIN_EGFR_DAYS PARENT SUBJECT (#.02) PATIENT ATTRIBUTE (#.05) METFORMIN-EGFR DAYS PARAMETER (#2) PARAMETER NAME (#.01) OCXO EXTERNAL FUNCTION CALL VALUE (#1) GEDAYS^ORKPS(|PATIENT IEN|) PARAMETER (#2) PARAMETER NAME (#.01) OCXO UP-ARROW PIECE NUMBER VALUE (#1) 1 OCX MDD LINK (#863.3) NAME (#.01) PATIENT.METFORMIN_EGFR_FLAG PARENT SUBJECT (#.02) PATIENT ATTRIBUTE (#.05) METFORMIN-EGFR FLAG PARAMETER (#2) PARAMETER NAME (#.01) OCXO EXTERNAL FUNCTION CALL VALUE (#1) GLEGFR^ORKPS(|PATIENT IEN|) PARAMETER (#2) PARAMETER NAME (#.01) OCXO UP-ARROW PIECE NUMBER VALUE (#1) 1 OCX MDD LINK (#863.3) NAME (#.01) PATIENT.METFORMIN_EGFR_RSLT PARENT SUBJECT (#.02) PATIENT ATTRIBUTE (#.05) METFORMIN-EGFR RESULT PARAMETER (#2) PARAMETER NAME (#.01) OCXO EXTERNAL FUNCTION CALL VALUE (#1) GLEGFR^ORKPS(|PATIENT IEN|) PARAMETER (#2) PARAMETER NAME (#.01) OCXO UP-ARROW PIECE NUMBER VALUE (#1) 3 OCX MDD LINK (#863.3) NAME (#.01) PATIENT.METFORMIN_EGFR_TEXT PARENT SUBJECT (#.02) PATIENT ATTRIBUTE (#.05) METFORMIN-EGFR TEXT PARAMETER (#2) PARAMETER NAME (#.01) OCXO EXTERNAL FUNCTION CALL VALUE (#1) GLEGFR^ORKPS(|PATIENT IEN|) PARAMETER (#2) PARAMETER NAME (#.01) OCXO UP-ARROW PIECE NUMBER VALUE (#1) 2 ORDER CHECK DATA FIELD NAME (#.01) RECENT METFORMIN EGFR DAYS (#860.4) DATA SOURCES (#100) DATA CONTEXT (#.01) DATABASE LOOKUP DATA SOURCE (#.02) DATABASE LOOKUP META DICTIONARY LINK PATIENT.METFORMIN_EGFR_DAYS (#1) DATATYPE (#101) NUMERIC ORDER CHECK DATA FIELD NAME (#.01) RECENT METFORMIN EGFR FLAG (#860.4) DATA SOURCES (#100) DATA CONTEXT (#.01) DATABASE LOOKUP DATA SOURCE (#.02) DATABASE LOOKUP META DICTIONARY LINK PATIENT.METFORMIN_EGFR_FLAG (#1) DATATYPE (#101) BOOLEAN ORDER CHECK DATA FIELD NAME (#.01) RECENT METFORMIN EGFR RESULT (#860.4) DATA SOURCES (#100) DATA CONTEXT (#.01) DATABASE LOOKUP DATA SOURCE (#.02) DATABASE LOOKUP META DICTIONARY LINK PATIENT.METFORMIN_EGFR_RSLT (#1) DATATYPE (#101) NUMERIC ORDER CHECK DATA FIELD NAME (#.01) RECENT METFORMIN EGFR TEXT (#860.4) DATA SOURCES (#100) DATA CONTEXT (#.01) DATABASE LOOKUP DATA SOURCE (#.02) DATABASE LOOKUP META DICTIONARY LINK PATIENT.METFORMIN_EGFR_TEXT (#1) DATATYPE (#101) FREE TEXT ORDER CHECK ELEMENT NAME (#.01) METFORMIN EGFR <= 45 (#860.3) ELEMENT CONTEXT (#.02) DATABASE LOOKUP CONDITIONAL EXPRESSION (#1) EXPRESSION SEQUENCE 1 NUMBER (#.01) DATA FIELD 1 (#1) RECENT METFORMIN EGFR RESULT OPERATOR/FUNCTION (#2) LESS THAN CONDITIONAL VALUE 1 45.0000000001 (#3) ORDER CHECK ELEMENT NAME (#.01) NO METFORMIN EGFR (#860.3) ELEMENT CONTEXT (#.02) DATABASE LOOKUP CONDITIONAL EXPRESSION (#1) EXPRESSION SEQUENCE 1 NUMBER (#.01) DATA FIELD 1 (#1) RECENT METFORMIN EGFR FLAG OPERATOR/FUNCTION (#2) LOGICAL FALSE ORDER CHECK RULE (#860.2) NAME (#.01) METFORMIN EGFR - LAB RESULTS STATUS (#.02) ACTIVE TRUTH ELEMENTS (#1) LABEL (.01) METFORMIN ORDER ELEMENT NAME (#.1) METFORMIN ORDER TRUTH ELEMENTS (#1) LABEL (.01) METFORMIN EGFR <= 45 TYPE (#.02) SIMPLE DEFINITION ELEMENT NAME (#.1) METFORMIN EGFR <= 45 TRUTH ELEMENTS (#1) LABEL (.01) NO METFORMIN EGFR ELEMENT NAME (#.1) NO METFORMIN EGFR RELATION ACTIONS (#2) RELATION INDEX (#.01) 1 RELATION EXPRESSION METFORMIN ORDER AND (#1) METFORMIN EGFR <= 45 ORDER CHECK (#2) METFORMIN EGFR-LAB RESULTS ORDER CHECK MESSAGE Metformin - EGFR results: (#6) |RECENT METFORMIN EGFR TEXT| RELATION ACTIONS (#2) RELATION INDEX (#.01) 2 RELATION EXPRESSION METFORMIN ORDER AND NO (#1) METFORMIN EGFR ORDER CHECK (#2) METFORMIN EGFR-LAB RESULTS ORDER CHECK MESSAGE Metformin - no eGFR (#6) calculated within past |RECENT METFORMIN EGFR DAYS| days. ORDER CHECKS (#100.8) NAME (#.01) METFORMIN EGFR-LAB RESULTS DESCRIPTION (#2) Triggered by selection of Imaging orderable items. If the patient is taking glucophage/metformin and the eGFR result within x number of days (determined by parameter) is equal or less than 45 or does not exist, the order check occurs. ORDER CHECK OVERRIDE NAME (#.01) Benefit of Therapy REASONS (#100.04) Outweighs Risk NATIONAL (#.05) YES ORDER CHECK OVERRIDE NAME (#.01) Patient tolerating current REASONS (#100.04) therapy with this medication NATIONAL (#.05) YES ORDER CHECK OVERRIDE NAME (#.01) Previous Adverse Reaction REASONS (#100.04) signs/symptoms managed by Patient. NATIONAL (#.05) YES ORDER CHECK OVERRIDE NAME (#.01) Renewal of Current Therapy REASONS (#100.04) NATIONAL (#.05) YES ORDER CHECK OVERRIDE NAME (#.01) Will Monitor Closely for REASONS (#100.04) Adverse Effects NATIONAL (#.05) YES ORDER CHECK OVERRIDE NAME (#.01) Documentation of Allergy/ REASONS (#100.04) Adverse Reaction is in Error NATIONAL (#.05) YES ORDER CHECK OVERRIDE NAME (#.01) Documentation of Allergy/ REASONS (#100.04) Adverse Reaction is to Different agent in same Drug class NATIONAL (#.05) YES ORDER CHECK OVERRIDE NAME (#.01) Patient report per REASONS (#100.04) interview is inconsistent with remote allergy data. NATIONAL (#.05) YES ORDER CHECK OVERRIDE NAME (#.01) Indicated for procedure. REASONS (#100.04) Risks mitigated and will NATIONAL (#.05) YES ORDER CHECK OVERRIDE NAME (#.01) Patient counselled risks/ REASONS (#100.04) benefits, verbalizes understanding, and elects to proceed SYSONYM (#.02) COUNSELLED TYPE (#.03) BOTH ACTIVE (#.04) YES NATIONAL (#.05) YES Modified File Entries Associated: File Name (Number) Field (Number) Old Value New Value ------------------ -------------- --------- --------- ORDER CHECK ELEMENT NAME (#.01) GLUCOPHAGE ORDER METFORMIN ORDER (#860.3) New Service Requests (NSRs): NSR 20160502 - FDA revised warning for Metformin order check to use eGFR instead of Serum Creatine. Patient Safety Issues (PSIs): HITPS-10603 Metformin and eGFR order check update Summary: An enhancement to Veterans Health Information Systems and Technology Architecture (VistA)/CPRS application to modify the current CPRS order check Glucophage-Lab Results to use eGFR instead of serum creatinine (SCr). The current order check using the old guidelines may result in providers discontinuing metformin when it could be safely continued with patient benefit. Defect Tracking System Ticket(s) & Overview: 1. INC26983427 - In CPRS in View Patient Notifications alert detail box, patient name is cut off at beginning. Problem: -------- When viewing alert details in the View Patient Notifications dialog, the patient's name is missing the first couple of letters of the last name as displayed LNAME,FNAME. Resolution: ----------- Routine ORB3UTL was modified to correct the removal of the first two characters of the patient's name. 2. INC29899541 - R1 - (GLA)"View Patient's Notifications" pop-up links to wrong Ordering Provider Problem: -------- The "View Patient's Notifications" pop-up (in CPRS under File) links to the wrong Ordering Provider. This issue is also present in the Pending Notifications on the Patient Selection dialog which is why the Ordering Provider column is left blank in the Pending Notifications. This issue is caused by the mishandling of non-Order Entry/Results Reporting (OE/RR) related notifications. Resolution: ----------- The code, to handle the identification of Ordering Providers, has been modified to account for non-OE/RR related notifications. There may be certain notifications that will not be able to identify an Ordering Provider and thus may display "N/A". Test Sites: ----------- William S. Middleton Memorial Veterans' Hospital (Madison, WI) Malcom Randall VAMC (Gainesville, FL) Coatesville VAMC (Coatesville, PA) Software and Documentation Retrieval Instructions: -------------------------------------------------- The software for this patch is being released in a PackMan message. 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 Technical Manual: GUI Version CPRSGUITM.DOCX CPRSGUITM.PDF CPRS User Manual: GUI Version CPRSGUIUM.DOCX CPRSGUIUM.PDF CPRS Technical Manual: List Manager Version CPRSLMTM.DOCX CPRSLMTM.PDF CPRS User Manual: List Manager Clinician's CPRSLMUM.DOCX Getting Started Guide CPRSLMUM.PDF CPRS Setup Guide CPRSSETUP.DOCX CPRSSETUP.PDF Patch Installation: ------------------- Pre/Post Installation Overview: There are no pre-installation routines to delete. There are post- Installations steps to complete and the post-installation routines can be deleted after it is determined that there are no issues with the installation that would require a backout. ***************************** IMPORTANT ***************************** ** Sites must create a Back-up of the installation (step 2B in ** ** the Installation Instructions) by choosing the backup type of ** ** Build (including Routines). The Back-Out plan relies on this ** ** feature!! ** ********************************************************************* 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. There are no options to disable during patch installation. 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 or build name. (ex. ) NOTE: Using 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*535. iii. When prompted for the following, enter "R" for Routines or "B" for Build. Select one of the following: B Build (including Routines) R Routines Only Backup Type: B// iv. When prompted "Do you wish to secure your build? NO//", press and take the default response of "NO". v. When prompted with, "Send mail to: Last name, First Name", press to take default recipient. Add any additional recipients. vi. When prompted with "Select basket to send to: IN//", press 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 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. Post-Installation Instructions: After a successful installation, sites should perform the following steps: (steps 1-3 below can be completed within the Order Checking Mgmt Menu ... [ORK ORDER CHK MGMT MENU]) 1. If needed, update the mapped local terms to the following Order Check National Terms: a. EGFR - Map your local laboratory test(s) that generate an eGFR Value. b. SERUM SPECIMEN - Map your local Topography Field Name that will be utilized related to Serum Specimens. c. PLASMA SPECIMEN - This national term is new. Map your local Topography Field Name that will be utilized related to Plasma Specimens. 2. If your site has determined the need to perform an eGFR lab test within a certain number of days from the current date to count for the METFORMIN EGFR-LAB RESULTS order check, then use the Set eGFR Date Range for Metformin-Lab Rslts [ORK METFORMIN EGFR] option to set your desired days range. 3. A new Order Check (METFORMIN EGFR-LAB RESULTS) has been created to replace the GLUCOPHAGE-LAB RESULTS order check. As such, any local settings you have for the GLUCOPHAGE-LAB RESULTS order check should be duplicated for the METFORMIN EGFR-LAB RESULTS order check. This includes the Enable/Disable an Order Check [ORK PROCESSING FLAG] option (defaulted to "Enabled" at the Package level) and the Set Clinical Danger Level for an Order Check [ORK CLINICAL DANGER LEVEL] option (defaulted to "High" at the Package level). 4. If your site has determined the need to add additional Override Reasons to the ORDER CHECK OVERRIDE REASONS (#100.04) file, then use the new Edit Override Reasons [ORCL OVERRIDE REASON] option to add the new entries. Example: -------- Select CPRS Configuration (Clin Coord) Option: OVR Edit Override Reasons Select OVERRIDE REASON: NEW OVERRIDE REASON Are you adding 'NEW OVERRIDE REASON' as a new ORDER CHECK OVERRIDE REASONS (the 9TH)? No// Y (Yes) NAME: NEW OVERRIDE REASON// SYNONYM: NOR TYPE: ? Enter an 'A' if used only for Allergy Checks, an 'O' if used only for Order Checks, a 'B' if used for both types of checks. Choose from: A ALLERGY O ORDER CHECK B BOTH R REMOTE COMMENT TYPE: O ORDER CHECK ACTIVE: ? Enter 'Yes' if this entry is currently active. Choose from: 1 YES 0 NO ACTIVE: Y YES Back-Out/Roll Back Plan: ------------------------ In the event of a catastrophic failure, the Area Manager will discuss with site personnel, product support, patient safety representatives, and the development team the possibility of backing out the patch and rollback of any necessary database changes. However, the Area Manager will make the final decision about backout and rollback. Back-Out: --------- In order to back-out the changes included with this patch, sites will need to Install the Build Back-up Transport message created in step 2B of the Installation instructions. This will remove all the components updated via the build. A restore routine will run to inactivate the new METFORMIN EGFR - LAB RESULTS order check rule which was created by the post-init routine during the installation. The order check and order check rule related components will remain on the system. The installer will be presented with an option to remove any locally created Order Check Override Reasons along with the NATIONAL (#.05) field in the ORDER CHECK OVERRIDE REASONS (#100.04) file. This prompt occurs during the installation process, so it is recommended to NOT queue the backup installation. The prompt utilizes a 30 second time out and if this occurs, the locally created Order Check Override Reasons and NATIONAL (#.05) field will remain. The default action is to leave this data on the system. Example Backout: ---------------- 1 Load a Distribution 2 Verify Checksums in Transport Global 3 Print Transport Global 4 Compare Transport Global to Current System 5 Backup a Transport Global 6 Install Package(s) Restart Install of Package(s) Unload a Distribution You have PENDING ALERTS Enter "VA to jump to VIEW ALERTS option Select Installation <++CPRSGOLD++> Option: 6 Install Package(s) Select INSTALL NAME: OR*3.0*535b 9/12/24@12:53:02 => Backup of OR*3.0*535 on Sep 12, 2024 This Distribution was loaded on Sep 12, 2024@12:53:02 with header of Backup of OR*3.0*535 on Sep 12, 2024 It consisted of the following Install(s): OR*3.0*535b Checking Install for Package OR*3.0*535b Install Questions for OR*3.0*535b Incoming Files: 100.04 ORDER CHECK OVERRIDE REASONS Note: You already have the 'ORDER CHECK OVERRIDE REASONS' File. 100.8 ORDER CHECKS Note: You already have the 'ORDER CHECKS' File. Want KIDS to Rebuild Menu Trees Upon Completion of Install? NO// Want KIDS to INHIBIT LOGONs during the install? NO// Want to DISABLE Scheduled Options, Menu Options, and Protocols? NO// Enter the Device you want to print the Install messages. You can queue the install by enter a 'Q' at the device prompt. Enter a '^' to abort the install. DEVICE: HOME// PSUEDO-TERMINAL Install Started for OR*3.0*535b : Sep 12, 2024@10:19:58 Build Distribution Date: Sep 12, 2024 Installing Routines: Sep 12, 2024@10:19:58 Installing Data Dictionaries: Sep 12, 2024@10:19:58 Installing PACKAGE COMPONENTS: Installing OPTION Installing PARAMETER DEFINITION Sep 12, 2024@10:19:58 Running Post-Install Routine: RSTR^ORY535R Inactivating METFORMIN EGFR - LAB RESULTS in the ORDER CHECK RULE (#860.2) file. METFORMIN EGFR - LAB RESULTS has been inactivated. Activating GLUCOPHAGE - LAB RESULTS in the ORDER CHECK RULE (#860.2) file. GLUCOPHAGE - LAB RESULTS has been activated. Renamed ORDER CHECK ELEMENT (#860.3) file entry METFORMIN ORDER to GLUCOPHAGE ORDER. ---Recompiling Order Check Routines----------------------------------- Build list of Active Rules, Elements and Datafields... 96 DATA FIELDS 77 ELEMENTS 39 RULES Compile DataField Navigation code... 101 DataField Navigation Code Arrays Compile Element Evaluation code... 71 Event Evaluation Code Arrays Compile Element MetaCode... 77 Element Metacode Arrays Get Compiler Function Code... 51 Compiler Include Functions Compile Rule Element Relation code... 55 Rule Element Relation Code Arrays Construct Decision Tree... 689 Sub-Routines Optimize Sub-Routines... 276 Sub-Routines 60% Optimization Assemble Routines... 38 OCXOZ* Routines ---Recompiling Complete--- Delete locally created Order Check Override Reasons in file 100.04. Answering YES results in the NATIONAL (#.05) field in the ORDER CHECK OVERRIDE REASONS (#100.04) file to be removed as well. Proceed? Enter Yes or No: NO// YES YES Removing local Order Check Override Reasons... Deleting 'Locally created Override Reason' --- 1 local Order Check Override Reasons removed! Removing NATIONAL (#.05) field from the ORDER CHECK OVERRIDE REASONS (#100.04) file ... ... COMPLETED! Deleting New-Style "B" index from the Data Dictionary for the NAME (#.01) field in the ORDER CHECK OVERRIDE REASONS (#100.04) file ... Removing index ... Deleting index definition ... Completed! Clearing 'B' indexes for file 100.04 Completed! Reindexing the 'B' cross reference for file 100.04 Completed! Updating Routine file... Updating KIDS files... OR*3.0*535b Installed. Sep 12, 2024@10:20:29 NO Install Message sent 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 20 The checksums below are new checksums, and can be checked with CHECK1^XTSUMBLD. Routine Name: ORB3UTL Before: B53105834 After: B71606459 **377,539,535** Routine Name: ORKMGR Before: B31961626 After: B34423211 **9,85,105,401,535** Routine Name: ORKPS Before:B104632974 After:B159984668 **6,32,74,94,123,141,190,232, 316,272,346,345,382,469,535** Routine Name: ORMGMRC Before: B47176451 After: B47474706 **3,26,68,92,153,174,195,255, 243,280,350,415,519,535** Routine Name: ORMLR Before: B55099277 After: B56365708 **3,92,153,174,195,243,315,535** Routine Name: ORMRA Before: B62138554 After: B64364903 **3,53,92,110,136,153,174,195, 228,243,296,535** Routine Name: ORRCLNP Before: B585941 After: B728538 **535** Routine Name: ORRCQLPT Before: B1006284 After: B1082338 **535** Routine Name: ORWORB Before:B144620893 After:B251590024 **10,85,116,148,173,190,215, 243,296,329,334,410,377,498, 405,596,535** Routine Name: ORX1 Before: B28462850 After: B38440525 **92,242,535** Routine Name: ORY535 Before: n/a After: B38968884 **535** Routine Name: ORY5350 Before: n/a After: B15697079 **535** Routine Name: ORY53501 Before: n/a After: B71169391 **535** Routine Name: ORY53502 Before: n/a After: B77628827 **535** Routine Name: ORY53503 Before: n/a After: B81479857 **535** Routine Name: ORY53504 Before: n/a After: B77580901 **535** Routine Name: ORY53505 Before: n/a After: B64611075 **535** Routine Name: ORY53506 Before: n/a After: B63511546 **535** Routine Name: ORY53507 Before: n/a After: B64740298 **535** Routine Name: ORY53508 Before: n/a After: B1125982 **535** Routine Name: ORY5351 Before: n/a After: B40625172 **535** Routine Name: ORY5352 Before: n/a After: B26767340 **535** Routine Name: ORY5353 Before: n/a After: B12998345 **535** Routine Name: ORY5354 Before: n/a After: B13528362 **535** Routine Name: ORY535ES Before: n/a After: B12657775 **535** Routine list of preceding patches: 242, 315, 401, 469, 519, 539, 596 ============================================================================= User Information: Entered By : Date Entered : JUL 07, 2020 Completed By: Date Completed: OCT 22, 2024 Released By : Date Released : OCT 29, 2024 ============================================================================= Packman Mail Message: ===================== $END TXT