$TXT Created by at MNTVBB.DOMAIN.EXT (KIDS) on Wednesday, 05/26/21 at 15:11 ============================================================================= Run Date: JUL 20, 2021 Designation: OR*3*556 Package : OR - ORDER ENTRY/RESULTS REPORTING Priority: Mandatory Version : 3 SEQ #471 Status: Released Compliance Date: AUG 20, 2021 ============================================================================= Associated patches: (v)OR*3*95 <<= must be installed BEFORE `OR*3*556' Subject: ORDER DIALOG ISSUES WHEN PROMPTS DEFINED WITH SAME ID Category: - Routine 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. Defect Tracking System Ticket(s) & Overview: =========================================== INC17239841: Order Dialog Issues When Prompts Defined With Same ID Problem: -------- If an order dialog is defined which contain prompts sharing the same "ID", information might be overlaid during the CPRS ordering process. In addition, CPRS might generate a software error. The Data Dictionary for the ID (#13) field of the ORDER DIALOG (#101.41) file states: "These values must be unique among entries within an order dialog but do not need to be unique across the entire file. Be sure to check the IDs assigned to generic text entries to make sure that all IDs are unique. In order to avoid potential problems it's recommended that you use unique IDs for any local entries that you create." During the creation of a local order dialog, the user might not be aware that more than one prompt is defined for the same "ID". Resolution: ----------- Modify routine ORCMEDT3 to display a warning message to the user who is defining a new order dialog in option "Enter/edit generic orders". Example of warning message: PROMPT: OR GTX WORD PROCESSING 1 word processing Sequence 1 (OR GTX FREE TEXT 1) is also defined with an ID of COMMENT. Select another prompt or define a new prompt with a different ID. WARNING: Do not change the ID field on an existing prompt so as to not affect order dialogs already using the existing prompt. (The ID field can only be edited in the option "Enter/edit prompts" - not this option.) PROMPT: This patch also includes a post-install routine to check entries in the ORDER DIALOG (#101.41) file which have a type of "D" for "dialog" in the TYPE (#4) field. Any of these entries which contain more than one prompt defined for the same "ID" are included in a post-install MailMan message sent to the installer of the patch as well as the "OR CACS" MailMan group. NOTES: 1. Order dialogs which have names beginning with "ZZ" are not checked since these are no longer in use.) 2. Order dialogs named "PSJI OR PAT FLUID OE", CLINIC OR PAT FLUID OE", and "FHW OP MEAL" are also not included in the post-install check. These dialogs appear to have been nationally released years ago and do have two prompts each with an ID of "ORDERABLE". However, there appear to be no problems caused by these order dialogs. MailMan message example if issues are found: Subj: OR*3.0*556 Post-Install [#3048781] 05/25/21@16:42 30 lines From: OR*3.0*556 Post-Install In 'IN' basket. Page 1 -------------------------------------------------------------------------- OR*3.0*556 post-install routine found 3 entries in the ORDER DIALOG (#101.41) file with more than one prompt defined for the same ID. Listed below are such entries which should be reviewed to determine if any prompts should be edited to have a different ID or replaced with new prompts. If your site has not experienced problems with these order dialogs, changes are probably not necessary. If the ID on an existing prompt does need to be changed, make sure the prompt does not exist on another order dialog and will now have the same ID as another prompt. The safest method is to create a new prompt with a different ID. Then replace the existing prompt with the new prompt. Order Dialog ID Prompt (#IEN) ------------------------ --------------- -------------------------- LAB MISC COMMENT OR GTX FREE TEXT 1 (#2) OR GTX WORD PROCESSING 1 (#3) ABC ORDERS COMMENT OR GTX FREE TEXT 1 (#1) OR GTX WORD PROCESSING 1 (#2) BASIC PANEL COMMENT OR GTX FREE TEXT 1 (#1) OR GTX WORD PROCESSING 1 (#2) MailMan message example if no issues are found: Subj: OR*3.0*556 Post-Install [#3048787] 05/25/21@17:10 3 lines From: OR*3.0*556 Post-Install In 'IN' basket. Page 1 *New* -------------------------------------------------------------------------- OR*3.0*556 post-install routine found no entries in the ORDER DIALOG (#101.41) file with more than one prompt defined for the same ID. Test Sites: ----------- Atlanta VA Health Care Sys New Mexico VA Health Care System - Albuquerque Software and Documentation Retrieval Instructions: -------------------------------------------------- The software for this patch is being released in a PackMan message. Patch Instructions: ------------------ 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 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 OR*3.0*556 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*550 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 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: ------------------------------ Review the MailMan message which was sent to the installer as well as members of the OR CACS MailMan group. Back-out/Roll Back Plan: ----------------------- Back-out will be done only with the concurrence and participation of development team and appropriate VA site/region personnel. The decision to back-out or rollback software will be a joint decision between development team, VA site/region personnel and other appropriate VA personnel. Prior to installing an updated KIDS package, the site/region should have saved a backup of the routine 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 routine can be loaded with the "Xtract PackMan" function at the Message Action prompt. The Packman function "INSTALL/CHECK MESSAGE" is then used to install the backed up routine onto the VistA System. The back-out plan is to restore the routine from the backup created. Validation of Back-out Procedure: -------------------------------- The Back-out Procedure can be verified by printing the first two lines of 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 6 The checksums below are new checksums, and can be checked with CHECK1^XTSUMBLD. Routine Name: OR556PST Before: n/a After: B31746955 **556** Routine Name: ORCMEDT3 Before: B42709794 After: B54553235 **8,46,60,95,556** Routine list of preceding patches: 95 ============================================================================= User Information: Entered By : Date Entered : APR 21, 2021 Completed By: Date Completed: JUL 19, 2021 Released By : Date Released : JUL 20, 2021 ============================================================================= Packman Mail Message: ===================== $END TXT