============================================================================= Run Date: JUN 01, 2010 Designation: PXRM*2*17 Package : PXRM - CLINICAL REMINDERS Priority: Mandatory Version : 2 SEQ #13 Status: Released Compliance Date: JUL 02, 2010 ============================================================================= Associated patches: (v)PXRM*2*12 <<= must be installed BEFORE `PXRM*2*17' (v)USR*1*33 <<= must be installed BEFORE `PXRM*2*17' Subject: POLYTRAUMA MARKER Category: - Enhancement (Mandatory) - Data Dictionary - Routine - Other Description: ============ General Overview: ================= This build is a multi-package build that contains USR*1.0*33 and PXRM*2.0*17. PXRM*2*17: The primary purpose of this patch is to update the national polytrauma reminder. Additionally multiple national reminder components are updated. The Exchange file entries installed by this patch are: VA-AAA SCREENING VA-PTSD REASSESSMENT (PCL) VA-POLYTRAUMA MARKER VA-BL DEPRESSION SCREEN VA-HF ETOH SELF SCORE AUD 10 VA-EMBEDDED FRAGMENTS RISK EVALUATION VA-GP EF CONTACT INFORMATION VA-GP ALC ADVICE2 VA-MH STOP CODES FOR PTSD EVALUATION VA-HF ACUTE ILLNESS EVAL DEPRESSION/PTSD REMINDER TERM UPDATES - PATCH 17 PXRM*2*17 COMPUTED FINDINGS See the Installation Guide, PXRM_2_17_IG.PDF, for complete details and instructions for installing these Exchange file entries. During the install you may be prompted for replacement items. Because of this the patch should not be queued and the site's Clinical Reminders manager should be on hand during the install. In addition the following changes are made. Reminder Computed Findings: Three national computed findings are included: VA-ASU USER CLASS (new ) VA-WAS INPATIENT (new) VA-ACTIVE PATIENT RECORD FLAGS (new) See the Installation Guide, PXRM_2_17_IG.PDF, or the online descriptions for details on how to use these computed findings. Reminder Evaluation: The resolution date calculation was not correct when the resolution logic contained a "NOT". In those cases where the resolution logic evaluated to true, the resolution date was calculated to be 0. This was corrected so that the resolution date will no longer be calculated as 0. The Clinical Maintenance output was not displaying the resolution finding header when the resolution logic evaluated to false, but one or more of the resolution findings was true. This was corrected. There was a bug in the display of drug findings; for multiple drug findings in a term, only one occurrence of each finding type was displaying. This was corrected. Other problems were reported with the display of drug findings. A complete fix of this pre-exisiting problem will require more time and testing than we have available for this patch, so a complete solution will have to come in a future patch. Nevertheless, one problem was rectified: The output was not consistent across inpatient, outpatient, and non-VA meds. The output was changed so that it is as consistent as possible (there are some fields that apply only to outpatient and some that apply only to non-VA.) A bug was reported where a non-CH lab test would not work when used as a term finding, but would work when used as a definition finding. This is corrected. A problem with an incorrect resolution date calculation for a resolution logic string containing a 'FF was corrected. Reminder Reports: Patch PXRM*2*12 added the new field OWNER to reminder report templates. E3R 20277 requested including this field when displaying the details of the template. This functionality has been added. If an owner is defined, the template will list the owner name. If an owner is not defined, the template will display "None" next to the owner field. Remedy ticket 372679 reported a bug where the Reminders Due Report was not producing any output when the selected output device was a host file. This was found to be the case at some, but not all sites. The reason for this is that sites can name a host file device anything they want and the report was expecting a certain set of names. The solution was to use the type instead of the name, because types are standardized. Reminder Sponsor: The following Sponsors are renamed: Mental Health and Behavioral Science Strategic Group to Office of Mental Health Services Mental Health and Behavioral Science Strategic Group and Women Veterans Health Program to Office of Mental Health Services and Women Veterans Health Program Reminder Taxonomies: A new option, PXRM TAXONOMY CODE SEARCH, has been added to the TAXONOMY MANAGEMENT MENU. This option will let the user input a code and then it will search all taxonomies in the account and list those where it is used. Miscellaneous: The mechanism used by the Clinical Reminders package to deliver MailMan messages was changed to make it more flexible. When PXRM*2.0*17 is installed in a test account, a MailMan message containing the value of ORQQPX NEW REMINDER PARAMS will be sent to the Clinical Reminders mail group. When the installation is done in a production account, the message will be sent to a Forum mail group. A problem with the MST History file not updating after recording one of the MST health factors was reported; Remedy ticket #367613. A fix for this problem is included and the post-init will start an MST synchronization job to ensure that the MST History file is up-to-date. USR*1*33 This patch changes displays of User Class Names in Authorization and Subscription Utility (ASU) options. User Class Names are now shown by the name of the entry in the User Class File (File #8930). Previously, they were shown by their display names. In particular, the User Class Definition Option [USR CLASS DEFINITION] has been changed to show the entry name of the User Class. The User Class Definition Option [USR CLASS DEFINITION] is found under the User Class Management Menu [USR CLASS MANAGEMENT MENU], which is found under the TIU Maintenance Menu [TIU IRM MAINTENANCE MENU]. In addition, the module used to list the User Classes a particular user belongs to has been enhanced. It may now be set to list classes by entry name rather than by display name, if desired. These changes are necessary because it is the entry name of the Class that users see in User Class edits and various ASU modules. Using the same name in displays avoids confusion. Remedy Tickets: ============== 367613 370830 370849 371207 372501 372679 375075 377769 378961 380637 388863 Documentation: ============== Updated documentation describing the new functionality introduced by this patch is available. The preferred method is to FTP the files from download.vista.med.va.gov. This transmits the files from the first available FTP server. Sites may also elect to retrieve software directly from a specific server as follows: Albany ftp.fo-albany.med.va.gov Hines ftp.fo-hines.med.va.gov Salt Lake City ftp.fo-slc.med.va.gov This documentation will be in the form of Adobe Acrobat files. The updated documentation associated with this patch is: Installation Guide: PXRM_2_17_IG.PDF ASU Technical Manual: ASUTM.PDF Clinical Reminders documentation can also be found in the VistA Documentation Library: (http://vista.med.va.gov/vdl/) or http://www.va.gov/vdl. Build Components: ================= Data Dictionary: ================ FILE # NAME ------------------------------------------------------------------------------- 811.8 REMINDER EXCHANGE 811.9 REMINDER DEFINITION Input Templates: ================ PXRM EDIT ELEMENT FILE #801.41 PXRM EDIT GROUP FILE #801.41 PXRM RESULT GROUP FILE #801.41 Options: ======== PXRM TAXONOMY CODE SEARCH PXRM TAXONOMY MANAGEMENT Host File ========== This is a multi-package build, consequently it will be available only as a host file. The name of the file is POLYTRAUMA_MARKER.KID. Sites will retrieve VistA software from the following FTP addresses. The preferred method is to FTP the files from download.vista.med.va.gov. This transmits the files from the first available FTP server. Sites may also elect to retrieve software directly from a specific server as follows: Albany ftp.fo-albany.med.va.gov Hines ftp.fo-hines.med.va.gov Salt Lake City ftp.fo-slc.med.va.gov Installation: ============= This patch can be loaded with users on the system. Installation will take between 5 and 15 minutes. A number of Clinical Reminders Exchange entries will be installed and the installer may be prompted for replacement items. Because of this the patch should not be queued and the site's Clinical Reminders manager should be on hand during the install. 1. Use the 'Load a Distribution' option on the KIDS installation menu. When prompted to enter a host file type in [DIR]:POLYTRAUMA_MARKER.KID, where [DIR] is the local directory where you have stored the host file. 2. On the KIDS menu under the 'INSTALLATION' menu, use the following options, as desired: Print Transport Global Compare Transport Global to Current System Verify Checksums in Transport Global Backup a Transport Global 3. On the KIDS menu under the 'INSTALLATION' menu, use the following option to install the patch: Install Package(s) (POLYTRAUMA MARKER 1.0) 4. When prompted "Want KIDS to Rebuild Menu Trees Upon Completion of Install? NO// respond 'NO'. 5. When prompted "Want KIDS to INHIBIT LOGONs during the install? NO//," respond 'NO'. 6. When prompted "Want to DISABLE Scheduled Options, Menu Options, and Protocols? NO// respond 'NO'. 7. The init routines PXRMP17E and PXRMP17I may be deleted once the installation has completed. Routine Information: ==================== The checksums below are new checksums, and can be checked with CHECK1^XTSUMBLD. Routine Name: PXRMASU Before: n/a After: B5254044 **17** Routine Name: PXRMCSD Before: B79007362 After: B79106380 **9,17** Routine Name: PXRMCSTX Before: B33579692 After: B33673848 **9,12,17** Routine Name: PXRMDATE Before: B44519996 After: B44842316 **4,6,12,17** Routine Name: PXRMDEDT Before: B86262729 After: B86296946 **4,6,12,17** Routine Name: PXRMDIN Before: B6252963 After: B6267991 **4,12,17** Routine Name: PXRMDLL Before:B109862966 After:B109993102 **10,6,12,17** Routine Name: PXRMDNVA Before: B5849758 After: B6143858 **4,6,17** Routine Name: PXRMDOUT Before: B6920012 After: B6975976 **4,12,17** Routine Name: PXRMERRH Before: B23062075 After: B20772290 **4,17** Routine Name: PXRMEUT Before: B48351043 After: B48500029 **4,6,17** Routine Name: PXRMEXHF Before: B42524501 After: B46776039 **12,17** Routine Name: PXRMEXIC Before: B60109992 After: B63523540 **6,12,17** Routine Name: PXRMEXIU Before: B73385085 After: B64740382 **4,6,12,17** Routine Name: PXRMEXLM Before: B46337843 After: B46384451 **6,12,17** Routine Name: PXRMEXLR Before: B10517107 After: B10532497 **6,17** Routine Name: PXRMEXPD Before:B185750477 After:B192593185 **12,17** Routine Name: PXRMEXSI Before: B37968697 After: B38100333 **6,12,17** Routine Name: PXRMFRPT Before: B94355730 After: B94986966 **12,17** Routine Name: PXRMHF Before: B40472232 After: B40611502 **6,17** Routine Name: PXRMINDC Before: B63791698 After: B64870601 **4,6,17** Routine Name: PXRMINDD Before: B62308083 After: B63358470 **4,6,17** Routine Name: PXRMINDX Before: B35688973 After: B35686901 **4,6,12,17** Routine Name: PXRMISE Before: B60475574 After: B61351354 **6,12,17** Routine Name: PXRMISF Before: B4462345 After: B4736920 **17** Routine Name: PXRMLEX Before: n/a After: B11804614 **17** Routine Name: PXRMLOG Before: B60610343 After: B60154772 **4,6,12,17** Routine Name: PXRMMSG Before: B1305508 After: B1574379 **17** Routine Name: PXRMMST Before: B74220111 After: B74680448 **4,6,17** Routine Name: PXRMOUTC Before: B31474703 After: B31296456 **4,6,17** Routine Name: PXRMOUTD Before: B14357446 After: B14911015 **4,17** Routine Name: PXRMOUTM Before: B29545226 After: B28898508 **4,6,17** Routine Name: PXRMOUTU Before: B15002967 After: B15077433 **17** Routine Name: PXRMP17E Before: n/a After: B6421914 **17** Routine Name: PXRMP17I Before: n/a After: B20469897 **17** Routine Name: PXRMP17U Before: n/a After: B3271684 **17** Routine Name: PXRMPDEM Before: B33576521 After: B55690004 **5,4,11,12,17** Routine Name: PXRMPDRS Before: B62510488 After: B64959167 **4,6,12,17** Routine Name: PXRMPINF Before: B7615404 After: B7931374 **12,17** Routine Name: PXRMPRF Before: n/a After: B4757195 **17** Routine Name: PXRMPSN Before: B24631910 After: B23141092 **12,17** Routine Name: PXRMRDI Before: B13129062 After: B14183125 **4,17** Routine Name: PXRMSTS Before:B176795226 After:B176990612 **12,17** Routine Name: PXRMSXRM Before: B40761861 After: B45463918 **6,17** Routine Name: PXRMTAXS Before: B665414 After: B5899083 **4,17** Routine Name: PXRMUTIL Before: B78823347 After: B85545936 **4,6,11,12,17** Routine Name: PXRMVITL Before: B14529698 After: B14590186 **6,12,17** Routine Name: PXRMXDT1 Before: B68239830 After: B69793720 **4,6,12,17** Routine Name: PXRMXQUE Before: B12463741 After: B12306770 **4,6,12,17** Routine Name: PXRMXTD Before: B11996049 After: B12493752 **4,6,12,17** Routine list of preceding patches: 12 ============================================================================= User Information: Entered By : REDINGTON,PATRICK Date Entered : NOV 02, 2009 Completed By: OLSEN,JAMES Date Completed: MAY 26, 2010 Released By : MONTGOMERY,ALAN Date Released : JUN 01, 2010 ============================================================================= Packman Mail Message: ===================== No routines included